Core - Revision history

Teo: /* Special Case: Avatar BPs */

2019-10-19T00:46:45Z

‎Special Case: Avatar BPs

Teo: relocate Avatar ability notes to be near the other ability notes..

2019-10-18T23:03:58Z

relocate Avatar ability notes to be near the other ability notes..

Teo: /* Abilities */

2017-06-09T19:00:25Z

‎Abilities

Teo: indent cleanup so example code actually aligns properly on the page

2015-08-29T00:47:21Z

indent cleanup so example code actually aligns properly on the page

Bluekirby0: /* Mob Pools */

2012-08-07T07:15:54Z

‎Mob Pools

Bluekirby0: /* Packets(/src/map/packets) */

2012-08-07T07:14:53Z

‎Packets(/src/map/packets)

Kegsay: /* Database */

2012-07-24T23:35:07Z

‎Database

Kegsay: /* Connect Server (aka Lobby Server) */

2012-07-23T21:15:08Z

‎Connect Server (aka Lobby Server)

Kegsay: /* Search Server */

2012-07-23T21:07:40Z

‎Search Server

Kegsay at 20:58, 23 July 2012

2012-07-23T20:58:09Z

@@ Line 114: / Line 114: @@
 * abilities.sql - The animation field is actually the MP cost.
 * abilities.sql - The recast ID is either 173 or 174 for BP:Rage or BP:Ward
-* abilities.sql - The ability ID is found in POLUtils (String Tables > English > Ability Names). It is the ''index'' in POLUtils - 16.
+* abilities.sql - The ability ID is found in rom\181\72.dat (String Tables > English > Ability Names in polutils).
 * mob_skills.sql - The family ID is the ID of the family of monsters (duh, so Avatar-Titan, Avatar-Garuda, etc).
-* mob_skills.sql - The mob_skill_id is found in monster_tp_movies.txt in /documentation/
+* mob_skills.sql - The mob_skill_id is found in rom/27/80.dat (Dialog Tables > English > Monster Skill Names in polutils) and documented in /documentation/monster_tp_moves.txt
 * mob_skills.sql - The mob_anim_time is actually the related ability ID (so Whispering Wind should be 578 as the ability ID for it is that).
 * mob_skills.sql - The mob_anim_id is the hard one and has to be packet captured or got via trial and error. The other avatar anim_ids are close in value to the current ones.

@@ Line 109: / Line 109: @@
 * '''recastId''' : The recast ID for this ability, I think the recast plugin on Windower has the IDs for this in their XML files?
 * '''animation''' : The animation ID to use for this ability. This has to be wizarded via packet captures or trial and error, I don't think this can be obtained automatically.
 === BCNM Info ===
@@ Line 206: / Line 216: @@
 === Traits ===
 * '''traitid''' : The unique client-side trait ID. Find these values in ROM/181/72 (or String Tables > English > Ability Names in POLUtils and go waaay down to 385+). These are 384 offset, so you must SUBTRACT 384 from the "index" field in POLUtils to get these values.
 == Flow of Control ==
 Possibly the most important thing to understand is how the server (map server in particular) actually works in terms of actual work performed based on a given input. Several examples will be examined to see how the server flows through the files mentioned above to get to the packet to send back. See [[Server Data Flow]].

@@ Line 87: / Line 87: @@
 === Abilities ===
-* '''Ability ID''' : The unique ID assigned by the client for this ability. Find these values in ROM/181/72 (or String Tables > English > Ability Names in POLUtils). These IDs are 16 offset, so you must SUBTRACT 16 from the "index" field in POLUtils.
+* '''Ability ID''' : The unique ID assigned by the client for this ability. Find these values in ROM/181/72 (or String Tables > English > Ability Names in POLUtils). These IDs are 528 offset, so you must SUBTRACT 528 from the "index" field in POLUtils.
 * '''Job''' : The unique Job ID assigned by the client. This is the same as for scripting, so WAR=1 MNK=2 WHM=3 ...
 * '''validTarget''' : This is a bitmask of the valid targets, given by the enum in battleentity.h

@@ Line 93: / Line 93: @@
   enum TARGETTYPE
