The Mana World - User contributions [en]

Template:I18n

2015-02-04T20:35:00Z

O11c: typo

<noinclude>This template contains translation links for user articles. This template is only for user articles. Development pages should not receive this.

Only use in the main namespace for now.
{{I18n}}


</noinclude>
<includeonly><div class="toc noprint" style="border: 1px solid #da72ff; color: #000; background-color: #eebeff; text-align: center; margin-bottom: 1em">
[[Ar:{{PAGENAMEE}}|العربية]]
- [[Cz:{{PAGENAMEE}}|Česky]]
- [[De:{{PAGENAMEE}}|Deutsch]]
- [[{{PAGENAMEE}}|English]]
- [[Es:{{PAGENAMEE}}|Español]]
- [[Fa:{{PAGENAMEE}}|پارسی]]
- [[Fr:{{PAGENAMEE}}|Français]]
- [[Id:{{PAGENAMEE}}|Bahasa Indonesia]]
- [[It:{{PAGENAMEE}}|Italiano]]
- [[Pl:{{PAGENAMEE}}|Polski]]
- [[Pt:{{PAGENAMEE}}|Português]]
- [[Ru:{{PAGENAMEE}}|Русский]]
- [[Sq:{{PAGENAMEE}}|Shqip]]
- [[Sv:{{PAGENAMEE}}|Svenska]]
- [[Tr:{{PAGENAMEE}}|Türkçe]]
- [[Zh:{{PAGENAMEE}}|繁體中文]]
</div></includeonly>

Template:I18n

2015-02-04T20:34:30Z

O11c: Add traditional chinese

Development:Joining the project

2014-07-07T03:45:54Z

O11c: /* Technical aspects */ blurb TMWA

So you want to help this project, but you have little or no idea how to get into it? '''The Mana World development team is ''not'' a closed circle''' like many other projects. You don't need to apply to anyone or ask for "being taken into the team". You don't have to ask for permission to work on something or wait for someone to assign a task to you. A team member is basically anyone who volunteers to do something for the game.

