Brian

___ ___ ___ ___ |_ |_ |_ | . | |_ | | |_ |_ | |___| |_|___|___|

You can if you want, but it's not recommended. For example, if a new script command was added in trunk/src/map/script.c and you updated /npc but not /src then the map-server would say "unknown syntax" because it does not know the new script command.

rAthena develops the emulator. Hosting an inter-server RO competition isn't really part of our mission. But I suppose if enough staff want to do it, anything is possible.

I vote no, because @unloadnpc requires the unique npc name. Also, warp npcs don't have Visible or Visible#hidden names, so it's just the unique name that's important. Yea, what Jman and Maki suggested.

If the coordinates you specify are invalid, then it will warp you to random coordinates. Try these coordinates: @warp prontera 155 180

Update and recompile again. It should be fixed in the latest rAthena. bugreport:6876

Warps added via @addwarp can be unloaded with @unloadnpc if you make note of the user-un-friendly warp name it gives you when you use @addwarp. Or if you have the right-click GM menu, you can right-click, kill the warp. 1. If we add a <name> option, I suggest add it at the end of the parameters and make it an optional param. Current format (that everyone is used to) is: Params: <map name> <x coord> <y coord> PS: code would also have to check if unique NPC name already exists because the warp added by @addwarp is a new npc object. 2. I vote no. Users who want this behavior can add the alias to trunk/conf/atcommand_athena.conf unloadnpc: ["removewarp"]

I think all the ones that have "start" and "end" message pairs, if it's something that happens very fast we can remove the start message. Ex: remove "[info]: Reading configuration file conf/inter_athena.conf..." keep "[info]: Finished reading conf/inter_athena.conf." For the functions that take longer to execute (ex: loading NPCs), keep the "start" and "end" messages.

Yes, recompile. You need to recompile after you edit any source file in trunk/src/.

Here is the proper way to delete all guilds: stop all 3 servers (login, char, map) connect to your MySQL server and execute these queries This will delete all guilds, reset all castles to no owner (and 0 economy & defense), and empty all guild storages! TRUNCATE TABLE `guild`; TRUNCATE TABLE `guild_alliance`; TRUNCATE TABLE `guild_castle`; TRUNCATE TABLE `guild_expulsion`; TRUNCATE TABLE `guild_member`; TRUNCATE TABLE `guild_position`; TRUNCATE TABLE `guild_skill`; TRUNCATE TABLE `guild_storage`; UPDATE `char` SET `guild_id`=0;

r15204/eathena/ looks like a pain to merge too.

As rafoka said, if your MySQL databases are hosted on another server in the Internet, they can persist even when your rAthena USB flash drive is moved to another computer. Another option is rAsql (see using_rAsql). This allows you to run a MySQL Server directly off a portable USB flash drive.

You might have the wrong map_ip configured in trunk/conf/map_athena.conf // Map Server IP // The IP address which clients will use to connect. // Set this to what your server's public IP address is. //map_ip: 127.0.0.1 It should be your WAN IP. Also make sure the map port (default is 5121) TCP and UDP is forwarded form your router to your computer's LAN IP.

prontera,155,180,0 script WoE Warper 910,{ if (gettime(3) == 19) { // 7 PM warp "your_castle_map",x,y; } else { mes "You can only use the WoE Warper between 7 PM and 8 PM."; } close; } Replace warp "your_castle_map",x,y; with the castle mapname and x,y where you want to warp them to.

trunk/conf/groups.conf add the commands they can use: groups: ( { id: 0 /* group 0 is the default group for every new account */ name: "Player" level: 0 inherit: ( /*empty list*/ ) commands: { mobinfo: true iteminfo: true } permissions: { /* without this basic permissions regular players could not trade or party */ can_trade: true can_party: true } }, @mi and @ii aliases are already defined in trunk/conf/atcommand_athena.conf

Added by mkbu95 in r16881/rathena/trunk/src/map/atcommand.c

Any crash info it sends prior to actually crashing would not be as valuable as the dump after crashing, right? What if we add a script (Bash, Perl, PHP, something) in /tools that users can run? - it would search ../ for core dumps - run them through GDB to get 'bt full' - send that to us (via email, HTML Post, or the easiest method we can think of) - would it be necessary to send copies or blocks of certain source files so we can see what line numbers are being referenced? - optionally delete the core dump after (so it doesn't resend it next time) or we can do the filtering on our end to ignore duplicates The script would be completely optional and would require them to run it in order for it to send anything.

If you want the NPC to talk when a player walks near it, you can use the OnTouch label. prontera,155,188,0 script Test_NPC 910,4,4,{ mes "You clicked me"; close; OnTouch: npctalk "Someone walked near me!"; end; } If you want the NPC to talk on a time interval (like every hour, or every 30 seconds) you can use OnClock labels or sleep inside of a loop. prontera,155,188,0 script Test_NPC 910,4,4,{ mes "You clicked me"; close; OnClock0700: npctalk "It's 7:00 AM"; end; OnClock1414: npctalk "It's 2:14 PM"; end; } prontera,155,188,0 script Test_NPC 910,4,4,{ mes "You clicked me"; close; OnInit: while (1) { sleep 30000; npctalk "Another 30 seconds have passed."; } end; }

After you've reattached to screen, type Ctrl+A, then press [ now you can PageUp / PageDown

3735

Here's another @maprecall: http://trac.assembla.../changeset/121/ 4 years old ... it might have to be edited a little to work with the current rAthena. Did you put your new @command or script command before those functions are declared in atcommand.c or script.c ? If you try to use buildin_areawarp_sub before it's declared, that would cause an error.

Edit this setting in trunk/conf/map_athena.conf //Makes server log selected message types to a file in the /log/ folder //1: Log Warning Messages //2: Log Error and SQL Error messages. //4: Log Debug Messages //Example: "console_msg_log: 7" logs all 3 kinds //Messages logged by this overrides console_silent setting console_msg_log: 0 You can also start the map-server_sql in screen, then you can reconnect later and see the output window.

Sounds more like a merge of Messenger into Skype. http://blogs.skype.com/en/2012/11/skypewlm.html

turn off your server make a backup of your SQL database(s) using mysqldump compress your server files into a .zip or .tar.gz file transfer the SQL backup and server files to your new server using SFTP or FTP Then on the new server: install the programs rAthena needs (mysql, make, gcc, pcre, etc.) setup MySQL database(s) and MySQL users import your MySQL backup unzip your server files backup compile rAthena on the new machine start rAthena