+  {
-  	TARGET_SELF				= 0x01,
+      TARGET_SELF            = 0x01,
-  	TARGET_PLAYER_PARTY		= 0x02,
+      TARGET_PLAYER_PARTY    = 0x02,
-  	TARGET_ENEMY			= 0x04,
+      TARGET_ENEMY           = 0x04,
-  	TARGET_PLAYER_ALLIANCE	= 0x08,
+      TARGET_PLAYER_ALLIANCE = 0x08,
-  	TARGET_PLAYER			= 0x10,
+      TARGET_PLAYER          = 0x10,
-  	TARGET_PLAYER_DEAD		= 0x20,
+      TARGET_PLAYER_DEAD     = 0x20,
-  	TARGET_NPC				= 0x40
+      TARGET_NPC             = 0x40
   };
@@ Line 131: / Line 131: @@
   enum SPAWNTYPE
+  {
-    SPAWNTYPE_NORMAL		= 0x00,     // 00:00-24:00
+      SPAWNTYPE_NORMAL        = 0x00, // 00:00-24:00
-    SPAWNTYPE_ATNIGHT		= 0x01,     // 20:00-04:00
+      SPAWNTYPE_ATNIGHT       = 0x01, // 20:00-04:00
-     SPAWNTYPE_ATEVENING		= 0x02,     // 18:00-06:00
+      SPAWNTYPE_ATEVENING     = 0x02, // 18:00-06:00
-    SPAWNTYPE_WEATHER		= 0x04,
+      SPAWNTYPE_WEATHER       = 0x04,
-    SPAWNTYPE_FOG			= 0x08,     // 02:00-07:00
+      SPAWNTYPE_FOG           = 0x08, // 02:00-07:00
-     SPAWNTYPE_MOONPHASE		= 0x10,
+      SPAWNTYPE_MOONPHASE     = 0x10,
-    SPAWNTYPE_LOTTERY		= 0x20,
+      SPAWNTYPE_LOTTERY       = 0x20,
-    SPAWNTYPE_WINDOWED		= 0x40,
+      SPAWNTYPE_WINDOWED      = 0x40,
-    SPAWNTYPE_SCRIPTED		= 0x80
+      SPAWNTYPE_SCRIPTED      = 0x80
   };
@@ Line 147: / Line 147: @@
   enum BEHAVIOUR
+  {
-    BEHAVIOUR_NONE				= 0x00,
+      BEHAVIOUR_NONE              = 0x00,
-    BEHAVIOUR_AGGRO_SIGHT		= 0x01,
+      BEHAVIOUR_AGGRO_SIGHT       = 0x01,
-     BEHAVIOUR_AGGRO_HEARING		= 0x02,
+      BEHAVIOUR_AGGRO_HEARING     = 0x02,
-    BEHAVIOUR_AGGRO_LOWHP		= 0x04,
+      BEHAVIOUR_AGGRO_LOWHP       = 0x04,
-    BEHAVIOUR_AGGRO_TRUEHEARING	= 0x08,
+      BEHAVIOUR_AGGRO_TRUEHEARING = 0x08,
-    BEHAVIOUR_AGGRO_TRUESIGHT	= 0x10,
+      BEHAVIOUR_AGGRO_TRUESIGHT   = 0x10,
-    BEHAVIOUR_AGGRO_MAGIC		= 0x20,
+      BEHAVIOUR_AGGRO_MAGIC       = 0x20,
-    BEHAVIOUR_AGGRO_WEAPONSKILL	= 0x40,
+      BEHAVIOUR_AGGRO_WEAPONSKILL = 0x40,
-    BEHAVIOUR_AGGRO_JOBABILITY	= 0x80,
+      BEHAVIOUR_AGGRO_JOBABILITY  = 0x80,
 };
@@ Line 162: / Line 162: @@
   enum MOBTYPE
+  {
-    MOBTYPE_NORMAL			= 0x00,
+      MOBTYPE_NORMAL      = 0x00,
-    MOBTYPE_PCSPAWNED		= 0x01,
+      MOBTYPE_PCSPAWNED   = 0x01,
-    MOBTYPE_NOTORIOUS		= 0x02,
+      MOBTYPE_NOTORIOUS   = 0x02,
-    MOBTYPE_FISHED			= 0x04,
+      MOBTYPE_FISHED      = 0x04,
-    MOBTYPE_CALLED			= 0x08,
+      MOBTYPE_CALLED      = 0x08,
-    MOBTYPE_BATTLEFIELD		= 0x10,
+      MOBTYPE_BATTLEFIELD = 0x10,
-    MOBTYPE_EVENT			= 0x20
+      MOBTYPE_EVENT       = 0x20
   };