'''Note:''' Besides reading this page the best way to start is asking for further information and assistance in our [https://webchat.freenode.net/?channels=#themanaworld-dev IRC development channel] or on the [https://forums.themanaworld.org/ forums].

If you know [[Dev:Working With Git|how to use Git]] you will even be more effective.

==Technical aspects==
The technical aspects of development of TMW include tweaking our custom server (tmwAthena). The server is done in C++ and scripts are done in the tmwAthena scripting language. Notably tmwAthena is an SVN snapshot from [http://eathena.ws/ eAthena] (a [http://en.wikipedia.org/wiki/Ragnarok_Online Ragnarok Online] game server emulator software) in early 2004. We've extensively hacked it and cleaned it over the years (it was at the moment of taking the snapshot in transition from the basis of an old hacky [http://en.wikipedia.org/wiki/MUD MUD] server to the current eAthena codebase). The technical aspects of the TMW project also include packaging data updates for the client.

===ManaPlus Client===
Originally just a fork of the official Mana client, ManaPlus got blessed when Mana stopped being updated and ran behind on features.

[http://manaplus.evolonline.org/ Site and downloads], [http://bugs.evolonline.org bug tracker].

===TMWA server===

The Mana World Athena is an MMORPG server that forked from eAthena, a Ragnarok Online clone, in early 2004. The major advantage of TMWA compared to RO clones is that it does not rely on a proprietary client that can't be changed, but nowadays we're quite distant from the RO community.

TMWA has been maintained by o11c (Ben Longbons) since early 2011 or so.
Before that, it never really had a proper maintainer, since everyone
thought that ManaServ was going to be the thing. But it won't ever be, so no more random hacks in TMWA, have a design plz kthxbye.

TMWA has a bugtracker: https://github.com/themanaworld/tmwa/issues
But it's probably worth getting on IRC first:
irc://chat.freenode.net/tmwa
https://webchat.freenode.net/?channels=#tmwa

Note that this channel is *only* for technical discussion of TMWA (and
attoconf), not general chat or TMW content development.

The Mana World (Athena) server originated as a snapshot of [http://eathena.ws eAthena]. It has since been extensively kludged, purged, optimized, and strictened, to the point that it will usually bitch at you if your scripts or config are wrong instead of silently doing the wrong thing. It it also well on the way to being a well-behaved package that can be installed with the usual package management tools (for all of you who don't know what package management tools are, your OS sucks and you deserve what you get), but we'd need to ship some sort of server data snapshots for that ...

There are no specific instructions to set up TMWA alone, the only instructions are in [[How to Develop]]. Particularly, building from a tarball will not work, use 'make dist' instead.

==Content==
Content means: new monsters, new equipment, new maps, new NPCs, new quests, new anything into the game.
Content does not mean: GFX, SFX.

Before anything can get into the game, it should be designed. After that it should be implemented server-sided. Then GFX and potentially also SFX can be requested for it and it can go into the game once they're done. Currently visioning ideas is a collective process anyone can take part in and the people doing scripting are cherry-picking whatever ideas they want to get into the game. Scripting stuff is also a free for all process. Once there is a good idea to expand the world, in general new maps can be requested. Reading the forums thoroughly and asking publicly usually gets you answers rather well.

==Graphics==
Graphics development could currently (June 2013) use a few pixel artists going about and retouching old mistakes in tilesets and sprite sets. Also if the content development crowd picks up and starts to provide concepts which would require new GFX work to be done, then there is going to be a demand for new equipment work, tilesets and sprite sets. Please remember to pay attention to our [[guidelines]].

Also do hunt for unfulfilled REQ topics on the forums if you're looking for something to do. Newbie pixel artists or people doing their first pixel art piece ever are also very welcome. The community can be pretty harsh at times, but there are also people around who actually do know what they're talking about. It is up to you to distinguish between these two.

==SFX / Music==
The SFX and music development scheme for TMW is currently not really all that active. New sounds and music are always appreciated.

Archive:TmwAthena Packets

2014-05-26T21:06:37Z

O11c: Link to the script

Note: you can get a more up-to-date, but less detail, description in [https://github.com/themanaworld/tmwa/blob/master/tools/protocol.py|the repository's protocol generator script]

== Overview ==
=== Packet Alignment ===
The alignment of the data within the packet payload can cause additional overhead if the data is not properly aligned to word boundaries. For example, in a 32-bit application, a word is a sequence of two eight-bit bytes. Any data that occupies 2 bytes or larger on this platform should always start at a (2 * n) offset (0, 2, 4, etc). Any data that is less than 2 bytes can start at any offset, so long as it does not span multiple words. A 16-bit integer could start at offset 0, 2, or 4, but not at 1, 3, or 5 because the first byte would be in one word and the second byte would be in the next word. Single byte words will always fall on word boundaries. The last piece of data should end on a word boundary as well. If any of the data are double words in size, the packet must also be a multiple of the double word size and any double word sized data must fall on a double word boundary.

To leverage the maximum efficiency, padding can be added between pieces of data to force subsequent data to be aligned to word boundaries. For example, if a packet contains a word, and a half word, either the data should be ordered as word, half word, and a half word of padding that will be discarded by the recipient. The same data, ordered as a half word, word, a half word of padding would take up the same amount of space, but the word would span two different words of the packet and cause inefficient processing of that packet.

The following colors are used to indicate the alignment of the packets:

<table>
<tr>
<th> Color Meaning </th>
<th> Examples </th>
</tr>
<tr>
<td style="background: green;">The packet contents and total size are properly aligned.</td>
<td> 2; 2 2; 2 2 4; 2 2 2*N</td>
</tr>
<tr>
<td style="background: chartreuse;">The packet contents are aligned, but they contain a variable-length element that may cause the whole packet to be improperly aligned.</td>
<td> 2 2 1*N</td>
</tr>
<tr>
<td style="background: yellow;">The packet contents are properly aligned, but do not end on a word boundary.</td>
<td> 2 1 ; 2 2 4 1 </td>
</tr>
<tr>
<td style="background: orange;">The packet contents are not properly aligned on word boundaries, but could be with skew padding.</td>
<td> 2 4 2 </td>
</tr>
<tr>
<td style="background: orangered;">The packet contents are not properly aligned if the number of varying elements is at least 2.</td>
<td> 2 2 (2 1)*N</td>
</tr>
<tr>
<td style="background: red;">The packet contents are not properly aligned on word boundaries, even with skew padding.</td>
<td> 2 4 2 4</td>
</tr>
</table>

== Client Packets ==
This is a new table that steal information from individual packet pages.

<table border="1" cellspacing="0" cellpadding="3" class="wikitable sortable">
<tr valign="top">
<th>Packet</th> <th>Length</th> <th>Name</th> <th>Client #define</th> <th>Sent and Parsed Locations</th>
</tr>

{{Net:0x0061|mode=row}}
{{Net:0x0062|mode=row}}
{{Net:0x0063|mode=row}}
{{Net:0x0064|mode=row}}
{{Net:0x0065|mode=row}}
{{Net:0x0066|mode=row}}
{{Net:0x0067|mode=row}}
{{Net:0x0068|mode=row}}
{{Net:0x0069|mode=row}}
{{Net:0x006A|mode=row}}
{{Net:0x006B|mode=row}}
{{Net:0x006C|mode=row}}
{{Net:0x006D|mode=row}}
{{Net:0x006E|mode=row}}
{{Net:0x006F|mode=row}}

{{Net:0x0070|mode=row}}
{{Net:0x0071|mode=row}}
{{Net:0x0072|mode=row}}
{{Net:0x0073|mode=row}}
{{Net:0x0078|mode=row}}
{{Net:0x007B|mode=row}}
{{Net:0x007C|mode=row}}
{{Net:0x007D|mode=row}}
{{Net:0x007E|mode=row}}
{{Net:0x007F|mode=row}}

{{Net:0x0080|mode=row}}
{{Net:0x0081|mode=row}}
{{Net:0x0085|mode=row}}
{{Net:0x0086|mode=row}}
{{Net:0x0087|mode=row}}
{{Net:0x0088|mode=row}}
{{Net:0x0089|mode=row}}
{{Net:0x008A|mode=row}}
{{Net:0x008C|mode=row}}
{{Net:0x008D|mode=row}}
{{Net:0x008E|mode=row}}

{{Net:0x0090|mode=row}}
{{Net:0x0091|mode=row}}
{{Net:0x0092|mode=row}}
{{Net:0x0094|mode=row}}
{{Net:0x0095|mode=row}}
{{Net:0x0096|mode=row}}
{{Net:0x0097|mode=row}}
{{Net:0x0098|mode=row}}
{{Net:0x0099|mode=row}}
{{Net:0x009A|mode=row}}
{{Net:0x009B|mode=row}}
{{Net:0x009C|mode=row}}
{{Net:0x009D|mode=row}}
{{Net:0x009E|mode=row}}
{{Net:0x009F|mode=row}}

{{Net:0x00A0|mode=row}}
{{Net:0x00A1|mode=row}}
{{Net:0x00A2|mode=row}}
{{Net:0x00A4|mode=row}}
{{Net:0x00A6|mode=row}}
{{Net:0x00A7|mode=row}}
{{Net:0x00A8|mode=row}}
{{Net:0x00A9|mode=row}}
{{Net:0x00AA|mode=row}}
{{Net:0x00AB|mode=row}}
{{Net:0x00AC|mode=row}}
{{Net:0x00AF|mode=row}}

{{Net:0x00B0|mode=row}}
{{Net:0x00B1|mode=row}}
{{Net:0x00B2|mode=row}}
{{Net:0x00B3|mode=row}}
{{Net:0x00B4|mode=row}}
{{Net:0x00B5|mode=row}}
{{Net:0x00B6|mode=row}}
{{Net:0x00B7|mode=row}}
{{Net:0x00B8|mode=row}}
{{Net:0x00B9|mode=row}}
{{Net:0x00BB|mode=row}}
{{Net:0x00BC|mode=row}}
{{Net:0x00BD|mode=row}}
{{Net:0x00BE|mode=row}}
{{Net:0x00BF|mode=row}}

{{Net:0x00C0|mode=row}}
{{Net:0x00C1|mode=row}}
{{Net:0x00C2|mode=row}}
{{Net:0x00C3|mode=row}}
{{Net:0x00C4|mode=row}}
{{Net:0x00C5|mode=row}}
{{Net:0x00C6|mode=row}}
{{Net:0x00C7|mode=row}}
{{Net:0x00C8|mode=row}}
{{Net:0x00C9|mode=row}}
{{Net:0x00CA|mode=row}}
{{Net:0x00CB|mode=row}}
{{Net:0x00CC|mode=row}}
{{Net:0x00CD|mode=row}}

{{Net:0x00E4|mode=row}}
{{Net:0x00E5|mode=row}}
{{Net:0x00E6|mode=row}}
{{Net:0x00E7|mode=row}}
{{Net:0x00E8|mode=row}}
{{Net:0x00E9|mode=row}}
{{Net:0x00EB|mode=row}}
{{Net:0x00EC|mode=row}}
{{Net:0x00ED|mode=row}}
{{Net:0x00EE|mode=row}}
{{Net:0x00EF|mode=row}}

{{Net:0x00F0|mode=row}}
{{Net:0x00F2|mode=row}}
{{Net:0x00F3|mode=row}}
{{Net:0x00F4|mode=row}}
{{Net:0x00F5|mode=row}}
{{Net:0x00F6|mode=row}}
{{Net:0x00F7|mode=row}}
{{Net:0x00F8|mode=row}}
{{Net:0x00F9|mode=row}}
{{Net:0x00FA|mode=row}}
{{Net:0x00FB|mode=row}}
{{Net:0x00FC|mode=row}}
{{Net:0x00FD|mode=row}}
{{Net:0x00FE|mode=row}}
{{Net:0x00FF|mode=row}}

{{Net:0x0100|mode=row}}
{{Net:0x0101|mode=row}}
{{Net:0x0102|mode=row}}
{{Net:0x0103|mode=row}}
{{Net:0x0104|mode=row}}
{{Net:0x0105|mode=row}}
{{Net:0x0106|mode=row}}
{{Net:0x0107|mode=row}}
{{Net:0x0108|mode=row}}
{{Net:0x0109|mode=row}}
{{Net:0x010C|mode=row}}
{{Net:0x010E|mode=row}}
{{Net:0x010F|mode=row}}

{{Net:0x0110|mode=row}}
{{Net:0x0112|mode=row}}
{{Net:0x0113|mode=row}}
{{Net:0x0116|mode=row}}
{{Net:0x0119|mode=row}}
{{Net:0x011B|mode=row}}

{{Net:0x0139|mode=row}}
{{Net:0x013A|mode=row}}
{{Net:0x013B|mode=row}}
{{Net:0x013C|mode=row}}

{{Net:0x0141|mode=row}}
{{Net:0x0142|mode=row}}
{{Net:0x0143|mode=row}}
{{Net:0x0146|mode=row}}
{{Net:0x0148|mode=row}}
{{Net:0x0149|mode=row}}
{{Net:0x014C|mode=row}}
{{Net:0x014D|mode=row}}
{{Net:0x014E|mode=row}}
{{Net:0x014F|mode=row}}

{{Net:0x0151|mode=row}}
{{Net:0x0152|mode=row}}
{{Net:0x0153|mode=row}}
{{Net:0x0154|mode=row}}
{{Net:0x0155|mode=row}}
{{Net:0x0156|mode=row}}
{{Net:0x0159|mode=row}}
{{Net:0x015A|mode=row}}
{{Net:0x015B|mode=row}}
{{Net:0x015C|mode=row}}
{{Net:0x015D|mode=row}}
{{Net:0x015E|mode=row}}

{{Net:0x0160|mode=row}}
{{Net:0x0161|mode=row}}
{{Net:0x0162|mode=row}}
{{Net:0x0163|mode=row}}
{{Net:0x0165|mode=row}}
{{Net:0x0166|mode=row}}
{{Net:0x0167|mode=row}}
{{Net:0x0168|mode=row}}
{{Net:0x0169|mode=row}}
{{Net:0x016A|mode=row}}
{{Net:0x016B|mode=row}}
{{Net:0x016C|mode=row}}
{{Net:0x016D|mode=row}}
{{Net:0x016E|mode=row}}
{{Net:0x016F|mode=row}}

{{Net:0x0170|mode=row}}
{{Net:0x0171|mode=row}}
{{Net:0x0172|mode=row}}
{{Net:0x0173|mode=row}}
{{Net:0x0174|mode=row}}
{{Net:0x017E|mode=row}}
{{Net:0x017F|mode=row}}

{{Net:0x0180|mode=row}}
{{Net:0x0181|mode=row}}
{{Net:0x0183|mode=row}}
{{Net:0x0184|mode=row}}
{{Net:0x018A|mode=row}}
{{Net:0x018B|mode=row}}

{{Net:0x0190|mode=row}}
{{Net:0x0195|mode=row}}
{{Net:0x0196|mode=row}}
{{Net:0x019B|mode=row}}
{{Net:0x019C|mode=row}}
{{Net:0x019D|mode=row}}

{{Net:0x01B1|mode=row}}
{{Net:0x01B6|mode=row}}

{{Net:0x01C8|mode=row}}

{{Net:0x01D4|mode=row}}
{{Net:0x01D5|mode=row}}
{{Net:0x01D7|mode=row}}
{{Net:0x01D8|mode=row}}
{{Net:0x01D9|mode=row}}
{{Net:0x01DA|mode=row}}
{{Net:0x01DE|mode=row}}

{{Net:0x01EE|mode=row}}

{{Net:0x01F0|mode=row}}

{{Net:0x020C|mode=row}}



{{Net:0x7530|mode=row}}
{{Net:0x7531|mode=row}}

</table>

== ManaPlus Packets ==
These packets were originally added by ManaPlus to support Evol.

<table border="1" cellspacing="0" cellpadding="3" class="wikitable sortable">
<tr valign="top">
<th>Packet</th> <th>Length</th> <th>Name</th> <th>Client #define</th> <th>Sent and Parsed Locations</th>
</tr>

{{Net:0x0212|mode=row}}

</table>

== Used packets ==
{| border="1" cellspacing="0" cellpadding="3"
|-valign="top"
!packet !! len !! client define !! sent location(s) !! parse location
|-valign="top"
|0x0061 || 50 || CMSG_CHAR_PASSWORD_CHANGE || src/net/tmwa/loginhandler.cpp:264 || src/char/char.c:3036
|-valign="top"
|0x0062 || 3 || SMSG_CHAR_PASSWORD_RESPONSE || src/char/char.c:2368 || src/net/tmwa/loginhandler.cpp:71
|-valign="top"
|0x0063 || -1 || SMSG_UPDATE_HOST || src/login/login.c:3732 || src/net/tmwa/loginhandler.cpp:103
|-valign="top"
|0x0064 || 55 || (hard-coded) || src/net/tmwa/loginhandler.cpp:298 || src/login/login.c:3644
|-valign="top"
|0x0065 || 17 || CMSG_CHAR_SERVER_CONNECT || src/net/tmwa/charserverhandler.cpp:340 || src/char/char.c:3049
|-valign="top"
|0x0066 || 3 || CMSG_CHAR_SELECT || src/net/tmwa/charserverhandler.cpp:283<br>src/char/char.c:3424 || src/char/char.c:3142
|-valign="top"
|0x0067 || 37 || CMSG_CHAR_CREATE || src/net/tmwa/charserverhandler.cpp:291 || src/char/char.c:3312
|-valign="top"
|0x0068 || 46 || CMSG_CHAR_DELETE || src/net/tmwa/charserverhandler.cpp:306 || src/char/char.c:3387
|-valign="top"
|0x0069 || -1 || SMSG_LOGIN_DATA || src/login/login.c:3795 || src/net/tmwa/loginhandler.cpp:114
|-valign="top"
|0x006A || 23 || SMSG_LOGIN_ERROR || src/login/login.c:3683<br>src/login/login.c:3833 || src/net/tmwa/loginhandler.cpp:149
|-valign="top"
|0x006B || -1 || SMSG_CHAR_LOGIN || src/char/char.c:1660 || src/net/tmwa/charserverhandler.cpp:101
|-valign="top"
|0x006C || 3 || SMSG_CHAR_LOGIN_ERROR || src/char/char.c:1948<br>src/char/char.c:1970<br>src/char/char.c:3110<br>src/char/char.c:3133 || src/net/tmwa/charserverhandler.cpp:75
|-valign="top"
|0x006D || 108 || SMSG_CHAR_CREATE_SUCCEEDED || src/char/char.c:3325 || src/net/tmwa/charserverhandler.cpp:118
|-valign="top"
|0x006E || 3 || SMSG_CHAR_CREATE_FAILED || src/char/char.c:3318 || src/net/tmwa/charserverhandler.cpp:137
|-valign="top"
|0x006F || 2 || SMSG_CHAR_DELETE_SUCCEEDED || src/char/char.c:3496 || src/net/tmwa/charserverhandler.cpp:144
|-valign="top"
|0x0070 || 3 || SMSG_CHAR_DELETE_FAILED || src/char/char.c:3156<br>src/char/char.c:3401<br>src/char/char.c:3432<br>src/char/char.c:3504 || src/net/tmwa/charserverhandler.cpp:153
|-valign="top"
|0x0071 || 28 || SMSG_CHAR_MAP_INFO || src/char/char.c:3272 || src/net/tmwa/charserverhandler.cpp:158
|-valign="top"
|0x0072 || 19 || CMSG_MAP_SERVER_CONNECT || src/net/tmwa/gamehandler.cpp:124 || src/map/clif.c:6729
|-valign="top"
|0x0073 || 11 || SMSG_MAP_LOGIN_SUCCESS || src/map/clif.c:609 || src/net/tmwa/gamehandler.cpp:67
|-valign="top"
|0x0078 || 54 || SMSG_BEING_VISIBLE || src/map/clif.c:823<br>src/map/clif.c:1060<br>src/map/clif.c:1185<br>src/map/clif.c:1382 || src/net/tmwa/beinghandler.cpp:121
|-valign="top"
|0x007B || 60 || SMSG_BEING_MOVE || src/map/clif.c:912<br>src/map/clif.c:1122 || src/net/tmwa/beinghandler.cpp:122
|-valign="top"
|0x007C || 41 || SMSG_BEING_SPAWN || src/map/clif.c:1279<br>src/map/clif.c:1347<br>src/map/clif.c:1372<br>src/map/clif.c:1414 || src/net/tmwa/beinghandler.cpp:239
|-valign="top"
|0x007D || 2 || CMSG_MAP_LOADED || src/net/tmwa/gamehandler.cpp:152 || src/map/clif.c:6786
|-valign="top"
|0x007E || 6 || CMSG_CLIENT_PING || src/net/tmwa/gamehandler.cpp:166 || src/map/clif.c:6942
|-valign="top"
|0x007F || 6 || SMSG_SERVER_PING || src/map/clif.c:1445 || src/net/tmwa/gamehandler.cpp:81
|-valign="top"
|0x0080 || 7 || SMSG_BEING_REMOVE || src/map/clif.c:65<br>src/map/clif.c:791 || src/net/tmwa/beinghandler.cpp:273
|-valign="top"
|0x0081 || 3 || SMSG_CONNECTION_PROBLEM || src/login/login.c:3700<br>src/login/login.c:3824<br>src/char/char.c:3264<br>src/map/clif.c:628 || src/net/tmwa/generalhandler.cpp:122
|-valign="top"
|0x0085 || 5 || CMSG_PLAYER_CHANGE_DEST || src/net/tmwa/playerhandler.cpp:621 || src/map/clif.c:6955
|-valign="top"
|0x0086 || 16 || SMSG_BEING_MOVE2 || || src/net/tmwa/beinghandler.cpp:246
|-valign="top"
|0x0087 || 12 || SMSG_WALK_RESPONSE || src/map/clif.c:1463 || src/net/tmwa/playerhandler.cpp:177
|-valign="top"
|0x0088 || 10 || SMSG_PLAYER_STOP || src/map/clif.c:1590 || src/net/tmwa/beinghandler.cpp:630
|-valign="top"
|0x0089 || 7 || CMSG_PLAYER_CHANGE_ACT<br>CMSG_PLAYER_ATTACK || src/net/tmwa/playerhandler.cpp:635<br>src/net/tmwa/playerhandler.cpp:566 || src/map/clif.c:7341
|-valign="top"
|0x008A || 29 || SMSG_BEING_ACTION || src/map/clif.c:3761<br>src/map/clif.c:6563 || src/net/tmwa/beinghandler.cpp:328
|-valign="top"
|0x008C || -1 || CMSG_CHAT_MESSAGE || src/net/tmwa/chathandler.cpp:199 || src/map/clif.c:7173
|-valign="top"
|0x008D || -1 || SMSG_BEING_CHAT || src/map/clif.c:7209<br>src/map/clif.c:7236 || src/net/tmwa/chathandler.cpp:113
|-valign="top"
|0x008E || -1 || SMSG_PLAYER_CHAT || src/map/clif.c:4603<br>src/map/clif.c:7219 || src/net/tmwa/chathandler.cpp:158
|-valign="top"
|0x0090 || 7 || CMSG_NPC_TALK || src/net/tmwa/npchandler.cpp:133 || src/map/clif.c:7738
|-valign="top"
|0x0091 || 22 || SMSG_PLAYER_WARP || src/map/clif.c:1545 || src/net/tmwa/playerhandler.cpp:185
|-valign="top"
|0x0092 || 28 || SMSG_CHANGE_MAP_SERVER || src/map/clif.c:1569 || src/net/tmwa/charserverhandler.cpp:179
|-valign="top"
|0x0094 || 6 || (hard-coded) || src/net/tmwa/beinghandler.cpp:92 || src/map/clif.c:7047
|-valign="top"
|0x0095 || 30 || SMSG_BEING_NAME_RESPONSE || src/map/clif.c:7057 || src/net/tmwa/beinghandler.cpp:484
|-valign="top"
|0x0096 || -1 || CMSG_CHAT_WHISPER || src/net/tmwa/chathandler.cpp:215 || src/map/clif.c:7459
|-valign="top"
|0x0097 || -1 || SMSG_WHISPER || src/map/clif.c:4771 || src/net/tmwa/chathandler.cpp:91
|-valign="top"
|0x0098 || 3 || SMSG_WHISPER_RESPONSE || src/map/clif.c:4785 || src/net/tmwa/chathandler.cpp:72
|-valign="top"
|0x0099 || -1 || CMSG_ADMIN_ANNOUNCE<br>CMSG_CHAT_ANNOUNCE || src/net/tmwa/adminhandler.cpp:84 || src/map/clif.c:7549
|-valign="top"
|0x009A || -1 || SMSG_GM_CHAT || src/map/clif.c:4623<br>src/map/clif.c:8359 || src/net/tmwa/chathandler.cpp:159
|-valign="top"
|0x009B || 5 || CMSG_PLAYER_CHANGE_DIR || src/net/tmwa/playerhandler.cpp:614 || src/map/clif.c:7278
|-valign="top"
|0x009C || 9 || SMSG_BEING_CHANGE_DIRECTION || src/map/clif.c:7293 || src/net/tmwa/beinghandler.cpp:499
|-valign="top"
|0x009D || 17 || SMSG_ITEM_VISIBLE || src/map/clif.c:3815 || src/net/tmwa/itemhandler.cpp:47
|-valign="top"
|0x009E || 17 || SMSG_ITEM_DROPPED || src/map/clif.c:671 || src/net/tmwa/itemhandler.cpp:48
|-valign="top"
|0x009F || 6 || CMSG_ITEM_PICKUP || src/net/tmwa/playerhandler.cpp:607 || src/map/clif.c:7573
|-valign="top"
|0x00A0 || 23 || SMSG_PLAYER_INVENTORY_ADD || src/map/clif.c:1855<br>src/map/clif.c:1876 || src/net/tmwa/inventoryhandler.cpp:218
|-valign="top"
|0x00A1 || 6 || SMSG_ITEM_REMOVE || src/map/clif.c:715 || src/net/tmwa/itemhandler.cpp:61
|-valign="top"
|0x00A2 || 6 || CMSG_PLAYER_INVENTORY_DROP || src/net/tmwa/inventoryhandler.cpp:473 || src/map/clif.c:7613
|-valign="top"
|0x00A4 || -1 || SMSG_PLAYER_EQUIPMENT || src/map/clif.c:2017 || src/net/tmwa/inventoryhandler.cpp:376
|-valign="top"
|0x00A6 || -1 || SMSG_PLAYER_STORAGE_EQUIP || src/map/clif.c:2144<br>src/map/clif.c:2273 || src/net/tmwa/inventoryhandler.cpp:187
|-valign="top"
|0x00A7 || 8 || CMSG_PLAYER_INVENTORY_USE || src/net/tmwa/inventoryhandler.cpp:465 || src/map/clif.c:7640
|-valign="top"
|0x00A8 || 7 || SMSG_ITEM_USE_RESPONSE || src/map/clif.c:2935 || src/net/tmwa/inventoryhandler.cpp:284
|-valign="top"
|0x00A9 || 6 || CMSG_PLAYER_EQUIP || src/net/tmwa/inventoryhandler.cpp:446 || src/map/clif.c:7666
|-valign="top"
|0x00AA || 7 || SMSG_PLAYER_EQUIP || src/map/clif.c:2819 || src/net/tmwa/inventoryhandler.cpp:401
|-valign="top"
|0x00AB || 4 || CMSG_PLAYER_UNEQUIP || src/net/tmwa/inventoryhandler.cpp:456 || src/map/clif.c:7706
|-valign="top"
|0x00AC || 7 || SMSG_PLAYER_UNEQUIP || src/map/clif.c:2839 || src/net/tmwa/inventoryhandler.cpp:412
|-valign="top"
|0x00AF || 6 || SMSG_PLAYER_INVENTORY_REMOVE || src/map/clif.c:1943 || src/net/tmwa/inventoryhandler.cpp:253
|-valign="top"
|0x00B0 || 8 || SMSG_PLAYER_STAT_UPDATE_1 || src/map/clif.c:2350<br>src/map/clif.c:2357 || src/net/tmwa/playerhandler.cpp:234
|-valign="top"
|0x00B1 || 8 || SMSG_PLAYER_STAT_UPDATE_2 || src/map/clif.c:2437<br>src/map/clif.c:2443<br>src/map/clif.c:2447<br>src/map/clif.c:2451<br>src/map/clif.c:2455 || src/net/tmwa/playerhandler.cpp:333
|-valign="top"
|0x00B2 || 3 || CMSG_PLAYER_RESTART || src/net/tmwa/charserverhandler.cpp:314<br>src/net/tmwa/playerhandler.cpp:642 || src/map/clif.c:7411
|-valign="top"
|0x00B3 || 3 || SMSG_CHAR_SWITCH_RESPONSE || src/map/clif.c:653 || src/net/tmwa/gamehandler.cpp:91
|-valign="top"
|0x00B4 || -1 || SMSG_NPC_MESSAGE || src/map/clif.c:1696 || src/net/tmwa/npchandler.cpp:102
|-valign="top"
|0x00B5 || 6 || SMSG_NPC_NEXT || src/map/clif.c:1716 || src/net/tmwa/npchandler.cpp:111
|-valign="top"
|0x00B6 || 6 || SMSG_NPC_CLOSE || src/map/clif.c:1734 || src/net/tmwa/npchandler.cpp:106
|-valign="top"
|0x00B7 || -1 || SMSG_NPC_CHOICE || src/map/clif.c:1752 || src/net/tmwa/npchandler.cpp:97
|-valign="top"
|0x00B8 || 7 || CMSG_NPC_LIST_CHOICE || src/net/tmwa/npchandler.cpp:159 || src/map/clif.c:8194
|-valign="top"
|0x00B9 || 6 || CMSG_NPC_NEXT_REQUEST || src/net/tmwa/npchandler.cpp:140 || src/map/clif.c:8206
|-valign="top"
|0x00BB || 5 || CMSG_STAT_UPDATE_REQUEST || src/net/tmwa/playerhandler.cpp:581 || src/map/clif.c:7993
|-valign="top"
|0x00BC || 6 || SMSG_PLAYER_STAT_UPDATE_4 || src/map/clif.c:2799 || src/net/tmwa/playerhandler.cpp:381
|-valign="top"
|0x00BD || 44 || SMSG_PLAYER_STAT_UPDATE_5 || src/map/clif.c:2702 || src/net/tmwa/playerhandler.cpp:401
|-valign="top"
|0x00BE || 5 || SMSG_PLAYER_STAT_UPDATE_6 || src/map/clif.c:2466 || src/net/tmwa/playerhandler.cpp:521
|-valign="top"
|0x00BF || 3 || CMSG_PLAYER_EMOTE || src/net/tmwa/playerhandler.cpp:573 || src/map/clif.c:7308
|-valign="top"
|0x00C0 || 7 || SMSG_BEING_EMOTION || src/map/clif.c:6469<br>src/map/clif.c:6488<br>src/map/clif.c:7317 || src/net/tmwa/beinghandler.cpp:385
|-valign="top"
|0x00C1 || 2 || CMSG_WHO_REQUEST<br>CMSG_CHAT_WHO || src/map/chathandler.cpp:264 || src/map/clif.c:7330
|-valign="top"
|0x00C2 || 6 || SMSG_WHO_ANSWER || src/map/clif.c:7332 || src/net/tmwa/gamehandler.cpp:86
|-valign="top"
|0x00C3 || 8 || SMSG_BEING_CHANGE_LOOKS || || src/net/tmwa/beinghandler.cpp:400
|-valign="top"
|0x00C4 || 6 || SMSG_NPC_BUY_SELL_CHOICE || src/map/clif.c:1611 || src/net/tmwa/buysellhandler.cpp:64
|-valign="top"
|0x00C5 || 7 || CMSG_NPC_BUY_SELL_REQUEST || src/net/tmwa/npchandler.cpp:193<br>src/net/tmwa/npchandler.cpp:200 || src/map/clif.c:7756
|-valign="top"
|0x00C6 || -1 || SMSG_NPC_BUY || src/map/clif.c:1631 || src/net/tmwa/buysellhandler.cpp:72
|-valign="top"
|0x00C7 || -1 || SMSG_NPC_SELL || src/map/clif.c:1663 || src/net/tmwa/buysellhandler.cpp:88
|-valign="top"
|0x00C8 || -1 || CMSG_NPC_BUY_REQUEST || src/net/tmwa/npchandler.cpp:207 || src/map/clif.c:7765
|-valign="top"
|0x00C9 || -1 || CMSG_NPC_SELL_REQUEST || src/net/tmwa/npchandler.cpp:215 || src/map/clif.c:7784
|-valign="top"
|0x00CA || 3 || SMSG_NPC_BUY_RESPONSE || src/map/clif.c:7775 || src/net/tmwa/buysellhandler.cpp:114
|-valign="top"
|0x00CB || 3 || SMSG_NPC_SELL_RESPONSE || src/map/clif.c:7794 || src/net/tmwa/buysellhandler.cpp:124
|-valign="top"
|0x00CC || 6 || CMSG_ADMIN_KICK || src/net/tmwa/adminhandler.cpp:104 || src/map/clif.c:8913
|-valign="top"
|0x00CD || 6 || SMSG_ADMIN_KICK_ACK || src/map/clif.c:6605 || src/net/tmwa/adminhandler.cpp:62
|-valign="top"
|0x00E4 || 6 || CMSG_TRADE_REQUEST || src/net/tmwa/tradehandler.cpp:241 || src/map/clif.c:7859
|-valign="top"
|0x00E5 || 26 || SMSG_TRADE_REQUEST || src/map/clif.c:3180 || src/net/tmwa/tradehandler.cpp:86
|-valign="top"
|0x00E6 || 3 || CMSG_TRADE_RESPONSE || src/net/tmwa/tradehandler.cpp:250 || src/map/clif.c:7876
|-valign="top"
|0x00E7 || 3 || SMSG_TRADE_RESPONSE || src/map/clif.c:3198 || src/net/tmwa/tradehandler.cpp:120
|-valign="top"
|0x00E8 || 8 || CMSG_TRADE_ITEM_ADD_REQUEST || src/net/tmwa/tradehandler.cpp:256<br>src/net/tmwa/tradehandler.cpp:268 || src/map/clif.c:7887
|-valign="top"
|0x00E9 || 19 || SMSG_TRADE_ITEM_ADD || src/map/clif.c:3218 || src/net/tmwa/tradehandler.cpp:159
|-valign="top"
|0x00EB || 2 || CMSG_TRADE_ADD_COMPLETE || src/net/tmwa/tradehandler.cpp:275 || src/map/clif.c:7898
|-valign="top"
|0x00EC || 3 || SMSG_TRADE_OK || src/map/clif.c:3320 || src/net/tmwa/tradehandler.cpp:218
|-valign="top"
|0x00ED || 2 || CMSG_TRADE_CANCEL_REQUEST || src/net/tmwa/tradehandler.cpp:285 || src/map/clif.c:7907
|-valign="top"
|0x00EE || 2 || SMSG_TRADE_CANCEL || src/map/clif.c:3338 || src/net/tmwa/tradehandler.cpp:223
|-valign="top"
|0x00EF || 2 || CMSG_TRADE_OK || src/net/tmwa/tradehandler.cpp:280 || src/map/clif.c:7916
|-valign="top"
|0x00F0 || 3 || SMSG_TRADE_COMPLETE || src/map/clif.c:3355 || src/net/tmwa/tradehandler.cpp:230
|-valign="top"
|0x00F2 || 6 || SMSG_PLAYER_STORAGE_STATUS || src/map/clif.c:3375<br>src/map/clif.c:3459 || src/net/tmwa/inventoryhandler.cpp:306
|-valign="top"
|0x00F3 || 8 || CMSG_MOVE_TO_STORAGE || src/net/tmwa/inventoryhandler.cpp:508 || src/map/clif.c:8370
|-valign="top"
|0x00F4 || 21 || SMSG_PLAYER_STORAGE_ADD || src/map/clif.c:3396<br>src/map/clif.c:3481 || src/net/tmwa/inventoryhandler.cpp:331
|-valign="top"
|0x00F5 || 8 || CSMG_MOVE_FROM_STORAGE || src/net/tmwa/inventoryhandler.cpp:514 || src/map/clif.c:8393
|-valign="top"
|0x00F6 || 8 || SMSG_PLAYER_STORAGE_REMOVE || src/map/clif.c:3543 || src/net/tmwa/inventoryhandler.cpp:353
|-valign="top"
|0x00F7 || 2 || CMSG_CLOSE_STORAGE || src/net/tmwa/inventoryhandler.cpp:500 || src/map/clif.c:8452
|-valign="top"
|0x00F8 || 2 || SMSG_PLAYER_STORAGE_CLOSE || src/map/clif.c:3562 || src/net/tmwa/inventoryhandler.cpp:365
|-valign="top"
|0x00F9 || 26 || CMSG_PARTY_CREATE || src/net/tmwa/partyhandler.cpp:313 || src/map/clif.c:8469
|-valign="top"
|0x00FA || 3 || SMSG_PARTY_CREATE || src/map/clif.c:5231 || src/net/tmwa/partyhandler.cpp:79
|-valign="top"
|0x00FB || -1 || SMSG_PARTY_INFO || src/map/clif.c:5249 || src/net/tmwa/partyhandler.cpp:88
|-valign="top"
|0x00FC || 6 || CMSG_PARTY_INVITE || src/net/tmwa/partyhandler.cpp:324 || src/map/clif.c:8510
|-valign="top"
|0x00FD || 27 || SMSG_PARTY_INVITE_RESPONSE || src/map/clif.c:5327 || src/net/tmwa/partyhandler.cpp:112
|-valign="top"
|0x00FE || 30 || SMSG_PARTY_INVITED || src/map/clif.c:5299 || src/net/tmwa/partyhandler.cpp:139
|-valign="top"
|0x00FF || 10 || CMSG_PARTY_INVITED || src/net/tmwa/partyhandler.cpp:352 || src/map/clif.c:8522
|-valign="top"
|0x0100 || 2 || CMSG_PARTY_LEAVE || src/net/tmwa/partyhandler.cpp:359 || src/map/clif.c:8540
|-valign="top"
|0x0101 || 6 || SMSG_PARTY_SETTINGS || src/map/clif.c:5358 || src/net/tmwa/partyhandler.cpp:157
|-valign="top"
|0x0102 || 6 || CMSG_PARTY_SETTINGS || src/net/tmwa/partyhandler.cpp:402<br>src/net/tmwa/partyhandler.cpp:412 || src/map/clif.c:8558
|-valign="top"
|0x0103 || 30 || CMSG_PARTY_KICK || src/net/tmwa/partyhandler.cpp:364<br>src/net/tmwa/partyhandler.cpp:379 || src/map/clif.c:8549
|-valign="top"
|0x0104 || 79 || SMSG_PARTY_MOVE || src/map/clif.c:5485 || src/net/tmwa/partyhandler.cpp:220
|-valign="top"
|0x0105 || 31 || SMSG_PARTY_LEAVE || src/map/clif.c:5383 || src/net/tmwa/partyhandler.cpp:232
|-valign="top"
|0x0106 || 10 || SMSG_PARTY_UPDATE_HP || src/map/clif.c:5463 || src/net/tmwa/partyhandler.cpp:263
|-valign="top"
|0x0107 || 10 || SMSG_PARTY_UPDATE_COORDS || src/map/clif.c:5443 || src/net/tmwa/partyhandler.cpp:283
|-valign="top"
|0x0108 || -1 || CMSG_PARTY_MESSAGE || src/net/tmwa/partyhandler.cpp:386 || src/map/clif.c:8571
|-valign="top"
|0x0109 || -1 || SMSG_PARTY_MESSAGE || src/map/clif.c:5424 || src/net/tmwa/partyhandler.cpp:290
|-valign="top"
|0x010C || 6 || SMSG_MVP || src/map/clif.c:5708 || src/net/tmwa/chathandler.cpp:187
|-valign="top"
|0x010E || 11 || SMSG_PLAYER_SKILL_UP<br>SMSG_GUILD_SKILL_UP || src/map/clif.c:4186<br>src/map/clif.c:6345 || src/net/tmwa/specialhandler.cpp:115<br>src/net/tmwa/guildhandler.cpp:253
|-valign="top"
|0x010F || -1 || SMSG_PLAYER_SKILLS || src/map/clif.c:4145 || src/net/tmwa/specialhandler.cpp:93
|-valign="top"
|0x0110 || 10 || SMSG_SKILL_FAILED || src/map/clif.c:4259 || src/net/tmwa/specialhandler.cpp:129
|-valign="top"
|0x0112 || 4 || CMSG_SKILL_LEVELUP_REQUEST || src/net/tmwa/playerhandler.cpp:597 || src/map/clif.c:8002
|-valign="top"
|0x0113 || 10 || CMSG_SKILL_USE_BEING || src/net/tmwa/specialhandler.cpp:234 || src/map/clif.c:8011
|-valign="top"
|0x0116 || 10 || CMSG_SKILL_USE_POSITION || src/net/tmwa/specialhandler.cpp:242 || src/map/clif.c:8088
|-valign="top"
|0x0119 || 13 || SMSG_PLAYER_STATUS_CHANGE || src/map/clif.c:1268<br>src/map/clif.c:2885 || src/net/tmwa/beinghandler.cpp:671
|-valign="top"
|0x011B || 20 || CMSG_SKILL_USE_MAP || src/net/tmwa/specialhandler.cpp:251 || src/map/clif.c:8158
|-valign="top"
|0x0139 || 16 || SMSG_PLAYER_MOVE_TO_ATTACK || src/map/clif.c:5510 || src/net/tmwa/beinghandler.cpp:662
|-valign="top"
|0x013A || 4 || SMSG_PLAYER_ATTACK_RANGE || src/map/clif.c:2474 || src/net/tmwa/inventoryhandler.cpp:423
|-valign="top"
|0x013B || 4 || SMSG_PLAYER_ARROW_MESSAGE || src/map/clif.c:2780 || src/net/tmwa/playerhandler.cpp:545
|-valign="top"
|0x013C || 4 || SMSG_PLAYER_ARROW_EQUIP || src/map/clif.c:2761 || src/net/tmwa/inventoryhandler.cpp:427
|-valign="top"
|0x0141 || 14 || SMSG_PLAYER_STAT_UPDATE_3 || src/map/clif.c:2482<br>src/map/clif.c:2489<br>src/map/clif.c:2496<br>src/map/clif.c:2503<br>src/map/clif.c:2510<br>src/map/clif.c:2517 || src/net/tmwa/playerhandler.cpp:370
|-valign="top"
|0x0142 || 6 || SMSG_NPC_INT_INPUT || src/map/clif.c:1772 || src/net/tmwa/npchandler.cpp:116
|-valign="top"
|0x0143 || 10 || CMSG_NPC_INT_RESPONSE || src/net/tmwa/npchandler.cpp:166 || src/map/clif.c:8215
|-valign="top"
|0x0146 || 6 || CMSG_NPC_CLOSE || src/net/tmwa/npchandler.cpp:146 || src/map/clif.c:8265
|-valign="top"
|0x0148 || 8 || SMSG_BEING_RESURRECT || src/map/clif.c:4667 || src/net/tmwa/beinghandler.cpp:293
|-valign="top"
|0x0149 || 9 || CMSG_ADMIN_MUTE || src/net/tmwa/adminhandler.cpp:137 || src/map/clif.c:9025
|-valign="top"
|0x014C || -1 || SMSG_GUILD_ALIANCE_INFO || src/map/clif.c:5962 || src/net/tmwa/guildhandler.cpp:157
|-valign="top"
|0x014D || 2 || CMSG_GUILD_CHECK_MASTER || || src/map/clif.c:8661
|-valign="top"
|0x014E || 6 || SMSG_GUILD_MASTER_OR_MEMBER || src/map/clif.c:5842 || src/net/tmwa/guildhandler.cpp:134
|-valign="top"
|0x014F || 6 || CMSG_GUILD_REQUEST_INFO || src/net/tmwa/guildhandler.cpp:457 || src/map/clif.c:8670
|-valign="top"
|0x0151 || 6 || CMSG_GUILD_REQUEST_EMBLEM || || src/map/clif.c:8760
|-valign="top"
|0x0152 || -1 || SMSG_GUILD_EMBLEM || src/map/clif.c:6135 || src/net/tmwa/guildhandler.cpp:243
|-valign="top"
|0x0153 || -1 || CMSG_GUILD_CHANGE_EMBLEM || || src/map/clif.c:8771
|-valign="top"
|0x0154 || -1 || SMSG_GUILD_MEMBER_LIST || src/map/clif.c:5996 || src/net/tmwa/guildhandler.cpp:171
|-valign="top"
|0x0155 || -1 || CMSG_GUILD_CHANGE_MEMBER_POS || || src/map/clif.c:8731
|-valign="top"
|0x0156 || -1 || SMSG_GUILD_MEMBER_POS_CHANGE || src/map/clif.c:6110 || src/net/tmwa/guildhandler.cpp:236
|-valign="top"
|0x0159 || 54 || CMSG_GUILD_LEAVE || src/net/tmwa/guildhandler.cpp:425 || src/map/clif.c:8807
|-valign="top"
|0x015A || 66 || SMSG_GUILD_LEAVE || src/map/clif.c:6252 || src/net/tmwa/guildhandler.cpp:322
|-valign="top"
|0x015B || 54 || CMSG_GUILD_EXPULSION || src/net/tmwa/guildhandler.cpp:434 || src/map/clif.c:8817
|-valign="top"
|0x015C || 90 || SMSG_GUILD_EXPULSION || src/map/clif.c:6270 || src/net/tmwa/guildhandler.cpp:327
|-valign="top"
|0x015D || 42 || CMSG_GUILD_BREAK || || src/map/clif.c:8907
|-valign="top"
|0x015E || 6 || SMSG_GUILD_BROKEN || src/map/clif.c:6453 || src/net/tmwa/guildhandler.cpp:384
|-valign="top"
|0x0160 || -1 || SMSG_GUILD_POS_INFO_LIST || src/map/clif.c:6062 || src/net/tmwa/guildhandler.cpp:212
|-valign="top"
|0x0161 || -1 || CMSG_GUILD_CHANGE_POS_INFO || || src/map/clif.c:8704
|-valign="top"
|0x0162 || -1 || SMSG_GUILD_SKILL_INFO || src/map/clif.c:6160 || src/net/tmwa/guildhandler.cpp:253
|-valign="top"
|0x0163 || -1 || SMSG_GUILD_EXPULSION_LIST || src/map/clif.c:6294 || src/net/tmwa/guildhandler.cpp:333
|-valign="top"
|0x0165 || 30 || CMSG_GUILD_CREATE || src/net/tmwa/guildhandler.cpp:396 || src/map/clif.c:8652
|-valign="top"
|0x0166 || -1 || SMSG_GUILD_POS_NAME_LIST || src/map/clif.c:6036 || src/net/tmwa/guildhandler.cpp:199
|-valign="top"
|0x0167 || 3 || SMSG_GUILD_CREATE_RESPONSE || src/map/clif.c:5771 || src/net/tmwa/guildhandler.cpp:91
|-valign="top"
|0x0168 || 14 || CMSG_GUILD_INVITE || src/net/tmwa/guildhandler.cpp:408 || src/map/clif.c:8789
|-valign="top"
|0x0169 || 3 || SMSG_GUILD_INVITE_ACK || src/map/clif.c:6235 || src/net/tmwa/guildhandler.cpp:288
|-valign="top"
|0x016A || 30 || SMSG_GUILD_INVITE || src/map/clif.c:6217 || src/net/tmwa/guildhandler.cpp:279
|-valign="top"
|0x016B || 10 || CMSG_GUILD_INVITE_REPLY || src/net/tmwa/guildhandler.cpp:416 || src/map/clif.c:8798
|-valign="top"
|0x016C || 43 || SMSG_GUILD_POSITION_INFO || src/map/clif.c:5792 || src/net/tmwa/guildhandler.cpp:114
|-valign="top"
|0x016D || 14 || SMSG_GUILD_MEMBER_LOGIN || src/map/clif.c:5811 || src/net/tmwa/guildhandler.cpp:128
|-valign="top"
|0x016E || 186 || CMSG_GUILD_CHANGE_NOTICE || || src/map/clif.c:8780
|-valign="top"
|0x016F || 182 || SMSG_GUILD_NOTICE || src/map/clif.c:6198 || src/net/tmwa/guildhandler.cpp:274
|-valign="top"
|0x0170 || 14 || CMSG_GUILD_ALLIANCE_REQUEST || || src/map/clif.c:8871
|-valign="top"
|0x0171 || 30 || SMSG_GUILD_REQ_ALLIANCE || src/map/clif.c:6367 || src/net/tmwa/guildhandler.cpp:366
|-valign="top"
|0x0172 || 10 || CMSG_GUILD_ALLIANCE_REPLY || || src/map/clif.c:8880
|-valign="top"
|0x0173 || 3 || SMSG_GUILD_REQ_ALLIANCE_ACK || src/map/clif.c:6385 || src/net/tmwa/guildhandler.cpp:371
|-valign="top"
|0x0174 || -1 || SMSG_GUILD_POSITION_CHANGED || src/map/clif.c:6087 || src/net/tmwa/guildhandler.cpp:227
|-valign="top"
|0x017E || -1 || CMSG_GUILD_MESSAGE || src/net/tmwa/guildhandler.cpp:443 || src/map/clif.c:8831
|-valign="top"
|0x017F || -1 || SMSG_GUILD_MESSAGE || src/map/clif.c:6323<br>src/map/clif.c:6581 || src/net/tmwa/guildhandler.cpp:347
|-valign="top"
|0x0180 || 6 || CMSG_GUILD_OPPOSITION || || src/map/clif.c:8898
|-valign="top"
|0x0181 || 3 || SMSG_GUILD_OPPOSITION_ACK || src/map/clif.c:6421 || src/net/tmwa/guildhandler.cpp:380
|-valign="top"
|0x0183 || 10 || CMSG_GUILD_ALLIANCE_DELETE || || src/map/clif.c:8889
|-valign="top"
|0x0184 || 10 || SMSG_GUILD_DEL_ALLIANCE || src/map/clif.c:6403 || src/net/tmwa/guildhandler.cpp:375
|-valign="top"
|0x018A || 4 || CMSG_CLIENT_QUIT || src/net/tmwa/gamehandler.cpp:161 || src/map/clif.c:6611
|-valign="top"
|0x018B || 4 || SMSG_MAP_QUIT_RESPONSE || src/map/clif.c:7012<br>src/map/clif.c:7440 || src/net/tmwa/gamehandler.cpp:98
|-valign="top"
|0x0190 || 90 || CMSG_SKILL_USE_POSITION_MORE || || src/map/clif.c:8088
|-valign="top"
|0x0195 || 102 || SMSG_PLAYER_GUILD_PARTY_INFO || src/map/clif.c:7107 || src/net/tmwa/beinghandler.cpp:490
|-valign="top"
|0x0196 || 9 || SMSG_BEING_STATUS_CHANGE || src/map/clif.c:4585 || src/net/tmwa/beinghandler.cpp:688
|-valign="top"
|0x019B || 10 || SMSG_BEING_SELFEFFECT || src/map/clif.c:2858<br>src/map/clif.c:6696 || src/net/tmwa/beinghandler.cpp:372
|-valign="top"
|0x019C || 4 || CMSG_ADMIN_LOCAL_ANNOUNCE || src/net/tmwa/adminhandler.cpp:91 || src/map/clif.c:8350
|-valign="top"
|0x019D || 6 || CMSG_ADMIN_HIDE || src/net/tmwa/adminhandler.cpp:98 || src/map/clif.c:8996
|-valign="top"
|0x01B1 || 7 || SMSG_TRADE_ITEM_ADD_RESPONSE || src/map/clif.c:3299 || src/net/tmwa/tradehandler.cpp:176
|-valign="top"
|0x01B6 || 114 || SMSG_GUILD_BASIC_INFO || src/map/clif.c:5865 || src/net/tmwa/guildhandler.cpp:138
|-valign="top"
|0x01C8 || 13 || SMSG_PLAYER_INVENTORY_USE || src/map/clif.c:2945 || src/net/tmwa/inventoryhandler.cpp:265
|-valign="top"
|0x01D4 || 6 || SMSG_NPC_STR_INPUT || src/map/clif.c:1790 || src/net/tmwa/npchandler.cpp:121
|-valign="top"
|0x01D5 || 8 || CMSG_NPC_STR_RESPONSE || src/net/tmwa/npchandler.cpp:173 || src/map/clif.c:8234
|-valign="top"
|0x01D7 || 11 || SMSG_BEING_CHANGE_LOOKS2 || src/map/clif.c:2608<br>src/map/clif.c:2675 || src/net/tmwa/beinghandler.cpp:401
|-valign="top"
|0x01D8 || 54 || SMSG_PLAYER_UPDATE_1 || src/map/clif.c:845 || src/net/tmwa/beinghandler.cpp:511
|-valign="top"
|0x01D9 || 53 || SMSG_PLAYER_UPDATE_2 || src/map/clif.c:1292 || src/net/tmwa/beinghandler.cpp:512
|-valign="top"
|0x01DA || 60 || SMSG_PLAYER_MOVE || src/map/clif.c:934 || src/net/tmwa/beinghandler.cpp:513
|-valign="top"
|0x01DE || 33 || SMSG_SKILL_DAMAGE || src/map/clif.c:4298 || src/net/tmwa/beinghandler.cpp:311
|-valign="top"
|0x01EE || -1 || SMSG_PLAYER_INVENTORY || src/map/clif.c:1965 || src/net/tmwa/inventoryhandler.cpp:134
|-valign="top"
|0x01F0 || -1 || SMSG_PLAYER_STORAGE_ITEMS || src/map/clif.c:2097<br>src/map/clif.c:2225 || src/net/tmwa/inventoryhandler.cpp:135
|-valign="top"
|0x020C || 10 || SMSG_ADMIN_IP || src/map/clif.c:7120 || src/net/tmwa/adminhandler.cpp:69
|-valign="top"
|0x7530 || 2 || CMSG_SERVER_VERSION_REQUEST || src/net/tmwa/loginhandler.cpp:220 || src/login/login.c:2257<br>src/login/login.c:4011<br>src/char/char.c:3568<br>src/map/clif.c:10174
|-valign="top"
|0x7531 || 10 || SMSG_SERVER_VERSION_RESPONSE || src/login/login.c:2260<br>src/login/login.c:4014<br>src/char/char.c:3569<br>src/map/clif.c:10175 || src/net/tmwa/loginhandler.cpp:197

|}

== Free Packets ==
These are packets that are not parsed or sent by the client, but have a known length, so they can be used by future servers and the client will just ignore them, not crash.

{| border="1" cellspacing="0" cellpadding="3"
|- valign="top"
!packet !!len !!notes
|- valign="top"
|0x0000 ||10 ||
|- valign="top"
|0x0074 ||3 ||
|- valign="top"
|0x0075 ||-1 ||
|- valign="top"
|0x0076 ||9 ||
|- valign="top"
|0x0077 ||5 ||
|- valign="top"
|0x0079 ||53 ||
|- valign="top"
|0x007A ||58 ||
|- valign="top"
|0x0082 ||2 ||
|- valign="top"
|0x0083 ||2 ||
|- valign="top"
|0x0084 ||2 ||
|- valign="top"
|0x008B ||23 ||
|- valign="top"
|0x0093 ||2 ||
|- valign="top"
|0x00A3 ||-1 ||
|- valign="top"
|0x00A5 ||-1 ||
|- valign="top"
|0x00AE ||-1 ||
|- valign="top"
|0x00BA ||2 ||
|- valign="top"
|0x00CE ||2 ||
|- valign="top"
|0x00CF ||27 ||clif_parse_PMIgnore
|- valign="top"
|0x00D0 ||3 ||clif_parse_PMIgnoreAll, used by ManaPlus
|- valign="top"
|0x00D1 ||4 ||
|- valign="top"
|0x00D2 ||4 ||used by ManaPlus (sent from atcommand.cpp)
|- valign="top"
|0x00D3 ||2 ||
|- valign="top"
|0x00D4 ||-1 ||
|- valign="top"
|0x00D5 ||-1 ||clif_parse_CreateChatRoom
|- valign="top"
|0x00D6 ||3 ||
|- valign="top"
|0x00D7 ||-1 ||
|- valign="top"
|0x00D8 ||6 ||
|- valign="top"
|0x00D9 ||14 ||clif_parse_ChatAddMember
|- valign="top"
|0x00DA ||3 ||
|- valign="top"
|0x00DB ||-1 ||
|- valign="top"
|0x00DC ||28 ||
|- valign="top"
|0x00DD ||29 ||
|- valign="top"
|0x00DE ||-1 ||clif_parse_ChatRoomStatusChange
|- valign="top"
|0x00DF ||-1 ||
|- valign="top"
|0x00E0 ||30 ||clif_parse_ChangeChatOwner
|- valign="top"
|0x00E1 ||30 ||
|- valign="top"
|0x00E2 ||26 ||clif_parse_KickFromChat
|- valign="top"
|0x00E3 ||2 ||clif_parse_ChatLeave
|- valign="top"
|0x00EA ||5 ||
|- valign="top"
|0x00F1 ||2 ||
|- valign="top"
|0x010A ||4 ||
|- valign="top"
|0x010B ||6 ||
|- valign="top"
|0x010D ||2 ||clif_parse_RequestMemo
|- valign="top"
|0x0111 ||39 ||
|- valign="top"
|0x0114 ||31 ||
|- valign="top"
|0x0115 ||35 ||
|- valign="top"
|0x0117 ||18 ||
|- valign="top"
|0x0118 ||2 ||clif_parse_StopAttack, used by ManaPlus
|- valign="top"
|0x011A ||15 ||SMSG_SKILL_NO_DAMAGE, used by ManaPlus
|- valign="top"
|0x011C ||68 ||
|- valign="top"
|0x011D ||2 ||clif_parse_RequestMemo
|- valign="top"
|0x011E ||3 ||
|- valign="top"
|0x011F ||16 ||
|- valign="top"
|0x0120 ||6 ||
|- valign="top"
|0x0121 ||14 ||
|- valign="top"
|0x0122 ||-1 ||
|- valign="top"
|0x0123 ||-1 ||
|- valign="top"
|0x0124 ||21 ||
|- valign="top"
|0x0125 ||8 ||
|- valign="top"
|0x0126 ||8 ||clif_parse_PutItemToCart
|- valign="top"
|0x0127 ||8 ||clif_parse_GetItemFromCart
|- valign="top"
|0x0128 ||8 ||clif_parse_MoveFromKafraToCart
|- valign="top"
|0x0129 ||8 ||clif_parse_MoveToKafraFromCart
|- valign="top"
|0x012A ||2 ||clif_parse_RemoveOption
|- valign="top"
|0x012B ||2 ||
|- valign="top"
|0x012C ||3 ||
|- valign="top"
|0x012D ||4 ||
|- valign="top"
|0x012E ||2 ||
|- valign="top"
|0x012F ||-1 ||
|- valign="top"
|0x0130 ||6 ||
|- valign="top"
|0x0131 ||86 ||
|- valign="top"
|0x0132 ||6 ||
|- valign="top"
|0x0133 ||-1 ||
|- valign="top"
|0x0134 ||-1 ||
|- valign="top"
|0x0135 ||7 ||
|- valign="top"
|0x0136 ||-1 ||
|- valign="top"
|0x0137 ||6 ||
|- valign="top"
|0x0138 ||3 ||
|- valign="top"
|0x013D ||6 ||
|- valign="top"
|0x013E ||24 ||SMSG_SKILL_CASTING, used by ManaPlus
|- valign="top"
|0x013F ||26 ||clif_parse_GM_Monster_Item
|- valign="top"
|0x0140 ||22 ||clif_parse_MapMove
|- valign="top"
|0x0144 ||23 ||
|- valign="top"
|0x0145 ||19 ||
|- valign="top"
|0x0147 ||39 ||
|- valign="top"
|0x014A ||6 ||
|- valign="top"
|0x014B ||27 ||
|- valign="top"
|0x0150 ||110 ||
|- valign="top"
|0x0157 ||6 ||
|- valign="top"
|0x0158 ||-1 ||
|- valign="top"
|0x015F ||42 ||
|- valign="top"
|0x0164 ||-1 ||
|- valign="top"
|0x0175 ||6 ||
|- valign="top"
|0x0176 ||106 ||
|- valign="top"
|0x0177 ||-1 ||
|- valign="top"
|0x0178 ||4 ||clif_parse_ItemIdentify
|- valign="top"
|0x0179 ||5 ||
|- valign="top"
|0x017A ||4 ||clif_parse_UseCard
|- valign="top"
|0x017B ||-1 ||
|- valign="top"
|0x017C ||6 ||clif_parse_InsertCard
|- valign="top"
|0x017D ||7 ||
|- valign="top"
|0x0182 ||106 ||
|- valign="top"
|0x0185 ||34 ||
|- valign="top"
|0x0187 ||6 ||src/char/char.c:3562
|- valign="top"
|0x0188 ||8 ||
|- valign="top"
|0x0189 ||4 ||
|- valign="top"
|0x018C ||29 ||
|- valign="top"
|0x018D ||-1 ||
|- valign="top"
|0x018E ||10 ||
|- valign="top"
|0x018F ||6 ||
|- valign="top"
|0x0191 ||86 ||
|- valign="top"
|0x0192 ||24 ||
|- valign="top"
|0x0193 ||6 ||clif_parse_SolveCharName
|- valign="top"
|0x0194 ||30 ||
|- valign="top"
|0x0197 ||4 ||clif_parse_ResetChar
|- valign="top"
|0x0198 ||8 ||
|- valign="top"
|0x0199 ||4 ||SMSG_PVP_MAP_MODE, used by ManaPlus
|- valign="top"
|0x019A ||14 ||SMSG_PVP_SET, used by ManaPlus
|- valign="top"
|0x019E ||2 ||
|- valign="top"
|0x019F ||6 ||
|- valign="top"
|0x01A0 ||3 ||
|- valign="top"
|0x01A1 ||3 ||
|- valign="top"
|0x01A2 ||35 ||
|- valign="top"
|0x01A3 ||5 ||
|- valign="top"
|0x01A4 ||11 ||
|- valign="top"
|0x01A5 ||26 ||
|- valign="top"
|0x01A6 ||-1 ||
|- valign="top"
|0x01A7 ||4 ||
|- valign="top"
|0x01A8 ||4 ||
|- valign="top"
|0x01A9 ||6 ||
|- valign="top"
|0x01AA ||10 ||
|- valign="top"
|0x01AB ||12 ||
|- valign="top"
|0x01AC ||6 ||
|- valign="top"
|0x01AD ||-1 ||
|- valign="top"
|0x01AE ||4 ||
|- valign="top"
|0x01AF ||4 ||clif_parse_ChangeCart
|- valign="top"
|0x01B0 ||11 ||
|- valign="top"
|0x01B2 ||-1 ||
|- valign="top"
|0x01B3 ||67 ||
|- valign="top"
|0x01B4 ||12 ||
|- valign="top"
|0x01B5 ||18 ||
|- valign="top"
|0x01B7 ||6 ||
|- valign="top"
|0x01B8 ||3 ||
|- valign="top"
|0x01B9 ||6 ||SMSG_SKILL_CAST_CANCEL, used by ManaPlus
|- valign="top"
|0x01BA ||26 ||clif_parse_Shift
|- valign="top"
|0x01BB ||26 ||clif_parse_Shift
|- valign="top"
|0x01BC ||26 ||clif_parse_Recall
|- valign="top"
|0x01BD ||26 ||clif_parse_Recall
|- valign="top"
|0x01BE ||2 ||
|- valign="top"
|0x01BF ||3 ||
|- valign="top"
|0x01C0 ||2 ||
|- valign="top"
|0x01C1 ||14 ||
|- valign="top"
|0x01C2 ||10 ||
|- valign="top"
|0x01C3 ||-1 ||
|- valign="top"
|0x01C4 ||22 ||
|- valign="top"
|0x01C5 ||22 ||
|- valign="top"
|0x01C6 ||4 ||
|- valign="top"
|0x01C7 ||2 ||
|- valign="top"
|0x01C9 ||97 ||
|- valign="top"
|0x01CB ||9 ||
|- valign="top"
|0x01CC ||9 ||
|- valign="top"
|0x01CD ||29 ||
|- valign="top"
|0x01CE ||6 ||clif_parse_AutoSpell
|- valign="top"
|0x01CF ||28 ||
|- valign="top"
|0x01D0 ||8 ||
|- valign="top"
|0x01D1 ||14 ||
|- valign="top"
|0x01D2 ||10 ||
|- valign="top"
|0x01D3 ||35 ||
|- valign="top"
|0x01D6 ||4 ||
|- valign="top"
|0x01DB ||2 ||src/login/login.c:3861
|- valign="top"
|0x01DC ||-1 ||src/login/login.c:3898
|- valign="top"
|0x01DD ||47 ||src/login/login.c:3645
|- valign="top"
|0x01DF ||6 ||clif_parse_GMReqNoChatCount
|- valign="top"
|0x01E0 ||30 ||
|- valign="top"
|0x01E1 ||8 ||
|- valign="top"
|0x01E2 ||34 ||
|- valign="top"
|0x01E3 ||14 ||
|- valign="top"
|0x01E4 ||2 ||
|- valign="top"
|0x01E5 ||6 ||
|- valign="top"
|0x01E6 ||26 ||
|- valign="top"
|0x01E7 ||2 ||clif_parse_sn_doridori
|- valign="top"
|0x01E8 ||28 ||clif_parse_CreateParty2
|- valign="top"
|0x01E9 ||81 ||
|- valign="top"
|0x01EA ||6 ||
|- valign="top"
|0x01EB ||10 ||
|- valign="top"
|0x01EC ||26 ||
|- valign="top"
|0x01ED ||2 ||clif_parse_sn_explosionspirits
|- valign="top"
|0x01EF ||-1 ||
|- valign="top"
|0x01F1 ||-1 ||
|- valign="top"
|0x01F2 ||20 ||
|- valign="top"
|0x01F3 ||10 ||
|- valign="top"
|0x01F4 ||32 ||
|- valign="top"
|0x01F5 ||9 ||
|- valign="top"
|0x01F6 ||34 ||
|- valign="top"
|0x01F7 ||14 ||
|- valign="top"
|0x01F8 ||2 ||
|- valign="top"
|0x01F9 ||6 ||
|- valign="top"
|0x01FA ||48 ||
|- valign="top"
|0x01FB ||56 ||
|- valign="top"
|0x01FC ||-1 ||
|- valign="top"
|0x01FD ||4 ||
|- valign="top"
|0x01FE ||5 ||
|- valign="top"
|0x01FF ||10 ||
|- valign="top"
|0x0200 ||26 ||src/login/login.c:3632
|- valign="top"
|0x0204 ||18 ||src/login/login.c:3638
|- valign="top"
|0x020B ||19 ||src/char/char.c:3030
|}

== Internal Packets ==
These packets are sent between the servers. Details are subject to change without notice.

=== login - char ===
<table border="1" cellspacing="0" cellpadding="3" class="wikitable sortable">
<tr valign="top">
<th>Packet</th> <th>Length</th> <th>Name</th> <th>Sent and Parsed Locations</th>
</tr>

{{Net:0x2709|mode=row_internal}}
{{Net:0x2711|mode=row_internal}}
{{Net:0x2712|mode=row_internal}}
{{Net:0x2713|mode=row_internal}}
{{Net:0x2714|mode=row_internal}}
{{Net:0x2716|mode=row_internal}}
{{Net:0x2717|mode=row_internal}}
{{Net:0x2722|mode=row_internal}}
{{Net:0x2723|mode=row_internal}}
{{Net:0x2724|mode=row_internal}}
{{Net:0x2727|mode=row_internal}}
{{Net:0x2731|mode=row_internal}}
{{Net:0x2740|mode=row_internal}}
{{Net:0x2741|mode=row_internal}}
</table>

=== login - admin ===
<table border="1" cellspacing="0" cellpadding="3" class="wikitable sortable">
<tr valign="top">
<th>Packet</th> <th>Length</th> <th>Name</th> <th>Sent and Parsed Locations</th>
</tr>


</table>

=== char - map ===
<table border="1" cellspacing="0" cellpadding="3" class="wikitable sortable">
<tr valign="top">
<th>Packet</th> <th>Length</th> <th>Name</th> <th>Sent and Parsed Locations</th>
</tr>


</table>

==== inter.cpp recv ====
<table>
<tr> <td> 0x3000 </td> <td> -1 </td> </tr>
<tr> <td> 0x3001 </td> <td> -1 </td> </tr>
<tr> <td> 0x3002 </td> <td> 7 </td> </tr>
<tr> <td> 0x3003 </td> <td> -1 </td> </tr>
<tr> <td> 0x3004 </td> <td> -1 </td> </tr>
<tr> <td> 0x3005 </td> <td> 6 </td> </tr>
<tr> <td> 0x3010 </td> <td> 6 </td> </tr>
<tr> <td> 0x3011 </td> <td> -1 </td> </tr>
<tr> <td> 0x3018 </td> <td> 10 </td> </tr>
<tr> <td> 0x3019 </td> <td> -1 </td> </tr>
<tr> <td> 0x3020 </td> <td> 72 </td> </tr>
<tr> <td> 0x3021 </td> <td> 6 </td> </tr>
<tr> <td> 0x3022 </td> <td> 52 </td> </tr>
<tr> <td> 0x3023 </td> <td> 14 </td> </tr>
<tr> <td> 0x3024 </td> <td> 10 </td> </tr>
<tr> <td> 0x3025 </td> <td> 29 </td> </tr>
<tr> <td> 0x3026 </td> <td> 6 </td> </tr>
<tr> <td> 0x3027 </td> <td> -1 </td> </tr>
<tr> <td> 0x3028 </td> <td> 34 </td> </tr>
<tr> <td> 0x3030 </td> <td> -1 </td> </tr>
<tr> <td> 0x3031 </td> <td> 6 </td> </tr>
<tr> <td> 0x3032 </td> <td> -1 </td> </tr>
<tr> <td> 0x3034 </td> <td> 55 </td> </tr>
<tr> <td> 0x3035 </td> <td> 19 </td> </tr>
<tr> <td> 0x3036 </td> <td> 6 </td> </tr>
<tr> <td> 0x3037 </td> <td> -1 </td> </tr>
<tr> <td> 0x3038 </td> <td> 14 </td> </tr>
<tr> <td> 0x3039 </td> <td> -1 </td> </tr>
<tr> <td> 0x303a </td> <td> -1 </td> </tr>
<tr> <td> 0x303b </td> <td> -1 </td> </tr>
<tr> <td> 0x303c </td> <td> 14 </td> </tr>
<tr> <td> 0x303d </td> <td> 19 </td> </tr>
<tr> <td> 0x303e </td> <td> 186 </td> </tr>
<tr> <td> 0x303f </td> <td> -1 </td> </tr>
<tr> <td> 0x3040 </td> <td> 5 </td> </tr>
<tr> <td> 0x3041 </td> <td> 9 </td> </tr>
<tr> <td> 0x3080 </td> <td> 48 </td> </tr>
<tr> <td> 0x3081 </td> <td> 14 </td> </tr>
<tr> <td> 0x3082 </td> <td> -1 </td> </tr>
<tr> <td> 0x3083 </td> <td> 6 </td> </tr>
</table>

==== intif.cpp recv ====
<table>
<tr> <td> 0x3800 </td> <td> -1 </td> </tr>
<tr> <td> 0x3801 </td> <td> -1 </td> </tr>
<tr> <td> 0x3802 </td> <td> 27 </td> </tr>
<tr> <td> 0x3803 </td> <td> -1 </td> </tr>
<tr> <td> 0x3804 </td> <td> -1 </td> </tr>
<tr> <td> 0x3810 </td> <td> -1 </td> </tr>
<tr> <td> 0x3811 </td> <td> 7 </td> </tr>
<tr> <td> 0x3818 </td> <td> -1 </td> </tr>
<tr> <td> 0x3819 </td> <td> 11 </td> </tr>
<tr> <td> 0x3820 </td> <td> 35 </td> </tr>
<tr> <td> 0x3821 </td> <td> -1 </td> </tr>
<tr> <td> 0x3822 </td> <td> 11 </td> </tr>
<tr> <td> 0x3823 </td> <td> 15 </td> </tr>
<tr> <td> 0x3824 </td> <td> 34 </td> </tr>
<tr> <td> 0x3825 </td> <td> 29 </td> </tr>
<tr> <td> 0x3826 </td> <td> 7 </td> </tr>
<tr> <td> 0x3827 </td> <td> -1 </td> </tr>
<tr> <td> 0x3830 </td> <td> 10 </td> </tr>
<tr> <td> 0x3831 </td> <td> -1 </td> </tr>
<tr> <td> 0x3832 </td> <td> 15 </td> </tr>
<tr> <td> 0x3834 </td> <td> 79 </td> </tr>
<tr> <td> 0x3835 </td> <td> 19 </td> </tr>
<tr> <td> 0x3836 </td> <td> 7 </td> </tr>
<tr> <td> 0x3837 </td> <td> -1 </td> </tr>
<tr> <td> 0x3839 </td> <td> -1 </td> </tr>
<tr> <td> 0x383a </td> <td> -1 </td> </tr>
<tr> <td> 0x383b </td> <td> -1 </td> </tr>
<tr> <td> 0x383c </td> <td> 14 </td> </tr>
<tr> <td> 0x383d </td> <td> 67 </td> </tr>
<tr> <td> 0x383e </td> <td> 186 </td> </tr>
<tr> <td> 0x383f </td> <td> -1 </td> </tr>
<tr> <td> 0x3840 </td> <td> 9 </td> </tr>
<tr> <td> 0x3841 </td> <td> 9 </td> </tr>
<tr> <td> 0x3842 </td> <td> -1 </td> </tr>
<tr> <td> 0x3880 </td> <td> 11 </td> </tr>
<tr> <td> 0x3881 </td> <td> -1 </td> </tr>
<tr> <td> 0x3882 </td> <td> 7 </td> </tr>
<tr> <td> 0x3883 </td> <td> 3 </td> </tr>
</table>

==== chrif.cpp recv ====
<table>
<tr> <td> 0x2af8 </td> <td> 60 </td> </tr>
<tr> <td> 0x2af9 </td> <td> 3 </td> </tr>
<tr> <td> 0x2afa </td> <td> 10 </td> </tr>
<tr> <td> 0x2afb </td> <td> 27 </td> </tr>
<tr> <td> 0x2afc </td> <td> 22 </td> </tr>
<tr> <td> 0x2afd </td> <td> -1 </td> </tr>
<tr> <td> 0x2afe </td> <td> 6 </td> </tr>
<tr> <td> 0x2aff </td> <td> -1 </td> </tr>
<tr> <td> 0x2b00 </td> <td> 6 </td> </tr>
<tr> <td> 0x2b01 </td> <td> -1 </td> </tr>
<tr> <td> 0x2b02 </td> <td> 18 </td> </tr>
<tr> <td> 0x2b03 </td> <td> 7 </td> </tr>
<tr> <td> 0x2b04 </td> <td> -1 </td> </tr>
<tr> <td> 0x2b05 </td> <td> 49 </td> </tr>
<tr> <td> 0x2b06 </td> <td> 44 </td> </tr>
<tr> <td> 0x2b08 </td> <td> 6 </td> </tr>
<tr> <td> 0x2b09 </td> <td> 30 </td> </tr>
<tr> <td> 0x2b0a </td> <td> -1 </td> </tr>
<tr> <td> 0x2b0b </td> <td> 10 </td> </tr>
<tr> <td> 0x2b0c </td> <td> 86 </td> </tr>
<tr> <td> 0x2b0d </td> <td> 7 </td> </tr>
<tr> <td> 0x2b0e </td> <td> 44 </td> </tr>
<tr> <td> 0x2b0f </td> <td> 34 </td> </tr>
<tr> <td> 0x2b10 </td> <td> -1 </td> </tr>
<tr> <td> 0x2b11 </td> <td> -1 </td> </tr>
<tr> <td> 0x2b12 </td> <td> 10 </td> </tr>
<tr> <td> 0x2b13 </td> <td> 6 </td> </tr>
<tr> <td> 0x2b14 </td> <td> 11 </td> </tr>
<tr> <td> 0x2b15 </td> <td> -1 </td> </tr>
</table>

==== char.cpp recv ====
<table>

</table>

User:O11c/how

2014-05-15T07:06:55Z

O11c: add transclusion

We're using Git as version control system for our source files and content. Have a look at our [[Working With Git|Tutorial]] about how to use Git.

=Set Up=
This is a how to help content development for official server (tmwAthena) using Ubuntu and the Mana+ client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwa-client-data), server-data (tmwa-server-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting.

==Install Dependencies==
In addition to the basic build tools (GCC, Make, headers, ...), [http://www.gnu.org/software/bison/ '''Bison'''], and [http://sourceforge.net/projects/flex/ '''Flex'''] are needed.

''' [https://www.debian.org/ Debian] derivates (including [http://www.ubuntu.com/ Ubuntu])'''
* Open a terminal.
sudo apt-get install g++ flex bison python make realpath git

''' [https://fedoraproject.org/ Fedora] derivates'''
* Open a terminal.
sudo yum install gcc-c++ flex bison make git

Note that you must have gcc 4.6 or later. Any modern distro will have this version, but "stable" distros with very long release cycles, such as Red Hat Enterprise Linux, might not.

==Set Up Own Server==
'''Here are the steps to use when creating a new local testing server.'''
* Open a terminal.
mkdir ~/tmwAthena
cd ~/tmwAthena/
git clone --recursive git://github.com/themanaworld/tmwa.git
git clone --recursive git://github.com/themanaworld/tmwa-server-data.git
cd tmwa/
./configure --user # ''(Assuming ~/bin is in your PATH if not use ./configure)''
make
make install
git config --global url.git@github.com:.pushInsteadOf git://github.com ''{{ref|push}} {{ref|once}}''
cd ../tmwa-server-data
* Preferably, add the update hooks.
ln -s ../../git/hooks/post-merge .git/hooks/
ln -s ../../../../git/hooks/post-merge .git/modules/client-data/hooks/ # ''(git 1.7.8 or newer)''
ln -s ../../../git/hooks/post-merge client-data/.git/hooks/ # ''(git 1.7.7 or older)''
make conf
cd client-data
git checkout master
cd music
git checkout master

==Hosting Updates==
TMW makes it easy to generate delta zips out of a repository, once it is initially set up.

It will put them in ~/www/updates/, which may be a symlink to wherever your web server is really serving. Setting up a webserver is not covered here.

Once everything is set up, just run 'make updates' from the server-data dir every time client-data changes. It will do nothing if appropriate, generate complete zips the first time, and incremental zips afterwards.

Some notes:
* You must put news.txt and skeleton resources.xml file (and maybe an empty resources2.txt) in ~/www/updates/ first.
* Music updates are never added; they should be in the skeleton and updated manually if needed.
* You definitely want to run one of the analyzer scripts frequently, and remove the old updates.

==Updating the Server==

== Running and Administrating the Server ==

The TMWAthena is in fact 3 servers:
* '''tmwa-login''' which manages accounts and connection to char server.
* '''tmwa-char''' which manages characters and connects them to the map server.
* '''tmwa-map''' which manages game content (maps, monsters, items, scripts...) and their interaction with characters

* Start the servers: Open a terminal and run all the local servers. To stop them, either close the terminal or type control-C.
cd ~/tmwAthena/tmwa-server-data/
./run-all
* In a new terminal, Launch '''tmwa-admin''' the administration tool, add yourself as an user and make yourself a GM:
cd ~/tmwAthena/tmwa-server-data/login
tmwa-admin
add <username> M <password>
gm <username> 99

'''Note''' : Be sure that you are running tmwa-admin from within the "login/" directory. Check that the config files are correct: the connection port should be 6901 for tmwa's configuration, not 6900, which is the hard-coded default.

'''See also:''' [[GM Commands]]

== Connecting ==
# Open a command line terminal and run your client pointing to your client data and your local server :
manaplus --server localhost --port 6901 -u -d ~/tmwAthena/tmwa-server-data/client-data

If all went well, you are now ready to test new content and participate with development.

== develop new content==
'''You are now free to do some changes, first close the client and your servers.'''

'''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.'''''
* Make your modifications (e.g. Change a map) and save them.
* Open a terminal.
cd ~/tmwAthena/tmwa-server-data/client-data''
git status''
git add [modified files]''
git commit''
git push'' {{note|push}}
cd ..
make maps ''(if you changed a map)''
git status
git add [modified files]
git add client-data (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''')
git commit
git push {{note|push}}
* Close the terminal.

{{note|push}} : a step for those with commit access to the remote repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested.

{{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories.

git format-patch -M -C origin/master
* pastebin the patch(es) and post for review at irc.freenode.net channel: #themanaworld-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part.

<span style="color:#FF0000"> '''Note :''' This is kind of outdated; with github it's often easier to do patches on branches there. see: '''[[Working With Git]]''' page</span>

'''You can also pull the data which has been modified.'''
* Open a terminal.
cd ~/tmwAthena/tmwa-server-data
git pull
* If you haven't installed the hook,
git submodule update --merge ''at toplevel (for client-data) and in client-data (for music)''
* Close the terminal.

'''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music.

= Git guide =

{| class="wikitable mw-collapsible mw-collapsed"
|-
!Git guide
|-
|
{{User:Cassy/Git}}
|}

=Making Content=
==Making Map Content==
See [[Mapping Tutorial]].
===Python Converter Tool===
After editing maps for the client, you need to generate the walkmaps and imports for the server. yhis can be done either by the '''[[Tiled]]''' application or by running the python script '''tmx_converter.py''' which is located in the '''tools''' folder of the '''Server Data''' folder.
(see [[Mapping Tutorial#Creating the WLK files]])
After that, commit and push the files that the converter edited. Note that, if you do not have push access to the main repository, you should let someone else update the submodule itself.

==Getting Art Content Into The Game==
* Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum].
* Work with the Art Director and collaborators on getting the art consistent.
* When finished, edit topic as [FND].
* Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT].
* XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT].
::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition.
* Project developer requests database entry reservations from a General Content Team developer.
::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory.
::* Map entry client data affected: .tmx files in the maps directory.
::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made.
::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory.
::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file.

===Handling General Content Team [REQ]s===
* General Content Team member adds a [REQ] topic to the graphics development forum.
* General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page.
* Art Director attempts to network with other artists to assign the art to an artist.

==Bit Masking==
Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing.

[http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script]

==Generating client updates==
* Shutdown all your servers.

* First we are going to check the config files to be sure the paths are correct.
cd ~/tmwAthena/tmwa-server-data/client-data/tools/
ls

Output:
add-git-attributes edit-all-to-export-tilesets.sh formatXML.sh list-tileset-order map-db.py minimap-render.py
adler32 edit-map-tileset-names.sh indent.xsl make-updates map-diff.py
End of output

* The easiest solution is to create a symbolic link to that directory
ln -s /var/www/tmwupdates ~/www/updates (your public www folder is /tmwupdates)

* You can Edit the make-updates file with gedit or nano or vi.
Search for the folowing lines:
output=~/www/updates
And change them to:
output=/var/www/tmwupdates (your public www folder is /tmwupdates)

*Save the file and get back in the terminal.
cd ~/tmwAthena/tmwa-server-data/login/conf
ls

Output:
ladmin_athena.conf lan_support.conf login_local.conf.example
ladmin_local.conf login_athena.conf
ladmin_local.conf.example login_local.conf
End of output

*Edit the login_local.conf with an editor and look for the following line:
update_host: http://updates.themanaworld.org/
*Change that line to:
update_host: http://127.0.0.1/tmwupdates/ (or use your external ip)
*Save the file and get back in the terminal.

* Open a terminal.
First we compile the adler32 tool to generate a hash.
cd ~/tmwAthena/tmwa-server-data/client-data/tools/adler32/
make

Output must be:
gcc -lz -o adler32 adler32.c

make install

* Now that we compiled the adler tool we can make us a update.
cd ~/tmwAthena/tmwa-server-data/
make updates

* Each time you want to make new updates
make sure you have a new commit then
cd ~/tmwAthena/tmwa-server-data/
make updates

User:O11c/how

2014-05-15T07:03:50Z

O11c: Import unmodified

We're using Git as version control system for our source files and content. Have a look at our [[Working With Git|Tutorial]] about how to use Git.

=Set Up=
This is a how to help content development for official server (tmwAthena) using Ubuntu and the Mana+ client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwa-client-data), server-data (tmwa-server-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting.

==Install Dependencies==
In addition to the basic build tools (GCC, Make, headers, ...), [http://www.gnu.org/software/bison/ '''Bison'''], and [http://sourceforge.net/projects/flex/ '''Flex'''] are needed.

''' [https://www.debian.org/ Debian] derivates (including [http://www.ubuntu.com/ Ubuntu])'''
* Open a terminal.
sudo apt-get install g++ flex bison python make realpath git

''' [https://fedoraproject.org/ Fedora] derivates'''
* Open a terminal.
sudo yum install gcc-c++ flex bison make git

Note that you must have gcc 4.6 or later. Any modern distro will have this version, but "stable" distros with very long release cycles, such as Red Hat Enterprise Linux, might not.

==Set Up Own Server==
'''Here are the steps to use when creating a new local testing server.'''
* Open a terminal.
mkdir ~/tmwAthena
cd ~/tmwAthena/
git clone --recursive git://github.com/themanaworld/tmwa.git
git clone --recursive git://github.com/themanaworld/tmwa-server-data.git
cd tmwa/
./configure --user # ''(Assuming ~/bin is in your PATH if not use ./configure)''
make
make install
git config --global url.git@github.com:.pushInsteadOf git://github.com ''{{ref|push}} {{ref|once}}''
cd ../tmwa-server-data
* Preferably, add the update hooks.
ln -s ../../git/hooks/post-merge .git/hooks/
ln -s ../../../../git/hooks/post-merge .git/modules/client-data/hooks/ # ''(git 1.7.8 or newer)''
ln -s ../../../git/hooks/post-merge client-data/.git/hooks/ # ''(git 1.7.7 or older)''
make conf
cd client-data
git checkout master
cd music
git checkout master

==Hosting Updates==
TMW makes it easy to generate delta zips out of a repository, once it is initially set up.

It will put them in ~/www/updates/, which may be a symlink to wherever your web server is really serving. Setting up a webserver is not covered here.

Once everything is set up, just run 'make updates' from the server-data dir every time client-data changes. It will do nothing if appropriate, generate complete zips the first time, and incremental zips afterwards.

Some notes:
* You must put news.txt and skeleton resources.xml file (and maybe an empty resources2.txt) in ~/www/updates/ first.
* Music updates are never added; they should be in the skeleton and updated manually if needed.
* You definitely want to run one of the analyzer scripts frequently, and remove the old updates.

==Updating the Server==

== Running and Administrating the Server ==

The TMWAthena is in fact 3 servers:
* '''tmwa-login''' which manages accounts and connection to char server.
* '''tmwa-char''' which manages characters and connects them to the map server.
* '''tmwa-map''' which manages game content (maps, monsters, items, scripts...) and their interaction with characters

* Start the servers: Open a terminal and run all the local servers. To stop them, either close the terminal or type control-C.
cd ~/tmwAthena/tmwa-server-data/
./run-all
* In a new terminal, Launch '''tmwa-admin''' the administration tool, add yourself as an user and make yourself a GM:
cd ~/tmwAthena/tmwa-server-data/login
tmwa-admin
add <username> M <password>
gm <username> 99

'''Note''' : Be sure that you are running tmwa-admin from within the "login/" directory. Check that the config files are correct: the connection port should be 6901 for tmwa's configuration, not 6900, which is the hard-coded default.

'''See also:''' [[GM Commands]]

== Connecting ==
# Open a command line terminal and run your client pointing to your client data and your local server :
manaplus --server localhost --port 6901 -u -d ~/tmwAthena/tmwa-server-data/client-data

If all went well, you are now ready to test new content and participate with development.

== develop new content==
'''You are now free to do some changes, first close the client and your servers.'''

'''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.'''''
* Make your modifications (e.g. Change a map) and save them.
* Open a terminal.
cd ~/tmwAthena/tmwa-server-data/client-data''
git status''
git add [modified files]''
git commit''
git push'' {{note|push}}
cd ..
make maps ''(if you changed a map)''
git status
git add [modified files]
git add client-data (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''')
git commit
git push {{note|push}}
* Close the terminal.

{{note|push}} : a step for those with commit access to the remote repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested.

{{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories.

git format-patch -M -C origin/master
* pastebin the patch(es) and post for review at irc.freenode.net channel: #themanaworld-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part.

<span style="color:#FF0000"> '''Note :''' This is kind of outdated; with github it's often easier to do patches on branches there. see: '''[[Working With Git]]''' page</span>

'''You can also pull the data which has been modified.'''
* Open a terminal.
cd ~/tmwAthena/tmwa-server-data
git pull
* If you haven't installed the hook,
git submodule update --merge ''at toplevel (for client-data) and in client-data (for music)''
* Close the terminal.

'''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music.

=Making Content=
==Making Map Content==
See [[Mapping Tutorial]].
===Python Converter Tool===
After editing maps for the client, you need to generate the walkmaps and imports for the server. yhis can be done either by the '''[[Tiled]]''' application or by running the python script '''tmx_converter.py''' which is located in the '''tools''' folder of the '''Server Data''' folder.
(see [[Mapping Tutorial#Creating the WLK files]])
After that, commit and push the files that the converter edited. Note that, if you do not have push access to the main repository, you should let someone else update the submodule itself.

==Getting Art Content Into The Game==
* Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum].
* Work with the Art Director and collaborators on getting the art consistent.
* When finished, edit topic as [FND].
* Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT].
* XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT].
::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition.
* Project developer requests database entry reservations from a General Content Team developer.
::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory.
::* Map entry client data affected: .tmx files in the maps directory.
::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made.
::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory.
::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file.

===Handling General Content Team [REQ]s===
* General Content Team member adds a [REQ] topic to the graphics development forum.
* General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page.
* Art Director attempts to network with other artists to assign the art to an artist.

==Bit Masking==
Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing.

[http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script]

==Generating client updates==
* Shutdown all your servers.

* First we are going to check the config files to be sure the paths are correct.
cd ~/tmwAthena/tmwa-server-data/client-data/tools/
ls

Output:
add-git-attributes edit-all-to-export-tilesets.sh formatXML.sh list-tileset-order map-db.py minimap-render.py
adler32 edit-map-tileset-names.sh indent.xsl make-updates map-diff.py
End of output

* The easiest solution is to create a symbolic link to that directory
ln -s /var/www/tmwupdates ~/www/updates (your public www folder is /tmwupdates)

* You can Edit the make-updates file with gedit or nano or vi.
Search for the folowing lines:
output=~/www/updates
And change them to:
output=/var/www/tmwupdates (your public www folder is /tmwupdates)

*Save the file and get back in the terminal.
cd ~/tmwAthena/tmwa-server-data/login/conf
ls

Output:
ladmin_athena.conf lan_support.conf login_local.conf.example
ladmin_local.conf login_athena.conf
ladmin_local.conf.example login_local.conf
End of output

*Edit the login_local.conf with an editor and look for the following line:
update_host: http://updates.themanaworld.org/
*Change that line to:
update_host: http://127.0.0.1/tmwupdates/ (or use your external ip)
*Save the file and get back in the terminal.

* Open a terminal.
First we compile the adler32 tool to generate a hash.
cd ~/tmwAthena/tmwa-server-data/client-data/tools/adler32/
make

Output must be:
gcc -lz -o adler32 adler32.c

make install

* Now that we compiled the adler tool we can make us a update.
cd ~/tmwAthena/tmwa-server-data/
make updates

* Each time you want to make new updates
make sure you have a new commit then
cd ~/tmwAthena/tmwa-server-data/
make updates

Friendly Bots

2014-05-03T01:06:34Z

O11c: mark AuctionBot and Confused Tree] as inactive; update contact info for guild

Bots (robots) are characters that are managed by special clients that allow them to perform automatic operations. Generally speaking, '''bots are not allowed'''. Under special circumstances, it's possible (but not common) to run a friendly bot that is fun or useful to players. Friendly bots must be authorized by The Mana World Committee before they may connect to the server. Like TMW, friendly bots should be free software.

==List of active authorized bots==

* [[ManaMarket]]
:Stands in the [[General Store]] in [[Hurnscald]]. Allows players to purchase items added by other players for sale.
* [[guild]]
:Sits in the theatre. It is used as a substitute for the missing guild support. In order to use it you have to be invited to an existing [[Player Groups|player group or guild]] who has its own channel. When you want to create your own group, ask any GM for more information. This bot was brought to TMW courtesy of [[Player Groups#Phoenix Council|The Phoenix Council]] and written by Jero.

==List of inactive authorized bots==

* [[Tradebot]]
:Stood in the General Store in [[Hurnscald]]. It allowed players to purchase items added by other players for sale.
* [[AuctionBot]]
:Stood in the General Store in [[Hurnscald]]. It was designed to be as fair as possible, and offered nice options to players.
* [[Confused Tree]]
:Stood in Hurnscald responding to certain words or smilies with smilies or words.

Forks

2014-04-24T21:32:38Z

O11c: Remove some forks with dead links

The open source nature of The Mana World (TMW) allows anyone to use it as a base for creating their own game. A lot of teams have made use of this opportunity to develop their own games. Projects listed on this page '''do not''' work with the official client. Projects that '''work''' with the official client are listed in the [[Servers]].

==Active forks==
These are projects which are still in active development.

===Evol Online===
Evol Online is a free and open source 2D MMORPG set inside a fantasy world.
The main purpose of the games developers is to make the game evolve by adding new content regularly and making the game more complex and more enjoyable for the players.

* http://www.evolonline.org/

==Inactive forks==
These are projects which are unfortunately, not in active development anymore.

===Aethyra===
A fork of TMW based on the eAthena branch with most of its contents from the original TMW, and plenty of custom content.

* http://www.aethyraproject.org
===Sirus Online===
An eAthena-based branch formed by people frustrated with the management of Endless Online. It had a good start until most of its players and some developers prefer to play and develop the original TMW.

===Damasca===
A project very similar in scope to TMW, although programmed in C# instead of C++. When the development slowed down due to insufficient manpower, developers attempted to rescue the project by using TMWserv and the TMW client, which were already too developed. Unfortunately, it did not turn out so well.

* http://www.damasca.net

[[Category:Forks]]

Classic:TmwAthena Scripting Reference

2014-04-23T15:36:36Z

O11c: update list of commands to what the server currently has

This page is a reference for commands believed to work in the eAthena scripting language still used by tmwAthena.

A number of problematic commands have been removed from this list, but not all commands have been tested.

== Language Commands ==
These are command that are closely tied to the language itself.

=== goto ===
<pre>
goto L_1;
</pre>
Unconditionally jump to a label. Often used in an "if" body.

=== callsub ===
<pre>
callsub S_labelname, arguments...;
</pre>
Jump to the given label. When the "return" statement is executed, continue on the next line.

It is not known whether "arguments..." works, we use temporary variables instead.

It might also be possible to use this as a function, if the form of return with a value is used, but we use temporary variables instead.

=== callfunc ===
<pre>
callfunc "function_name", arguments...;
</pre>
Jump to the given function script. When the "return" statement is executed, continue on the next line of this script.

It is not known whether "arguments..." works, we use temporary variables instead.

It might also be possible to use this as a function, if the form of return with a value is used, but we use temporary variables instead.

"return" is broken if this is used from within an if(). If you need a conditional callfunc, first goto a label.

=== return ===
<pre>
return;
return expr;
</pre>
Return from this script or sublabel to the calling function.

It is unknown what happens if this is used from the top-level script, use "close" or "end" instead.

We use temporary variables instead of the form that returns an expression.

=== set ===
<pre>
set variable, expression;
</pre>
Very common command, to set variables.

=== setarray ===
<pre>
setarray arrayvariable, val1, val2, ...;
</pre>
Set elements of an array. Previous elements are not cleared. At most 128 elements can be assigned.

It is currently possible, but deprecated, to specify a (zero-based) array index to start at the given part of an array. It's pretty amazing that that code works anyway.

Remember that there are no permanent arrays, only temporary.

=== cleararray ===
<pre>
cleararray variable, value, count;
</pre>
Fill an array with "count" copies of "value".

=== getarraysize ===
<pre>
getarraysize variable;
</pre>
Get the size of an array.

The size of an array is simply one more than the index of the last nonzero integer or nonempty string.

WARNING: most functions that set an array do not bother to clear out high indices. You should almost always use an explicitly-provided size instead.

=== getelementofarray ===
<pre>
getelementofarray(arrayname, index_expr)
</pre>
This function is invoked internally by the arrayname[index_expr] syntax.

=== if ===
<pre>
if (condition) condition_command [conditional_command_args, ...];
</pre>
If condition is zero, do nothing. Else, evaluate the conditional command.

The only thing special about the if command is the lack of commas during parsing (from my reading this is only a warning?). During execution it is perfectly normal.

Note: you must not use a callsub or callfunc as conditional_command.

=== end ===
<pre>
end;
</pre>
Stop executing the script.

Don't use this if you have opened a dialog to the player, use "close" instead. Or, use "close2" and *then* "end".

=== debugmes ===
<pre>
debugmes "string"
</pre>
Print a message to stdout.

== Message Commands ==
These are commands for dialog or one-way chat with players.

=== mes ===
<pre>
mes "string";
</pre>
Display a line of text to the player. If a dialog box is not already open for the attached NPC, one will be created.

It is unknown if the client properly supports dialog with multiple NPCs simultaneously. Note that the server only allows each account one paused script at a time, so it probably wouldn't work anyway.

If you need to include the '''"''' character inside the message, (especially for dialogs) insert it as '''\"'''.
When doing several messages without a next; in between, there should be only a single \" at the beginning and the end each.

'''Example''':
mes "[Me Myself]";
mes "";
mes "(I clear my throat)"
mes "";
mes "\"I start talking here, and don't close the quotation marks, because I'm not yet done talking.";
mes "And start a new line, but without new quotation marks.";
mes "Here I stop talking, so I close the quotation marks.\"";
gives:
[Me Myself]

(I clear my throat)

"I start talking here, and don't close the quotation marks, because I'm not yet done talking.<br>
And start a new line, but without new quotation marks.<br>
Here I stop talking, so I close the quotation marks."

=== next ===
<pre>
next;
</pre>
Stop the script until the user presses "Next" in the dialog.

=== close ===
<pre>
close;
</pre>
Stop executing the script and give the user a "Close" button in the dialog.

=== close2 ===
<pre>
close2;
</pre>
Stop the script until the user presses the "Close" button in the dialog, then keep executing the script.

WARNING: unlike close, this command is a blocking command, the usual caveats apply.

=== menu ===
<pre>
menu
"option 1", L_1,
"option 2", L_2;
</pre>
Display a list of choices to the player, then branch to the specified label.

Additionally, the temporary variable "@menu" is set to the 1-based index of the choice.

The options must not contain the character ":", as the protocol uses it as a separator.

=== input ===
<pre>
input variable_name;
</pre>
Input an integer or string to the given variable, depending on whether has the '$' string postfix.

The implementation allows variable_name to be omitted if input is an integer, in case l14 is used. Don't use this.

=== announce ===
<pre>
announce "message", flag;
</pre>
Do a GM message.

If flag & 0xF == 0 forward it to all map servers.
If flag & 0x8, message is from the OID (NPC? usually?) rather than the RID (player).

If (flag & 0x7) == 1, send to all on map.
If (flag & 0x7) == 2, send to all in line of sight.
If (flag & 0x7) == 3, send to self only.
If (flag & 0x7) == anything else, send to all clients.

=== mapannounce ===
<pre>
mapannounce "mapname", "message", flag;
</pre>
Send an announcement to all players in map.

Only flag & 0x10 is interpreted, which does not work with the Mana client. So, flag must be 0.

=== message ===
<pre>
message "player", "message";
</pre>
Display (in chat) a message from the server to a single user.

=== npctalk ===
<pre>
npctalk "message";
</pre>
Make an NPC say something publicly.

Note: in many cases areaannounce is a better choice.

== Character Commands ==
These have to do with attributes of the player.

=== setlook ===
<pre>
setlook type, value;
</pre>
Set an aspect of a character's appearance. Used e.g. by the barber.

There are constant provided for the LOOK type, and for hair color and hair style.

=== heal ===
<pre>
heal hp, sp
</pre>
Increase or decrease the player's hp and sp.

=== itemheal ===
<pre>
itemheal "ii"
</pre>
Increase or decrease the player's hp and sp, for use in item scripts.

=== percentheal ===
<pre>
percentheal "ii"
</pre>
Increase or decrease the player's hp and sp, by percentage of max HP.

This is probably the best way to instakill the player.

=== readparam ===
<pre>
readparam(type[, "playername"])
</pre>
Return one of the core parameters of a player.

type is one of the bCamelCase constants, see db/const.txt

=== getcharid ===
<pre>
getcharid(type[ "playername"])
</pre>
Get an id of the attached (or given) player.

Type is:
0: char id
1: party id
2: guild id (deprecated)
3: account id

You usually want 3.

=== strcharinfo ===
<pre>
strcharinfo(num)
</pre>
Return string information about an account:
num==0: name
num==1: party name
num==2: guild name (deprecated)

=== sc_start ===
<pre>
sc_start type, tick, val1[, beingid];
</pre>
Apply a status effect to a player (or monster?).

type is one of the sc_* constants.

=== sc_end ===
<pre>
sc_end type;
</pre>
Immediately end status effect on current player.

=== sc_check ===
<pre>
sc_check(type)
</pre>
Whether a status effect is currently active.

=== resetstatus ===
<pre>
resetstatus;
</pre>

=== changesex ===
<pre>
changesex;
</pre>
Ask the login server (via the char server) to toggle this account's sex, then kick the player.

=== attachrid ===
<pre>
attachrid(id)
</pre>
Change the being associated with this script.

Return true if such a player is logged in.

=== detachrid ===
<pre>
detachrid;
</pre>
Detach the player associated with this script.

=== isloggedin ===
<pre>
isloggedin(id)
</pre>
Return true if the given ID is logged in.

Often you shouldn't use this, but attachrid(id) instead

=== marriage ===
<pre>
marriage("otherplayer")
</pre>
Marry the attached player to the other player.

Return 1 on success and 0 on failure.

=== divorce ===
<pre>
divorce()
</pre>
Divorce the attached player from their partner

Return 1 on success and 0 on failure.

=== getpartnerid2 ===
<pre>
getpartnerid2()
</pre>
Return the ID of the attached player's partner (0 is none).

=== getexp ===
<pre>
getexp base, job;
</pre>
Increase the types of experience.

=== getinventorylist ===
<pre>
getinventorylist;
</pre>
Fill in some arrays of useful information: "@inventorylist_id", "@inventorylist_amount", "@inventorylist_equip".

The arrays are not cleared between calls, use "@inventory_count".

=== getactivatedpoolskilllist ===
<pre>
getactivatedpoolskilllist;
</pre>
Same, but only activated pool skills.

=== getunactivatedpoolskilllist ===
<pre>
getunactivatedpoolskilllist;
</pre>
Same, but only unactivated pool skills.

=== poolskill ===
<pre>
poolskill skill_id;
</pre>
Activate a poolable skill.

=== unpoolskill ===
<pre>
unpoolskill skill_id;
</pre>
Deactivate a poolable skill.

=== misceffect ===
<pre>
misceffect type, "player_name";
misceffect type, being_id;
misceffect type;
</pre>
Display a miscellaneous effect on a being.

In the third form, it will use the OID if possible, and fallback to the RID.

=== getlook ===
<pre>
getlook(type)
</pre>
Return part of the player's appearance:
val==1: hair
val==2: weapon
val==3: bottom
val==4: middle
val==5: top
val==6: hair color
val==8: shield
val==9: shoes

On failure, return -1.

=== getsavepoint ===
<pre>
getsavepoint(type)
</pre>
type==0: Return savepoint map
type==1: Return savepoint x
type==2: Return savepoint y

This is believed to be the only function (other than callfunc and callsub of course) that returns a different type depending on its arguments.

=== shop ===
<pre>
shop "npcname";
</pre>
Close the script and open the given NPC's shop.

=== isdead ===
<pre>
isdead()
</pre>
Return 1 if the attached player is dead, else 0.

=== fakenpcname ===
<pre>
fakenpcname "name", "newname", new_sprite_id;
</pre>
Change the appearance of an NPC.

== Location Commands ==
These are commands that have to do with the location of players

=== warp ===
<pre>
warp "mapname", x, y;
</pre>
Warp the attached player to the given location. "mapname" may have the special values "Random", "SavePoint", and "Save" (case-sensitive), but x and y are still required.

=== isat ===
<pre>
isat("mapname", x, y)
</pre>
Return 1 if the attached player is at the given location, 0 otherwise.

=== areawarp ===
<pre>
areawarp "src_map", x0, y0, x1, y1, "dst_map", x, y;
</pre>
Warp all players in the given area to the given location.

=== getusers ===
<pre>
getusers(type)
</pre>
Count users.

If flag & 0x8, base on OID instead of RID.
If (flag & 0x7) == 0, return users on the map.
If (flag & 0x7) == 1, return users on the server.

=== getmapusers ===
<pre>
getmapusers("mapname")
</pre>
Count users on a given map.

=== getareausers ===
<pre>
getareausers("mapname", x0, y0, x1, y1, z)
</pre>
Count users in an area.
z can be set to 1 or be left out to check for players who are alive.

=== mapwarp ===
<pre>
mapwarp "src_map", "dst_map", x, y;
</pre>
Warp all players from source map to destination location.

=== npcwarp ===
<pre>
npcwarp x, y, "npcname";
</pre>
Move an NPC to a different location on the same map.

=== isin ===
<pre>
isin("mapname", x0, y0, x1, y1)
</pre>
Check if the player is in the area.

=== getx ===
<pre>
getx()
</pre>
Return attached player's x coordinate.

=== gety ===
<pre>
gety()
</pre>
Return attached player's y coordinate.

=== getmap ===
<pre>
getmap()
</pre>
Return attached player's current map.

== Item Commands ==
These have to do with items or inventory.

=== getitem ===
<pre>
getitem "itemname", count[, unused_argument[, playerid]];
getitem itemid, count[, unused_argument[, playerid]];
"ii**"
</pre>
Grant the attached player (or the given player) "count" copies of an item.

If itemname is unrecognized you get an iten (727) instead.

;Warning:
<pre>
delitem: only deletes one item if applied to not-stackable item (equipment)
getitem: gives item stacked, even if it's equipment
fix: use a loop and only delete/give one item at a time</pre>

=== makeitem ===
<pre>
makeitem "itemname", count, "mapname", x, y;
makeitem itemid, count, "mapname", x, y;
</pre>
Drop items on the ground.

The special "mapname" value "this" means the map of the attached player.

=== delitem ===
<pre>
delitem "itemname", count;
delitem itemid, count;
</pre>
Remove items from the attached player's inventory.

This command is buggy if the player does not have enough of the item. And if the item is not stackable, the command will delete only one of them, even if a higher number is specified.
;Warning:
<pre>
delitem: only deletes one item if applied to not-stackable item (equipment)
getitem: gives item stacked, even if it's equipment
fix: use a loop and only delete/give one item at a time</pre>

=== countitem ===
<pre>
countitem("itemname")
countitem(itemid)
</pre>
Return the number of the given item in the player's inventory.

=== checkweight ===
<pre>
checkweight("itemname", count)
checkweight(itemid, count)
</pre>
Return 0 if adding "count" of the item would put player above max weight, 1 if it would still be less than max weight.
Also returns 0 if item does not exist.

=== getequipid ===
<pre>
getequipid(equip_point)
</pre>
Return the ID of the item in the given equip slot.

equip_point is one of the equip_* constants

=== getequipname ===
<pre>
getequipname(equip_point)
</pre>
Return the name of the item in the given equip slot.

equip_point is one of the equip_* constants

=== statusup2 ===
<pre>
statusup2 bType, delta;
</pre>
Permanently increase or decrease a stat.

=== bonus ===
<pre>
bonus bType, delta
</pre>
Temporarily increase a stat. For use in item scripts only.

=== skill ===
<pre>
skill id, level[, flag = 1];
</pre>
Grant a skill.

flag==0: permanent skill
flag==1: temporary skill (item scripts only)

(Untested)

=== setskill ===
<pre>
setskill id, level;
</pre>
Grant a skill permanently.

=== getskilllv ===
<pre>
getskilllv(skill)
</pre>
Return the player's level of the given skill.

=== getgmlevel ===
<pre>
getgmlevel()
</pre>
Return the player's GM level.

=== getopt2 ===
<pre>
getopt2()
</pre>
Return the player's opt2 flags.

=== setopt2 ===
<pre>
setopt2 flags;
</pre>
Set the player's opt2 flags.

=== savepoint ===
<pre>
savepoint "mapname", x, y;
</pre>
Set the player's save point. Used e.g. by Soul Menhirs, and during the time travel quest.

=== openstorage ===
<pre>
openstorage;
</pre>
Open the player's storage.

=== getitemname ===
<pre>
getitemname("itemname")
getitemname(itemid)
</pre>
Return the name of the item, or "Unknown Item".

=== nude ===
<pre>
nude;
</pre>
Unequip all items.

=== unequipbyid ===
<pre>
unequipbyid slot_id;
</pre>
Unequip whatever is in the slot

=== getareadropitem ===
<pre>
getareadropitem("mapname", x0, y0, x1, y1, "itemname"[, delitems = 0]);
getareadropitem("mapname", x0, y0, x1, y1, itemid[, delitems = 0]);
</pre>
Count items on the floor in an area. If delitems, the items will be deleted as well.

== Common Functions ==
These are not mostly not related to the RPG or the scripting language.

=== rand ===
<pre>
rand(range)
rand(min, max)
</pre>
In the first form, return a random number between 0 (inclusive) and range (exclusive). Return 0 if range is not positive.
In the second form, return a random number between min and max, inclusive. Min and max may be swapped.

=== gettimetick ===
<pre>
gettimetick(type)
</pre>
Return one of the ticks

type==0 (or other): milliseconds since some point in time, wraps every 50 days.
type==1: time since midnight, UTC.
type==2: seconds since the epoch.

You should almost always use type 2.

=== gettime ===
<pre>
gettime(type)
</pre>
Get a component of the time (UTC).

1: second (0-59)
2: minute (0-59)
3: hour (0-23)
4: day of week (0-6)
5: day of month (1-31)
6: month (1-12)
7: year (1902-2038)

== Timers and Events ==
These have to do with transfering control in ways that are not immediately obvious.

The most common ones are initnpctimer or startnpctimer, stopnpctimer, and setnpctimer.

=== donpcevent ===
<pre>
donpcevent "event";
</pre>
Manually invoke an NPC event.

=== addtimer ===
<pre>
addtimer tick, "event";
</pre>
Invoke an NPC event after a delay, for the attached NPC.

This command does the same thing as areatimer, but for only the attached player.

=== initnpctimer ===
<pre>
initnpctimer;
</pre>
Set the NPC's attached timer to tick 0 and start it.

This is equivalent to setnpctimer, 0; startnpctimer;

=== stopnpctimer ===
<pre>
stopnpctimer;
</pre>
Stop the NPC's attached timer.

This DOES NOT do anything about the tick. But that's okay, you should normally be starting it with initnpctimer.

=== startnpctimer ===
<pre>
startnpctimer;
</pre>
Start the NPC's attached timer, without setting the tick.

=== setnpctimer ===
<pre>
setnpctimer tick;
</pre>
Set the NPC's timer to a specific tick. Generally, this is only useful for tick 0.

=== getnpctimer ===
<pre>
getnpctimer(type)
</pre>
Get the current tick of an NPC's timer.

type==0: timer event tick (like setnpctimer)
type==1: bool if it has a next timer.
type==2: timer amount

=== cmdothernpc ===
<pre>
cmdothernpc "npc", "Foo";
</pre>
Invoke ::OnCommandFoo

=== mobcount ===
<pre>
mobcount("mapname", "event")
</pre>
Count the remaining mobs from the spawn with the given event. Has an offset of -1.

=== areatimer ===
<pre>
areatimer "mapname", x0, y0, x1, y1, tick, "event";
</pre>
Add a PC event timer to all players in the area.

After "tick" milliseconds, the given NPC event will fire with each player as the RID.

== Unsorted Commands ==
These are commands that still need sorting, please edit this page, see talk page for category (and subcategory?) suggestions.

=== monster ===
<pre>
monster "mapname", x, y, "string", class, count[, "event"];
</pre>
Spawn monsters at a point. If you define an OnDead event using a trigger area then the event is shot only inside that area, hence the event is ignored when the monster is killed outside the trigger area.

=== areamonster ===
<pre>
areamonster "mapname", x0, y0, x1, y1, "string", class, count[, "event"];
</pre>
Spawn monsters in an area. If you define an OnDead event using a trigger area then the event is shot only inside that area, hence the event is ignored when the monster is killed outside the trigger area.

=== killmonster ===
<pre>
killmonster "mapname", "event";
</pre>
Kill monsters on a map.

Unless it is "All", "event" must match the one used at spawn time.

If "All" is given, this function properly preserves permanently respawning monsters.

=== killmonsterall ===
<pre>
killmonsterall "mapname";
</pre>
Kill all monsters unconditionally.

This command might prevent monsters from respawning. Instead use "killmonster" with "event" == "All".

=== enablenpc ===
<pre>
enablenpc "name";
</pre>
Enable an NPC.

=== disablenpc ===
<pre>
disablenpc "name";
</pre>
Disable an NPC.

=== setmapflag ===
<pre>
setmapflag "mapname", flag;
</pre>
Set an arbitrary mapflag.

=== removemapflag ===
<pre>
removemapflag "mapname", flag;
</pre>
Unset an arbitrary mapflag.

=== getmapflag ===
<pre>
getmapflag("mapname", flag);
</pre>
Check an arbitrary mapflag.

=== pvpon ===
<pre>
pvpon "mapname";
</pre>
Allow PvP on a map.

=== pvpoff ===
<pre>
pvpoff "mapname";
</pre>
Deny PvP on a map.

=== emotion ===
<pre>
emotion emote_index;
</pre>
Show a smiley above the OID.

=== getspellinvocation ===
<pre>
getspellinvocation("spell-identifier")
</pre>
Return the #invocation used for a spell, or "...".

=== specialeffect ===
<pre>
specialeffect type;
</pre>
Display a special effect on the OID.

Same as "misceffect", but does not fallback when there is no OID.

=== specialeffect2 ===
<pre>
specialeffect2 type;
</pre>
Same as "misceffect", but works when there is an OID.

=== gmcommand ===
<pre>
gmcommand "@command maybe with arguments";
</pre>
Run a GM command, at level 99.

== Undocumented Commands ==
pow (deprecated), bonus2, mapexit

MediaWiki:Website-url

2014-04-22T22:36:56Z

O11c: https

https://www.themanaworld.org/

MediaWiki:Sidebar

2014-04-22T22:22:37Z

O11c:

User talk:Evets

2014-04-22T17:32:03Z

O11c: Welcome!

'''Welcome to ''TheManaWorld''!'''
We hope you will contribute much and well.
You will probably want to read the [[Help:Contents|help pages]].
Again, welcome and have fun! [[User_talk:o11c|o]][[User:o11c|11]][[Special:Contributions/o11c|c]] 17:32, 22 April 2014 (UTC)

User:Evets

2014-04-22T17:32:02Z

O11c: Creating user page for new user.

I enjoyed playing on The Mana World, and I have an interest in improving upon the project via programming, suggestions, bug reports, editing the wiki, or otherwise. I've worked on other personal projects before, but not any relatively large (more than a couple of friends) projects.
Aside from programming, I'm also experienced in web development, and I'm a dedicated Linux user.

Development:How to Develop

2014-04-12T21:30:40Z

O11c: Add Fedora deps

We're using Git as version control system for our source files and content. Have a look at our [[Working With Git|Tutorial]] about how to use Git.

=Set Up=
This is a how to help content development for official server (tmwAthena) using Ubuntu and the Mana+ client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwa-client-data), server-data (tmwa-server-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting.

==Install Dependencies==
In addition to the basic build tools (GCC, Make, headers, ...), [http://www.gnu.org/software/bison/ '''Bison'''], and [http://sourceforge.net/projects/flex/ '''Flex'''] are needed.

''' [https://www.debian.org/ Debian] derivates (including [http://www.ubuntu.com/ Ubuntu])'''
* Open a terminal.
sudo apt-get install g++ flex bison python make realpath git

''' [https://fedoraproject.org/ Fedora] derivates'''
* Open a terminal.
sudo yum install gcc-c++ flex bison make git

Note that you must have gcc 4.6 or later. Any modern distro will have this version, but "stable" distros with very long release cycles, such as Red Hat Enterprise Linux, might not.

==Set Up Own Server==
'''Here are the steps to use when creating a new local testing server.'''
* Open a terminal.
mkdir ~/tmwAthena
cd ~/tmwAthena/
git clone --recursive git://github.com/themanaworld/tmwa.git
git clone --recursive git://github.com/themanaworld/tmwa-server-data.git
cd tmwa/
./configure --user # ''(Assuming ~/bin is in your PATH if not use ./configure)''
make
make install
git config --global url.git@github.com:.pushInsteadOf git://github.com ''{{ref|push}} {{ref|once}}''
cd ../tmwa-server-data
* Preferably, add the update hooks.
ln -s ../../git/hooks/post-merge .git/hooks/
ln -s ../../../../git/hooks/post-merge .git/modules/client-data/hooks/ # ''(git 1.7.8 or newer)''
ln -s ../../../git/hooks/post-merge client-data/.git/hooks/ # ''(git 1.7.7 or older)''
make conf
cd client-data
git checkout master
cd music
git checkout master

==Hosting Updates==
TMW makes it easy to generate delta zips out of a repository, once it is initially set up.

It will put them in ~/www/updates/, which may be a symlink to wherever your web server is really serving. Setting up a webserver is not covered here.

Once everything is set up, just run 'make updates' from the server-data dir every time client-data changes. It will do nothing if appropriate, generate complete zips the first time, and incremental zips afterwards.

Some notes:
* You must put news.txt and skeleton resources.xml file (and maybe an empty resources2.txt) in ~/www/updates/ first.
* Music updates are never added; they should be in the skeleton and updated manually if needed.
* You definitely want to run one of the analyzer scripts frequently, and remove the old updates.

==Updating the Server==

== Running and Administrating the Server ==

The TMWAthena is in fact 3 servers:
* '''tmwa-login''' which manages accounts and connection to char server.
* '''tmwa-char''' which manages characters and connects them to the map server.
* '''tmwa-map''' which manages game content (maps, monsters, items, scripts...) and their interaction with characters

* Start the servers: Open a terminal and run all the local servers. To stop them, either close the terminal or type control-C.
cd ~/tmwAthena/tmwa-server-data/
./run-all
* In a new terminal, Launch '''tmwa-admin''' the administration tool, add yourself as an user and make yourself a GM:
cd ~/tmwAthena/tmwa-server-data/login
tmwa-admin
add <username> M <password>
gm <username> 99

'''Note''' : Be sure that you are running tmwa-admin from within the "login/" directory. Check that the config files are correct: the connection port should be 6901 for tmwa's configuration, not 6900, which is the hard-coded default.

'''See also:''' [[GM Commands]]

== Connecting ==
# Open a command line terminal and run your client pointing to your client data and your local server :
manaplus --server localhost --port 6901 -u -d ~/tmwAthena/tmwa-server-data/client-data

If all went well, you are now ready to test new content and participate with development.

== develop new content==
'''You are now free to do some changes, first close the client and your servers.'''

'''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.'''''
* Make your modifications (e.g. Change a map) and save them.
* Open a terminal.
cd ~/tmwAthena/tmwa-server-data/client-data''
git status''
git add [modified files]''
git commit''
git push'' {{note|push}}
cd ..
make maps ''(if you changed a map)''
git status
git add [modified files]
git add client-data (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''')
git commit
git push {{note|push}}
* Close the terminal.

{{note|push}} : a step for those with commit access to the remote repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested.

{{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories.

git format-patch -M -C origin/master
* pastebin the patch(es) and post for review at irc.freenode.net channel: #themanaworld-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part.

<span style="color:#FF0000"> '''Note :''' This is kind of outdated; with github it's often easier to do patches on branches there. see: '''[[Working With Git]]''' page</span>

'''You can also pull the data which has been modified.'''
* Open a terminal.
cd ~/tmwAthena/tmwa-server-data
git pull
* If you haven't installed the hook,
git submodule update --merge ''at toplevel (for client-data) and in client-data (for music)''
* Close the terminal.

'''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music.

=Making Content=
==Making Map Content==
See [[Mapping Tutorial]].
===Python Converter Tool===
After editing maps for the client, you need to generate the walkmaps and imports for the server. yhis can be done either by the '''[[Tiled]]''' application or by running the python script '''tmx_converter.py''' which is located in the '''tools''' folder of the '''Server Data''' folder.
(see [[Mapping Tutorial#Creating the WLK files]])
After that, commit and push the files that the converter edited. Note that, if you do not have push access to the main repository, you should let someone else update the submodule itself.

==Getting Art Content Into The Game==
* Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum].
* Work with the Art Director and collaborators on getting the art consistent.
* When finished, edit topic as [FND].
* Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT].
* XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT].
::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition.
* Project developer requests database entry reservations from a General Content Team developer.
::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory.
::* Map entry client data affected: .tmx files in the maps directory.
::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made.
::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory.
::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file.

===Handling General Content Team [REQ]s===
* General Content Team member adds a [REQ] topic to the graphics development forum.
* General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page.
* Art Director attempts to network with other artists to assign the art to an artist.

==Bit Masking==
Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing.

[http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script]

==Generating client updates==
* Shutdown all your servers.

* First we are going to check the config files to be sure the paths are correct.
cd ~/tmwAthena/tmwa-server-data/client-data/tools/
ls

Output:
add-git-attributes edit-all-to-export-tilesets.sh formatXML.sh list-tileset-order map-db.py minimap-render.py
adler32 edit-map-tileset-names.sh indent.xsl make-updates map-diff.py
End of output

* The easiest solution is to create a symbolic link to that directory
ln -s /var/www/tmwupdates ~/www/updates (your public www folder is /tmwupdates)

* You can Edit the make-updates file with gedit or nano or vi.
Search for the folowing lines:
output=~/www/updates
And change them to:
output=/var/www/tmwupdates (your public www folder is /tmwupdates)

*Save the file and get back in the terminal.
cd ~/tmwAthena/tmwa-server-data/login/conf
ls

Output:
ladmin_athena.conf lan_support.conf login_local.conf.example
ladmin_local.conf login_athena.conf
ladmin_local.conf.example login_local.conf
End of output

*Edit the login_local.conf with an editor and look for the following line:
update_host: http://updates.themanaworld.org/
*Change that line to:
update_host: http://127.0.0.1/tmwupdates/ (or use your external ip)
*Save the file and get back in the terminal.

* Open a terminal.
First we compile the adler32 tool to generate a hash.
cd ~/tmwAthena/tmwa-server-data/client-data/tools/adler32/
make

Output must be:
gcc -lz -o adler32 adler32.c

make install

* Now that we compiled the adler tool we can make us a update.
cd ~/tmwAthena/tmwa-server-data/
make updates

* Each time you want to make new updates
make sure you have a new commit then
cd ~/tmwAthena/tmwa-server-data/
make updates

Classic:TmwAthena Scripting Standards

2014-04-10T20:38:37Z

O11c: /* NPC Dialogs */ fix formatting - stupid leading whitespace

This is an attempt to standardize the eAthena coding. Any suggestions are welcome to be posted on the discussion page before editing.
=Code Formatting=
== Indentation ==
* Code is indented with four spaces.
* Code in the same block should have the same indentation.
* Labels have no indentation.
* Menu options are on their own lines and are indented further.
Example:
menu
"Yes.", L_Yes,
"No.", L_No;
* When using an if-statement, there should be a line break after the condition and the conditional command should be indented further. An exception to this is a series of if-statements at the beginning of a major code block which use gotos to jump to the correct position in the script. In this case the goto should be in the same line as the if-statement.
Example:
// if-statement and conditional command in the same line, gotos aligned
if (@quest >= 3) goto L_Done;
if (@quest == 2) goto L_Progress;
if (@quest == 1) goto L_Question;

// conditional command in the next line and indented further
if (BaseLevel < 40)
set @cost, 100;

== Whitespaces==
In many places whitespaces can increase readability. Examples are
* When concatenating text and variables:
mes "\"Hello " + strcharinfo(0) + "!\"";
instead of
mes "\"Hello "+strcharinfo(0)+"!\"";
* When assigning values to variables:
set @var, 3;
instead of
set @var,3;
* In menus:
menu
"Yes.", L_Yes,
"No.", L_No;
instead of
menu
"Yes.",L_Yes,
"No.",L_No;

== Code Blocks ==
* Code blocks should be separated from the others in a dinstinct way: insert a blank line between code blocks.
* Individual blocks should be together No blank lines within a block.
* The opening brackets should be on a new line, not at the end of the parent line; the closing ones should be in a line of their own.
* A 'menu' must not be in the body of an if statement. Instead, goto a new block for the menu, or negate the logic and goto somewhere else if the label should not be shown.
* The 'next' command goes at the end of a block (before a goto), never at the beginning. Make sure 'next' is never followed by something that leads to a 'close' without intervening text.

==Labels and Subfunctions==
* Labels should be named in this way: L_CamelCase
* Subfunctions should be named in this way: S_CamelCase
* Labels should always start with L_, except those that act as a subfunction, which should start with S_
* Newline before every label
* No newline after a label
* There must not be a fallthrough or goto to a subfunction label.
* A subfunction label must not goto a normal label. It may, however, goto another label that is specific to that subfunction, and eventually reach a return.

* Many scripts use a label L_Close, which is used to reset temporary player variables to 0, and then ends the scripts with the close; command. If you use a label with that purpose, it should be named L_Close for consistency. (There are older scripts which use different names, e.g. L_end, but new ones should go with L_Close.)

==Comments==
At the beginning of a script file there should be documented
* who is the author
* the purpose of the script
* which variables are used and what's their purpose
* any additional information that can help to understand the script
Example:
// Author: devxy
// This file contains the NPC John, who is part of the Example quest.
// Quest states are saved in Quest_Example.
// State 1: started the quest
// State 2: did the next step
[...]

Within the script there should be comments if there are parts which might be difficult to understand.

In some of the older scripts there are boxed comments used like this:
//#################################################################################
//# NPC John - By Smith #
//# #
//# ... #
//#################################################################################
Don't use them in new scripts.

== NPC Dialogs ==
In the following example our NPC dialog formatting guidelines are explained.
mes "[Example NPC Olaf]";
mes "\"When I start speaking my name is put in square brackets, and my spoken text here is in quotation marks.\"";
next;
mes "\"The next between my previous line and this one interrupted my speaking, so I started with new quotation marks.";
mes "But didn't close them in the same line, because I continue to speak here.";
mes "A new message command can be used to have a line break in the dialog without interrupting the speaking.";
mes "At the end I close the quotation marks again.\"";
next;
mes "Olaf stops speaking and scratches his head. This is a descriptive text, so it isn't put into quotation marks.";
next;
mes "[Example NPC Olaf]";
mes "\"Now that I start speaking again, I need my name in brackets again before my actual text starts, because something else happened in between.";
mes "It isn't that difficult, right?\"";
menu
"I agree.", L_Agree,
"(Leave.)", L_Close;

L_Agree:
mes "[Example NPC Olaf]";
mes "\"It's the same after there was a menu with the player saying or doing something, again I put my name into sqaure brackets before starting to speak.\"";
next;
mes "\"In the menu you can see that something the player says isn't put into quotation marks, but just as plain text.";
mes "And an action the player takes is put into usual brackets.\"";
goto L_Close;

L_Close:
close;

=Variables=
==Document Variables==
in every file, document every variable as one of:

* # account variable (prefix #) (note that there are also ## variable which didn't work in the stable version of the server)
* permanent player variable (no prefix)
* @ temporary player variable (prefix @) - used after the script close;s or end;s.
* @ dynamic player variable (prefix @) - passed into or out of callsub or callfunc
* @ lexical (local) player variable (prefix @) - used only within the function (scripthelp.txt documents that ".@" means this but I don't know if that works)
* @ local constant (prefix @) - not dependent on the player, used only within the function. e.g. lots of @QUEST_FOO_{SHIFT,MASK}
* $ global permanent variable (prefix $) (I'm not sure if we have any of these right now)
* $ npc permanent variable (prefix $) same as above but only used by one NPC
* $ global temporary variable (prefix $@)
* $@ npc temporary variable (prefix $@) same as above but only used by one NPC, scripthelp.txt mentions prefix "." but I don't know if that works
* special variable (in db/const.txt with a 1 following)
* global constant (in const.txt)

'''If we use a consistent method of documenting these, we can then generate a list of all variables by type.'''

==Variables initialization==
Check for troublesome arrays:
A troublesome array is defined as an array that is not
*initialized all at once
*initialized by appending elements to the end, for use in a menu
Nothing needs to be done, merely document them. I want this information at hand when I design the new scripting language to minimize conversion pains.
I wouldn't be surprised if there were no troublesome arrays at all. If there are only a couple it might be worth refactoring the code to remove them, but that might be a high-level decision which is beyond the scope of this proposal.

Set dynamic and local @variables to 0 before close;

==Naming Variables==

==Using as little variables as you need==
So there are some quests, which require lots of variables.
Think of monster oil quest, Oric and Warum quest etc.

This can often be done by bitmasking:
One variable has 32 bits. So a variabe can store 2^32 different numbers: 4294967296

But sometimes you only need numbers from 0 to 15, but more of these variables.
but numbers in range 0 to 15 can be stored in 4 bits ( 2^4 = 16 different numbers)

Here is an example how to use bitmasking:
[[Media:Tester.txt]]
== Defining Map Objects ==

These sections describe how to define map objects.

=== Warp Definitions ===
<span style="color:OrangeRed">'''Shouldn't be done manually.'''</span>
Warps are what move players between maps. They can also be used to move players around a single map, if needed. Warps are defined like this:

map1,startX,startY|warp|name|width,height,map2,endX,endY

Key:
{|
|map1 ||the starting map
|-
|startX||the x-coordinate of the starting warp tile
|-
|startY||the y-coordinate of the starting warp tile
|-
|name ||the name of the warp, unused but must be defined
|-
|width ||the width of the warp
|-
|height||the height of the warp
|-
|map2 ||the ending map
|-
|endX ||the x-coordinate of the tile the player will end up on
|-
|endY ||the y-coordinate of the tile the player will end up on
|}

Width and height are described in detail here: [[Dev:TmwAthena Scripting Standards/Warp Details|Warp Details]].

=== Monster Definitions ===
<span style="color:OrangeRed">'''Shouldn't be done manually.'''</span>
Monsters are defined like this:

<map name>,<x>,<y>,<width>,<height>|monster|<name>|<mobID>,<count>,<spawn1>,<spawn2>,{<eventcode>}

{|
|map name ||the map the monsters should appear on
|-
|x ||the x-coordinate of the spawn tile
|-
|y ||the y-coordinate of the spawn tile
|-
|width ||the tile width of the spawn area
|-
|height ||the tile height of the spawn area
|-
|name ||the name of the mob, unused but must be defined. '''DO NOT''' use the keywords such as "spawn" in this name to avoid conflict with other game systems (magic for example)
|-
|mobID ||the mob identifier of the desired monster (in the monster db)the number to spawn
|-
|count ||the number to spawn
|-
|spawn1 ||the minimum delay between successive spawns (per individual)
|-
|spawn2 ||the minimum delay between death and respawn (per individual)
|-
|eventcode ||the script event to fire upon death
|}
A detailed description of position and area can be found here: [[Dev:TmwAthena Scripting Standards/Mob Details|Mob Details]].

=== NPC Definitions ===
<map name>,<x>,<y>,<facing>|script|<Name>|<spriteID>,<nowiki>{<code>}</nowiki>
<map name>,<x>,<y>,<facing>|script|<Name>|<spriteID>,<triggerX>,<triggerY>,<nowiki>{<code>}</nowiki>

{|
|map name ||the map the monsters should appear on
|-
|x ||the x-coordinate of the spawn tile
|-
|y ||the y-coordinate of the spawn tile
|-
|facing ||Direction the NPC faces to. '''It must be set to 0''' in TMW
|-
|height ||the tile height of the spawn area
|-
|Name ||the name of the NPC
|-
|spriteID ||the mob identifier of the desired NPC. Sprite ID
|-
|triggerX ||
|-
|triggerY ||
|-
|eventcode ||the script event to fire upon death
|}
* Server side :
::NPC definitions (script) are usually stored as : <br/>(tmwa-server-data/)world/map/npc/<map name>/<NPC Name>.txt or in the file :<br/>(tmwa-server-data/)world/map/npc/<map name>/npc.txt
* Client side :
::The NPC is associated with a sprite (the image that will appear in the game), and a XML file which tells the client some display parameters.<br/>(tmwa-client-data/)graphics/sprites/npcs/npc-<Name>.png<br/>(tmwa-client-data/)graphics/sprites/npcs/npc-<Name>.xml<br/>The NPC spriteID is linked to graphic files and XML in the file : (tmwa-client-data/)npcs.xml



== Script Functions ==
function|script|<function name>|<nowiki>{<code>}</nowiki>
Actual script functions are stored or imported in the files : (tmwa-server-data/)world/map/npc/functions/<function name>.txt, regardless rhey are called from a Map, NPC, Mob or item.

==Script Loading==
The main script import file is:[https://github.com/themanaworld/tmwa-server-data/blob/master/world/map/npc/scripts.conf (tmwa-server-data/)world/map/npc/scripts.conf] <br/>
It loads [https://github.com/themanaworld/tmwa-server-data/blob/master/world/map/npc/_import.txt (tmwa-server-data/)world/map/npc/_import.txt] which imports all NPC scripts wich are stored under the respective map name folders, usually under NPC name.

=Examples=
== Open a chest and get reward ==
An example is given by a quest to get a key for a chest (in fact 3 keys):

{| style="width:850px;" border=0 cellspacing="10"
|-valign="Top"
|<pre>
// A treasure chest. You need three keys to open it.
//
// TMW_Quest (document variable here)
//

002-4.gat,93,37,0|script|Treasure|111,
{
if (TMW_Quest >= 38) goto L_Finished;

mes "There is a chest here.";
mes "Do you want to try to open it?";
next;
menu
"Yes.", L_Yes,
"No.", L_Close;

L_Close:
close;

L_Yes:
if(countitem("TreasureKey") < 3)
goto L_Not_Enough;
getinventorylist;
if (@inventorylist_count == 100 && countitem("TreasureKey") > 3)
goto L_TooMany;
mes "You opened the chest and found a short bow!";
delitem "TreasureKey", 3;
getitem "ShortBow", 1;
set TMW_Quest, 38;
close;

L_Not_Enough:
mes "It seems that you do not have the right key for this chest yet...";
close;

L_Finished:
mes "You have already opened this chest.";
close;

L_TooMany:
mes "You do not have enough room to loot this chest. Maybe you should try again later.";
close;
}
</pre>
|}
This script starts with describing the NPC (the chest, NPC sprite 111) and its location (map 002-4 X=93, Y=37, in tiles from top left of the map). Then follows what happens on activation:
First, the variable ''"TMW_Quest"'' is checked to know if the player already accomplished the quest <span style="color:OrangeRed">'''(the variable should be documented)'''</span>, If he has the script continues at label ''L_Finished'', the player is reminded fe alredy accomplished the task and script finishes, if not the scrip continues. A message is shown (mes), then an option dialog (menu) is displayed with two possible answers : "Yes." or "No.". If the player answers "No." the script stops (close;); if he answers "Yes." the script continues at label ''L_Yes''. Now player is checked to know if he has at least 3 keys, if not script branches to label ''L_Not_Enough'' tells the player he "has not the right key" and script closes. If he has keys enough, his inventory list is retrieved by the built-in function "getinventorylist" and it's content is checked to know if the player will have room enough to store the reward after the 3 keys use. If not, script goes to label ''L_TooMany'' and script close after a warning message, If yes 3 keys are deleted in player's inventory, he gets the reward: a Short Bow and the variable TMW_Quest is set to 38.

For more examples of the current system, check out the current scripts in use by the server. Beware though, this could affect your enjoyment of the game as it does spoil some of the mystery. Here's a link to git so you can view them in your browser:

https://github.com/themanaworld/tmwa-server-data/tree/master/world/map/npc

Note that anything said by an NPC should be put in double quotes ("). You can do that like this: "'''\"'''Hello!'''\"''' she said."

=References=
* [[Dev:TmwAthena Scripting Basics]]
* [[Dev:TmwAthena Scripting Reference]]
* [http://forums.themanaworld.org/viewtopic.php?f=13&t=13653 script cleanup/scripting standards proposal]

Classic:TmwAthena Scripting Standards

2014-04-10T20:37:38Z

O11c: /* NPC Dialogs */ remove implicit "next" label

Classic:TmwAthena Scripting Standards

2014-04-10T20:36:57Z

O11c: /* Open a chest and get reward */ remove implicit "next" label

This is an attempt to standardize the eAthena coding. Any suggestions are welcome to be posted on the discussion page before editing.
=Code Formatting=
== Indentation ==
* Code is indented with four spaces.
* Code in the same block should have the same indentation.
* Labels have no indentation.
* Menu options are on their own lines and are indented further.
Example:
menu
"Yes.", L_Yes,
"No.", L_No;
* When using an if-statement, there should be a line break after the condition and the conditional command should be indented further. An exception to this is a series of if-statements at the beginning of a major code block which use gotos to jump to the correct position in the script. In this case the goto should be in the same line as the if-statement.
Example:
// if-statement and conditional command in the same line, gotos aligned
if (@quest >= 3) goto L_Done;
if (@quest == 2) goto L_Progress;
if (@quest == 1) goto L_Question;

// conditional command in the next line and indented further
if (BaseLevel < 40)
set @cost, 100;

== Whitespaces==
In many places whitespaces can increase readability. Examples are
* When concatenating text and variables:
mes "\"Hello " + strcharinfo(0) + "!\"";
instead of
mes "\"Hello "+strcharinfo(0)+"!\"";
* When assigning values to variables:
set @var, 3;
instead of
set @var,3;
* In menus:
menu
"Yes.", L_Yes,
"No.", L_No;
instead of
menu
"Yes.",L_Yes,
"No.",L_No;

== Code Blocks ==
* Code blocks should be separated from the others in a dinstinct way: insert a blank line between code blocks.
* Individual blocks should be together No blank lines within a block.
* The opening brackets should be on a new line, not at the end of the parent line; the closing ones should be in a line of their own.
* A 'menu' must not be in the body of an if statement. Instead, goto a new block for the menu, or negate the logic and goto somewhere else if the label should not be shown.
* The 'next' command goes at the end of a block (before a goto), never at the beginning. Make sure 'next' is never followed by something that leads to a 'close' without intervening text.

==Labels and Subfunctions==
* Labels should be named in this way: L_CamelCase
* Subfunctions should be named in this way: S_CamelCase
* Labels should always start with L_, except those that act as a subfunction, which should start with S_
* Newline before every label
* No newline after a label
* There must not be a fallthrough or goto to a subfunction label.
* A subfunction label must not goto a normal label. It may, however, goto another label that is specific to that subfunction, and eventually reach a return.

* Many scripts use a label L_Close, which is used to reset temporary player variables to 0, and then ends the scripts with the close; command. If you use a label with that purpose, it should be named L_Close for consistency. (There are older scripts which use different names, e.g. L_end, but new ones should go with L_Close.)

==Comments==
At the beginning of a script file there should be documented
* who is the author
* the purpose of the script
* which variables are used and what's their purpose
* any additional information that can help to understand the script
Example:
// Author: devxy
// This file contains the NPC John, who is part of the Example quest.
// Quest states are saved in Quest_Example.
// State 1: started the quest
// State 2: did the next step
[...]

Within the script there should be comments if there are parts which might be difficult to understand.

In some of the older scripts there are boxed comments used like this:
//#################################################################################
//# NPC John - By Smith #
//# #
//# ... #
//#################################################################################
Don't use them in new scripts.

== NPC Dialogs ==
In the following example our NPC dialog formatting guidelines are explained.
mes "[Example NPC Olaf]";
mes "\"When I start speaking my name is put in square brackets, and my spoken text here is in quotation marks.\"";
next;
mes "\"The next between my previous line and this one interrupted my speaking, so I started with new quotation marks.";
mes "But didn't close them in the same line, because I continue to speak here.";
mes "A new message command can be used to have a line break in the dialog without interrupting the speaking.";
mes "At the end I close the quotation marks again.\"";
next;
mes "Olaf stops speaking and scratches his head. This is a descriptive text, so it isn't put into quotation marks.";
next;
mes "[Example NPC Olaf]";
mes "\"Now that I start speaking again, I need my name in brackets again before my actual text starts, because something else happened in between.";
mes "It isn't that difficult, right?\"";
menu
"I agree.", -,
"(Leave.)", L_Close;
mes "[Example NPC Olaf]";
mes "\"It's the same after there was a menu with the player saying or doing something, again I put my name into sqaure brackets before starting to speak.\"";
next;
mes "\"In the menu you can see that something the player says isn't put into quotation marks, but just as plain text.";
mes "And an action the player takes is put into usual brackets.\"";
goto L_Close;

L_Close:
close;

=Variables=
==Document Variables==
in every file, document every variable as one of:

* # account variable (prefix #) (note that there are also ## variable which didn't work in the stable version of the server)
* permanent player variable (no prefix)
* @ temporary player variable (prefix @) - used after the script close;s or end;s.
* @ dynamic player variable (prefix @) - passed into or out of callsub or callfunc
* @ lexical (local) player variable (prefix @) - used only within the function (scripthelp.txt documents that ".@" means this but I don't know if that works)
* @ local constant (prefix @) - not dependent on the player, used only within the function. e.g. lots of @QUEST_FOO_{SHIFT,MASK}
* $ global permanent variable (prefix $) (I'm not sure if we have any of these right now)
* $ npc permanent variable (prefix $) same as above but only used by one NPC
* $ global temporary variable (prefix $@)
* $@ npc temporary variable (prefix $@) same as above but only used by one NPC, scripthelp.txt mentions prefix "." but I don't know if that works
* special variable (in db/const.txt with a 1 following)
* global constant (in const.txt)

'''If we use a consistent method of documenting these, we can then generate a list of all variables by type.'''

==Variables initialization==
Check for troublesome arrays:
A troublesome array is defined as an array that is not
*initialized all at once
*initialized by appending elements to the end, for use in a menu
Nothing needs to be done, merely document them. I want this information at hand when I design the new scripting language to minimize conversion pains.
I wouldn't be surprised if there were no troublesome arrays at all. If there are only a couple it might be worth refactoring the code to remove them, but that might be a high-level decision which is beyond the scope of this proposal.

Set dynamic and local @variables to 0 before close;

==Naming Variables==

==Using as little variables as you need==
So there are some quests, which require lots of variables.
Think of monster oil quest, Oric and Warum quest etc.

This can often be done by bitmasking:
One variable has 32 bits. So a variabe can store 2^32 different numbers: 4294967296

But sometimes you only need numbers from 0 to 15, but more of these variables.
but numbers in range 0 to 15 can be stored in 4 bits ( 2^4 = 16 different numbers)

Here is an example how to use bitmasking:
[[Media:Tester.txt]]
== Defining Map Objects ==

These sections describe how to define map objects.

=== Warp Definitions ===
<span style="color:OrangeRed">'''Shouldn't be done manually.'''</span>
Warps are what move players between maps. They can also be used to move players around a single map, if needed. Warps are defined like this:

map1,startX,startY|warp|name|width,height,map2,endX,endY

Key:
{|
|map1 ||the starting map
|-
|startX||the x-coordinate of the starting warp tile
|-
|startY||the y-coordinate of the starting warp tile
|-
|name ||the name of the warp, unused but must be defined
|-
|width ||the width of the warp
|-
|height||the height of the warp
|-
|map2 ||the ending map
|-
|endX ||the x-coordinate of the tile the player will end up on
|-
|endY ||the y-coordinate of the tile the player will end up on
|}

Width and height are described in detail here: [[Dev:TmwAthena Scripting Standards/Warp Details|Warp Details]].

=== Monster Definitions ===
<span style="color:OrangeRed">'''Shouldn't be done manually.'''</span>
Monsters are defined like this:

<map name>,<x>,<y>,<width>,<height>|monster|<name>|<mobID>,<count>,<spawn1>,<spawn2>,{<eventcode>}

{|
|map name ||the map the monsters should appear on
|-
|x ||the x-coordinate of the spawn tile
|-
|y ||the y-coordinate of the spawn tile
|-
|width ||the tile width of the spawn area
|-
|height ||the tile height of the spawn area
|-
|name ||the name of the mob, unused but must be defined. '''DO NOT''' use the keywords such as "spawn" in this name to avoid conflict with other game systems (magic for example)
|-
|mobID ||the mob identifier of the desired monster (in the monster db)the number to spawn
|-
|count ||the number to spawn
|-
|spawn1 ||the minimum delay between successive spawns (per individual)
|-
|spawn2 ||the minimum delay between death and respawn (per individual)
|-
|eventcode ||the script event to fire upon death
|}
A detailed description of position and area can be found here: [[Dev:TmwAthena Scripting Standards/Mob Details|Mob Details]].

=== NPC Definitions ===
<map name>,<x>,<y>,<facing>|script|<Name>|<spriteID>,<nowiki>{<code>}</nowiki>
<map name>,<x>,<y>,<facing>|script|<Name>|<spriteID>,<triggerX>,<triggerY>,<nowiki>{<code>}</nowiki>

{|
|map name ||the map the monsters should appear on
|-
|x ||the x-coordinate of the spawn tile
|-
|y ||the y-coordinate of the spawn tile
|-
|facing ||Direction the NPC faces to. '''It must be set to 0''' in TMW
|-
|height ||the tile height of the spawn area
|-
|Name ||the name of the NPC
|-
|spriteID ||the mob identifier of the desired NPC. Sprite ID
|-
|triggerX ||
|-
|triggerY ||
|-
|eventcode ||the script event to fire upon death
|}
* Server side :
::NPC definitions (script) are usually stored as : <br/>(tmwa-server-data/)world/map/npc/<map name>/<NPC Name>.txt or in the file :<br/>(tmwa-server-data/)world/map/npc/<map name>/npc.txt
* Client side :
::The NPC is associated with a sprite (the image that will appear in the game), and a XML file which tells the client some display parameters.<br/>(tmwa-client-data/)graphics/sprites/npcs/npc-<Name>.png<br/>(tmwa-client-data/)graphics/sprites/npcs/npc-<Name>.xml<br/>The NPC spriteID is linked to graphic files and XML in the file : (tmwa-client-data/)npcs.xml



== Script Functions ==
function|script|<function name>|<nowiki>{<code>}</nowiki>
Actual script functions are stored or imported in the files : (tmwa-server-data/)world/map/npc/functions/<function name>.txt, regardless rhey are called from a Map, NPC, Mob or item.

==Script Loading==
The main script import file is:[https://github.com/themanaworld/tmwa-server-data/blob/master/world/map/npc/scripts.conf (tmwa-server-data/)world/map/npc/scripts.conf] <br/>
It loads [https://github.com/themanaworld/tmwa-server-data/blob/master/world/map/npc/_import.txt (tmwa-server-data/)world/map/npc/_import.txt] which imports all NPC scripts wich are stored under the respective map name folders, usually under NPC name.

=Examples=
== Open a chest and get reward ==
An example is given by a quest to get a key for a chest (in fact 3 keys):

{| style="width:850px;" border=0 cellspacing="10"
|-valign="Top"
|<pre>
// A treasure chest. You need three keys to open it.
//
// TMW_Quest (document variable here)
//

002-4.gat,93,37,0|script|Treasure|111,
{
if (TMW_Quest >= 38) goto L_Finished;

mes "There is a chest here.";
mes "Do you want to try to open it?";
next;
menu
"Yes.", L_Yes,
"No.", L_Close;

L_Close:
close;

L_Yes:
if(countitem("TreasureKey") < 3)
goto L_Not_Enough;
getinventorylist;
if (@inventorylist_count == 100 && countitem("TreasureKey") > 3)
goto L_TooMany;
mes "You opened the chest and found a short bow!";
delitem "TreasureKey", 3;
getitem "ShortBow", 1;
set TMW_Quest, 38;
close;

L_Not_Enough:
mes "It seems that you do not have the right key for this chest yet...";
close;

L_Finished:
mes "You have already opened this chest.";
close;

L_TooMany:
mes "You do not have enough room to loot this chest. Maybe you should try again later.";
close;
}
</pre>
|}
This script starts with describing the NPC (the chest, NPC sprite 111) and its location (map 002-4 X=93, Y=37, in tiles from top left of the map). Then follows what happens on activation:
First, the variable ''"TMW_Quest"'' is checked to know if the player already accomplished the quest <span style="color:OrangeRed">'''(the variable should be documented)'''</span>, If he has the script continues at label ''L_Finished'', the player is reminded fe alredy accomplished the task and script finishes, if not the scrip continues. A message is shown (mes), then an option dialog (menu) is displayed with two possible answers : "Yes." or "No.". If the player answers "No." the script stops (close;); if he answers "Yes." the script continues at label ''L_Yes''. Now player is checked to know if he has at least 3 keys, if not script branches to label ''L_Not_Enough'' tells the player he "has not the right key" and script closes. If he has keys enough, his inventory list is retrieved by the built-in function "getinventorylist" and it's content is checked to know if the player will have room enough to store the reward after the 3 keys use. If not, script goes to label ''L_TooMany'' and script close after a warning message, If yes 3 keys are deleted in player's inventory, he gets the reward: a Short Bow and the variable TMW_Quest is set to 38.

For more examples of the current system, check out the current scripts in use by the server. Beware though, this could affect your enjoyment of the game as it does spoil some of the mystery. Here's a link to git so you can view them in your browser:

https://github.com/themanaworld/tmwa-server-data/tree/master/world/map/npc

Note that anything said by an NPC should be put in double quotes ("). You can do that like this: "'''\"'''Hello!'''\"''' she said."

=References=
* [[Dev:TmwAthena Scripting Basics]]
* [[Dev:TmwAthena Scripting Reference]]
* [http://forums.themanaworld.org/viewtopic.php?f=13&t=13653 script cleanup/scripting standards proposal]

Classic:TmwAthena Scripting Reference

2014-04-10T20:35:17Z

O11c: /* menu */ Remove default label

This page is a reference for commands believed to work in the eAthena scripting language still used by tmwAthena.

A number of problematic commands have been removed from this list, but not all commands have been tested.

== Language Commands ==
These are command that are closely tied to the language itself.

=== goto ===
<pre>
goto L_1;
</pre>
Unconditionally jump to a label. Often used in an "if" body.

=== callsub ===
<pre>
callsub S_labelname, arguments...;
</pre>
Jump to the given label. When the "return" statement is executed, continue on the next line.

It is not known whether "arguments..." works, we use temporary variables instead.

It might also be possible to use this as a function, if the form of return with a value is used, but we use temporary variables instead.

=== callfunc ===
<pre>
callfunc "function_name", arguments...;
</pre>
Jump to the given function script. When the "return" statement is executed, continue on the next line of this script.

It is not known whether "arguments..." works, we use temporary variables instead.

It might also be possible to use this as a function, if the form of return with a value is used, but we use temporary variables instead.

"return" is broken if this is used from within an if(). If you need a conditional callfunc, first goto a label.

=== return ===
<pre>
return;
return expr;
</pre>
Return from this script or sublabel to the calling function.

It is unknown what happens if this is used from the top-level script, use "close" or "end" instead.

We use temporary variables instead of the form that returns an expression.

=== getarg ===
<pre>
getarg(index)
</pre>
Return (by reference?) an argument of "callsub" or "callfunc". Aborts the script if used at toplevel of if out of range.

We use temporary variables instead.

=== set ===
<pre>
set variable, expression;
</pre>
Very common command, to set variables.

=== setarray ===
<pre>
setarray arrayvariable, val1, val2, ...;
</pre>
Set elements of an array. Previous elements are not cleared. At most 128 elements can be assigned.

It is currently possible, but deprecated, to specify a (zero-based) array index to start at the given part of an array. It's pretty amazing that that code works anyway.

Remember that there are no permanent arrays, only temporary.

=== cleararray ===
<pre>
cleararray variable, value, count;
</pre>
Fill an array with "count" copies of "value".

=== copyarray ===
<pre>
copyarray dest_var, src_var, count;
</pre>
Copy elements of an array.

This function looks broken to me.

=== getarraysize ===
<pre>
getarraysize variable;
</pre>
Get the size of an array.

The size of an array is simply one more than the index of the last nonzero integer or nonempty string.

WARNING: most functions that set an array do not bother to clear out high indices. You should almost always use an explicitly-provided size instead.

=== deletearray ===
<pre>
deletearray variable[, count = 1];
</pre>
Remove count elements from an array.

If there are elements beyond count, they will be shifted into lower indices.

After that, all remaining elements will be set to 0 or "".

This function is currently broken, instead use cleararray variable, 0, count;

=== getelementofarray ===
<pre>
getelementofarray(arrayname, index_expr)
</pre>
This function is invoked internally by the arrayname[index_expr] syntax.

=== if ===
<pre>
if (condition) condition_command [conditional_command_args, ...];
</pre>
If condition is zero, do nothing. Else, evaluate the conditional command.

The only thing special about the if command is the lack of commas during parsing (from my reading this is only a warning?). During execution it is perfectly normal.

Note: you must not use a callsub or callfunc as conditional_command.

=== end ===
<pre>
end;
</pre>
Stop executing the script.

Don't use this if you have opened a dialog to the player, use "close" instead. Or, use "close2" and *then* "end".

=== debugmes ===
<pre>
debugmes "string"
</pre>
Print a message to stdout.

== Message Commands ==
These are commands for dialog or one-way chat with players.

=== mes ===
<pre>
mes "string";
</pre>
Display a line of text to the player. If a dialog box is not already open for the attached NPC, one will be created.

It is unknown if the client properly supports dialog with multiple NPCs simultaneously. Note that the server only allows each account one paused script at a time, so it probably wouldn't work anyway.

If you need to include the '''"''' character inside the message, (especially for dialogs) insert it as '''\"'''.
When doing several messages without a next; in between, there should be only a single \" at the beginning and the end each.

'''Example''':
mes "[Me Myself]";
mes "";
mes "(I clear my throat)"
mes "";
mes "\"I start talking here, and don't close the quotation marks, because I'm not yet done talking.";
mes "And start a new line, but without new quotation marks.";
mes "Here I stop talking, so I close the quotation marks.\"";
gives:
[Me Myself]

(I clear my throat)

"I start talking here, and don't close the quotation marks, because I'm not yet done talking.<br>
And start a new line, but without new quotation marks.<br>
Here I stop talking, so I close the quotation marks."

=== next ===
<pre>
next;
</pre>
Stop the script until the user presses "Next" in the dialog.

=== close ===
<pre>
close;
</pre>
Stop executing the script and give the user a "Close" button in the dialog.

=== close2 ===
<pre>
close2;
</pre>
Stop the script until the user presses the "Close" button in the dialog, then keep executing the script.

WARNING: unlike close, this command is a blocking command, the usual caveats apply.

=== menu ===
<pre>
menu
"option 1", L_1,
"option 2", L_2;
</pre>
Display a list of choices to the player, then branch to the specified label.

Additionally, the temporary variable "@menu" is set to the 1-based index of the choice.

The options must not contain the character ":", as the protocol uses it as a separator.

=== input ===
<pre>
input variable_name;
</pre>
Input an integer or string to the given variable, depending on whether has the '$' string postfix.

The implementation allows variable_name to be omitted if input is an integer, in case l14 is used. Don't use this.

=== announce ===
<pre>
announce "message", flag;
</pre>
Do a GM message.

If flag & 0xF == 0 forward it to all map servers.
If flag & 0x8, message is from the OID (NPC? usually?) rather than the RID (player).

If (flag & 0x7) == 1, send to all on map.
If (flag & 0x7) == 2, send to all in line of sight.
If (flag & 0x7) == 3, send to self only.
If (flag & 0x7) == anything else, send to all clients.

=== mapannounce ===
<pre>
mapannounce "mapname", "message", flag;
</pre>
Send an announcement to all players in map.

Only flag & 0x10 is interpreted, which does not work with the Mana client. So, flag must be 0.

=== areaannounce ===
<pre>
areaannounce "mapname", x0, y0, x1, y1, "message", flag;
</pre>
Send an announcement to all players in area.

Only flag & 0x10 is interpreted, which does not work with the Mana client. So, flag must be 0.

=== message ===
<pre>
message "player", "message";
</pre>
Display (in chat) a message from the server to a single user.

=== npctalk ===
<pre>
npctalk "message";
</pre>
Make an NPC say something publicly.

Note: in many cases areaannounce is a better choice.

== Character Commands ==
These have to do with attributes of the player.

=== setlook ===
<pre>
setlook type, value;
</pre>
Set an aspect of a character's appearance. Used e.g. by the barber.

There are constant provided for the LOOK type, and for hair color and hair style.

=== heal ===
<pre>
heal hp, sp
</pre>
Increase or decrease the player's hp and sp.

=== itemheal ===
<pre>
itemheal "ii"
</pre>
Increase or decrease the player's hp and sp, for use in item scripts.

=== percentheal ===
<pre>
percentheal "ii"
</pre>
Increase or decrease the player's hp and sp, by percentage of max HP.

This is probably the best way to instakill the player.

=== readparam ===
<pre>
readparam(type[, "playername"])
</pre>
Return one of the core parameters of a player.

type is one of the bCamelCase constants, see db/const.txt

=== getcharid ===
<pre>
getcharid(type[ "playername"])
</pre>
Get an id of the attached (or given) player.

Type is:
0: char id
1: party id
2: guild id (deprecated)
3: account id

You usually want 3.

=== getpartyname ===
<pre>
getpartyname(partyid)
</pre>
Return the name of the party with the given id, or "null".

=== getpartymember ===
<pre>
getpartymember partyid
</pre>
Fills in the array $@partymembername$

=== strcharinfo ===
<pre>
strcharinfo(num)
</pre>
Return string information about an account:
num==0: name
num==1: party name
num==2: guild name (deprecated)

=== sc_start ===
<pre>
sc_start type, tick, val1[, beingid];
</pre>
Apply a status effect to a player (or monster?).

type is one of the sc_* constants.

=== sc_start2 ===
<pre>
sc_start2 type, tick, val1, chance[, beingid];
</pre>
Chance of applying a status effect, out of 10000.

=== sc_end ===
<pre>
sc_end type;
</pre>
Immediately end status effect on current player.

=== sc_check ===
<pre>
sc_check(type)
</pre>
Whether a status effect is currently active.

=== getscrate ===
<pre>
getscrate(type, rate[, being_id])
</pre>
If the sc is poison, modify rate by (3 + vit + luk/3) percent.

The form that accepts a being_id is broken in the current stable version of the server.

=== resetlvl ===
<pre>
resetlvl type;
</pre>

=== resetstatus ===
<pre>
resetstatus;
</pre>

=== resetskill ===
<pre>
resetskill;
</pre>

=== changesex ===
<pre>
changesex;
</pre>
Ask the login server (via the char server) to toggle this account's sex, then kick the player.

=== attachrid ===
<pre>
attachrid(id)
</pre>
Change the being associated with this script.

Return true if such a player is logged in.

=== detachrid ===
<pre>
detachrid;
</pre>
Detach the player associated with this script.

=== isloggedin ===
<pre>
isloggedin(id)
</pre>
Return true if the given ID is logged in.

Often you shouldn't use this, but attachrid(id) instead

=== marriage ===
<pre>
marriage("otherplayer")
</pre>
Marry the attached player to the other player.

Return 1 on success and 0 on failure.

=== divorce ===
<pre>
divorce()
</pre>
Divorce the attached player from their partner

Return 1 on success and 0 on failure.

=== getpartnerid2 ===
<pre>
getpartnerid2()
</pre>
Return the ID of the attached player's partner (0 is none).

=== getexp ===
<pre>
getexp base, job;
</pre>
Increase the types of experience.

=== getinventorylist ===
<pre>
getinventorylist;
</pre>
Fill in some arrays of useful information: "@inventorylist_id", "@inventorylist_amount", "@inventorylist_equip".

The arrays are not cleared between calls, use "@inventory_count".

=== getskilllist ===
<pre>
getskilllist;
</pre>
Fill in some arrays of useful information: "@skilllist_id", "@skilllist_lv", "@skilllist_flag".

The arrays are not cleared between calls, use "@skill_count".

=== getpoolskilllist ===
<pre>
getpoolskilllist;
</pre>
Same, but only poolable skills.

=== getactivatedpoolskilllist ===
<pre>
getactivatedpoolskilllist;
</pre>
Same, but only activated pool skills.

=== getunactivatedpoolskilllist ===
<pre>
getunactivatedpoolskilllist;
</pre>
Same, but only unactivated pool skills.

=== poolskill ===
<pre>
poolskill skill_id;
</pre>
Activate a poolable skill.

=== unpoolskill ===
<pre>
unpoolskill skill_id;
</pre>
Deactivate a poolable skill.

=== checkpoolskill ===
<pre>
checkpoolskill(skill_id)
</pre>
Check if a pool skill is activated

=== misceffect ===
<pre>
misceffect type, "player_name";
misceffect type, being_id;
misceffect type;
</pre>
Display a miscellaneous effect on a being.

In the third form, it will use the OID if possible, and fallback to the RID.

=== getlook ===
<pre>
getlook(type)
</pre>
Return part of the player's appearance:
val==1: hair
val==2: weapon
val==3: bottom
val==4: middle
val==5: top
val==6: hair color
val==8: shield
val==9: shoes

On failure, return -1.

=== getsavepoint ===
<pre>
getsavepoint(type)
</pre>
type==0: Return savepoint map
type==1: Return savepoint x
type==2: Return savepoint y

This is believed to be the only function (other than callfunc and callsub of course) that returns a different type depending on its arguments.

=== shop ===
<pre>
shop "npcname";
</pre>
Close the script and open the given NPC's shop.

=== isdead ===
<pre>
isdead()
</pre>
Return 1 if the attached player is dead, else 0.

=== fakenpcname ===
<pre>
fakenpcname "name", "newname", new_sprite_id;
</pre>
Change the appearance of an NPC.

== Location Commands ==
These are commands that have to do with the location of players

=== warp ===
<pre>
warp "mapname", x, y;
</pre>
Warp the attached player to the given location. "mapname" may have the special values "Random", "SavePoint", and "Save" (case-sensitive), but x and y are still required.

=== isat ===
<pre>
isat("mapname", x, y)
</pre>
Return 1 if the attached player is at the given location, 0 otherwise.

=== areawarp ===
<pre>
areawarp "src_map", x0, y0, x1, y1, "dst_map", x, y;
</pre>
Warp all players in the given area to the given location.

=== getusers ===
<pre>
getusers(type)
</pre>
Count users.

If flag & 0x8, base on OID instead of RID.
If (flag & 0x7) == 0, return users on the map.
If (flag & 0x7) == 1, return users on the server.

=== getmapusers ===
<pre>
getmapusers("mapname")
</pre>
Count users on a given map.

=== getareausers ===
<pre>
getareausers("mapname", x0, y0, x1, y1, z)
</pre>
Count users in an area.
z can be set to 1 or be left out to check for players who are alive.

=== mapwarp ===
<pre>
mapwarp "src_map", "dst_map", x, y;
</pre>
Warp all players from source map to destination location.

=== npcwarp ===
<pre>
npcwarp x, y, "npcname";
</pre>
Move an NPC to a different location on the same map.

=== isin ===
<pre>
isin("mapname", x0, y0, x1, y1)
</pre>
Check if the player is in the area.

=== getx ===
<pre>
getx()
</pre>
Return attached player's x coordinate.

=== gety ===
<pre>
gety()
</pre>
Return attached player's y coordinate.

=== getmap ===
<pre>
getmap()
</pre>
Return attached player's current map.

== Item Commands ==
These have to do with items or inventory.

=== getitem ===
<pre>
getitem "itemname", count[, unused_argument[, playerid]];
getitem itemid, count[, unused_argument[, playerid]];
"ii**"
</pre>
Grant the attached player (or the given player) "count" copies of an item.

If itemname is unrecognized you get an iten (727) instead.

;Warning:
<pre>
delitem: only deletes one item if applied to not-stackable item (equipment)
getitem: gives item stacked, even if it's equipment
fix: use a loop and only delete/give one item at a time</pre>

=== makeitem ===
<pre>
makeitem "itemname", count, "mapname", x, y;
makeitem itemid, count, "mapname", x, y;
</pre>
Drop items on the ground.

The special "mapname" value "this" means the map of the attached player.

=== delitem ===
<pre>
delitem "itemname", count;
delitem itemid, count;
</pre>
Remove items from the attached player's inventory.

This command is buggy if the player does not have enough of the item. And if the item is not stackable, the command will delete only one of them, even if a higher number is specified.
;Warning:
<pre>
delitem: only deletes one item if applied to not-stackable item (equipment)
getitem: gives item stacked, even if it's equipment
fix: use a loop and only delete/give one item at a time</pre>

=== countitem ===
<pre>
countitem("itemname")
countitem(itemid)
</pre>
Return the number of the given item in the player's inventory.

=== checkweight ===
<pre>
checkweight("itemname", count)
checkweight(itemid, count)
</pre>
Return 0 if adding "count" of the item would put player above max weight, 1 if it would still be less than max weight.
Also returns 0 if item does not exist.

=== getequipid ===
<pre>
getequipid(equip_point)
</pre>
Return the ID of the item in the given equip slot.

equip_point is one of the equip_* constants

=== getequipname ===
<pre>
getequipname(equip_point)
</pre>
Return the name of the item in the given equip slot.

equip_point is one of the equip_* constants

=== getequipisequiped ===
<pre>
getequipisequiped(num)
</pre>
Return 1 if the player currently has an item equipped in the slot.

=== statusup ===
<pre>
statusup bType;
</pre>
Permanently increase a stat by one point.

=== statusup2 ===
<pre>
statusup2 bType, delta;
</pre>
Permanently increase or decrease a stat.

=== bonus ===
<pre>
bonus bType, delta
</pre>
Temporarily increase a stat. For use in item scripts only.

=== skill ===
<pre>
skill id, level[, flag = 1];
</pre>
Grant a skill.

flag==0: permanent skill
flag==1: temporary skill (item scripts only)

(Untested)

=== setskill ===
<pre>
setskill id, level;
</pre>
Grant a skill permanently.

=== getskilllv ===
<pre>
getskilllv(skill)
</pre>
Return the player's level of the given skill.

=== getgmlevel ===
<pre>
getgmlevel()
</pre>
Return the player's GM level.

=== getopt2 ===
<pre>
getopt2()
</pre>
Return the player's opt2 flags.

=== setopt2 ===
<pre>
setopt2 flags;
</pre>
Set the player's opt2 flags.

=== checkoption ===
<pre>
checkoption(type)
</pre>
Return 1 if the player has any of the given (XOR'ed) option bits. Usually only one is given.

=== setoption ===
<pre>
setoption type
</pre>
Set the player's option flags exactly (not OR'ing).

=== savepoint ===
<pre>
savepoint "mapname", x, y;
</pre>
Set the player's save point. Used e.g. by Soul Menhirs, and during the time travel quest.

=== openstorage ===
<pre>
openstorage;
</pre>
Open the player's storage.

=== getitemname ===
<pre>
getitemname("itemname")
getitemname(itemid)
</pre>
Return the name of the item, or "Unknown Item".

=== clearitem ===
<pre>
clearitem;
</pre>
Remove all items from a player's inventory.

=== nude ===
<pre>
nude;
</pre>
Unequip all items.

=== hasitems ===
<pre>
hasitems()
</pre>
Return 1 if the player has any inventory, 0 otherwise.

=== unequipbyid ===
<pre>
unequipbyid slot_id;
</pre>
Unequip whatever is in the slot

=== getareadropitem ===
<pre>
getareadropitem("mapname", x0, y0, x1, y1, "itemname"[, delitems = 0]);
getareadropitem("mapname", x0, y0, x1, y1, itemid[, delitems = 0]);
</pre>
Count items on the floor in an area. If delitems, the items will be deleted as well.

== Common Functions ==
These are not mostly not related to the RPG or the scripting language.

=== rand ===
<pre>
rand(range)
rand(min, max)
</pre>
In the first form, return a random number between 0 (inclusive) and range (exclusive). Return 0 if range is not positive.
In the second form, return a random number between min and max, inclusive. Min and max may be swapped.

=== gettimetick ===
<pre>
gettimetick(type)
</pre>
Return one of the ticks

type==0 (or other): milliseconds since some point in time, wraps every 50 days.
type==1: time since midnight, UTC.
type==2: seconds since the epoch.

You should almost always use type 2.

=== gettime ===
<pre>
gettime(type)
</pre>
Get a component of the time (UTC).

1: second (0-59)
2: minute (0-59)
3: hour (0-23)
4: day of week (0-6)
5: day of month (1-31)
6: month (1-12)
7: year (1902-2038)

== Timers and Events ==
These have to do with transfering control in ways that are not immediately obvious.

The most common ones are initnpctimer or startnpctimer, stopnpctimer, and setnpctimer.

=== doevent ===
<pre>
doevent "event";
</pre>
Manually invoke an NPC event.

=== donpcevent ===
<pre>
donpcevent "event";
</pre>
Manually invoke an NPC event.

=== addtimer ===
<pre>
addtimer tick, "event";
</pre>
Invoke an NPC event after a delay, for the attached NPC.

This command does the same thing as areatimer, but for only the attached player.

=== deltimer ===
<pre>
deltimer "event";
</pre>
This command is untested and might freeze the server.

=== initnpctimer ===
<pre>
initnpctimer;
</pre>
Set the NPC's attached timer to tick 0 and start it.

This is equivalent to setnpctimer, 0; startnpctimer;

=== stopnpctimer ===
<pre>
stopnpctimer;
</pre>
Stop the NPC's attached timer.

This DOES NOT do anything about the tick. But that's okay, you should normally be starting it with initnpctimer.

=== startnpctimer ===
<pre>
startnpctimer;
</pre>
Start the NPC's attached timer, without setting the tick.

=== setnpctimer ===
<pre>
setnpctimer tick;
</pre>
Set the NPC's timer to a specific tick. Generally, this is only useful for tick 0.

=== getnpctimer ===
<pre>
getnpctimer(type)
</pre>
Get the current tick of an NPC's timer.

type==0: timer event tick (like setnpctimer)
type==1: bool if it has a next timer.
type==2: timer amount

=== cmdothernpc ===
<pre>
cmdothernpc "npc", "Foo";
</pre>
Invoke ::OnCommandFoo

=== mobcount ===
<pre>
mobcount("mapname", "event")
</pre>
Count the remaining mobs from the spawn with the given event. Has an offset of -1.

=== areatimer ===
<pre>
areatimer "mapname", x0, y0, x1, y1, tick, "event";
</pre>
Add a PC event timer to all players in the area.

After "tick" milliseconds, the given NPC event will fire with each player as the RID.

== Unsorted Commands ==
These are commands that still need sorting, please edit this page, see talk page for category (and subcategory?) suggestions.

=== monster ===
<pre>
monster "mapname", x, y, "string", class, count[, "event"];
</pre>
Spawn monsters at a point. If you define an OnDead event using a trigger area then the event is shot only inside that area, hence the event is ignored when the monster is killed outside the trigger area.

=== areamonster ===
<pre>
areamonster "mapname", x0, y0, x1, y1, "string", class, count[, "event"];
</pre>
Spawn monsters in an area. If you define an OnDead event using a trigger area then the event is shot only inside that area, hence the event is ignored when the monster is killed outside the trigger area.

=== killmonster ===
<pre>
killmonster "mapname", "event";
</pre>
Kill monsters on a map.

Unless it is "All", "event" must match the one used at spawn time.

If "All" is given, this function properly preserves permanently respawning monsters.

=== killmonsterall ===
<pre>
killmonsterall "mapname";
</pre>
Kill all monsters unconditionally.

This command might prevent monsters from respawning. Instead use "killmonster" with "event" == "All".

=== enablenpc ===
<pre>
enablenpc "name";
</pre>
Enable an NPC.

=== disablenpc ===
<pre>
disablenpc "name";
</pre>
Disable an NPC.

=== hideoffnpc ===
<pre>
hideoffnpc "name";
</pre>
What does this do?

=== hideonnpc ===
<pre>
hideonnpc "name";
</pre>
What does this do?

=== setmapflagnosave ===
<pre>
setmapflagnosave "mapname", "savemap", x, y;
</pre>
Set the nosave flag and respawn location.

=== setmapflag ===
<pre>
setmapflag "mapname", flag;
</pre>
Set an arbitrary mapflag.

=== removemapflag ===
<pre>
removemapflag "mapname", flag;
</pre>
Unset an arbitrary mapflag.

=== getmapflag ===
<pre>
getmapflag("mapname", flag);
</pre>
Check an arbitrary mapflag.

=== pvpon ===
<pre>
pvpon "mapname";
</pre>
Allow PvP on a map.

=== pvpoff ===
<pre>
pvpoff "mapname";
</pre>
Deny PvP on a map.

=== emotion ===
<pre>
emotion emote_index;
</pre>
Show a smiley above the OID.

=== getspellinvocation ===
<pre>
getspellinvocation("spell-identifier")
</pre>
Return the #invocation used for a spell, or "...".

=== getanchorinvocation ===
<pre>
getanchorinvocation "anchor-identifier"
</pre>
Return the invocation used for a teleport anchor (?)

=== strmobinfo ===
<pre>
strmobinfo(num, class)
</pre>
Info about a type of mob:
num==1: name
num==2: jname
num==3: lv
num==4: maxhp
num==5: maxsp
num==6: base_exp
num==7: job_exp

Note that only types 1 and 2 actually return strings, the rest return integers

=== specialeffect ===
<pre>
specialeffect type;
</pre>
Display a special effect on the OID.

Same as "misceffect", but does not fallback when there is no OID.

=== specialeffect2 ===
<pre>
specialeffect2 type;
</pre>
Same as "misceffect", but works when there is an OID.

=== gmcommand ===
<pre>
gmcommand "@command maybe with arguments";
</pre>
Run a GM command, at level 99.

User talk:Jmf

2014-02-21T16:15:22Z

O11c: Welcome!

User:Jmf

2014-02-21T16:15:21Z

O11c: Creating user page for new user.

Hey, I am jmf and just joined The Mana World.
I am quite enthusiastic about this and I want to contribute to the project.
I have some experience with C++ and I have previously translated texts for some other FLOSS projects.
That's about all that is there to say about myself.

Template:I18n

2014-02-17T18:34:18Z

O11c: Add Czech

User talk:McGreen

2014-02-09T20:12:09Z

O11c: Welcome!

User:McGreen

2014-02-09T20:12:09Z

O11c: Creating user page for new user.

Just a guy who wants to spend some time in the Mana World.
Grown up in Gheenteld, a tiny village in the Lapragth district I - even though I'm still young - went through quite some adventures.
If you're interested in my story, drop me a line and I'll gladly point you to a site that tells my story.

User talk:Falium

2014-02-09T20:11:14Z

O11c: Welcome!

User:Falium

2014-02-09T20:11:14Z

O11c: Creating user page for new user.

Falium is a random person who likes to correct minor mistakes (spelling, typos, etc.) on wiki sites.

This person has been interested in The Mana World for a few years, but only recently began playing on
the public server.

Falium has an average typing speed of 54 WPM, with a peak of 98 WPM. (It depends
on whether or not the words are being transcribed or invented at the time of typing.)

Falium believes that people who detonate explosive devices for a living must either
have a ton of fun doing it, or have no better source of income.

User talk:Camren

2014-02-09T20:10:42Z

O11c: Welcome!

User:Camren

2014-02-09T20:10:41Z

O11c: Creating user page for new user.

i would like to play with players i never curse im very nice and never ever begg for items and i also never spam. this game seems like a wonder full game to play i would also like to request this account because i need a mana market account so i may sell the items that i do not need.

User talk:Bhar

2014-02-09T20:10:28Z

O11c: Welcome!

User:Bhar

2014-02-09T20:10:27Z

O11c: Creating user page for new user.

Hi,
I played to The Mana World on 2009 and leave it for a time, now i'm back and i'm playing with a new account, well i want to have a new one here.
I come from France, i'm 35 now… I don't know what to say more...
Thanks for the game, thanks for all.
Bruno (bhar)

User talk:Samuraiii

2014-02-09T20:10:18Z

O11c: Welcome!

User:Samuraiii

2014-02-09T20:10:18Z

O11c: Creating user page for new user.

I would like to to help translating pages of wiki to Czech. I am user and adorer of Open Source projects for ten years and Really like Mana World and wont to help by translating wiki and maybe also some time client and all other related strings in game.
Samuraiii

User talk:Ametz

2014-02-09T20:10:01Z

O11c: Welcome!

User:Ametz

2014-02-09T20:10:01Z

O11c: Creating user page for new user.

Male, Sweden, started playing The Mana World a few years ago, and just come back to play some more, lvl 73 + a lvl 40+ ish.
My brother also play The Mana World nowdays and he likes it, alot have changed since i played last tho.
Like the map, more content and such.

Classic talk:Monster Design

2014-01-10T08:03:32Z

O11c: /* To do */ note stuff

===IRC, 19.12.2013, UTC+1===
(Irrelevant lines deleted)

<pre>[09:23:22] <Cassy_at_work> o11c: btw can you please check the red marked text at the bottom of this page: https://wiki.themanaworld.org/index.php/Dev:Monster_Design
... I think that's a short look at it and it can be deleted (text in "expand")
[09:37:49] <o11c> Cassy: mob stats are largely ignored ... I know LUK has an effect on crits, and there are a couple other things, but ...
[09:41:52] <o11c> Cassy: all the spoilered stuff is deletable, yeah
[09:43:32] <o11c> Cassy: detector and change target exist, but don't do anything (welcome to tmwa!)
[09:52:02] <Cassy_at_work> o11c: so for my notes on STR and VIT I can say those actually don't do anything?
[10:04:54] <o11c> Cassy_at_work: I'm not actually sure about STR and VIT
[10:05:05] <o11c> combat calculations are kind of complicated
[10:06:10] <Cassy_at_work> o11c: oki, I'll just add a note there then that it's not sure what those do</pre>

[[User:Cassy|Cassy]] ([[User talk:Cassy|talk]]) 20:14, 20 December 2013 (UTC)

===To do===
* '''LV''': What real use does it have? It is added to dex for "to hit" and to agi for "flee".
* '''SP''': What real use does it have? Should be "currently unused" as mobs don't use magic so far, but there are entries for Luvia (60) and ViciousSquirrel (1). Completely unused.
* '''EXP''': Adding a link to the page on GitHub where it says how EXP is calculated. ?
* '''JEXP''': Adding some information about that tool that calculates it for you. make mobxp?
* '''LUK''': What are perfect dodge, lucky flee and perfect flee? Various combat chances - show in client as "miss" and "dodge".
* '''Scale''': What does it do? Absolutely nothing.
* '''Amotion''': Is sent to client. Appears in one calculation regarding mobs in the "attack" state, setting "attackable time". Note that '''Adelay''' sets "think time" instead. I'm not sure exactly what either of those mean.
* '''Dmotion''': Is sent to client. Used to set canmove_tick.
* '''Item1''': unused
* '''Item2''': unused
* '''MEXP''': unused
* '''ExpPer''': unused
* '''MVP1id''': unused
* '''MVP1per''': unused
* '''mutationcount''': Which attributes can increase?
LV, MAX_HP, STR, AGI, VIT, INT, DEX, LUK, ATK1, ATK2, ADELAY, DEF, MDEF, SPEED, MAX_HP // double chance to modify hp, no chance to modify xp_base
* everything saying "''(follows)''"

[[User:Cassy|Cassy]] ([[User talk:Cassy|talk]]) 12:29, 8 January 2014 (UTC)

Updated. [[User:Cassy|Cassy]] ([[User talk:Cassy|talk]]) 14:48, 9 January 2014 (UTC)
Edited. [[User_talk:o11c|o]][[User:o11c|11]][[Special:Contributions/o11c|c]] 08:03, 10 January 2014 (UTC)

Development:How to Develop

2014-01-02T05:42:04Z

O11c: /* Install Dependencies */ Add 'realpath' package to list; not everybody has it by default.

We're using Git as version control system for our source files and content. Have a look at our [[Working With Git|Tutorial]] about how to use Git.

=Set Up=
This is a how to help content development for official server (tmwAthena) using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwa-client-data), server-data (tmwa-server-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting.

==Install Dependencies==
In addition to the basic build tools (GCC, Make, headers, ...), [http://www.gnu.org/software/bison/ '''Bison'''], and [http://sourceforge.net/projects/flex/ '''Flex'''] are needed.

''' [http://www.debian.org/index.html Debian] derivates (including [http://www.ubuntu.com/ Ubuntu])'''
* Open a terminal.
sudo apt-get install g++ flex bison python make realpath

Note that you must have gcc 4.6 or later. Any modern distro will have this version, but "stable" distros with very long release cycles, such as Red Hat Enterprise Linux, might not.

==Set Up Own Server==
'''Here are the steps to use when creating a new local testing server.'''
* Open a terminal.
mkdir ~/tmwAthena
cd ~/tmwAthena/
git clone --recursive git://github.com/themanaworld/tmwa.git
git clone --recursive git://github.com/themanaworld/tmwa-server-data.git
cd tmwa/
./configure --user # ''Assuming ~/bin is in your PATH)''
make
make install
git config --global url.git@github.com:.pushInsteadOf git://github.com ''{{ref|push}} {{ref|once}}''
cd ../tmwa-server-data
* Preferably, add the update hooks.
ln -s ../../git/hooks/post-merge .git/hooks/
ln -s ../../../../git/hooks/post-merge .git/modules/client-data/hooks/ # ''(git 1.7.8 or newer)''
ln -s ../../../git/hooks/post-merge client-data/.git/hooks/ # ''(git 1.7.7 or older)''
make conf
cd client-data
git checkout master
cd music
git checkout master

==Hosting Updates==
TMW makes it easy to generate delta zips out of a repository, once it is initially set up.

It will put them in ~/www/updates/, which may be a symlink to wherever your web server is really serving. Setting up a webserver is not covered here.

Once everything is set up, just run 'make updates' from the server-data dir every time client-data changes. It will do nothing if appropriate, generate complete zips the first time, and incremental zips afterwards.

Some notes:
* You must put news.txt and skeleton resources.xml file (and maybe an empty resources2.txt) in ~/www/updates/ first.
* Music updates are never added; they should be in the skeleton and updated manually if needed.
* You definitely want to run one of the analyzer scripts frequently, and remove the old updates.

==Updating the Server==

== Running and Administrating the Server ==

The TMWAthena is in fact 3 servers:
* '''tmwa-login''' which manages accounts and connection to char server.
* '''tmwa-char''' which manages characters and connects them to the map server.
* '''tmwa-map''' which manages game content (maps, monsters, items, scripts...) and their interaction with characters

* Start the servers: Open a terminal and run all the local servers. To stop them, either close the terminal or type control-C.
cd ~/tmwAthena/tmwa-server-data/
./run-all
* In a new terminal, Launch '''tmwa-admin''' the administration tool, add yourself as an user and make yourself a GM:
cd ~/tmwAthena/tmwa-server-data/login
tmwa-admin
add <username> M <password>
gm <username> 99

'''Note''' : Be sure that you are running tmwa-admin from within the "login/" directory. Check that the config files are correct: the connection port should be 6901 for tmwa's configuration, not 6900, which is the hard-coded default.

'''See also:''' [[GM Commands]]

== Connecting ==
# Open a command line terminal and run your client pointing to your client data and your local server :
manaplus --server localhost --port 6901 -u -d ~/tmwAthena/tmwa-server-data/client-data
or
mana --server localhost --port 6901 -u -d ~/tmwAthena/tmwa-server-data/client-data

If all went well, you are now ready to test new content and participate with development.

== develop new content==
'''You are now free to do some changes, first close the client and your servers.'''

'''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.'''''
* Make your modifications (e.g. Change a map) and save them.
* Open a terminal.
cd ~/tmwAthena/tmwa-server-data/client-data''
git status''
git add [modified files]''
git commit''
git push'' {{note|push}}
cd ..
make maps ''(if you changed a map)''
git status
git add [modified files]
git add client-data (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''')
git commit
git push {{note|push}}
* Close the terminal.

{{note|push}} : a step for those with commit access to the remote repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested.

{{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories.

git format-patch -M -C origin/master
* pastebin the patch(es) and post for review at irc.freenode.net channel: #themanaworld-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part.

<span style="color:#FF0000"> '''Note :''' This is kind of outdated; with github it's often easier to do patches on branches there. see: '''[[Working With Git]]''' page</span>

'''You can also pull the data which has been modified.'''
* Open a terminal.
cd ~/tmwAthena/tmwa-server-data
git pull
* If you haven't installed the hook,
git submodule update --merge ''at toplevel (for client-data) and in client-data (for music)''
* Close the terminal.

'''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music.

=Making Content=
==Making Map Content==
See [[Mapping Tutorial]].
===Python Converter Tool===
After editing maps for the client, you need to generate the walkmaps and imports for the server. yhis can be done either by the '''[[Tiled]]''' application or by running the python script '''tmx_converter.py''' which is located in the '''tools''' folder of the '''Server Data''' folder.
(see [[Mapping Tutorial#Creating the WLK files]])
After that, commit and push the files that the converter edited. Note that, if you do not have push access to the main repository, you should let someone else update the submodule itself.

==Getting Art Content Into The Game==
* Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum].
* Work with the Art Director and collaborators on getting the art consistent.
* When finished, edit topic as [FND].
* Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT].
* XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT].
::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition.
* Project developer requests database entry reservations from a General Content Team developer.
::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory.
::* Map entry client data affected: .tmx files in the maps directory.
::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made.
::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory.
::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file.

===Handling General Content Team [REQ]s===
* General Content Team member adds a [REQ] topic to the graphics development forum.
* General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page.
* Art Director attempts to network with other artists to assign the art to an artist.

==Bit Masking==
Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing.

[http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script]

==Generating client updates==
* Shutdown all your servers.

* First we are going to check the config files to be sure the paths are correct.
cd ~/tmwAthena/tmwa-server-data/client-data/tools/
ls

Output:
add-git-attributes edit-all-to-export-tilesets.sh formatXML.sh list-tileset-order map-db.py minimap-render.py
adler32 edit-map-tileset-names.sh indent.xsl make-updates map-diff.py
End of output

* The easiest solution is to create a symbolic link to that directory
ln -s /var/www/tmwupdates ~/www/updates (your public www folder is /tmwupdates)

* You can Edit the make-updates file with gedit or nano or vi.
Search for the folowing lines:
output=~/www/updates
And change them to:
output=/var/www/tmwupdates (your public www folder is /tmwupdates)

*Save the file and get back in the terminal.
cd ~/tmwAthena/tmwa-server-data/login/conf
ls

Output:
ladmin_athena.conf lan_support.conf login_local.conf.example
ladmin_local.conf login_athena.conf
ladmin_local.conf.example login_local.conf
End of output

*Edit the login_local.conf with an editor and look for the following line:
update_host: http://updates.themanaworld.org/
*Change that line to:
update_host: http://127.0.0.1/tmwupdates/ (or use your external ip)
*Save the file and get back in the terminal.

* Open a terminal.
First we compile the adler32 tool to generate a hash.
cd ~/tmwAthena/tmwa-server-data/client-data/tools/adler32/
make

Output must be:
gcc -lz -o adler32 adler32.c

make install

* Now that we compiled the adler tool we can make us a update.
cd ~/tmwAthena/tmwa-server-data/
make updates

* Each time you want to make new updates
make sure you have a new commit then
cd ~/tmwAthena/tmwa-server-data/
make updates

Development:How to Develop

2013-12-22T03:13:16Z

O11c: /* Set Up Own Server */ make the configure notes less confusing, especially with recent changes

We're using Git as version control system for our source files and content. Have a look at our [[Working With Git|Tutorial]] about how to use Git.

=Set Up=
This is a how to help content development for official server (tmwAthena) using Ubuntu and the Mana client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwa-client-data), server-data (tmwa-server-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting.

==Install Dependencies==
In addition to the basic build tools (GCC, Make, headers, ...), [http://www.gnu.org/software/bison/ '''Bison'''], and [http://sourceforge.net/projects/flex/ '''Flex'''] are needed.

''' [http://www.debian.org/index.html Debian] derivates (including [http://www.ubuntu.com/ Ubuntu])'''
* Open a terminal.
sudo apt-get install g++ flex bison python make

Note that you must have gcc 4.6 or later. Any modern distro will have this version, but "stable" distros with very long release cycles, such as Red Hat Enterprise Linux, might not.

==Set Up Own Server==
'''Here are the steps to use when creating a new local testing server.'''
* Open a terminal.
mkdir ~/tmwAthena
cd ~/tmwAthena/
git clone --recursive git://github.com/themanaworld/tmwa.git
git clone --recursive git://github.com/themanaworld/tmwa-server-data.git
cd tmwa/
./configure --user # ''Assuming ~/bin is in your PATH)''
make
make install
git config --global url.git@github.com:.pushInsteadOf git://github.com ''{{ref|push}} {{ref|once}}''
cd ../tmwa-server-data
* Preferably, add the update hooks.
ln -s ../../git/hooks/post-merge .git/hooks/
ln -s ../../../../git/hooks/post-merge .git/modules/client-data/hooks/ # ''(git 1.7.8 or newer)''
ln -s ../../../git/hooks/post-merge client-data/.git/hooks/ # ''(git 1.7.7 or older)''
make conf
cd client-data
git checkout master
cd music
git checkout master

==Hosting Updates==
TMW makes it easy to generate delta zips out of a repository, once it is initially set up.

It will put them in ~/www/updates/, which may be a symlink to wherever your web server is really serving. Setting up a webserver is not covered here.

Once everything is set up, just run 'make updates' from the server-data dir every time client-data changes. It will do nothing if appropriate, generate complete zips the first time, and incremental zips afterwards.

Some notes:
* You must put news.txt and skeleton resources.xml file (and maybe an empty resources2.txt) in ~/www/updates/ first.
* Music updates are never added; they should be in the skeleton and updated manually if needed.
* You definitely want to run one of the analyzer scripts frequently, and remove the old updates.

==Updating the Server==

== Running and Administrating the Server ==

The TMWAthena is in fact 3 servers:
* '''tmwa-login''' which manages accounts and connection to char server.
* '''tmwa-char''' which manages characters and connects them to the map server.
* '''tmwa-map''' which manages game content (maps, monsters, items, scripts...) and their interaction with characters

* Start the servers: Open a terminal and run all the local servers. To stop them, either close the terminal or type control-C.
cd ~/tmwAthena/tmwa-server-data/
./run-all
* In a new terminal, Launch '''tmwa-admin''' the administration tool, add yourself as an user and make yourself a GM:
cd ~/tmwAthena/tmwa-server-data/login
tmwa-admin
add <username> M <password>
gm <username> 99

'''Note''' : Be sure that you are running tmwa-admin from within the "login/" directory. Check that the config files are correct: the connection port should be 6901 for tmwa's configuration, not 6900, which is the hard-coded default.

'''See also:''' [[GM Commands]]

== Connecting ==
# Open a command line terminal and run your client pointing to your client data and your local server :
manaplus --server localhost --port 6901 -u -d ~/tmwAthena/tmwa-server-data/client-data
or
mana --server localhost --port 6901 -u -d ~/tmwAthena/tmwa-server-data/client-data

If all went well, you are now ready to test new content and participate with development.

== develop new content==
'''You are now free to do some changes, first close the client and your servers.'''

'''''Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.'''''
* Make your modifications (e.g. Change a map) and save them.
* Open a terminal.
cd ~/tmwAthena/tmwa-server-data/client-data''
git status''
git add [modified files]''
git commit''
git push'' {{note|push}}
cd ..
make maps ''(if you changed a map)''
git status
git add [modified files]
git add client-data (if ''git status'' shows ''(new commits)''. '''Don't do this if you don't have push access to client-data!''')
git commit
git push {{note|push}}
* Close the terminal.

{{note|push}} : a step for those with commit access to the remote repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where ''git push'' is suggested.

{{note|once}} : you only need to do this once, no matter how many times you independently clone the repositories.

git format-patch -M -C origin/master
* pastebin the patch(es) and post for review at irc.freenode.net channel: #themanaworld-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part.

<span style="color:#FF0000"> '''Note :''' This is kind of outdated; with github it's often easier to do patches on branches there. see: '''[[Working With Git]]''' page</span>

'''You can also pull the data which has been modified.'''
* Open a terminal.
cd ~/tmwAthena/tmwa-server-data
git pull
* If you haven't installed the hook,
git submodule update --merge ''at toplevel (for client-data) and in client-data (for music)''
* Close the terminal.

'''See Also:''' [http://wiki.themanaworld.org/images/3/33/README.mv.txt README.mv.txt] - Documentation on using git submodules, like client-data and tmw-music.

=Making Content=
==Making Map Content==
See [[Mapping Tutorial]].
===Python Converter Tool===
After editing maps for the client, you need to generate the walkmaps and imports for the server. yhis can be done either by the '''[[Tiled]]''' application or by running the python script '''tmx_converter.py''' which is located in the '''tools''' folder of the '''Server Data''' folder.
(see [[Mapping Tutorial#Creating the WLK files]])
After that, commit and push the files that the converter edited. Note that, if you do not have push access to the main repository, you should let someone else update the submodule itself.

==Getting Art Content Into The Game==
* Post [CPT] or [WIP] art on the [http://forums.themanaworld.org/viewforum.php?f=8 graphics development forum].
* Work with the Art Director and collaborators on getting the art consistent.
* When finished, edit topic as [FND].
* Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT].
* XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT].
::* Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition.
* Project developer requests database entry reservations from a General Content Team developer.
::* Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory.
::* Map entry client data affected: .tmx files in the maps directory.
::* Map entry requires the running of the .tmx converter (aka java converter) before commits can be made.
::* Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory.
::* Art content client data affected: entry added in items.xml, monsters.xml or other identification file.

===Handling General Content Team [REQ]s===
* General Content Team member adds a [REQ] topic to the graphics development forum.
* General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the [[Art in Development]] page.
* Art Director attempts to network with other artists to assign the art to an artist.

==Bit Masking==
Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing.

[http://dl.dropbox.com/u/6520164/tester1.txt Bit Masking Test Script]

==Generating client updates==
* Shutdown all your servers.

* First we are going to check the config files to be sure the paths are correct.
cd ~/tmwAthena/tmwa-server-data/client-data/tools/
ls

Output:
add-git-attributes edit-all-to-export-tilesets.sh formatXML.sh list-tileset-order map-db.py minimap-render.py
adler32 edit-map-tileset-names.sh indent.xsl make-updates map-diff.py
End of output

* The easiest solution is to create a symbolic link to that directory
ln -s /var/www/tmwupdates ~/www/updates (your public www folder is /tmwupdates)

* You can Edit the make-updates file with gedit or nano or vi.
Search for the folowing lines:
output=~/www/updates
And change them to:
output=/var/www/tmwupdates (your public www folder is /tmwupdates)

*Save the file and get back in the terminal.
cd ~/tmwAthena/tmwa-server-data/login/conf
ls

Output:
ladmin_athena.conf lan_support.conf login_local.conf.example
ladmin_local.conf login_athena.conf
ladmin_local.conf.example login_local.conf
End of output

*Edit the login_local.conf with an editor and look for the following line:
update_host: http://updates.themanaworld.org/
*Change that line to:
update_host: http://127.0.0.1/tmwupdates/ (or use your external ip)
*Save the file and get back in the terminal.

* Open a terminal.
First we compile the adler32 tool to generate a hash.
cd ~/tmwAthena/tmwa-server-data/client-data/tools/adler32/
make

Output must be:
gcc -lz -o adler32 adler32.c

make install

* Now that we compiled the adler tool we can make us a update.
cd ~/tmwAthena/tmwa-server-data/
make updates

* Each time you want to make new updates
make sure you have a new commit then
cd ~/tmwAthena/tmwa-server-data/
make updates

Template:Packet

2013-12-21T20:35:21Z

O11c: typo (templates are hard)

{{#switch: {{{mode}}}
| row =
<tr valign="top"> <td> [[Net:{{{id}}}|{{{id}}}]] </td> <td style="background: {{{alignment|purple}}}"> {{{length}}} </td> <td> {{{nicename}}} </td> <td> {{{define}}} </td> <td> Sent: {{{sent}}} <br/> Parsed: {{{parsed}}} </td> </tr>
| row_internal =
<tr valign="top"> <td> [[Net:{{{id}}}|{{{id}}}]] </td> <td style="background: {{{alignment|purple}}}"> {{{length}}} </td> <td> {{{nicename}}} </td> <td> Sent: {{{sent}}} <br/> Parsed: {{{parsed}}} </td> </tr>
| #default =
[[Dev:TmwAthena Packets|< Back]]
==={{{nicename}}}===
<table style="border: dashed 1px #aac">
<tr><th style="text-align: right">Packet ID:</th><td>[[Net:{{{id}}}|{{{id}}}]]</td></tr>
<tr><th style="text-align: right">Packet Length:</th><td style="background: {{{alignment|purple}}}">{{{length}}}</td></tr>
<tr><th style="text-align: right">Client Defined:</th><td>{{{define}}}</td></tr>
<tr><th style="text-align: right">Sent Location(s):</th><td>{{{sent}}}</td></tr>
<tr><th style="text-align: right">Parsed Location(s):</th><td>{{{parsed}}}</td></tr>
</table>

=== Fields ===
<table style="border-collapse: collapse;" cellspacing="0" cellpadding="3">
<tr valign="top">
<th style="text-align: left; font-weight: normal; border-bottom: solid 1px #888;padding-right:12px;">Offset</th>
<th style="text-align: left; font-weight: normal; border-bottom: solid 1px #888;padding-right:12px;">Length</th>
<th style="text-align: left; font-weight: normal; border-bottom: solid 1px #888;padding-right:12px;">Contents</th>
</tr>
{{{fields}}}
</table>

=== Description ===
{{{description}}}
}}

Template:Packet

2013-12-21T20:34:48Z

O11c: make it a link too </facepalm>

{{#switch: {{{mode}}}
| row =
<tr valign="top"> <td> [[Net:{{{id}}}|{{{id}}}]] </td> <td style="background: {{{alignment|purple}}}"> {{{length}}} </td> <td> {{{nicename}}} </td> <td> {{{define}}} </td> <td> Sent: {{{sent}}} <br/> Parsed: {{{parsed}}} </td> </tr>
| row_internal =
<tr valign="top"> <td> [[Net:{{{id}}}|{{{id}}}]] </td> <td style="background: {{{alignment|purple}}}"> {{{length}}} </td> <td> {{{nicename}}} </td> <td> Sent: {{{sent}}} <br/> Parsed: {{{parsed}}} </td> </tr>
| #default =
[[Dev:TmwAthena Packets|< Back]]
==={{{nicename}}}===
<table style="border: dashed 1px #aac">
<tr><th style="text-align: right">Packet ID:</th><td>[[Net:{{{id}}}|{{{id}}}]</td></tr>
<tr><th style="text-align: right">Packet Length:</th><td style="background: {{{alignment|purple}}}">{{{length}}}</td></tr>
<tr><th style="text-align: right">Client Defined:</th><td>{{{define}}}</td></tr>
<tr><th style="text-align: right">Sent Location(s):</th><td>{{{sent}}}</td></tr>
<tr><th style="text-align: right">Parsed Location(s):</th><td>{{{parsed}}}</td></tr>
</table>

=== Fields ===
<table style="border-collapse: collapse;" cellspacing="0" cellpadding="3">
<tr valign="top">
<th style="text-align: left; font-weight: normal; border-bottom: solid 1px #888;padding-right:12px;">Offset</th>
<th style="text-align: left; font-weight: normal; border-bottom: solid 1px #888;padding-right:12px;">Length</th>
<th style="text-align: left; font-weight: normal; border-bottom: solid 1px #888;padding-right:12px;">Contents</th>
</tr>
{{{fields}}}
</table>

=== Description ===
{{{description}}}
}}

Template:Packet

2013-12-21T20:33:01Z

O11c: add id to make errors obvious

{{#switch: {{{mode}}}
| row =
<tr valign="top"> <td> [[Net:{{{id}}}|{{{id}}}]] </td> <td style="background: {{{alignment|purple}}}"> {{{length}}} </td> <td> {{{nicename}}} </td> <td> {{{define}}} </td> <td> Sent: {{{sent}}} <br/> Parsed: {{{parsed}}} </td> </tr>
| row_internal =
<tr valign="top"> <td> [[Net:{{{id}}}|{{{id}}}]] </td> <td style="background: {{{alignment|purple}}}"> {{{length}}} </td> <td> {{{nicename}}} </td> <td> Sent: {{{sent}}} <br/> Parsed: {{{parsed}}} </td> </tr>
| #default =
[[Dev:TmwAthena Packets|< Back]]
==={{{nicename}}}===
<table style="border: dashed 1px #aac">
<tr><th style="text-align: right">Packet ID:</th><td>{{{id}}}</td></tr>
<tr><th style="text-align: right">Packet Length:</th><td style="background: {{{alignment|purple}}}">{{{length}}}</td></tr>
<tr><th style="text-align: right">Client Defined:</th><td>{{{define}}}</td></tr>
<tr><th style="text-align: right">Sent Location(s):</th><td>{{{sent}}}</td></tr>
<tr><th style="text-align: right">Parsed Location(s):</th><td>{{{parsed}}}</td></tr>
</table>

=== Fields ===
<table style="border-collapse: collapse;" cellspacing="0" cellpadding="3">
<tr valign="top">
<th style="text-align: left; font-weight: normal; border-bottom: solid 1px #888;padding-right:12px;">Offset</th>
<th style="text-align: left; font-weight: normal; border-bottom: solid 1px #888;padding-right:12px;">Length</th>
<th style="text-align: left; font-weight: normal; border-bottom: solid 1px #888;padding-right:12px;">Contents</th>
</tr>
{{{fields}}}
</table>

=== Description ===
{{{description}}}
}}

Net:0x006B

2013-12-16T21:19:14Z

O11c: fix packet number

{{packet
|nicename=Update Character List
|id=0x006B
|mode={{{mode}}}
|length=-1
|alignment=orangered
|define=SMSG_CHAR_LOGIN
|sent={{tmwa location|src/char/char.cpp}}
|parsed={{mana location|src/net/tmwa/charserverhandler.cpp|77}}
|fields=
{{packet field | 0 | 2 | Packet ID }}
{{packet field | 2 | 2 | Packet Length (24 + (106 * CharacterCount) + 0) }}
{{packet field | 4 | 20 | ''Unused'' }}
{{packet field | <br/><hr/> | <br/><hr/> | <strong>Character Subpacket</strong> (Repeated for each character, see also [[Net:0x006D]])<hr/> }}
{{packet field | X+0 | 4 | char id }}
{{packet field | X+4 | 4 | exp }}
{{packet field | X+8 | 4 | zeny }}
{{packet field | X+12 | 4 | job xp }}
{{packet field | X+16 | 4 | job level }}
{{packet field | X+20 | 2 | shoes }}
{{packet field | X+22 | 2 | gloves }}
{{packet field | X+24 | 2 | cape }}
{{packet field | X+26 | 2 | misc1 }}
{{packet field | X+28 | 4 | option }}
{{packet field | X+32 | 4 | karma }}
{{packet field | X+36 | 4 | manner }}
{{packet field | X+40 | 2 | status point }}
{{packet field | X+42 | 2 | hp }}
{{packet field | X+44 | 2 | max hp }}
{{packet field | X+46 | 2 | sp }}
{{packet field | X+48 | 2 | max sp }}
{{packet field | X+50 | 2 | speed, always 150 }}
{{packet field | X+52 | 2 | species }}
{{packet field | X+54 | 2 | hair }}
{{packet field | X+56 | 2 | weapon (always 0) }}
{{packet field | X+58 | 2 | level }}
{{packet field | X+60 | 2 | skill points }}
{{packet field | X+62 | 2 | "head bottom" - legs }}
{{packet field | X+64 | 2 | shield }}
{{packet field | X+66 | 2 | "head top" - helmet }}
{{packet field | X+68 | 2 | "head middle" - torso }}
{{packet field | X+70 | 2 | hair color }}
{{packet field | X+72 | 2 | misc2 (calculated, not stored) }}
{{packet field | X+74 | 24 | name }}
{{packet field | X+98 | 1 | str }}
{{packet field | X+99 | 1 | agi }}
{{packet field | X+100 | 1 | vit }}
{{packet field | X+101 | 1 | int }}
{{packet field | X+102 | 1 | dex }}
{{packet field | X+103 | 1 | luk }}
{{packet field | X+104 | 1 | char num }}
{{packet field | X+105 | 1 | ''unused'' }}
|description=
Sent in response to [[Net:0x0065|Character Server Connection Request]], either directly or via [[Net:0x2713]].

Upon receiving this packet, the client is able to select a character to play with, create a character in a new slot, or deleted an existing character.
}}

Net:0x0067

2013-12-16T21:18:32Z

O11c: fix id

{{packet
|nicename= Create Character Request
|id=0x0067
|mode={{{mode}}}
|length=37
|alignment=white
|define= CMSG_CHAR_CREATE
|sent={{mana location|src/net/tmwa/charserverhandler.cpp|315}}
|parsed={{tmwa location|src/char/char.cpp|2436}}
|fields=
{{packet field | 0 | 2| Packet ID }}
{{packet field | 2 | 24| Char Name }}
{{packet field | 26 | 6| Char Stats }}
{{packet field | 32 | 1| Char Selection Slot }}
{{packet field | 33 | 2| Hair color }}
{{packet field | 35 | 2| Hair Style }}

|description=
Sent by a client to the character server to request the creation of a character and determan the characters name, stats, slot, hair color and hair style.
If it fails to make a new char, sends packet 0x6e;. otherwise, sends packet 0x00.

}}

MediaWiki:Sidebar

2013-12-10T21:38:21Z

O11c: fix manasource downloads link

User talk:Jowalling

2013-12-06T06:35:13Z

O11c: Welcome!

User:Jowalling

2013-12-06T06:35:12Z

O11c: Creating user page for new user.

Studied Basic, Lisp and Cobalt in the 80's. Continued with Lisp, and took courses in C++, followed by Red Had linux administration in the 90's and early 2000's. Got away from Linux for awhile due to daughter and wife and their wicked windows ways. Have returned to Linux completely on my laptop. Getting back into Linux, and would like to help this project in some way.

Archive:TmwAthena Packets

2013-12-06T01:03:33Z

O11c: /* Packet Alignment */ fix orangered example

== Overview ==
=== Packet Alignment ===
The alignment of the data within the packet payload can cause additional overhead if the data is not properly aligned to word boundaries. For example, in a 32-bit application, a word is a sequence of two eight-bit bytes. Any data that occupies 2 bytes or larger on this platform should always start at a (2 * n) offset (0, 2, 4, etc). Any data that is less than 2 bytes can start at any offset, so long as it does not span multiple words. A 16-bit integer could start at offset 0, 2, or 4, but not at 1, 3, or 5 because the first byte would be in one word and the second byte would be in the next word. Single byte words will always fall on word boundaries. The last piece of data should end on a word boundary as well. If any of the data are double words in size, the packet must also be a multiple of the double word size and any double word sized data must fall on a double word boundary.

To leverage the maximum efficiency, padding can be added between pieces of data to force subsequent data to be aligned to word boundaries. For example, if a packet contains a word, and a half word, either the data should be ordered as word, half word, and a half word of padding that will be discarded by the recipient. The same data, ordered as a half word, word, a half word of padding would take up the same amount of space, but the word would span two different words of the packet and cause inefficient processing of that packet.

The following colors are used to indicate the alignment of the packets:

<table>
<tr>
<th> Color Meaning </th>
<th> Examples </th>
</tr>
<tr>
<td style="background: green;">The packet contents and total size are properly aligned.</td>
<td> 2; 2 2; 2 2 4; 2 2 2*N</td>
</tr>
<tr>
<td style="background: chartreuse;">The packet contents are aligned, but they contain a variable-length element that may cause the whole packet to be improperly aligned.</td>
<td> 2 2 1*N</td>
</tr>
<tr>
<td style="background: yellow;">The packet contents are properly aligned, but do not end on a word boundary.</td>
<td> 2 1 ; 2 2 4 1 </td>
</tr>
<tr>
<td style="background: orange;">The packet contents are not properly aligned on word boundaries, but could be with skew padding.</td>
<td> 2 4 2 </td>
</tr>
<tr>
<td style="background: orangered;">The packet contents are not properly aligned if the number of varying elements is at least 2.</td>
<td> 2 2 (2 1)*N</td>
</tr>
<tr>
<td style="background: red;">The packet contents are not properly aligned on word boundaries, even with skew padding.</td>
<td> 2 4 2 4</td>
</tr>
</table>

== Client Packets ==
This is a new table that steal information from individual packet pages.

<table border="1" cellspacing="0" cellpadding="3" class="wikitable sortable">
<tr valign="top">
<th>Packet</th> <th>Length</th> <th>Name</th> <th>Client #define</th> <th>Sent and Parsed Locations</th>
</tr>

{{Net:0x0061|mode=row}}
{{Net:0x0062|mode=row}}
{{Net:0x0063|mode=row}}
{{Net:0x0064|mode=row}}
{{Net:0x0065|mode=row}}
{{Net:0x0066|mode=row}}
{{Net:0x0067|mode=row}}
{{Net:0x0068|mode=row}}
{{Net:0x0069|mode=row}}
{{Net:0x006A|mode=row}}
{{Net:0x006B|mode=row}}
{{Net:0x006C|mode=row}}
{{Net:0x006D|mode=row}}
{{Net:0x006E|mode=row}}
{{Net:0x006F|mode=row}}

{{Net:0x0070|mode=row}}
{{Net:0x0071|mode=row}}
{{Net:0x0072|mode=row}}
{{Net:0x0073|mode=row}}
{{Net:0x0078|mode=row}}
{{Net:0x007B|mode=row}}
{{Net:0x007C|mode=row}}
{{Net:0x007D|mode=row}}
{{Net:0x007E|mode=row}}
{{Net:0x007F|mode=row}}

{{Net:0x0080|mode=row}}
{{Net:0x0081|mode=row}}
{{Net:0x0085|mode=row}}
{{Net:0x0086|mode=row}}
{{Net:0x0087|mode=row}}
{{Net:0x0088|mode=row}}
{{Net:0x0089|mode=row}}
{{Net:0x008A|mode=row}}
{{Net:0x008C|mode=row}}
{{Net:0x008D|mode=row}}
{{Net:0x008E|mode=row}}

{{Net:0x0090|mode=row}}
{{Net:0x0091|mode=row}}
{{Net:0x0092|mode=row}}
{{Net:0x0094|mode=row}}
{{Net:0x0095|mode=row}}
{{Net:0x0096|mode=row}}
{{Net:0x0097|mode=row}}
{{Net:0x0098|mode=row}}
{{Net:0x0099|mode=row}}
{{Net:0x009A|mode=row}}
{{Net:0x009B|mode=row}}
{{Net:0x009C|mode=row}}
{{Net:0x009D|mode=row}}
{{Net:0x009E|mode=row}}
{{Net:0x009F|mode=row}}

{{Net:0x00A0|mode=row}}
{{Net:0x00A1|mode=row}}
{{Net:0x00A2|mode=row}}
{{Net:0x00A4|mode=row}}
{{Net:0x00A6|mode=row}}
{{Net:0x00A7|mode=row}}
{{Net:0x00A8|mode=row}}
{{Net:0x00A9|mode=row}}
{{Net:0x00AA|mode=row}}
{{Net:0x00AB|mode=row}}
{{Net:0x00AC|mode=row}}
{{Net:0x00AF|mode=row}}

{{Net:0x00B0|mode=row}}
{{Net:0x00B1|mode=row}}
{{Net:0x00B2|mode=row}}
{{Net:0x00B3|mode=row}}
{{Net:0x00B4|mode=row}}
{{Net:0x00B5|mode=row}}
{{Net:0x00B6|mode=row}}
{{Net:0x00B7|mode=row}}
{{Net:0x00B8|mode=row}}
{{Net:0x00B9|mode=row}}
{{Net:0x00BB|mode=row}}
{{Net:0x00BC|mode=row}}
{{Net:0x00BD|mode=row}}
{{Net:0x00BE|mode=row}}
{{Net:0x00BF|mode=row}}

{{Net:0x00C0|mode=row}}
{{Net:0x00C1|mode=row}}
{{Net:0x00C2|mode=row}}
{{Net:0x00C3|mode=row}}
{{Net:0x00C4|mode=row}}
{{Net:0x00C5|mode=row}}
{{Net:0x00C6|mode=row}}
{{Net:0x00C7|mode=row}}
{{Net:0x00C8|mode=row}}
{{Net:0x00C9|mode=row}}
{{Net:0x00CA|mode=row}}
{{Net:0x00CB|mode=row}}
{{Net:0x00CC|mode=row}}
{{Net:0x00CD|mode=row}}

{{Net:0x00E4|mode=row}}
{{Net:0x00E5|mode=row}}
{{Net:0x00E6|mode=row}}
{{Net:0x00E7|mode=row}}
{{Net:0x00E8|mode=row}}
{{Net:0x00E9|mode=row}}
{{Net:0x00EB|mode=row}}
{{Net:0x00EC|mode=row}}
{{Net:0x00ED|mode=row}}
{{Net:0x00EE|mode=row}}
{{Net:0x00EF|mode=row}}

{{Net:0x00F0|mode=row}}
{{Net:0x00F2|mode=row}}
{{Net:0x00F3|mode=row}}
{{Net:0x00F4|mode=row}}
{{Net:0x00F5|mode=row}}
{{Net:0x00F6|mode=row}}
{{Net:0x00F7|mode=row}}
{{Net:0x00F8|mode=row}}
{{Net:0x00F9|mode=row}}
{{Net:0x00FA|mode=row}}
{{Net:0x00FB|mode=row}}
{{Net:0x00FC|mode=row}}
{{Net:0x00FD|mode=row}}
{{Net:0x00FE|mode=row}}
{{Net:0x00FF|mode=row}}

{{Net:0x0100|mode=row}}
{{Net:0x0101|mode=row}}
{{Net:0x0102|mode=row}}
{{Net:0x0103|mode=row}}
{{Net:0x0104|mode=row}}
{{Net:0x0105|mode=row}}
{{Net:0x0106|mode=row}}
{{Net:0x0107|mode=row}}
{{Net:0x0108|mode=row}}
{{Net:0x0109|mode=row}}
{{Net:0x010C|mode=row}}
{{Net:0x010E|mode=row}}
{{Net:0x010F|mode=row}}

{{Net:0x0110|mode=row}}
{{Net:0x0112|mode=row}}
{{Net:0x0113|mode=row}}
{{Net:0x0116|mode=row}}
{{Net:0x0119|mode=row}}
{{Net:0x011B|mode=row}}

{{Net:0x0139|mode=row}}
{{Net:0x013A|mode=row}}
{{Net:0x013B|mode=row}}
{{Net:0x013C|mode=row}}

{{Net:0x0141|mode=row}}
{{Net:0x0142|mode=row}}
{{Net:0x0143|mode=row}}
{{Net:0x0146|mode=row}}
{{Net:0x0148|mode=row}}
{{Net:0x0149|mode=row}}
{{Net:0x014C|mode=row}}
{{Net:0x014D|mode=row}}
{{Net:0x014E|mode=row}}
{{Net:0x014F|mode=row}}

{{Net:0x0151|mode=row}}
{{Net:0x0152|mode=row}}
{{Net:0x0153|mode=row}}
{{Net:0x0154|mode=row}}
{{Net:0x0155|mode=row}}
{{Net:0x0156|mode=row}}
{{Net:0x0159|mode=row}}
{{Net:0x015A|mode=row}}
{{Net:0x015B|mode=row}}
{{Net:0x015C|mode=row}}
{{Net:0x015D|mode=row}}
{{Net:0x015E|mode=row}}

{{Net:0x0160|mode=row}}
{{Net:0x0161|mode=row}}
{{Net:0x0162|mode=row}}
{{Net:0x0163|mode=row}}
{{Net:0x0165|mode=row}}
{{Net:0x0166|mode=row}}
{{Net:0x0167|mode=row}}
{{Net:0x0168|mode=row}}
{{Net:0x0169|mode=row}}
{{Net:0x016A|mode=row}}
{{Net:0x016B|mode=row}}
{{Net:0x016C|mode=row}}
{{Net:0x016D|mode=row}}
{{Net:0x016E|mode=row}}
{{Net:0x016F|mode=row}}

{{Net:0x0170|mode=row}}
{{Net:0x0171|mode=row}}
{{Net:0x0172|mode=row}}
{{Net:0x0173|mode=row}}
{{Net:0x0174|mode=row}}
{{Net:0x017E|mode=row}}
{{Net:0x017F|mode=row}}

{{Net:0x0180|mode=row}}
{{Net:0x0181|mode=row}}
{{Net:0x0183|mode=row}}
{{Net:0x0184|mode=row}}
{{Net:0x018A|mode=row}}
{{Net:0x018B|mode=row}}

{{Net:0x0190|mode=row}}
{{Net:0x0195|mode=row}}
{{Net:0x0196|mode=row}}
{{Net:0x019B|mode=row}}
{{Net:0x019C|mode=row}}
{{Net:0x019D|mode=row}}

{{Net:0x01B1|mode=row}}
{{Net:0x01B6|mode=row}}

{{Net:0x01C8|mode=row}}

{{Net:0x01D4|mode=row}}
{{Net:0x01D5|mode=row}}
{{Net:0x01D7|mode=row}}
{{Net:0x01D8|mode=row}}
{{Net:0x01D9|mode=row}}
{{Net:0x01DA|mode=row}}
{{Net:0x01DE|mode=row}}

{{Net:0x01EE|mode=row}}

{{Net:0x01F0|mode=row}}

{{Net:0x020C|mode=row}}



{{Net:0x7530|mode=row}}
{{Net:0x7531|mode=row}}

</table>

== ManaPlus Packets ==
These packets were originally added by ManaPlus to support Evol.

<table border="1" cellspacing="0" cellpadding="3" class="wikitable sortable">
<tr valign="top">
<th>Packet</th> <th>Length</th> <th>Name</th> <th>Client #define</th> <th>Sent and Parsed Locations</th>
</tr>

{{Net:0x0212|mode=row}}

</table>

== Used packets ==
{| border="1" cellspacing="0" cellpadding="3"
|-valign="top"
!packet !! len !! client define !! sent location(s) !! parse location
|-valign="top"
|0x0061 || 50 || CMSG_CHAR_PASSWORD_CHANGE || src/net/tmwa/loginhandler.cpp:264 || src/char/char.c:3036
|-valign="top"
|0x0062 || 3 || SMSG_CHAR_PASSWORD_RESPONSE || src/char/char.c:2368 || src/net/tmwa/loginhandler.cpp:71
|-valign="top"
|0x0063 || -1 || SMSG_UPDATE_HOST || src/login/login.c:3732 || src/net/tmwa/loginhandler.cpp:103
|-valign="top"
|0x0064 || 55 || (hard-coded) || src/net/tmwa/loginhandler.cpp:298 || src/login/login.c:3644
|-valign="top"
|0x0065 || 17 || CMSG_CHAR_SERVER_CONNECT || src/net/tmwa/charserverhandler.cpp:340 || src/char/char.c:3049
|-valign="top"
|0x0066 || 3 || CMSG_CHAR_SELECT || src/net/tmwa/charserverhandler.cpp:283<br>src/char/char.c:3424 || src/char/char.c:3142
|-valign="top"
|0x0067 || 37 || CMSG_CHAR_CREATE || src/net/tmwa/charserverhandler.cpp:291 || src/char/char.c:3312
|-valign="top"
|0x0068 || 46 || CMSG_CHAR_DELETE || src/net/tmwa/charserverhandler.cpp:306 || src/char/char.c:3387
|-valign="top"
|0x0069 || -1 || SMSG_LOGIN_DATA || src/login/login.c:3795 || src/net/tmwa/loginhandler.cpp:114
|-valign="top"
|0x006A || 23 || SMSG_LOGIN_ERROR || src/login/login.c:3683<br>src/login/login.c:3833 || src/net/tmwa/loginhandler.cpp:149
|-valign="top"
|0x006B || -1 || SMSG_CHAR_LOGIN || src/char/char.c:1660 || src/net/tmwa/charserverhandler.cpp:101
|-valign="top"
|0x006C || 3 || SMSG_CHAR_LOGIN_ERROR || src/char/char.c:1948<br>src/char/char.c:1970<br>src/char/char.c:3110<br>src/char/char.c:3133 || src/net/tmwa/charserverhandler.cpp:75
|-valign="top"
|0x006D || 108 || SMSG_CHAR_CREATE_SUCCEEDED || src/char/char.c:3325 || src/net/tmwa/charserverhandler.cpp:118
|-valign="top"
|0x006E || 3 || SMSG_CHAR_CREATE_FAILED || src/char/char.c:3318 || src/net/tmwa/charserverhandler.cpp:137
|-valign="top"
|0x006F || 2 || SMSG_CHAR_DELETE_SUCCEEDED || src/char/char.c:3496 || src/net/tmwa/charserverhandler.cpp:144
|-valign="top"
|0x0070 || 3 || SMSG_CHAR_DELETE_FAILED || src/char/char.c:3156<br>src/char/char.c:3401<br>src/char/char.c:3432<br>src/char/char.c:3504 || src/net/tmwa/charserverhandler.cpp:153
|-valign="top"
|0x0071 || 28 || SMSG_CHAR_MAP_INFO || src/char/char.c:3272 || src/net/tmwa/charserverhandler.cpp:158
|-valign="top"
|0x0072 || 19 || CMSG_MAP_SERVER_CONNECT || src/net/tmwa/gamehandler.cpp:124 || src/map/clif.c:6729
|-valign="top"
|0x0073 || 11 || SMSG_MAP_LOGIN_SUCCESS || src/map/clif.c:609 || src/net/tmwa/gamehandler.cpp:67
|-valign="top"
|0x0078 || 54 || SMSG_BEING_VISIBLE || src/map/clif.c:823<br>src/map/clif.c:1060<br>src/map/clif.c:1185<br>src/map/clif.c:1382 || src/net/tmwa/beinghandler.cpp:121
|-valign="top"
|0x007B || 60 || SMSG_BEING_MOVE || src/map/clif.c:912<br>src/map/clif.c:1122 || src/net/tmwa/beinghandler.cpp:122
|-valign="top"
|0x007C || 41 || SMSG_BEING_SPAWN || src/map/clif.c:1279<br>src/map/clif.c:1347<br>src/map/clif.c:1372<br>src/map/clif.c:1414 || src/net/tmwa/beinghandler.cpp:239
|-valign="top"
|0x007D || 2 || CMSG_MAP_LOADED || src/net/tmwa/gamehandler.cpp:152 || src/map/clif.c:6786
|-valign="top"
|0x007E || 6 || CMSG_CLIENT_PING || src/net/tmwa/gamehandler.cpp:166 || src/map/clif.c:6942
|-valign="top"
|0x007F || 6 || SMSG_SERVER_PING || src/map/clif.c:1445 || src/net/tmwa/gamehandler.cpp:81
|-valign="top"
|0x0080 || 7 || SMSG_BEING_REMOVE || src/map/clif.c:65<br>src/map/clif.c:791 || src/net/tmwa/beinghandler.cpp:273
|-valign="top"
|0x0081 || 3 || SMSG_CONNECTION_PROBLEM || src/login/login.c:3700<br>src/login/login.c:3824<br>src/char/char.c:3264<br>src/map/clif.c:628 || src/net/tmwa/generalhandler.cpp:122
|-valign="top"
|0x0085 || 5 || CMSG_PLAYER_CHANGE_DEST || src/net/tmwa/playerhandler.cpp:621 || src/map/clif.c:6955
|-valign="top"
|0x0086 || 16 || SMSG_BEING_MOVE2 || || src/net/tmwa/beinghandler.cpp:246
|-valign="top"
|0x0087 || 12 || SMSG_WALK_RESPONSE || src/map/clif.c:1463 || src/net/tmwa/playerhandler.cpp:177
|-valign="top"
|0x0088 || 10 || SMSG_PLAYER_STOP || src/map/clif.c:1590 || src/net/tmwa/beinghandler.cpp:630
|-valign="top"
|0x0089 || 7 || CMSG_PLAYER_CHANGE_ACT<br>CMSG_PLAYER_ATTACK || src/net/tmwa/playerhandler.cpp:635<br>src/net/tmwa/playerhandler.cpp:566 || src/map/clif.c:7341
|-valign="top"
|0x008A || 29 || SMSG_BEING_ACTION || src/map/clif.c:3761<br>src/map/clif.c:6563 || src/net/tmwa/beinghandler.cpp:328
|-valign="top"
|0x008C || -1 || CMSG_CHAT_MESSAGE || src/net/tmwa/chathandler.cpp:199 || src/map/clif.c:7173
|-valign="top"
|0x008D || -1 || SMSG_BEING_CHAT || src/map/clif.c:7209<br>src/map/clif.c:7236 || src/net/tmwa/chathandler.cpp:113
|-valign="top"
|0x008E || -1 || SMSG_PLAYER_CHAT || src/map/clif.c:4603<br>src/map/clif.c:7219 || src/net/tmwa/chathandler.cpp:158
|-valign="top"
|0x0090 || 7 || CMSG_NPC_TALK || src/net/tmwa/npchandler.cpp:133 || src/map/clif.c:7738
|-valign="top"
|0x0091 || 22 || SMSG_PLAYER_WARP || src/map/clif.c:1545 || src/net/tmwa/playerhandler.cpp:185
|-valign="top"
|0x0092 || 28 || SMSG_CHANGE_MAP_SERVER || src/map/clif.c:1569 || src/net/tmwa/charserverhandler.cpp:179
|-valign="top"
|0x0094 || 6 || (hard-coded) || src/net/tmwa/beinghandler.cpp:92 || src/map/clif.c:7047
|-valign="top"
|0x0095 || 30 || SMSG_BEING_NAME_RESPONSE || src/map/clif.c:7057 || src/net/tmwa/beinghandler.cpp:484
|-valign="top"
|0x0096 || -1 || CMSG_CHAT_WHISPER || src/net/tmwa/chathandler.cpp:215 || src/map/clif.c:7459
|-valign="top"
|0x0097 || -1 || SMSG_WHISPER || src/map/clif.c:4771 || src/net/tmwa/chathandler.cpp:91
|-valign="top"
|0x0098 || 3 || SMSG_WHISPER_RESPONSE || src/map/clif.c:4785 || src/net/tmwa/chathandler.cpp:72
|-valign="top"
|0x0099 || -1 || CMSG_ADMIN_ANNOUNCE<br>CMSG_CHAT_ANNOUNCE || src/net/tmwa/adminhandler.cpp:84 || src/map/clif.c:7549
|-valign="top"
|0x009A || -1 || SMSG_GM_CHAT || src/map/clif.c:4623<br>src/map/clif.c:8359 || src/net/tmwa/chathandler.cpp:159
|-valign="top"
|0x009B || 5 || CMSG_PLAYER_CHANGE_DIR || src/net/tmwa/playerhandler.cpp:614 || src/map/clif.c:7278
|-valign="top"
|0x009C || 9 || SMSG_BEING_CHANGE_DIRECTION || src/map/clif.c:7293 || src/net/tmwa/beinghandler.cpp:499
|-valign="top"
|0x009D || 17 || SMSG_ITEM_VISIBLE || src/map/clif.c:3815 || src/net/tmwa/itemhandler.cpp:47
|-valign="top"
|0x009E || 17 || SMSG_ITEM_DROPPED || src/map/clif.c:671 || src/net/tmwa/itemhandler.cpp:48
|-valign="top"
|0x009F || 6 || CMSG_ITEM_PICKUP || src/net/tmwa/playerhandler.cpp:607 || src/map/clif.c:7573
|-valign="top"
|0x00A0 || 23 || SMSG_PLAYER_INVENTORY_ADD || src/map/clif.c:1855<br>src/map/clif.c:1876 || src/net/tmwa/inventoryhandler.cpp:218
|-valign="top"
|0x00A1 || 6 || SMSG_ITEM_REMOVE || src/map/clif.c:715 || src/net/tmwa/itemhandler.cpp:61
|-valign="top"
|0x00A2 || 6 || CMSG_PLAYER_INVENTORY_DROP || src/net/tmwa/inventoryhandler.cpp:473 || src/map/clif.c:7613
|-valign="top"
|0x00A4 || -1 || SMSG_PLAYER_EQUIPMENT || src/map/clif.c:2017 || src/net/tmwa/inventoryhandler.cpp:376
|-valign="top"
|0x00A6 || -1 || SMSG_PLAYER_STORAGE_EQUIP || src/map/clif.c:2144<br>src/map/clif.c:2273 || src/net/tmwa/inventoryhandler.cpp:187
|-valign="top"
|0x00A7 || 8 || CMSG_PLAYER_INVENTORY_USE || src/net/tmwa/inventoryhandler.cpp:465 || src/map/clif.c:7640
|-valign="top"
|0x00A8 || 7 || SMSG_ITEM_USE_RESPONSE || src/map/clif.c:2935 || src/net/tmwa/inventoryhandler.cpp:284
|-valign="top"
|0x00A9 || 6 || CMSG_PLAYER_EQUIP || src/net/tmwa/inventoryhandler.cpp:446 || src/map/clif.c:7666
|-valign="top"
|0x00AA || 7 || SMSG_PLAYER_EQUIP || src/map/clif.c:2819 || src/net/tmwa/inventoryhandler.cpp:401
|-valign="top"
|0x00AB || 4 || CMSG_PLAYER_UNEQUIP || src/net/tmwa/inventoryhandler.cpp:456 || src/map/clif.c:7706
|-valign="top"
|0x00AC || 7 || SMSG_PLAYER_UNEQUIP || src/map/clif.c:2839 || src/net/tmwa/inventoryhandler.cpp:412
|-valign="top"
|0x00AF || 6 || SMSG_PLAYER_INVENTORY_REMOVE || src/map/clif.c:1943 || src/net/tmwa/inventoryhandler.cpp:253
|-valign="top"
|0x00B0 || 8 || SMSG_PLAYER_STAT_UPDATE_1 || src/map/clif.c:2350<br>src/map/clif.c:2357 || src/net/tmwa/playerhandler.cpp:234
|-valign="top"
|0x00B1 || 8 || SMSG_PLAYER_STAT_UPDATE_2 || src/map/clif.c:2437<br>src/map/clif.c:2443<br>src/map/clif.c:2447<br>src/map/clif.c:2451<br>src/map/clif.c:2455 || src/net/tmwa/playerhandler.cpp:333
|-valign="top"
|0x00B2 || 3 || CMSG_PLAYER_RESTART || src/net/tmwa/charserverhandler.cpp:314<br>src/net/tmwa/playerhandler.cpp:642 || src/map/clif.c:7411
|-valign="top"
|0x00B3 || 3 || SMSG_CHAR_SWITCH_RESPONSE || src/map/clif.c:653 || src/net/tmwa/gamehandler.cpp:91
|-valign="top"
|0x00B4 || -1 || SMSG_NPC_MESSAGE || src/map/clif.c:1696 || src/net/tmwa/npchandler.cpp:102
|-valign="top"
|0x00B5 || 6 || SMSG_NPC_NEXT || src/map/clif.c:1716 || src/net/tmwa/npchandler.cpp:111
|-valign="top"
|0x00B6 || 6 || SMSG_NPC_CLOSE || src/map/clif.c:1734 || src/net/tmwa/npchandler.cpp:106
|-valign="top"
|0x00B7 || -1 || SMSG_NPC_CHOICE || src/map/clif.c:1752 || src/net/tmwa/npchandler.cpp:97
|-valign="top"
|0x00B8 || 7 || CMSG_NPC_LIST_CHOICE || src/net/tmwa/npchandler.cpp:159 || src/map/clif.c:8194
|-valign="top"
|0x00B9 || 6 || CMSG_NPC_NEXT_REQUEST || src/net/tmwa/npchandler.cpp:140 || src/map/clif.c:8206
|-valign="top"
|0x00BB || 5 || CMSG_STAT_UPDATE_REQUEST || src/net/tmwa/playerhandler.cpp:581 || src/map/clif.c:7993
|-valign="top"
|0x00BC || 6 || SMSG_PLAYER_STAT_UPDATE_4 || src/map/clif.c:2799 || src/net/tmwa/playerhandler.cpp:381
|-valign="top"
|0x00BD || 44 || SMSG_PLAYER_STAT_UPDATE_5 || src/map/clif.c:2702 || src/net/tmwa/playerhandler.cpp:401
|-valign="top"
|0x00BE || 5 || SMSG_PLAYER_STAT_UPDATE_6 || src/map/clif.c:2466 || src/net/tmwa/playerhandler.cpp:521
|-valign="top"
|0x00BF || 3 || CMSG_PLAYER_EMOTE || src/net/tmwa/playerhandler.cpp:573 || src/map/clif.c:7308
|-valign="top"
|0x00C0 || 7 || SMSG_BEING_EMOTION || src/map/clif.c:6469<br>src/map/clif.c:6488<br>src/map/clif.c:7317 || src/net/tmwa/beinghandler.cpp:385
|-valign="top"
|0x00C1 || 2 || CMSG_WHO_REQUEST<br>CMSG_CHAT_WHO || src/map/chathandler.cpp:264 || src/map/clif.c:7330
|-valign="top"
|0x00C2 || 6 || SMSG_WHO_ANSWER || src/map/clif.c:7332 || src/net/tmwa/gamehandler.cpp:86
|-valign="top"
|0x00C3 || 8 || SMSG_BEING_CHANGE_LOOKS || || src/net/tmwa/beinghandler.cpp:400
|-valign="top"
|0x00C4 || 6 || SMSG_NPC_BUY_SELL_CHOICE || src/map/clif.c:1611 || src/net/tmwa/buysellhandler.cpp:64
|-valign="top"
|0x00C5 || 7 || CMSG_NPC_BUY_SELL_REQUEST || src/net/tmwa/npchandler.cpp:193<br>src/net/tmwa/npchandler.cpp:200 || src/map/clif.c:7756
|-valign="top"
|0x00C6 || -1 || SMSG_NPC_BUY || src/map/clif.c:1631 || src/net/tmwa/buysellhandler.cpp:72
|-valign="top"
|0x00C7 || -1 || SMSG_NPC_SELL || src/map/clif.c:1663 || src/net/tmwa/buysellhandler.cpp:88
|-valign="top"
|0x00C8 || -1 || CMSG_NPC_BUY_REQUEST || src/net/tmwa/npchandler.cpp:207 || src/map/clif.c:7765
|-valign="top"
|0x00C9 || -1 || CMSG_NPC_SELL_REQUEST || src/net/tmwa/npchandler.cpp:215 || src/map/clif.c:7784
|-valign="top"
|0x00CA || 3 || SMSG_NPC_BUY_RESPONSE || src/map/clif.c:7775 || src/net/tmwa/buysellhandler.cpp:114
|-valign="top"
|0x00CB || 3 || SMSG_NPC_SELL_RESPONSE || src/map/clif.c:7794 || src/net/tmwa/buysellhandler.cpp:124
|-valign="top"
|0x00CC || 6 || CMSG_ADMIN_KICK || src/net/tmwa/adminhandler.cpp:104 || src/map/clif.c:8913
|-valign="top"
|0x00CD || 6 || SMSG_ADMIN_KICK_ACK || src/map/clif.c:6605 || src/net/tmwa/adminhandler.cpp:62
|-valign="top"
|0x00E4 || 6 || CMSG_TRADE_REQUEST || src/net/tmwa/tradehandler.cpp:241 || src/map/clif.c:7859
|-valign="top"
|0x00E5 || 26 || SMSG_TRADE_REQUEST || src/map/clif.c:3180 || src/net/tmwa/tradehandler.cpp:86
|-valign="top"
|0x00E6 || 3 || CMSG_TRADE_RESPONSE || src/net/tmwa/tradehandler.cpp:250 || src/map/clif.c:7876
|-valign="top"
|0x00E7 || 3 || SMSG_TRADE_RESPONSE || src/map/clif.c:3198 || src/net/tmwa/tradehandler.cpp:120
|-valign="top"
|0x00E8 || 8 || CMSG_TRADE_ITEM_ADD_REQUEST || src/net/tmwa/tradehandler.cpp:256<br>src/net/tmwa/tradehandler.cpp:268 || src/map/clif.c:7887
|-valign="top"
|0x00E9 || 19 || SMSG_TRADE_ITEM_ADD || src/map/clif.c:3218 || src/net/tmwa/tradehandler.cpp:159
|-valign="top"
|0x00EB || 2 || CMSG_TRADE_ADD_COMPLETE || src/net/tmwa/tradehandler.cpp:275 || src/map/clif.c:7898
|-valign="top"
|0x00EC || 3 || SMSG_TRADE_OK || src/map/clif.c:3320 || src/net/tmwa/tradehandler.cpp:218
|-valign="top"
|0x00ED || 2 || CMSG_TRADE_CANCEL_REQUEST || src/net/tmwa/tradehandler.cpp:285 || src/map/clif.c:7907
|-valign="top"
|0x00EE || 2 || SMSG_TRADE_CANCEL || src/map/clif.c:3338 || src/net/tmwa/tradehandler.cpp:223
|-valign="top"
|0x00EF || 2 || CMSG_TRADE_OK || src/net/tmwa/tradehandler.cpp:280 || src/map/clif.c:7916
|-valign="top"
|0x00F0 || 3 || SMSG_TRADE_COMPLETE || src/map/clif.c:3355 || src/net/tmwa/tradehandler.cpp:230
|-valign="top"
|0x00F2 || 6 || SMSG_PLAYER_STORAGE_STATUS || src/map/clif.c:3375<br>src/map/clif.c:3459 || src/net/tmwa/inventoryhandler.cpp:306
|-valign="top"
|0x00F3 || 8 || CMSG_MOVE_TO_STORAGE || src/net/tmwa/inventoryhandler.cpp:508 || src/map/clif.c:8370
|-valign="top"
|0x00F4 || 21 || SMSG_PLAYER_STORAGE_ADD || src/map/clif.c:3396<br>src/map/clif.c:3481 || src/net/tmwa/inventoryhandler.cpp:331
|-valign="top"
|0x00F5 || 8 || CSMG_MOVE_FROM_STORAGE || src/net/tmwa/inventoryhandler.cpp:514 || src/map/clif.c:8393
|-valign="top"
|0x00F6 || 8 || SMSG_PLAYER_STORAGE_REMOVE || src/map/clif.c:3543 || src/net/tmwa/inventoryhandler.cpp:353
|-valign="top"
|0x00F7 || 2 || CMSG_CLOSE_STORAGE || src/net/tmwa/inventoryhandler.cpp:500 || src/map/clif.c:8452
|-valign="top"
|0x00F8 || 2 || SMSG_PLAYER_STORAGE_CLOSE || src/map/clif.c:3562 || src/net/tmwa/inventoryhandler.cpp:365
|-valign="top"
|0x00F9 || 26 || CMSG_PARTY_CREATE || src/net/tmwa/partyhandler.cpp:313 || src/map/clif.c:8469
|-valign="top"
|0x00FA || 3 || SMSG_PARTY_CREATE || src/map/clif.c:5231 || src/net/tmwa/partyhandler.cpp:79
|-valign="top"
|0x00FB || -1 || SMSG_PARTY_INFO || src/map/clif.c:5249 || src/net/tmwa/partyhandler.cpp:88
|-valign="top"
|0x00FC || 6 || CMSG_PARTY_INVITE || src/net/tmwa/partyhandler.cpp:324 || src/map/clif.c:8510
|-valign="top"
|0x00FD || 27 || SMSG_PARTY_INVITE_RESPONSE || src/map/clif.c:5327 || src/net/tmwa/partyhandler.cpp:112
|-valign="top"
|0x00FE || 30 || SMSG_PARTY_INVITED || src/map/clif.c:5299 || src/net/tmwa/partyhandler.cpp:139
|-valign="top"
|0x00FF || 10 || CMSG_PARTY_INVITED || src/net/tmwa/partyhandler.cpp:352 || src/map/clif.c:8522
|-valign="top"
|0x0100 || 2 || CMSG_PARTY_LEAVE || src/net/tmwa/partyhandler.cpp:359 || src/map/clif.c:8540
|-valign="top"
|0x0101 || 6 || SMSG_PARTY_SETTINGS || src/map/clif.c:5358 || src/net/tmwa/partyhandler.cpp:157
|-valign="top"
|0x0102 || 6 || CMSG_PARTY_SETTINGS || src/net/tmwa/partyhandler.cpp:402<br>src/net/tmwa/partyhandler.cpp:412 || src/map/clif.c:8558
|-valign="top"
|0x0103 || 30 || CMSG_PARTY_KICK || src/net/tmwa/partyhandler.cpp:364<br>src/net/tmwa/partyhandler.cpp:379 || src/map/clif.c:8549
|-valign="top"
|0x0104 || 79 || SMSG_PARTY_MOVE || src/map/clif.c:5485 || src/net/tmwa/partyhandler.cpp:220
|-valign="top"
|0x0105 || 31 || SMSG_PARTY_LEAVE || src/map/clif.c:5383 || src/net/tmwa/partyhandler.cpp:232
|-valign="top"
|0x0106 || 10 || SMSG_PARTY_UPDATE_HP || src/map/clif.c:5463 || src/net/tmwa/partyhandler.cpp:263
|-valign="top"
|0x0107 || 10 || SMSG_PARTY_UPDATE_COORDS || src/map/clif.c:5443 || src/net/tmwa/partyhandler.cpp:283
|-valign="top"
|0x0108 || -1 || CMSG_PARTY_MESSAGE || src/net/tmwa/partyhandler.cpp:386 || src/map/clif.c:8571
|-valign="top"
|0x0109 || -1 || SMSG_PARTY_MESSAGE || src/map/clif.c:5424 || src/net/tmwa/partyhandler.cpp:290
|-valign="top"
|0x010C || 6 || SMSG_MVP || src/map/clif.c:5708 || src/net/tmwa/chathandler.cpp:187
|-valign="top"
|0x010E || 11 || SMSG_PLAYER_SKILL_UP<br>SMSG_GUILD_SKILL_UP || src/map/clif.c:4186<br>src/map/clif.c:6345 || src/net/tmwa/specialhandler.cpp:115<br>src/net/tmwa/guildhandler.cpp:253
|-valign="top"
|0x010F || -1 || SMSG_PLAYER_SKILLS || src/map/clif.c:4145 || src/net/tmwa/specialhandler.cpp:93
|-valign="top"
|0x0110 || 10 || SMSG_SKILL_FAILED || src/map/clif.c:4259 || src/net/tmwa/specialhandler.cpp:129
|-valign="top"
|0x0112 || 4 || CMSG_SKILL_LEVELUP_REQUEST || src/net/tmwa/playerhandler.cpp:597 || src/map/clif.c:8002
|-valign="top"
|0x0113 || 10 || CMSG_SKILL_USE_BEING || src/net/tmwa/specialhandler.cpp:234 || src/map/clif.c:8011
|-valign="top"
|0x0116 || 10 || CMSG_SKILL_USE_POSITION || src/net/tmwa/specialhandler.cpp:242 || src/map/clif.c:8088
|-valign="top"
|0x0119 || 13 || SMSG_PLAYER_STATUS_CHANGE || src/map/clif.c:1268<br>src/map/clif.c:2885 || src/net/tmwa/beinghandler.cpp:671
|-valign="top"
|0x011B || 20 || CMSG_SKILL_USE_MAP || src/net/tmwa/specialhandler.cpp:251 || src/map/clif.c:8158
|-valign="top"
|0x0139 || 16 || SMSG_PLAYER_MOVE_TO_ATTACK || src/map/clif.c:5510 || src/net/tmwa/beinghandler.cpp:662
|-valign="top"
|0x013A || 4 || SMSG_PLAYER_ATTACK_RANGE || src/map/clif.c:2474 || src/net/tmwa/inventoryhandler.cpp:423
|-valign="top"
|0x013B || 4 || SMSG_PLAYER_ARROW_MESSAGE || src/map/clif.c:2780 || src/net/tmwa/playerhandler.cpp:545
|-valign="top"
|0x013C || 4 || SMSG_PLAYER_ARROW_EQUIP || src/map/clif.c:2761 || src/net/tmwa/inventoryhandler.cpp:427
|-valign="top"
|0x0141 || 14 || SMSG_PLAYER_STAT_UPDATE_3 || src/map/clif.c:2482<br>src/map/clif.c:2489<br>src/map/clif.c:2496<br>src/map/clif.c:2503<br>src/map/clif.c:2510<br>src/map/clif.c:2517 || src/net/tmwa/playerhandler.cpp:370
|-valign="top"
|0x0142 || 6 || SMSG_NPC_INT_INPUT || src/map/clif.c:1772 || src/net/tmwa/npchandler.cpp:116
|-valign="top"
|0x0143 || 10 || CMSG_NPC_INT_RESPONSE || src/net/tmwa/npchandler.cpp:166 || src/map/clif.c:8215
|-valign="top"
|0x0146 || 6 || CMSG_NPC_CLOSE || src/net/tmwa/npchandler.cpp:146 || src/map/clif.c:8265
|-valign="top"
|0x0148 || 8 || SMSG_BEING_RESURRECT || src/map/clif.c:4667 || src/net/tmwa/beinghandler.cpp:293
|-valign="top"
|0x0149 || 9 || CMSG_ADMIN_MUTE || src/net/tmwa/adminhandler.cpp:137 || src/map/clif.c:9025
|-valign="top"
|0x014C || -1 || SMSG_GUILD_ALIANCE_INFO || src/map/clif.c:5962 || src/net/tmwa/guildhandler.cpp:157
|-valign="top"
|0x014D || 2 || CMSG_GUILD_CHECK_MASTER || || src/map/clif.c:8661
|-valign="top"
|0x014E || 6 || SMSG_GUILD_MASTER_OR_MEMBER || src/map/clif.c:5842 || src/net/tmwa/guildhandler.cpp:134
|-valign="top"
|0x014F || 6 || CMSG_GUILD_REQUEST_INFO || src/net/tmwa/guildhandler.cpp:457 || src/map/clif.c:8670
|-valign="top"
|0x0151 || 6 || CMSG_GUILD_REQUEST_EMBLEM || || src/map/clif.c:8760
|-valign="top"
|0x0152 || -1 || SMSG_GUILD_EMBLEM || src/map/clif.c:6135 || src/net/tmwa/guildhandler.cpp:243
|-valign="top"
|0x0153 || -1 || CMSG_GUILD_CHANGE_EMBLEM || || src/map/clif.c:8771
|-valign="top"
|0x0154 || -1 || SMSG_GUILD_MEMBER_LIST || src/map/clif.c:5996 || src/net/tmwa/guildhandler.cpp:171
|-valign="top"
|0x0155 || -1 || CMSG_GUILD_CHANGE_MEMBER_POS || || src/map/clif.c:8731
|-valign="top"
|0x0156 || -1 || SMSG_GUILD_MEMBER_POS_CHANGE || src/map/clif.c:6110 || src/net/tmwa/guildhandler.cpp:236
|-valign="top"
|0x0159 || 54 || CMSG_GUILD_LEAVE || src/net/tmwa/guildhandler.cpp:425 || src/map/clif.c:8807
|-valign="top"
|0x015A || 66 || SMSG_GUILD_LEAVE || src/map/clif.c:6252 || src/net/tmwa/guildhandler.cpp:322
|-valign="top"
|0x015B || 54 || CMSG_GUILD_EXPULSION || src/net/tmwa/guildhandler.cpp:434 || src/map/clif.c:8817
|-valign="top"
|0x015C || 90 || SMSG_GUILD_EXPULSION || src/map/clif.c:6270 || src/net/tmwa/guildhandler.cpp:327
|-valign="top"
|0x015D || 42 || CMSG_GUILD_BREAK || || src/map/clif.c:8907
|-valign="top"
|0x015E || 6 || SMSG_GUILD_BROKEN || src/map/clif.c:6453 || src/net/tmwa/guildhandler.cpp:384
|-valign="top"
|0x0160 || -1 || SMSG_GUILD_POS_INFO_LIST || src/map/clif.c:6062 || src/net/tmwa/guildhandler.cpp:212
|-valign="top"
|0x0161 || -1 || CMSG_GUILD_CHANGE_POS_INFO || || src/map/clif.c:8704
|-valign="top"
|0x0162 || -1 || SMSG_GUILD_SKILL_INFO || src/map/clif.c:6160 || src/net/tmwa/guildhandler.cpp:253
|-valign="top"
|0x0163 || -1 || SMSG_GUILD_EXPULSION_LIST || src/map/clif.c:6294 || src/net/tmwa/guildhandler.cpp:333
|-valign="top"
|0x0165 || 30 || CMSG_GUILD_CREATE || src/net/tmwa/guildhandler.cpp:396 || src/map/clif.c:8652
|-valign="top"
|0x0166 || -1 || SMSG_GUILD_POS_NAME_LIST || src/map/clif.c:6036 || src/net/tmwa/guildhandler.cpp:199
|-valign="top"
|0x0167 || 3 || SMSG_GUILD_CREATE_RESPONSE || src/map/clif.c:5771 || src/net/tmwa/guildhandler.cpp:91
|-valign="top"
|0x0168 || 14 || CMSG_GUILD_INVITE || src/net/tmwa/guildhandler.cpp:408 || src/map/clif.c:8789
|-valign="top"
|0x0169 || 3 || SMSG_GUILD_INVITE_ACK || src/map/clif.c:6235 || src/net/tmwa/guildhandler.cpp:288
|-valign="top"
|0x016A || 30 || SMSG_GUILD_INVITE || src/map/clif.c:6217 || src/net/tmwa/guildhandler.cpp:279
|-valign="top"
|0x016B || 10 || CMSG_GUILD_INVITE_REPLY || src/net/tmwa/guildhandler.cpp:416 || src/map/clif.c:8798
|-valign="top"
|0x016C || 43 || SMSG_GUILD_POSITION_INFO || src/map/clif.c:5792 || src/net/tmwa/guildhandler.cpp:114
|-valign="top"
|0x016D || 14 || SMSG_GUILD_MEMBER_LOGIN || src/map/clif.c:5811 || src/net/tmwa/guildhandler.cpp:128
|-valign="top"
|0x016E || 186 || CMSG_GUILD_CHANGE_NOTICE || || src/map/clif.c:8780
|-valign="top"
|0x016F || 182 || SMSG_GUILD_NOTICE || src/map/clif.c:6198 || src/net/tmwa/guildhandler.cpp:274
|-valign="top"
|0x0170 || 14 || CMSG_GUILD_ALLIANCE_REQUEST || || src/map/clif.c:8871
|-valign="top"
|0x0171 || 30 || SMSG_GUILD_REQ_ALLIANCE || src/map/clif.c:6367 || src/net/tmwa/guildhandler.cpp:366
|-valign="top"
|0x0172 || 10 || CMSG_GUILD_ALLIANCE_REPLY || || src/map/clif.c:8880
|-valign="top"
|0x0173 || 3 || SMSG_GUILD_REQ_ALLIANCE_ACK || src/map/clif.c:6385 || src/net/tmwa/guildhandler.cpp:371
|-valign="top"
|0x0174 || -1 || SMSG_GUILD_POSITION_CHANGED || src/map/clif.c:6087 || src/net/tmwa/guildhandler.cpp:227
|-valign="top"
|0x017E || -1 || CMSG_GUILD_MESSAGE || src/net/tmwa/guildhandler.cpp:443 || src/map/clif.c:8831
|-valign="top"
|0x017F || -1 || SMSG_GUILD_MESSAGE || src/map/clif.c:6323<br>src/map/clif.c:6581 || src/net/tmwa/guildhandler.cpp:347
|-valign="top"
|0x0180 || 6 || CMSG_GUILD_OPPOSITION || || src/map/clif.c:8898
|-valign="top"
|0x0181 || 3 || SMSG_GUILD_OPPOSITION_ACK || src/map/clif.c:6421 || src/net/tmwa/guildhandler.cpp:380
|-valign="top"
|0x0183 || 10 || CMSG_GUILD_ALLIANCE_DELETE || || src/map/clif.c:8889
|-valign="top"
|0x0184 || 10 || SMSG_GUILD_DEL_ALLIANCE || src/map/clif.c:6403 || src/net/tmwa/guildhandler.cpp:375
|-valign="top"
|0x018A || 4 || CMSG_CLIENT_QUIT || src/net/tmwa/gamehandler.cpp:161 || src/map/clif.c:6611
|-valign="top"
|0x018B || 4 || SMSG_MAP_QUIT_RESPONSE || src/map/clif.c:7012<br>src/map/clif.c:7440 || src/net/tmwa/gamehandler.cpp:98
|-valign="top"
|0x0190 || 90 || CMSG_SKILL_USE_POSITION_MORE || || src/map/clif.c:8088
|-valign="top"
|0x0195 || 102 || SMSG_PLAYER_GUILD_PARTY_INFO || src/map/clif.c:7107 || src/net/tmwa/beinghandler.cpp:490
|-valign="top"
|0x0196 || 9 || SMSG_BEING_STATUS_CHANGE || src/map/clif.c:4585 || src/net/tmwa/beinghandler.cpp:688
|-valign="top"
|0x019B || 10 || SMSG_BEING_SELFEFFECT || src/map/clif.c:2858<br>src/map/clif.c:6696 || src/net/tmwa/beinghandler.cpp:372
|-valign="top"
|0x019C || 4 || CMSG_ADMIN_LOCAL_ANNOUNCE || src/net/tmwa/adminhandler.cpp:91 || src/map/clif.c:8350
|-valign="top"
|0x019D || 6 || CMSG_ADMIN_HIDE || src/net/tmwa/adminhandler.cpp:98 || src/map/clif.c:8996
|-valign="top"
|0x01B1 || 7 || SMSG_TRADE_ITEM_ADD_RESPONSE || src/map/clif.c:3299 || src/net/tmwa/tradehandler.cpp:176
|-valign="top"
|0x01B6 || 114 || SMSG_GUILD_BASIC_INFO || src/map/clif.c:5865 || src/net/tmwa/guildhandler.cpp:138
|-valign="top"
|0x01C8 || 13 || SMSG_PLAYER_INVENTORY_USE || src/map/clif.c:2945 || src/net/tmwa/inventoryhandler.cpp:265
|-valign="top"
|0x01D4 || 6 || SMSG_NPC_STR_INPUT || src/map/clif.c:1790 || src/net/tmwa/npchandler.cpp:121
|-valign="top"
|0x01D5 || 8 || CMSG_NPC_STR_RESPONSE || src/net/tmwa/npchandler.cpp:173 || src/map/clif.c:8234
|-valign="top"
|0x01D7 || 11 || SMSG_BEING_CHANGE_LOOKS2 || src/map/clif.c:2608<br>src/map/clif.c:2675 || src/net/tmwa/beinghandler.cpp:401
|-valign="top"
|0x01D8 || 54 || SMSG_PLAYER_UPDATE_1 || src/map/clif.c:845 || src/net/tmwa/beinghandler.cpp:511
|-valign="top"
|0x01D9 || 53 || SMSG_PLAYER_UPDATE_2 || src/map/clif.c:1292 || src/net/tmwa/beinghandler.cpp:512
|-valign="top"
|0x01DA || 60 || SMSG_PLAYER_MOVE || src/map/clif.c:934 || src/net/tmwa/beinghandler.cpp:513
|-valign="top"
|0x01DE || 33 || SMSG_SKILL_DAMAGE || src/map/clif.c:4298 || src/net/tmwa/beinghandler.cpp:311
|-valign="top"
|0x01EE || -1 || SMSG_PLAYER_INVENTORY || src/map/clif.c:1965 || src/net/tmwa/inventoryhandler.cpp:134
|-valign="top"
|0x01F0 || -1 || SMSG_PLAYER_STORAGE_ITEMS || src/map/clif.c:2097<br>src/map/clif.c:2225 || src/net/tmwa/inventoryhandler.cpp:135
|-valign="top"
|0x020C || 10 || SMSG_ADMIN_IP || src/map/clif.c:7120 || src/net/tmwa/adminhandler.cpp:69
|-valign="top"
|0x7530 || 2 || CMSG_SERVER_VERSION_REQUEST || src/net/tmwa/loginhandler.cpp:220 || src/login/login.c:2257<br>src/login/login.c:4011<br>src/char/char.c:3568<br>src/map/clif.c:10174
|-valign="top"
|0x7531 || 10 || SMSG_SERVER_VERSION_RESPONSE || src/login/login.c:2260<br>src/login/login.c:4014<br>src/char/char.c:3569<br>src/map/clif.c:10175 || src/net/tmwa/loginhandler.cpp:197

|}

== Free Packets ==
These are packets that are not parsed or sent by the client, but have a known length, so they can be used by future servers and the client will just ignore them, not crash.

{| border="1" cellspacing="0" cellpadding="3"
|- valign="top"
!packet !!len !!notes
|- valign="top"
|0x0000 ||10 ||
|- valign="top"
|0x0074 ||3 ||
|- valign="top"
|0x0075 ||-1 ||
|- valign="top"
|0x0076 ||9 ||
|- valign="top"
|0x0077 ||5 ||
|- valign="top"
|0x0079 ||53 ||
|- valign="top"
|0x007A ||58 ||
|- valign="top"
|0x0082 ||2 ||
|- valign="top"
|0x0083 ||2 ||
|- valign="top"
|0x0084 ||2 ||
|- valign="top"
|0x008B ||23 ||
|- valign="top"
|0x0093 ||2 ||
|- valign="top"
|0x00A3 ||-1 ||
|- valign="top"
|0x00A5 ||-1 ||
|- valign="top"
|0x00AE ||-1 ||
|- valign="top"
|0x00BA ||2 ||
|- valign="top"
|0x00CE ||2 ||
|- valign="top"
|0x00CF ||27 ||clif_parse_PMIgnore
|- valign="top"
|0x00D0 ||3 ||clif_parse_PMIgnoreAll, used by ManaPlus
|- valign="top"
|0x00D1 ||4 ||
|- valign="top"
|0x00D2 ||4 ||used by ManaPlus (sent from atcommand.cpp)
|- valign="top"
|0x00D3 ||2 ||
|- valign="top"
|0x00D4 ||-1 ||
|- valign="top"
|0x00D5 ||-1 ||clif_parse_CreateChatRoom
|- valign="top"
|0x00D6 ||3 ||
|- valign="top"
|0x00D7 ||-1 ||
|- valign="top"
|0x00D8 ||6 ||
|- valign="top"
|0x00D9 ||14 ||clif_parse_ChatAddMember
|- valign="top"
|0x00DA ||3 ||
|- valign="top"
|0x00DB ||-1 ||
|- valign="top"
|0x00DC ||28 ||
|- valign="top"
|0x00DD ||29 ||
|- valign="top"
|0x00DE ||-1 ||clif_parse_ChatRoomStatusChange
|- valign="top"
|0x00DF ||-1 ||
|- valign="top"
|0x00E0 ||30 ||clif_parse_ChangeChatOwner
|- valign="top"
|0x00E1 ||30 ||
|- valign="top"
|0x00E2 ||26 ||clif_parse_KickFromChat
|- valign="top"
|0x00E3 ||2 ||clif_parse_ChatLeave
|- valign="top"
|0x00EA ||5 ||
|- valign="top"
|0x00F1 ||2 ||
|- valign="top"
|0x010A ||4 ||
|- valign="top"
|0x010B ||6 ||
|- valign="top"
|0x010D ||2 ||clif_parse_RequestMemo
|- valign="top"
|0x0111 ||39 ||
|- valign="top"
|0x0114 ||31 ||
|- valign="top"
|0x0115 ||35 ||
|- valign="top"
|0x0117 ||18 ||
|- valign="top"
|0x0118 ||2 ||clif_parse_StopAttack, used by ManaPlus
|- valign="top"
|0x011A ||15 ||SMSG_SKILL_NO_DAMAGE, used by ManaPlus
|- valign="top"
|0x011C ||68 ||
|- valign="top"
|0x011D ||2 ||clif_parse_RequestMemo
|- valign="top"
|0x011E ||3 ||
|- valign="top"
|0x011F ||16 ||
|- valign="top"
|0x0120 ||6 ||
|- valign="top"
|0x0121 ||14 ||
|- valign="top"
|0x0122 ||-1 ||
|- valign="top"
|0x0123 ||-1 ||
|- valign="top"
|0x0124 ||21 ||
|- valign="top"
|0x0125 ||8 ||
|- valign="top"
|0x0126 ||8 ||clif_parse_PutItemToCart
|- valign="top"
|0x0127 ||8 ||clif_parse_GetItemFromCart
|- valign="top"
|0x0128 ||8 ||clif_parse_MoveFromKafraToCart
|- valign="top"
|0x0129 ||8 ||clif_parse_MoveToKafraFromCart
|- valign="top"
|0x012A ||2 ||clif_parse_RemoveOption
|- valign="top"
|0x012B ||2 ||
|- valign="top"
|0x012C ||3 ||
|- valign="top"
|0x012D ||4 ||
|- valign="top"
|0x012E ||2 ||
|- valign="top"
|0x012F ||-1 ||
|- valign="top"
|0x0130 ||6 ||
|- valign="top"
|0x0131 ||86 ||
|- valign="top"
|0x0132 ||6 ||
|- valign="top"
|0x0133 ||-1 ||
|- valign="top"
|0x0134 ||-1 ||
|- valign="top"
|0x0135 ||7 ||
|- valign="top"
|0x0136 ||-1 ||
|- valign="top"
|0x0137 ||6 ||
|- valign="top"
|0x0138 ||3 ||
|- valign="top"
|0x013D ||6 ||
|- valign="top"
|0x013E ||24 ||SMSG_SKILL_CASTING, used by ManaPlus
|- valign="top"
|0x013F ||26 ||clif_parse_GM_Monster_Item
|- valign="top"
|0x0140 ||22 ||clif_parse_MapMove
|- valign="top"
|0x0144 ||23 ||
|- valign="top"
|0x0145 ||19 ||
|- valign="top"
|0x0147 ||39 ||
|- valign="top"
|0x014A ||6 ||
|- valign="top"
|0x014B ||27 ||
|- valign="top"
|0x0150 ||110 ||
|- valign="top"
|0x0157 ||6 ||
|- valign="top"
|0x0158 ||-1 ||
|- valign="top"
|0x015F ||42 ||
|- valign="top"
|0x0164 ||-1 ||
|- valign="top"
|0x0175 ||6 ||
|- valign="top"
|0x0176 ||106 ||
|- valign="top"
|0x0177 ||-1 ||
|- valign="top"
|0x0178 ||4 ||clif_parse_ItemIdentify
|- valign="top"
|0x0179 ||5 ||
|- valign="top"
|0x017A ||4 ||clif_parse_UseCard
|- valign="top"
|0x017B ||-1 ||
|- valign="top"
|0x017C ||6 ||clif_parse_InsertCard
|- valign="top"
|0x017D ||7 ||
|- valign="top"
|0x0182 ||106 ||
|- valign="top"
|0x0185 ||34 ||
|- valign="top"
|0x0187 ||6 ||src/char/char.c:3562
|- valign="top"
|0x0188 ||8 ||
|- valign="top"
|0x0189 ||4 ||
|- valign="top"
|0x018C ||29 ||
|- valign="top"
|0x018D ||-1 ||
|- valign="top"
|0x018E ||10 ||
|- valign="top"
|0x018F ||6 ||
|- valign="top"
|0x0191 ||86 ||
|- valign="top"
|0x0192 ||24 ||
|- valign="top"
|0x0193 ||6 ||clif_parse_SolveCharName
|- valign="top"
|0x0194 ||30 ||
|- valign="top"
|0x0197 ||4 ||clif_parse_ResetChar
|- valign="top"
|0x0198 ||8 ||
|- valign="top"
|0x0199 ||4 ||SMSG_PVP_MAP_MODE, used by ManaPlus
|- valign="top"
|0x019A ||14 ||SMSG_PVP_SET, used by ManaPlus
|- valign="top"
|0x019E ||2 ||
|- valign="top"
|0x019F ||6 ||
|- valign="top"
|0x01A0 ||3 ||
|- valign="top"
|0x01A1 ||3 ||
|- valign="top"
|0x01A2 ||35 ||
|- valign="top"
|0x01A3 ||5 ||
|- valign="top"
|0x01A4 ||11 ||
|- valign="top"
|0x01A5 ||26 ||
|- valign="top"
|0x01A6 ||-1 ||
|- valign="top"
|0x01A7 ||4 ||
|- valign="top"
|0x01A8 ||4 ||
|- valign="top"
|0x01A9 ||6 ||
|- valign="top"
|0x01AA ||10 ||
|- valign="top"
|0x01AB ||12 ||
|- valign="top"
|0x01AC ||6 ||
|- valign="top"
|0x01AD ||-1 ||
|- valign="top"
|0x01AE ||4 ||
|- valign="top"
|0x01AF ||4 ||clif_parse_ChangeCart
|- valign="top"
|0x01B0 ||11 ||
|- valign="top"
|0x01B2 ||-1 ||
|- valign="top"
|0x01B3 ||67 ||
|- valign="top"
|0x01B4 ||12 ||
|- valign="top"
|0x01B5 ||18 ||
|- valign="top"
|0x01B7 ||6 ||
|- valign="top"
|0x01B8 ||3 ||
|- valign="top"
|0x01B9 ||6 ||SMSG_SKILL_CAST_CANCEL, used by ManaPlus
|- valign="top"
|0x01BA ||26 ||clif_parse_Shift
|- valign="top"
|0x01BB ||26 ||clif_parse_Shift
|- valign="top"
|0x01BC ||26 ||clif_parse_Recall
|- valign="top"
|0x01BD ||26 ||clif_parse_Recall
|- valign="top"
|0x01BE ||2 ||
|- valign="top"
|0x01BF ||3 ||
|- valign="top"
|0x01C0 ||2 ||
|- valign="top"
|0x01C1 ||14 ||
|- valign="top"
|0x01C2 ||10 ||
|- valign="top"
|0x01C3 ||-1 ||
|- valign="top"
|0x01C4 ||22 ||
|- valign="top"
|0x01C5 ||22 ||
|- valign="top"
|0x01C6 ||4 ||
|- valign="top"
|0x01C7 ||2 ||
|- valign="top"
|0x01C9 ||97 ||
|- valign="top"
|0x01CB ||9 ||
|- valign="top"
|0x01CC ||9 ||
|- valign="top"
|0x01CD ||29 ||
|- valign="top"
|0x01CE ||6 ||clif_parse_AutoSpell
|- valign="top"
|0x01CF ||28 ||
|- valign="top"
|0x01D0 ||8 ||
|- valign="top"
|0x01D1 ||14 ||
|- valign="top"
|0x01D2 ||10 ||
|- valign="top"
|0x01D3 ||35 ||
|- valign="top"
|0x01D6 ||4 ||
|- valign="top"
|0x01DB ||2 ||src/login/login.c:3861
|- valign="top"
|0x01DC ||-1 ||src/login/login.c:3898
|- valign="top"
|0x01DD ||47 ||src/login/login.c:3645
|- valign="top"
|0x01DF ||6 ||clif_parse_GMReqNoChatCount
|- valign="top"
|0x01E0 ||30 ||
|- valign="top"
|0x01E1 ||8 ||
|- valign="top"
|0x01E2 ||34 ||
|- valign="top"
|0x01E3 ||14 ||
|- valign="top"
|0x01E4 ||2 ||
|- valign="top"
|0x01E5 ||6 ||
|- valign="top"
|0x01E6 ||26 ||
|- valign="top"
|0x01E7 ||2 ||clif_parse_sn_doridori
|- valign="top"
|0x01E8 ||28 ||clif_parse_CreateParty2
|- valign="top"
|0x01E9 ||81 ||
|- valign="top"
|0x01EA ||6 ||
|- valign="top"
|0x01EB ||10 ||
|- valign="top"
|0x01EC ||26 ||
|- valign="top"
|0x01ED ||2 ||clif_parse_sn_explosionspirits
|- valign="top"
|0x01EF ||-1 ||
|- valign="top"
|0x01F1 ||-1 ||
|- valign="top"
|0x01F2 ||20 ||
|- valign="top"
|0x01F3 ||10 ||
|- valign="top"
|0x01F4 ||32 ||
|- valign="top"
|0x01F5 ||9 ||
|- valign="top"
|0x01F6 ||34 ||
|- valign="top"
|0x01F7 ||14 ||
|- valign="top"
|0x01F8 ||2 ||
|- valign="top"
|0x01F9 ||6 ||
|- valign="top"
|0x01FA ||48 ||
|- valign="top"
|0x01FB ||56 ||
|- valign="top"
|0x01FC ||-1 ||
|- valign="top"
|0x01FD ||4 ||
|- valign="top"
|0x01FE ||5 ||
|- valign="top"
|0x01FF ||10 ||
|- valign="top"
|0x0200 ||26 ||src/login/login.c:3632
|- valign="top"
|0x0204 ||18 ||src/login/login.c:3638
|- valign="top"
|0x020B ||19 ||src/char/char.c:3030
|}

== Internal Packets ==
These packets are sent between the servers. Details are subject to change without notice.

=== login - char ===
<table border="1" cellspacing="0" cellpadding="3" class="wikitable sortable">
<tr valign="top">
<th>Packet</th> <th>Length</th> <th>Name</th> <th>Sent and Parsed Locations</th>
</tr>

{{Net:0x2716|mode=row_internal}}
{{Net:0x2717|mode=row_internal}}
{{Net:0x2740|mode=row_internal}}
{{Net:0x2741|mode=row_internal}}
</table>

=== login - admin ===
<table border="1" cellspacing="0" cellpadding="3" class="wikitable sortable">
<tr valign="top">
<th>Packet</th> <th>Length</th> <th>Name</th> <th>Sent and Parsed Locations</th>
</tr>


</table>

=== char - map ===
<table border="1" cellspacing="0" cellpadding="3" class="wikitable sortable">
<tr valign="top">
<th>Packet</th> <th>Length</th> <th>Name</th> <th>Sent and Parsed Locations</th>
</tr>


</table>

==== inter.cpp recv ====
<table>
<tr> <td> 0x3000 </td> <td> -1 </td> </tr>
<tr> <td> 0x3001 </td> <td> -1 </td> </tr>
<tr> <td> 0x3002 </td> <td> 7 </td> </tr>
<tr> <td> 0x3003 </td> <td> -1 </td> </tr>
<tr> <td> 0x3004 </td> <td> -1 </td> </tr>
<tr> <td> 0x3005 </td> <td> 6 </td> </tr>
<tr> <td> 0x3010 </td> <td> 6 </td> </tr>
<tr> <td> 0x3011 </td> <td> -1 </td> </tr>
<tr> <td> 0x3018 </td> <td> 10 </td> </tr>
<tr> <td> 0x3019 </td> <td> -1 </td> </tr>
<tr> <td> 0x3020 </td> <td> 72 </td> </tr>
<tr> <td> 0x3021 </td> <td> 6 </td> </tr>
<tr> <td> 0x3022 </td> <td> 52 </td> </tr>
<tr> <td> 0x3023 </td> <td> 14 </td> </tr>
<tr> <td> 0x3024 </td> <td> 10 </td> </tr>
<tr> <td> 0x3025 </td> <td> 29 </td> </tr>
<tr> <td> 0x3026 </td> <td> 6 </td> </tr>
<tr> <td> 0x3027 </td> <td> -1 </td> </tr>
<tr> <td> 0x3028 </td> <td> 34 </td> </tr>
<tr> <td> 0x3030 </td> <td> -1 </td> </tr>
<tr> <td> 0x3031 </td> <td> 6 </td> </tr>
<tr> <td> 0x3032 </td> <td> -1 </td> </tr>
<tr> <td> 0x3034 </td> <td> 55 </td> </tr>
<tr> <td> 0x3035 </td> <td> 19 </td> </tr>
<tr> <td> 0x3036 </td> <td> 6 </td> </tr>
<tr> <td> 0x3037 </td> <td> -1 </td> </tr>
<tr> <td> 0x3038 </td> <td> 14 </td> </tr>
<tr> <td> 0x3039 </td> <td> -1 </td> </tr>
<tr> <td> 0x303a </td> <td> -1 </td> </tr>
<tr> <td> 0x303b </td> <td> -1 </td> </tr>
<tr> <td> 0x303c </td> <td> 14 </td> </tr>
<tr> <td> 0x303d </td> <td> 19 </td> </tr>
<tr> <td> 0x303e </td> <td> 186 </td> </tr>
<tr> <td> 0x303f </td> <td> -1 </td> </tr>
<tr> <td> 0x3040 </td> <td> 5 </td> </tr>
<tr> <td> 0x3041 </td> <td> 9 </td> </tr>
<tr> <td> 0x3080 </td> <td> 48 </td> </tr>
<tr> <td> 0x3081 </td> <td> 14 </td> </tr>
<tr> <td> 0x3082 </td> <td> -1 </td> </tr>
<tr> <td> 0x3083 </td> <td> 6 </td> </tr>
</table>

==== intif.cpp recv ====
<table>
<tr> <td> 0x3800 </td> <td> -1 </td> </tr>
<tr> <td> 0x3801 </td> <td> -1 </td> </tr>
<tr> <td> 0x3802 </td> <td> 27 </td> </tr>
<tr> <td> 0x3803 </td> <td> -1 </td> </tr>
<tr> <td> 0x3804 </td> <td> -1 </td> </tr>
<tr> <td> 0x3810 </td> <td> -1 </td> </tr>
<tr> <td> 0x3811 </td> <td> 7 </td> </tr>
<tr> <td> 0x3818 </td> <td> -1 </td> </tr>
<tr> <td> 0x3819 </td> <td> 11 </td> </tr>
<tr> <td> 0x3820 </td> <td> 35 </td> </tr>
<tr> <td> 0x3821 </td> <td> -1 </td> </tr>
<tr> <td> 0x3822 </td> <td> 11 </td> </tr>
<tr> <td> 0x3823 </td> <td> 15 </td> </tr>
<tr> <td> 0x3824 </td> <td> 34 </td> </tr>
<tr> <td> 0x3825 </td> <td> 29 </td> </tr>
<tr> <td> 0x3826 </td> <td> 7 </td> </tr>
<tr> <td> 0x3827 </td> <td> -1 </td> </tr>
<tr> <td> 0x3830 </td> <td> 10 </td> </tr>
<tr> <td> 0x3831 </td> <td> -1 </td> </tr>
<tr> <td> 0x3832 </td> <td> 15 </td> </tr>
<tr> <td> 0x3834 </td> <td> 79 </td> </tr>
<tr> <td> 0x3835 </td> <td> 19 </td> </tr>
<tr> <td> 0x3836 </td> <td> 7 </td> </tr>
<tr> <td> 0x3837 </td> <td> -1 </td> </tr>
<tr> <td> 0x3839 </td> <td> -1 </td> </tr>
<tr> <td> 0x383a </td> <td> -1 </td> </tr>
<tr> <td> 0x383b </td> <td> -1 </td> </tr>
<tr> <td> 0x383c </td> <td> 14 </td> </tr>
<tr> <td> 0x383d </td> <td> 67 </td> </tr>
<tr> <td> 0x383e </td> <td> 186 </td> </tr>
<tr> <td> 0x383f </td> <td> -1 </td> </tr>
<tr> <td> 0x3840 </td> <td> 9 </td> </tr>
<tr> <td> 0x3841 </td> <td> 9 </td> </tr>
<tr> <td> 0x3842 </td> <td> -1 </td> </tr>
<tr> <td> 0x3880 </td> <td> 11 </td> </tr>
<tr> <td> 0x3881 </td> <td> -1 </td> </tr>
<tr> <td> 0x3882 </td> <td> 7 </td> </tr>
<tr> <td> 0x3883 </td> <td> 3 </td> </tr>
</table>

==== chrif.cpp recv ====
<table>
<tr> <td> 0x2af8 </td> <td> 60 </td> </tr>
<tr> <td> 0x2af9 </td> <td> 3 </td> </tr>
<tr> <td> 0x2afa </td> <td> 10 </td> </tr>
<tr> <td> 0x2afb </td> <td> 27 </td> </tr>
<tr> <td> 0x2afc </td> <td> 22 </td> </tr>
<tr> <td> 0x2afd </td> <td> -1 </td> </tr>
<tr> <td> 0x2afe </td> <td> 6 </td> </tr>
<tr> <td> 0x2aff </td> <td> -1 </td> </tr>
<tr> <td> 0x2b00 </td> <td> 6 </td> </tr>
<tr> <td> 0x2b01 </td> <td> -1 </td> </tr>
<tr> <td> 0x2b02 </td> <td> 18 </td> </tr>
<tr> <td> 0x2b03 </td> <td> 7 </td> </tr>
<tr> <td> 0x2b04 </td> <td> -1 </td> </tr>
<tr> <td> 0x2b05 </td> <td> 49 </td> </tr>
<tr> <td> 0x2b06 </td> <td> 44 </td> </tr>
<tr> <td> 0x2b08 </td> <td> 6 </td> </tr>
<tr> <td> 0x2b09 </td> <td> 30 </td> </tr>
<tr> <td> 0x2b0a </td> <td> -1 </td> </tr>
<tr> <td> 0x2b0b </td> <td> 10 </td> </tr>
<tr> <td> 0x2b0c </td> <td> 86 </td> </tr>
<tr> <td> 0x2b0d </td> <td> 7 </td> </tr>
<tr> <td> 0x2b0e </td> <td> 44 </td> </tr>
<tr> <td> 0x2b0f </td> <td> 34 </td> </tr>
<tr> <td> 0x2b10 </td> <td> -1 </td> </tr>
<tr> <td> 0x2b11 </td> <td> -1 </td> </tr>
<tr> <td> 0x2b12 </td> <td> 10 </td> </tr>
<tr> <td> 0x2b13 </td> <td> 6 </td> </tr>
<tr> <td> 0x2b14 </td> <td> 11 </td> </tr>
<tr> <td> 0x2b15 </td> <td> -1 </td> </tr>
</table>

==== char.cpp recv ====
<table>

</table>

User talk:Gshlvr

2013-12-04T00:45:41Z

O11c: Welcome!

User:Gshlvr

2013-12-04T00:45:39Z

O11c: Creating user page for new user.

Ron is a young adult male born in Florida, USA and currently residing in the Tampa Bay area of Florida. He is in the process of acquiring his Associates degree with a focus on engineering and hopes to one day be employed in the computer software industry.

His interests include art, horticulture, political science, biology, philosophy, technology, linguistics and futurology.

User talk:Oddshocks

2013-11-29T19:30:45Z

O11c: Welcome!

User:Oddshocks

2013-11-29T19:30:44Z

O11c: Creating user page for new user.

David Gay is a free software hacker living in Rochester, NY. He will complete his bachelor's degree in Information Technology at Rochester Institute of Technology mid-2014, whereupon he plans to move to Seattle, WA. David is an avid supporter of free and open source software and is a captain at the RIT Lab for Technological Literacy, AKA the FOSSBox. He also does independent web development contracting. When he isn't being pestered by silly coursework, he enjoys writing code, reading about software, and listening to jam rock bands like the Grateful Dead. He has already contributed a thing or two to The Mana World, but hopes to do much more in the future as he gets a feel for the game.

Set up a Server

2013-11-21T20:57:11Z

O11c: replace yet another outdated "how to" page with a link to the real one

#REDIRECT [[Dev:How to Develop]]