GreenBox

The ZC_NOTIFY_CRAZYKILLER(0x210) packet makes the nick of a player a little red, apparently it is used on PK systems.

1992

the client doesn't have to support all packets, it need's just one packet version

1974

actually, i created the atcommands for debugging. the correct way to use it is by scripts using pcstopfollow to remove the follow state

pc_locked_follow and pc_locked_walk are commands to be used on the source lockedwalk @lockedwalk are the same command, but one is to be used on scripts, lockedfollow and @lockedfollow is the same i've made lockedfollow to remove the lock after the target stop walking for the first time

Yesterday I implemented this packetdb format, some clients(like the default one 2011-11-16) are with missing packets, 2011-11-02 worked perfectly. newpacketdb.patch

This snippet add some commands that will make the player follow/walk to somewhere and until he reach the destination he can't act(walk, attach, use skills, etc). lockedwalk-r15938.diff http://pastebin.com/Ef7ZRNjN Added commands: - pc_locked_walk(sd, x, y) [sRC] - pc_locked_follow(sd, target) [sRC] - lockedwalk <x> <y> [script] - lockedfollow <target> [script] - @lockedwalk <x> <y> [Atcommand] - @lockedfollow <target> [Atcommand]

i have a program that reads the packetdb and guess the client version by the comments, just need to adjust the output format

The current format of the packetdb should be reviewed as you can use only the PACKETVER(client date) to choose the packets. Use of packet_ver(version) and the PACKETVER is redundant. Another thing, a new flag can be added for the packets(CLIENT_TYPE?) to choose between two parallel client types(eg.: kRO and iRO or kRO and bRO), so far we only have kRO clients but this will help if someone wants to add another client type. I sugest a format like this: // client: date type // packet id, packet size, function, positions // [...] // client: 20111005 0 0x0364,5,walktoxy,2 0x0817,6,ticksend,2 0x0366,5,changedir,2:4 0x0815,6,takeitem,2 [...] The packet type would be 0 for kRO clients, this is needed when the packets from clients with the same date from two official servers are different(eg.: bRO & kRO). Even if rAthena never add support for another clients types this will be usefull for someone that wants to add.

1904

1898

1890

RO2 seems to use Gamebryo engine that doesn't have a free version, but it can be done using some other modern engine like UDK3. Games like Lineage 2 and Blade n' Soul are made with it. The most painful task would be recreate all actors models(maybe just one model with different skins?), port all custom files like .str, .spr, .act, .rsm(or create a custom reader for them). Maps will need some special tool to be ported, i don't think that udk can read another type of map file.

1887

-bash: ./athena-start: /bin/sh^M: bad interpreter: No such file or directory Probably the file was saved with Windows line endings, you can convert it using dos2unix.

1 8 5 9

1853

1824

1821

1817

I think that this can help: http://pastebin.com/VBrm7M9j

Wine?

1734

1722