@@ Line 191: / Line 191: @@
   enum EFFECTFLAG
+  {
-    EFFECTFLAG_NONE             = 0x0000,
+      EFFECTFLAG_NONE             = 0x0000,
-    EFFECTFLAG_DISPELABLE       = 0x0001,
+      EFFECTFLAG_DISPELABLE       = 0x0001,
-    EFFECTFLAG_ERASABLE         = 0x0002,
+      EFFECTFLAG_ERASABLE         = 0x0002,
-    EFFECTFLAG_ATTACK           = 0x0004,
+      EFFECTFLAG_ATTACK           = 0x0004,
-−
-    EFFECTFLAG_DAMAGE           = 0x0010,
+      EFFECTFLAG_DAMAGE           = 0x0010,
-    EFFECTFLAG_DEATH            = 0x0020,
+      EFFECTFLAG_DEATH            = 0x0020,
-    EFFECTFLAG_MAGIC_BEGIN      = 0x0040,
+      EFFECTFLAG_MAGIC_BEGIN      = 0x0040,
-    EFFECTFLAG_MAGIC_END        = 0x0080,
+      EFFECTFLAG_MAGIC_END        = 0x0080,
-    EFFECTFLAG_ON_ZONE          = 0x0100,
+      EFFECTFLAG_ON_ZONE          = 0x0100,
-    EFFECTFLAG_NO_LOSS_MESSAGE  = 0x0200,     // Suppress effect worn off message.
+      EFFECTFLAG_NO_LOSS_MESSAGE  = 0x0200, // Suppress effect worn off message.
 };

@@ Line 143: / Line 143: @@
 === Mob Pools ===
-* '''modelid''' : This is the unique model ID that this monster represents. This has to be captured from packets, so see [[Packets/0x0e]].
+* '''modelid''' : This is the unique model ID that this monster represents. This has to be captured from packet 0x0e.
 * '''behavior''' : This is a lovely mis-spelling of 'behaviour'. It is also a bitmask which represents how the monster should behave:
   enum BEHAVIOUR

@@ Line 45: / Line 45: @@
 === Packets(/src/map/packets) ===
-This defines the packet structures that will be sent to the client. If an update breaks FFXI, this is where you have to go to fix it (because the packet strucutres have changed!). This is a VERY meaty section, so has its own section.
+This defines the packet structures that will be sent to the client. If an update breaks FFXI, this is where you have to go to fix it (because the packet strucutres have changed!).
-−
-[[Packets]]
 === Other (/src/map) ===

@@ Line 76: / Line 76: @@
 The Lobby Server is a magical server whereby almost certainly a wizard did it. It consists of three distinct sub-servers (for some reason) which don't always get along. This is the least documented server and one of the more obfuscated ones. The three processes are discussed below (but not in that much detail)
-=== 1 ===
+=== login_parse ===
-=== 2 ===
+=== lobbyview_parse ===
-=== 3 ===
+=== lobbydata_parse ===
 == Database ==

@@ Line 66: / Line 66: @@
 === Searching ===
 === Auction House ===
 == Connect Server (aka Lobby Server) ==

@@ Line 173: / Line 173: @@
 * '''mob_skill_id''' : The unique ID that governs this monsters skill. This can be found in trunk/documentation/mob_tp_movies.txt or via the DATs.
 * '''mob_anim_id''' : The unique animation ID that represents this skill. This is found by trial and error or via packet capturing.
-* ''mob_skill_aoe''' : 0 for non-aoe, 1 for AoE around SELF(monster), 2 for AoE around TARGET(think bomb toss), 4 for conal AoE (not-implemented),
+* '''mob_skill_aoe''' : 0 for non-aoe, 1 for AoE around SELF(monster), 2 for AoE around TARGET(think bomb toss), 4 for conal AoE (not-implemented),
 === NPC List ===
@@ Line 198: / Line 198: @@
      EFFECTFLAG_NO_LOSS_MESSAGE  = 0x0200,     // Suppress effect worn off message.
 };
 == Flow of Control ==
-Possibly the most important thing to understand is how the server (map server in particular) actually works in terms of actual work performed based on a given input. Several examples will be examined to see how the server flows through the files mentioned above to get to the packet to send back.
+Possibly the most important thing to understand is how the server (map server in particular) actually works in terms of actual work performed based on a given input. Several examples will be examined to see how the server flows through the files mentioned above to get to the packet to send back. See [[Server Data Flow]].