Netherworld Research - User contributions [en]

Main Page

2018-09-30T13:00:01Z

FireFly: Add "main NIS games" (fsvo 'main') + their ports; specifically, add D2 and D5 as they already have pages

A wiki in which we reverse engineer NIS's shit

Spoiler: it often ''is'' shit

We mainly hang out on IRC, in '''#disgaea''' on Badnik (''irc.badnik.zone''). Currently (FSVO 'currently') focusing on understanding Disgaea 1 better.

== Games ==
* [[Rhapsody: A Musical Adventure]] (PS1, DS)
* [[La Pucelle: Tactics]] (PS2, PSP)
* [[Disgaea 1]] (PS2, PSP, [[Disgaea 1/DS|DS]], PC, Switch, PS4, TTHM)
* [[Phantom Brave]] (PS2, Wii, PSP, PC)
* [[Makai Kingdom]] (PS2, PSP)
* [[Disgaea 2]] (PS2, PSP, PC)
* [[Disgaea 3]] (PS3, Vita)
* [[Disgaea 4]] (PS3, Vita)
* [[Disgaea D2]] (PS3)
* [[Disgaea 5]] (PS4, Switch, PC)

== I want to edit ==
PM xkeeper on IRC then.

== See also ==
* [[Project:Resources|Links and resources]] - more information about Disgaea and other NIS titles

Disgaea 1/DS

2018-09-30T12:51:18Z

FireFly: Expand on the 'why' of D1DS's differences

Disgaea 1 got ported to the Nintendo DS, aptly named '''Disgaea DS'''.

As far as game engine internals go, DS probably has the most differences compared to the other ports. This is most noticeable in the low-resolution sprites, lack of voice acting, etc. Presumably the main reason for these changes is to save space, since the DS game fits on a 16 MiB cartridge (compared to the full CD-rom of the original game).

* [[/File tree]] shows an overview of the romfs.
* The [[MPDS format]] is used for maps in this port (compressed [[MPD format|MPD files]])

[[Category:Games]]

Table files (D1DS)

2018-01-20T21:27:55Z

FireFly: Document mitem.dat structure

'''Table files''' are files describing properties and statistics of various entities inside the game, e.g. items, classes or characters. Each file essentially corresponds to a database table, with rows and columns, or (probably more true to the actual implementation) a row count followed by an array of some struct, with that many elements.

This page documents the structs for the various table files inside [[D1DS]].

Each table starts with the number of rows, as a u32, sometimes repeated twice for seemingly no good reason. (One ugly way to deal with this is to start by reading two u32's, and then seek back 4 bytes if they're equal.)

== char.dat ==
Holds character/class data.

<pre>
struct {
char name[19];
char title[19];
u8 type; // 0 = Static? (cutscene/geo); 3 = Usable in-battle; 4 = Prinny; 6 = Prism Red (Doll)
u8 unk1;
u8 pad1;
u8 gender; // 1 = Male; 2 = Female; 11 = Male (generic); 12 = Female (generic); 13 = Other (generic)
u8 unk2;
u8 tier; // "Tier" into class/colour palette index
u8 magic_rate; // Rate of specials acquisition, judging by http://ningyokan.nisfan.net/game/disgaea/usa/usa-units3.html
u8 jump;

struct {
u8 fist, sword, spear, bow, gun, axe, staff;
} wpn_mastery;
u8 pad2;

struct {
u8 hp, sp, atk, def, int, spd, hit, res;
} aptitude;

u16 immunity; // Bitfield of immunities (0 for most, 255 for Divine Majin)
u16 id;
u16 family; // Seemingly corresponds to row in "create character" screen, e.g. Male/Female Brawler kept separate, but mages are grouped, as are skulls.
u16 unk3; // (always 100)
u16 unk4; // (always 20)
u16 throw;
u16 help; // (Key into charhelp.dat) Help entry text for this character, or 0.

struct {
u16 hp, sp, atk, def, int, spd, hit, res;
} base_stats;

u16 unk5; // (always 5)
u16 move_range;
u16 move_class; // 0 = normal; 1 = flying; 2 = warping
u16 unk6; // (always 1)
u16 unk7;
u16 unk8;
u16 unk9; // (always 10)
u8 pad3[4];
u16 unk10;
u16 counter;

u16 magic[32]; // (Key into magic.dat) Special index, for specials learned by this char/class, or 0 for unused.
u16 magic_lvl[32]; // Level at which character learns the corresponding special
};
</pre>

== charhelp.dat ==
Class help descriptions. These are shown in the "create character" screen, and so the table file includes strings that aren't ever shown in-game (e.g. for story characters or enemies).

<pre>
struct {
u16 id;
char description[62];
};
</pre>

== dungeon.dat ==
Gatekeeper warp data, powering the warp menu.

<pre>
struct {
char name[18];
u8 pad;
u16 id;
u16 talk; // talk.dat entry to execute when map is selected from warp menu
};
</pre>

== ge.dat ==
Geo effects.

<pre>
struct {
char name[21];
char description[57];
u16 id;
};
</pre>

== geocube.dat ==
Geocube effects (multiplayer).

<pre>
struct {
u8 id;
u8 unk1;
u8 unk2;
u8 unk3;
u16 unk4;
char name[17];
char description[65];
};
</pre>

== habit.dat ==
Item inhabitants.

<pre>
struct {
u32 unk1;
char name[21];
u8 pad1[1];
u16 id;
u8[20] item_chance; // Chance to appear in an item, by item class. Which element corresponds to which item class isn't known exactly.
// My best guess: ? Fist Sword Spear Bow Gun Axe Staff Monster ? Armor Belt Shoes Orb Glasses Muscle ? ? EX ?
u8 pad2[1];
};
</pre>

== hospital.dat ==
Hospital rewards, with minimum requirements.

<pre>
struct {
u16 id;
u16 req_deceased;
u32 item; // (Key into mitem.dat) Item to obtain
u32 req_hp;
u32 req_sp;
};
</pre>

== magic.dat ==
Specials/spells.

<pre>
struct {
u16 id;
u16 wpn_level; // Min. weapon skill level to unlock, if unlocked by weapon
u16 power; // Determines damage (TBD: how?)
u16 sp; // Base SP cost (TBD: determine growth curve)
char name[17];
char description[57];
u16 unk1; // ??
u8 effect_param[5]; // Parameter to skill effect (see below)
u8 wpn_type; // 0 = not weapon tied; 1 = fist; 2 = sword; 3 = spear; 4 = bow; 5 = gun; 6 = axe
u8 element; // 0 = none; 1 = fire; 2 = wind; 3 = ice; 4 = star
u8 spell_class; // 2 = melee; 3 = magic; 4 = heal; 5 = buff; 6 = debuff
u8 wpn_type_2; // (copy of wpn_type)
u8 range;
u8 pattern; // Attack pattern, complex, see below
u8 range_up; // Attack range vertically, constraints on height difference between tiles
u8 range_down;
u8 effect[5]; // Attack effects (see below), or 0 for no effect
};
</pre>

Some of these fields warrant additional explanation. The ''effect'' and ''effect_param'' fields allow up to 5 effects to be associated with a spell. Known effect numbers are listed below.

{| class="wikitable"
! # !! Description
|-
| 1 || ?
|-
| 2 || ?
|-
| 11 || Atk +n%
|-
| 12 || Def +n%
|-
| 13 || Res +n%
|-
| 14 || Int +n%
|-
| 21 || Poison (n = % chance to inflict)
|-
| 22 || Sleep
|-
| 23 || Paralyze
|-
| 24 || Amnesia
|-
| 25 || Deprave
|-
| 101 || Cure ailments (n=?)
|-
| 102 || HP Drain
|-
| 104 || Self-destruct
|}

The ''pattern'' field describes the attack pattern (which tiles are targeted relative to the user, etc). (TBD: document these.)

== mitem.dat ==
Item table.

<pre>
struct {
u32 price;
u16 id;

struct {
u16 hp, sp, atk, def, int, spd, hit, res;
} base_stats;

char name[17];
char description[81];
u8 rank;
u8 range;
u8 jump;
u8 icon;
u8 type; // (see below)
u8 movement;
u8 ailment; // 21 = poison; 22 = sleep; 23 = paralyze; 24 = amnesia; 25 = deprave
u8 pad1[1];
};
</pre>

The following item types are known.
{| class="wikitable"
! # !! Name
|-
| 1 || Wpn/Fist
|-
| 2 || Wpn/Sword
|-
| 3 || Wpn/Spear
|-
| 4 || Wpn/Bow
|-
| 5 || Wpn/Gun
|-
| 6 || Wpn/Axe
|-
| 7 || Wpn/Staff
|-
| 8 || Wpn/Monster
|-
| 10 || Armor/Armor
|-
| 11 || Armor/Belt
|-
| 12 || Armor/Shoes
|-
| 13 || Armor/Orb
|-
| 14 || Armor/Glasses
|-
| 15 || Armor/Muscle
|-
| 18 || Etc/EX
|-
| 19 || Etc/Symbol
|-
| 20 || Etc/Use
|-
| 21 || Etc/Special (Hand)
|-
| 22 || Etc/Special (Gency)
|}

== musicshop.dat ==
Song list for the music shop.

<pre>
struct {
u32 price;
u8 pad1[4];
u16 id;
u16 song_id; // Uncertain
char name[21];
char title[65];
u16 options; // 0 = locked; 1 = starts unlocked; 3 = starts unlocked & default selected
};
</pre>

== thief.dat ==
Stat stealing entries.

<pre>
struct {
char name[21];
u16 type; // 0 = steal HP; 1 = SP; 2 = Atk; 3 = Def; 4 = Int; 5 = Spd; 6 = Hit; 7 = Res; 10 = Exp; 11 = HL?
u8 pad1[1];
u32 unk1; // (always 1)
};
</pre>

== wish.dat ==
Dark Assembly bills.

<pre>
struct {
u32 mana;
u8 id;
u16 rank; // Min. rank required to reveal bill
i8 skew; // Skews senators' general opinion on the bill, -100 to +100 (higher is more favourable)
char name[31];
char description[53];
};
</pre>

== zukan.dat ==
Bestiary entries.

<pre>
struct {
u16 id;
u16 class_id;
char name[21];
char line1[45];
char line2[45];
char line3[45];
char line4[45];
char line5[45];
char line6[45];
char line7[45];
char line8[45];
u8 pad1[3];
};
</pre>

== External links ==
* [https://docs.google.com/spreadsheets/d/1QuShaZsuQe1cRybufzAFD97f6xQ0JlLXDIvsynusxZc/edit?usp=sharing D1DS table files in spreadsheet form]

Table files (D1DS)

2018-01-20T21:19:06Z

FireFly: Document magic.dat structure

'''Table files''' are files describing properties and statistics of various entities inside the game, e.g. items, classes or characters. Each file essentially corresponds to a database table, with rows and columns, or (probably more true to the actual implementation) a row count followed by an array of some struct, with that many elements.

This page documents the structs for the various table files inside [[D1DS]].

Each table starts with the number of rows, as a u32, sometimes repeated twice for seemingly no good reason. (One ugly way to deal with this is to start by reading two u32's, and then seek back 4 bytes if they're equal.)

== char.dat ==
Holds character/class data.

<pre>
struct {
char name[19];
char title[19];
u8 type; // 0 = Static? (cutscene/geo); 3 = Usable in-battle; 4 = Prinny; 6 = Prism Red (Doll)
u8 unk1;
u8 pad1;
u8 gender; // 1 = Male; 2 = Female; 11 = Male (generic); 12 = Female (generic); 13 = Other (generic)
u8 unk2;
u8 tier; // "Tier" into class/colour palette index
u8 magic_rate; // Rate of specials acquisition, judging by http://ningyokan.nisfan.net/game/disgaea/usa/usa-units3.html
u8 jump;

struct {
u8 fist, sword, spear, bow, gun, axe, staff;
} wpn_mastery;
u8 pad2;

struct {
u8 hp, sp, atk, def, int, spd, hit, res;
} aptitude;

u16 immunity; // Bitfield of immunities (0 for most, 255 for Divine Majin)
u16 id;
u16 family; // Seemingly corresponds to row in "create character" screen, e.g. Male/Female Brawler kept separate, but mages are grouped, as are skulls.
u16 unk3; // (always 100)
u16 unk4; // (always 20)
u16 throw;
u16 help; // (Key into charhelp.dat) Help entry text for this character, or 0.

struct {
u16 hp, sp, atk, def, int, spd, hit, res;
} base_stats;

u16 unk5; // (always 5)
u16 move_range;
u16 move_class; // 0 = normal; 1 = flying; 2 = warping
u16 unk6; // (always 1)
u16 unk7;
u16 unk8;
u16 unk9; // (always 10)
u8 pad3[4];
u16 unk10;
u16 counter;

u16 magic[32]; // (Key into magic.dat) Special index, for specials learned by this char/class, or 0 for unused.
u16 magic_lvl[32]; // Level at which character learns the corresponding special
};
</pre>

== charhelp.dat ==
Class help descriptions. These are shown in the "create character" screen, and so the table file includes strings that aren't ever shown in-game (e.g. for story characters or enemies).

<pre>
struct {
u16 id;
char description[62];
};
</pre>

== dungeon.dat ==
Gatekeeper warp data, powering the warp menu.

<pre>
struct {
char name[18];
u8 pad;
u16 id;
u16 talk; // talk.dat entry to execute when map is selected from warp menu
};
</pre>

== ge.dat ==
Geo effects.

<pre>
struct {
char name[21];
char description[57];
u16 id;
};
</pre>

== geocube.dat ==
Geocube effects (multiplayer).

<pre>
struct {
u8 id;
u8 unk1;
u8 unk2;
u8 unk3;
u16 unk4;
char name[17];
char description[65];
};
</pre>

== habit.dat ==
Item inhabitants.

<pre>
struct {
u32 unk1;
char name[21];
u8 pad1[1];
u16 id;
u8[20] item_chance; // Chance to appear in an item, by item class. Which element corresponds to which item class isn't known exactly.
// My best guess: ? Fist Sword Spear Bow Gun Axe Staff Monster ? Armor Belt Shoes Orb Glasses Muscle ? ? EX ?
u8 pad2[1];
};
</pre>

== hospital.dat ==
Hospital rewards, with minimum requirements.

<pre>
struct {
u16 id;
u16 req_deceased;
u32 item; // (Key into mitem.dat) Item to obtain
u32 req_hp;
u32 req_sp;
};
</pre>

== magic.dat ==
Specials/spells.

<pre>
struct {
u16 id;
u16 wpn_level; // Min. weapon skill level to unlock, if unlocked by weapon
u16 power; // Determines damage (TBD: how?)
u16 sp; // Base SP cost (TBD: determine growth curve)
char name[17];
char description[57];
u16 unk1; // ??
u8 effect_param[5]; // Parameter to skill effect (see below)
u8 wpn_type; // 0 = not weapon tied; 1 = fist; 2 = sword; 3 = spear; 4 = bow; 5 = gun; 6 = axe
u8 element; // 0 = none; 1 = fire; 2 = wind; 3 = ice; 4 = star
u8 spell_class; // 2 = melee; 3 = magic; 4 = heal; 5 = buff; 6 = debuff
u8 wpn_type_2; // (copy of wpn_type)
u8 range;
u8 pattern; // Attack pattern, complex, see below
u8 range_up; // Attack range vertically, constraints on height difference between tiles
u8 range_down;
u8 effect[5]; // Attack effects (see below), or 0 for no effect
};
</pre>

Some of these fields warrant additional explanation. The ''effect'' and ''effect_param'' fields allow up to 5 effects to be associated with a spell. Known effect numbers are listed below.

{| class="wikitable"
! # !! Description
|-
| 1 || ?
|-
| 2 || ?
|-
| 11 || Atk +n%
|-
| 12 || Def +n%
|-
| 13 || Res +n%
|-
| 14 || Int +n%
|-
| 21 || Poison (n = % chance to inflict)
|-
| 22 || Sleep
|-
| 23 || Paralyze
|-
| 24 || Amnesia
|-
| 25 || Deprave
|-
| 101 || Cure ailments (n=?)
|-
| 102 || HP Drain
|-
| 104 || Self-destruct
|}

The ''pattern'' field describes the attack pattern (which tiles are targeted relative to the user, etc). (TBD: document these.)

== mitem.dat ==
Item table.

== musicshop.dat ==
Song list for the music shop.

<pre>
struct {
u32 price;
u8 pad1[4];
u16 id;
u16 song_id; // Uncertain
char name[21];
char title[65];
u16 options; // 0 = locked; 1 = starts unlocked; 3 = starts unlocked & default selected
};
</pre>

== thief.dat ==
Stat stealing entries.

<pre>
struct {
char name[21];
u16 type; // 0 = steal HP; 1 = SP; 2 = Atk; 3 = Def; 4 = Int; 5 = Spd; 6 = Hit; 7 = Res; 10 = Exp; 11 = HL?
u8 pad1[1];
u32 unk1; // (always 1)
};
</pre>

== wish.dat ==
Dark Assembly bills.

<pre>
struct {
u32 mana;
u8 id;
u16 rank; // Min. rank required to reveal bill
i8 skew; // Skews senators' general opinion on the bill, -100 to +100 (higher is more favourable)
char name[31];
char description[53];
};
</pre>

== zukan.dat ==
Bestiary entries.

<pre>
struct {
u16 id;
u16 class_id;
char name[21];
char line1[45];
char line2[45];
char line3[45];
char line4[45];
char line5[45];
char line6[45];
char line7[45];
char line8[45];
u8 pad1[3];
};
</pre>

== External links ==
* [https://docs.google.com/spreadsheets/d/1QuShaZsuQe1cRybufzAFD97f6xQ0JlLXDIvsynusxZc/edit?usp=sharing D1DS table files in spreadsheet form]

Table files (D1DS)

2018-01-20T20:56:58Z

FireFly: Fix formatting & add link to spreadsheet

Table files (D1DS)

2018-01-20T20:55:01Z

FireFly: Add structs for most other table files

Table files (D1DS)

2018-01-20T19:59:06Z

FireFly: Start by documenting char.dat

DSARCIDX format

2018-01-20T19:04:16Z

FireFly: Created page with "The '''DSARCIDX format''' is a run-of-the-mill archive format. No built-in compression, has filenames but only "flat"--no directory tree. == Header == <pre> struct header {..."

The '''DSARCIDX format''' is a run-of-the-mill archive format. No built-in compression, has filenames but only "flat"--no directory tree.

== Header ==
<pre>
struct header {
char magic[8]; // "DSARCIDX"
u32 count;
u32 unk1; // always 00
u16 ids[count];
};
</pre>

This is seemingly padded to a 4-byte boundary by 0xFF bytes.
The meaning of the file IDs is uncertain, but in e.g. bg.dat the file bgXXX.mpb corresponds to the entry with ID X (with gaps in the numbering being present).

== File directory ==
The header is followed by the file directory, with one entry per file in the archive.

<pre>
struct file_entry {
char filename[40];
u32 size;
u32 offset; // relative to start of archive
} entries[count];
</pre>

== File data ==
This is followed by the file data. The data for each file is aligned to an 8-byte boundary, padded with null bytes between files if necessary.

[[Category:File formats]]

Project:Resources

2018-01-12T20:44:58Z

FireFly: Single hyphens

Links and other resources with handy information or details about the Disgaea series, its internals, etc.

== Community websites ==
* [http://makaisenki.shoutwiki.com/wiki/Main_Page Makai Senki Wiki] - Disgaea series & NIS lore, story and media wiki
* [http://akurasu.net/wiki/Makai_Senki_Disgaea Akurasu Wiki] - Contains lots of game-mechanical details and formulas for things such as exp yield or steal %

== Game internals ==
* [http://tcrf.net TCRF] - Duh, unused material found in all sorts of video games, Disgaea series included

Main Page

2018-01-12T20:44:31Z

FireFly: Add 'See also'

A wiki in which we reverse engineer NIS's shit

Spoiler: it often ''is'' shit

We mainly hang out on IRC, in '''#disgaea''' on Badnik (''irc.badnik.zone''). Currently (FSVO 'currently') focusing on understanding Disgaea 1 better.

== Games ==
* [[Disgaea 1]] (PS2, PSP, [[Disgaea 1/DS|DS]], PC, TTHM)

== I want to edit ==
PM xkeeper on IRC then.

== See also ==
* [[Project:Resources|Links and resources]] - more information about Disgaea and other NIS titles

Project:Resources

2018-01-12T20:42:22Z

FireFly: Could be fleshed out more, of course, but it's a start

Links and other resources with handy information or details about the Disgaea series, its internals, etc.

== Community websites ==
* [http://makaisenki.shoutwiki.com/wiki/Main_Page Makai Senki Wiki] -- Disgaea series & NIS lore, story and media wiki
* [http://akurasu.net/wiki/Makai_Senki_Disgaea Akurasu Wiki] -- Contains lots of game-mechanical details and formulas for things such as exp yield or steal %

== Game internals ==
* [http://tcrf.net TCRF] -- Duh, unused material found in all sorts of video games, Disgaea series included

Main Page

2018-01-12T20:30:01Z

FireFly:

A wiki in which we reverse engineer NIS's shit

Spoiler: it often ''is'' shit

We mainly hang out on IRC, in '''#disgaea''' on Badnik (''irc.badnik.zone''). Currently (FSVO 'currently') focusing on understanding Disgaea 1 better.

== Games ==
* [[Disgaea 1]] (PS2, PSP, [[Disgaea 1/DS|DS]], PC, TTHM)

== I want to edit ==
PM xkeeper on IRC then.

LZS format

2017-02-26T17:48:59Z

FireFly: This is not markdown

The '''LZS format''' appears to be a compression format used for compressed archives. Here, both the compression and the underlying archive format are described.

Somewhat confusingly, it appears to not use either of [https://en.wikipedia.org/wiki/Lempel–Ziv–Stac LZS] or [https://en.wikipedia.org/wiki/Lempel–Ziv–Storer–Szymanski LZSS] compression, despite the name.

It appears in at least ''Disgaea 2 PC''.

== Magic ==
The file starts with a <code>char magic[4]</code> ''"dat\0"'', not part of the compressed data.

== Compression ==
LZ77-based compression (that is, has literal data and backreferences, the latter referring back to a portion of data that has already been output but occurs again).

<pre>
struct header {
u32 compressed_size; // including this 12-byte header
u32 decompressed_size;
u32 marker; // marker used to denote backrefs in the compressed data. 0x00-0xFF.
};
</pre>

This header is followed by the compressed data, which consists of literal bytes (copied straight to output) or backrefs. Backrefs are encoded as

<pre>
struct backref { u8 marker, dist, count; };
</pre>

representing that ''count'' bytes should be copied from ''dist'' back into the output history. If ''dist > marker'', then 1 should be subtracted from it.

Why this extra complication? Because two ''marker'' bytes in a row denote an escaped literal ''marker'' byte. Thus, a decompression loop looks something like this:

<pre>
while (read_ctr < header.compressed_size - sizeof(struct header)) {
u8 v = READ();
if (v == header.marker) {
u8 dist = READ();
if (dist == header.marker) {
WRITE(header.marker); // marker repeated twice = an escaped marker byte
} else {
u8 count = READ();
if (dist > header.marker) dist--;
for (size_t i = 0; i < count; i++) WRITE(HISTORY(dist));
}
} else {
WRITE(v);
}
}
</pre>

After this step, ''header.decompressed_size'' bytes should have been written.

== Archive format ==
The underlying archive consists of a header with the number of files, a table of offsets and filenames, and file data; nothing weird here.

<pre>
struct header {
u32 count; // #files in the archive
u32 unk1; // 0
u32 unk2; // 0
u32 unk3; // 0
};
</pre>

The header is followed by ''header.count'' file entries.

<pre>
struct file_entry {
u32 end_offset;
char filename[0x1C];
};
</pre>

After this comes the file data. The first file runs from this point for ''entries[0].end_offset'' bytes. That is, all of the ''end_offset''s are counted starting from after the file metadata table.

[[Category:File formats]]

LZS format

2017-02-26T17:47:16Z

FireFly: Point out lack of relation to LZS/LZSS

The '''LZS format''' appears to be a compression format used for compressed archives. Here, both the compression and the underlying archive format are described.

Somewhat confusingly, it appears to not use either of [https://en.wikipedia.org/wiki/Lempel–Ziv–Stac LZS] or [https://en.wikipedia.org/wiki/Lempel–Ziv–Storer–Szymanski LZSS] compression, despite the name.

It appears in at least ''Disgaea 2 PC''.

== Magic ==
The file starts with a <code>char magic[4]</code> ''"dat\0"'', not part of the compressed data.

== Compression ==
LZ77-based compression (that is, has literal data and backreferences, the latter referring back to a portion of data that has already been output but occurs again).

<pre>
struct header {
u32 compressed_size; // including this 12-byte header
u32 decompressed_size;
u32 marker; // marker used to denote backrefs in the compressed data. 0x00-0xFF.
};
</pre>

This header is followed by the compressed data, which consists of literal bytes (copied straight to output) or backrefs. Backrefs are encoded as

<pre>
struct backref { u8 marker, dist, count; };
</pre>

representing that ''count'' bytes should be copied from ''dist'' back into the output history. If ''dist > marker'', then 1 should be subtracted from it.

Why this extra complication? Because two ''marker'' bytes in a row denote an escaped literal ''marker'' byte. Thus, a decompression loop looks something like this:

<pre>
while (read_ctr < header.compressed_size - sizeof(struct header)) {
u8 v = READ();
if (v == header.marker) {
u8 dist = READ();
if (dist == header.marker) {
WRITE(header.marker); // marker repeated twice = an escaped marker byte
} else {
u8 count = READ();
if (dist > header.marker) dist--;
for (size_t i = 0; i < count; i++) WRITE(HISTORY(dist));
}
} else {
WRITE(v);
}
}
</pre>

After this step, ''header.decompressed_size'' bytes should have been written.

== Archive format ==
The underlying archive consists of a header with the number of files, a table of offsets and filenames, and file data; nothing weird here.

<pre>
struct header {
u32 count; // #files in the archive
u32 unk1; // 0
u32 unk2; // 0
u32 unk3; // 0
};
</pre>

The header is followed by `header.count` file entries.

<pre>
struct file_entry {
u32 end_offset;
char filename[0x1C];
};
</pre>

After this comes the file data. The first file runs from this point for `entries[0].end_offset` bytes. That is, all of the ''end_offset''s are counted starting from after the file metadata table.

[[Category:File formats]]

LZS format

2017-02-26T17:45:26Z

FireFly: Document LZS archives as found in D2PC

The '''LZS format''' appears to be a compression format used for compressed archives. Here, both the compression and the underlying archive format are described.

It appears in at least Disgaea 2 PC.

== Magic ==
The file starts with a <code>char magic[4]</code> ''"dat\0"'', not part of the compressed data.

== Compression ==
LZ77-based compression (that is, has literal data and backreferences, the latter referring back to a portion of data that has already been output but occurs again).

<pre>
struct header {
u32 compressed_size; // including this 12-byte header
u32 decompressed_size;
u32 marker; // marker used to denote backrefs in the compressed data. 0x00-0xFF.
};
</pre>

This header is followed by the compressed data, which consists of literal bytes (copied straight to output) or backrefs. Backrefs are encoded as

<pre>
struct backref { u8 marker, dist, count; };
</pre>

representing that ''count'' bytes should be copied from ''dist'' back into the output history. If ''dist > marker'', then 1 should be subtracted from it.

Why this extra complication? Because two ''marker'' bytes in a row denote an escaped literal ''marker'' byte. Thus, a decompression loop looks something like this:

<pre>
while (read_ctr < header.compressed_size - sizeof(struct header)) {
u8 v = READ();
if (v == header.marker) {
u8 dist = READ();
if (dist == header.marker) {
WRITE(header.marker); // marker repeated twice = an escaped marker byte
} else {
u8 count = READ();
if (dist > header.marker) dist--;
for (size_t i = 0; i < count; i++) WRITE(HISTORY(dist));
}
} else {
WRITE(v);
}
}
</pre>

After this step, ''header.decompressed_size'' bytes should have been written.

== Archive format ==
The underlying archive consists of a header with the number of files, a table of offsets and filenames, and file data; nothing weird here.

<pre>
struct header {
u32 count; // #files in the archive
u32 unk1; // 0
u32 unk2; // 0
u32 unk3; // 0
};
</pre>

The header is followed by `header.count` file entries.

<pre>
struct file_entry {
u32 end_offset;
char filename[0x1C];
};
</pre>

After this comes the file data. The first file runs from this point for `entries[0].end_offset` bytes. That is, all of the ''end_offset''s are counted starting from after the file metadata table.

[[Category:File formats]]

Disgaea 1

2017-02-26T17:31:25Z

FireFly: +cat

See also TCRF for details/unused content:
* [[tcrf:Disgaea: Hour of Darkness|Disgaea: Hour of Darkness]]
* [[tcrf:Disgaea DS|Disgaea DS]]

=== Ports ===
* [[/DS]]: Disgaea DS

=== Pages ===
Take a look at the following

* [[/Map editor|/Map editor]]
* [[/Debug mode|/Debug mode]]

* [[MPD format]] for how the maps work
* [[IMY format]] for how the IMY compression works

=== Data ===

* [[/Map list]] shows which maps are on what platforms

=== Unsorted notes ===

Four different "teams":

[[File:D1PC-Teams.png|300px]]
* Player: your units
* Enemy: attacks everything else
* Neutral: attacks Enemy
* "Red": attacks Player, normally not used

[[Category:Games]]

Disgaea 2

2017-02-26T17:30:54Z

FireFly: Whee

The sequel to the horse wiener game, etc etc.

== Pages ==

* [[LZS format]] (compressed archive format, used at least in the PC port)

[[Category:Games]]

Disgaea 1/Map editor

2016-09-09T02:53:45Z

FireFly: PCSX2 info

This article documents how to use the built-in '''map editor'''.

== Emulator settings ==
To enable the map-editor, you need to activate debug mode. If you use the PCSX2 emulator, you could accomplish this by creating a file called ''4D2CAC9D.pnach'' with the following content:

patch=1,EE,20147078,word,00000000
patch=1,EE,20100440,word,8F8485AC
patch=1,EE,20100444,word,34840002
patch=1,EE,20100448,word,1000000B
patch=1,EE,2010044C,word,AF8485AC

Put the file in the ''PCSX2/cheats/'' directory, and make sure to start the game with the 'Boot CDVD (fast)' option.

=== Import/export maps ===
In order to export maps from the game, you need to enable Host File System in PCSX2. You then need to make sure that the directory ''PCSX2/host/map/mpXXX'' exists, where ''XXX'' is the first three digits of the map you want to save. After that, exporting to HDD should work, and write the map file to your actual host filesystem.

== Camera controls ==
* {{ps/l1}}/{{ps/r1}} on P1's controller rotates the camera.
* All other camera controls require a second controller plugged in
** {{ps/l1}}/{{ps/r1}} on P2's controller zooms the camera; {{ps/l2}}/{{ps/r2}} does the same at a different speed.
** {{ps/dpad}} or Left Stick pans the camera.

== Editor modes ==
The editor could be put into several different modes, adjusted via {{ps/left}}/{{ps/right}} in the topmost menu entry. Each mode is documented separately.

=== Cursor ===
* Default selection. Allows you to casually browse the map.
** If you hold down {{ps/x}} and push a direction on {{ps/dpad}}, you can shift the entire map in that direction, one tile at a time.

=== Vertex ===
* This option allows you to manipulate the existing terrain of the map.
** If you wish to create new Vertex tiles, see the "Texture" section later for more details.
* {{ps/square}} brings up the Vertex Tools menu.
** Highlight "Y Inc. and Dec." and toggle through your desired selection with {{ps/left}} and {{ps/right}}.
** This will set the amount of incremental force that will be applied when using the vertex editor tool.
* The "Precinct Vertex" option determines whether your modifications impact the surrounding tiles or not.
** If set to "Off" you will only modify the positioning of the current vertex only. However if set to "On" any changes you make to the current vertex will adjust surrounding tiles as well. This can be particularly useful to toggle between when attempting to create realistic slopes, or when attempting to make very precise edits without altering the surrounding environment.
* There is an "Invisible" third option also present in this menu.
** It acts the same as the "Area" option in the main editor window, and allows you to toggle between individual chunks.
* To modify a vertex, simply hover your cursor over the desired tile, hold {{ps/circle}}, and press {{ps/up}} or {{ps/down}}.
** You can toggle between vertex face selection with {{ps/l2}} and {{ps/r2}}. This allows for precise modification of the terrain from every angle.

=== Texture ===
The Texture mode allows you to change the textures of the five faces of a map tile.

* {{ps/l2}}/{{ps/r2}} switches between the faces S, E, N, W, Top.
* {{ps/circle}} draws the currently selected texture to the selected face of the selected tile.
* {{ps/square}} brings up the ''texture slice picker''.
** {{ps/r2}} moves between the settings on the right-hand side, and the texture slice picker in the tileset to the left.
** {{ps/l1}}/{{ps/r1}} switches between the different textures currently loaded.
** Option #1 controls rotation of the texture slice (0, 90, 180, 270)
** Option #2 controls mirroring of the texture slice(?) (None, X, Y, XY)
** Option #3 sets the blending mode of the texture (Normal, Translucent, Addition, Subtraction)
** Option #4 (??? TBD) (Right-Up Vertex, Left-Down Vertex, Right-Down Vertex)
** Option #5 is used for drawing several textures (Mono Face, Sequence Face)
** Option #6 controls what operation to perform (Put Face, Delete Face, Delete Box)
** Option #7 (??? TBD) (Ground, Put Shadow)

=== Put Character ===
* This option allows you to place actors on the map, and adjust their settings accordingly.
* To setup an actor, simply hover your cursor over the desired tile and press {{ps/x}}.
** A large list of options will present itself as follows.
** The first option determines the actor type. Press {{ps/left}} or {{ps/right}} to toggle between options, of additional note the Actor ID of the selected actor will be displayed to the left of this option (when applicable). Alternatively you can press {{ps/x}} instead, this will present you with a sub-menu that allows you to easily scroll through all available units and their classes.
** The "Lv0001" option should be fairly self explanatory in nature. Simply press {{ps/left}} or {{ps/right}} to increase or decrease the level of your actor.
** The "Enemy1" option determines enemy behavior in battle. "Enemy1" behaves as normal, the unit will be hostile to you and other threats. "Enemy2" however will set the unit to "Neutral" status, here they will not attack the player unprovoked, and instead will focus on the "Enemy1" type actors. "Enemy3" will only attack the player, ignoring all other threats on the map in favor of eliminating the player character.
** The "Direction" option allows you to set the direction the actor is facing at the start of battle. Simply press {{ps/left}} or {{ps/right}} until you find the desired position, then press {{ps/x}} to apply your changes.
** The next option allows you to modify enemy AI behavior. Press {{ps/left}} or {{ps/right}} to toggle between options. "Rush" seems to be default enemy behavior, where they will recklessly rush in with all their bravado. "Fixed Cannon" will force the actor to remain stationary, but it will attack if an appropriate target is in its immediate range. "Do nothing" is pretty self explanatory, the actor will not do anything under any circumstance. "Intercept" prioritizes the protection of its allied units above all else, acting to stop the player or other hostile actor that may pose a threat.
** The "Equip" option will open open a small sub-menu if selected with {{ps/x}}. Here you can use {{ps/left}} or {{ps/right}} to set the desired item to an equipment slot, or press {{ps/up}} and {{ps/down}} to toggle between the slots themselves. If you wish to clear an item from a slot, simply highlight it and press {{ps/triangle}}.
** The following option is a Stats modifier for the current actor. Press {{ps/left}} or {{ps/right}} to toggle between the eight available options. "Common" uses stats derived from the actor database in CHAR.DAT, whereas "BossLv.1" and higher adds some kind of modifier to all stats - increasing their power considerably with each increment.
** The "Move" option is self explanatory. Simply press {{ps/x}} and then move your cursor to the new desired location of the unit, where again you press {{ps/x}} to place it.
** The "Delete" option will delete the actor from the map forever. Beware, for this no way to undo this!
** The "Appear" option determines if an actor is always present on a map or not. "Appear Normal" ensures they are always present. "Absent 2nd" ensures that the actor will not appear if the map is replayed a second time, useful for maps with one-time boss encounters. "Appear 2nd" ensures the actor is not there the first time you visit the map, but will be present every revisit afterward!
** The "Geo" option allows you to modify what kind of Geo Effect property the current actor has. Press {{ps/left}} or {{ps/right}} to toggle between options, and press {{ps/l1}} and {{ps/l2}} to switch between Geo Symbol colors for the effect. While normally this is only ever used on Geo Symbols, this property can be set on any actor!

=== Put Object ===
* This option only works when an individual area is selected for the current map.
** If your map view is set to "All Area" the controls for this function will be disabled.
* {{ps/square}} brings up the Object Select menu.
** Highlight "N000" and toggle through your desired selection with {{ps/left}} and {{ps/right}}.
** Press {{ps/x}} to select and place the desired object. A series of additional options will now display.
* Y modifies the Y Axis of the object. Negative values are higher in height, positive are lower.
* RX, RY, and RZ modify the rotation of the object on the X, Y, and Z axis respectively.
* SX, SY, and SZ modify the scale of the object on the X, Y, and Z axis respectively.
* FlowU and FlowV control horizontal and vertical movement of animated textures. (Where applicable.)

=== Put Event ===
* This option only works when an individual area is selected for the current map.
** If your map view is set to "All Area" the controls for this function will be disabled.
* {{ps/square}} button brings up the Event Select menu.
** Two options should be visible from this menu, both seemingly identical looking, but serving an individual purpose.
** The first "No0000" option is the event tile you're modifying, whereas the second "No0000" option is the actual event you're setting it to.
** As such, you may only have up to 16 event tiles per map, including the base panel event, effectively leaving you with 15 additional event tiles.
** The editor is unfortunately not very descriptive regarding which event you have currently selected, so it may be a good idea to keep notes while editing!
* '''Currently Known Events:'''
** 0000 - Null (Clears Event Tile)
** 0001 - Base Panel
** 0002 - Victory Tile (map is won when a unit walks onto it)

=== Limit Moving ===
* This option allows you to create or remove certain types of collision on the map.
* You can toggle between Collision options with {{ps/square}}.
** Once your selection is made, simply hover over the tile of your choice and press {{ps/x}}.
* The top option represents your current selection, whereas the bottom option represents the collision type on the current tile.
** Unlimited - No Restriction.
** Flying Only - Only units capable of Flight may pass.
** All Disable - Impassable by any means.

=== Item Realm Only ===
TBD

=== Geo Effect ===
* This option allows you to place Geo Effect panels on the map.
* You can toggle between Geo Panel colors with {{ps/l2}} and {{ps/r2}}.
** Once your selection is made, simply hover over the tile of your choice and press {{ps/x}}.
** To remove a Geo Effect tile, simply toggle through the colors until your selection is "Null" and then overwrite the existing tile with "Null" to clear it.

=== Unite MAP ===
TBD

Disgaea 1/Map editor

2016-09-09T01:16:28Z

FireFly: /* Texture */ Add some notes about the Texture mode

== Camera controls ==
* {{ps/l1}}/{{ps/r1}} on P1's controller rotates the camera.
* All other camera controls require a second controller plugged in
** {{ps/l1}}/{{ps/r1}} on P2's controller zooms the camera; {{ps/l2}}/{{ps/r2}} does the same at a different speed.
** {{ps/dpad}} or Left Stick pans the camera.

== Editor modes ==
The editor could be put into several different modes, adjusted via {{ps/left}}/{{ps/right}} in the topmost menu entry. Each mode is documented separately.

=== Cursor ===
* Default selection. Allows you to casually browse the map.
** If you hold down {{ps/x}} and push a direction on {{ps/dpad}}, you can shift the entire map in that direction, one tile at a time.

=== Vertex ===
* This option allows you to manipulate the existing terrain of the map.
** If you wish to create new Vertex tiles, see the "Texture" section later for more details.
* {{ps/square}} brings up the Vertex Tools menu.
** Highlight "Y Inc. and Dec." and toggle through your desired selection with {{ps/left}} and {{ps/right}}.
** This will set the amount of incremental force that will be applied when using the vertex editor tool.
* The "Precinct Vertex" option determines whether your modifications impact the surrounding tiles or not.
** If set to "Off" you will only modify the positioning of the current vertex only. However if set to "On" any changes you make to the current vertex will adjust surrounding tiles as well. This can be particularly useful to toggle between when attempting to create realistic slopes, or when attempting to make very precise edits without altering the surrounding environment.
* There is an "Invisible" third option also present in this menu.
** It acts the same as the "Area" option in the main editor window, and allows you to toggle between individual chunks.
* To modify a vertex, simply hover your cursor over the desired tile, hold {{ps/circle}}, and press {{ps/up}} or {{ps/down}}.
** You can toggle between vertex face selection with {{ps/l2}} and {{ps/r2}}. This allows for precise modification of the terrain from every angle.

=== Texture ===
The Texture mode allows you to change the textures of the five faces of a map tile.

* {{ps/l2}}/{{ps/r2}} switches between the faces S, E, N, W, Top.
* {{ps/circle}} draws the currently selected texture to the selected face of the selected tile.
* {{ps/square}} brings up the ''texture slice picker''.
** {{ps/r2}} moves between the settings on the right-hand side, and the texture slice picker in the tileset to the left.
** {{ps/l1}}/{{ps/r1}} switches between the different textures currently loaded.
** Option #1 controls rotation of the texture slice (0, 90, 180, 270)
** Option #2 controls mirroring of the texture slice(?) (None, X, Y, XY)
** Option #3 sets the blending mode of the texture (Normal, Translucent, Addition, Subtraction)
** Option #4 (??? TBD) (Right-Up Vertex, Left-Down Vertex, Right-Down Vertex)
** Option #5 is used for drawing several textures (Mono Face, Sequence Face)
** Option #6 controls what operation to perform (Put Face, Delete Face, Delete Box)
** Option #7 (??? TBD) (Ground, Put Shadow)

=== Put Character ===
* This option allows you to place actors on the map, and adjust their settings accordingly.
* To setup an actor, simply hover your cursor over the desired tile and press {{ps/x}}.
** A large list of options will present itself as follows.
** The first option determines the actor type. Press {{ps/left}} or {{ps/right}} to toggle between options, of additional note the Actor ID of the selected actor will be displayed to the left of this option (when applicable). Alternatively you can press {{ps/x}} instead, this will present you with a sub-menu that allows you to easily scroll through all available units and their classes.
** The "Lv0001" option should be fairly self explanatory in nature. Simply press {{ps/left}} or {{ps/right}} to increase or decrease the level of your actor.
** The "Enemy1" option determines enemy behavior in battle. "Enemy1" behaves as normal, the unit will be hostile to you and other threats. "Enemy2" however will set the unit to "Neutral" status, here they will not attack the player unprovoked, and instead will focus on the "Enemy1" type actors. "Enemy3" will only attack the player, ignoring all other threats on the map in favor of eliminating the player character.
** The "Direction" option allows you to set the direction the actor is facing at the start of battle. Simply press {{ps/left}} or {{ps/right}} until you find the desired position, then press {{ps/x}} to apply your changes.
** The next option allows you to modify enemy AI behavior. Press {{ps/left}} or {{ps/right}} to toggle between options. "Rush" seems to be default enemy behavior, where they will recklessly rush in with all their bravado. "Fixed Cannon" will force the actor to remain stationary, but it will attack if an appropriate target is in its immediate range. "Do nothing" is pretty self explanatory, the actor will not do anything under any circumstance. "Intercept" prioritizes the protection of its allied units above all else, acting to stop the player or other hostile actor that may pose a threat.
** The "Equip" option will open open a small sub-menu if selected with {{ps/x}}. Here you can use {{ps/left}} or {{ps/right}} to set the desired item to an equipment slot, or press {{ps/up}} and {{ps/down}} to toggle between the slots themselves. If you wish to clear an item from a slot, simply highlight it and press {{ps/triangle}}.
** The following option is a Stats modifier for the current actor. Press {{ps/left}} or {{ps/right}} to toggle between the eight available options. "Common" uses stats derived from the actor database in CHAR.DAT, whereas "BossLv.1" and higher adds some kind of modifier to all stats - increasing their power considerably with each increment.
** The "Move" option is self explanatory. Simply press {{ps/x}} and then move your cursor to the new desired location of the unit, where again you press {{ps/x}} to place it.
** The "Delete" option will delete the actor from the map forever. Beware, for this no way to undo this!
** The "Appear" option determines if an actor is always present on a map or not. "Appear Normal" ensures they are always present. "Absent 2nd" ensures that the actor will not appear if the map is replayed a second time, useful for maps with one-time boss encounters. "Appear 2nd" ensures the actor is not there the first time you visit the map, but will be present every revisit afterward!
** The "Geo" option allows you to modify what kind of Geo Effect property the current actor has. Press {{ps/left}} or {{ps/right}} to toggle between options, and press {{ps/l1}} and {{ps/l2}} to switch between Geo Symbol colors for the effect. While normally this is only ever used on Geo Symbols, this property can be set on any actor!

=== Put Object ===
* This option only works when an individual area is selected for the current map.
** If your map view is set to "All Area" the controls for this function will be disabled.
* {{ps/square}} brings up the Object Select menu.
** Highlight "N000" and toggle through your desired selection with {{ps/left}} and {{ps/right}}.
** Press {{ps/x}} to select and place the desired object. A series of additional options will now display.
* Y modifies the Y Axis of the object. Negative values are higher in height, positive are lower.
* RX, RY, and RZ modify the rotation of the object on the X, Y, and Z axis respectively.
* SX, SY, and SZ modify the scale of the object on the X, Y, and Z axis respectively.
* FlowU and FlowV control horizontal and vertical movement of animated textures. (Where applicable.)

=== Put Event ===
* This option only works when an individual area is selected for the current map.
** If your map view is set to "All Area" the controls for this function will be disabled.
* {{ps/square}} button brings up the Event Select menu.
** Two options should be visible from this menu, both seemingly identical looking, but serving an individual purpose.
** The first "No0000" option is the event tile you're modifying, whereas the second "No0000" option is the actual event you're setting it to.
** As such, you may only have up to 16 event tiles per map, including the base panel event, effectively leaving you with 15 additional event tiles.
** The editor is unfortunately not very descriptive regarding which event you have currently selected, so it may be a good idea to keep notes while editing!
* '''Currently Known Events:'''
** 0000 - Null (Clears Event Tile)
** 0001 - Base Panel
** 0002 - Victory Tile (map is won when a unit walks onto it)

=== Limit Moving ===
* This option allows you to create or remove certain types of collision on the map.
* You can toggle between Collision options with {{ps/square}}.
** Once your selection is made, simply hover over the tile of your choice and press {{ps/x}}.
* The top option represents your current selection, whereas the bottom option represents the collision type on the current tile.
** Unlimited - No Restriction.
** Flying Only - Only units capable of Flight may pass.
** All Disable - Impassable by any means.

=== Item Realm Only ===
TBD

=== Geo Effect ===
* This option allows you to place Geo Effect panels on the map.
* You can toggle between Geo Panel colors with {{ps/l2}} and {{ps/r2}}.
** Once your selection is made, simply hover over the tile of your choice and press {{ps/x}}.
** To remove a Geo Effect tile, simply toggle through the colors until your selection is "Null" and then overwrite the existing tile with "Null" to clear it.

=== Unite MAP ===
TBD

Disgaea 1/Map editor

2016-09-08T23:56:21Z

FireFly: Add some camera options, add missing modes (to be documented)

== Camera controls ==
* {{ps/l1}}/{{ps/r1}} on P1's controller rotates the camera.
* All other camera controls require a second controller plugged in
** {{ps/l1}}/{{ps/r1}} on P2's controller zooms the camera; {{ps/l2}}/{{ps/r2}} does the same at a different speed.
** {{ps/dpad}} or Left Stick pans the camera.

== Editor modes ==
The editor could be put into several different modes, adjusted via {{ps/left}}/{{ps/right}} in the topmost menu entry. Each mode is documented separately.

=== Cursor ===
* Default selection. Allows you to casually browse the map.
** If you hold down {{ps/x}} and push a direction on {{ps/dpad}}, you can shift the entire map in that direction, one tile at a time.

=== Vertex ===
* This option allows you to manipulate the existing terrain of the map.
** If you wish to create new Vertex tiles, see the "Texture" section later for more details.
* {{ps/square}} brings up the Vertex Tools menu.
** Highlight "Y Inc. and Dec." and toggle through your desired selection with {{ps/left}} and {{ps/right}}.
** This will set the amount of incremental force that will be applied when using the vertex editor tool.
* The "Precinct Vertex" option determines whether your modifications impact the surrounding tiles or not.
** If set to "Off" you will only modify the positioning of the current vertex only. However if set to "On" any changes you make to the current vertex will adjust surrounding tiles as well. This can be particularly useful to toggle between when attempting to create realistic slopes, or when attempting to make very precise edits without altering the surrounding environment.
* There is an "Invisible" third option also present in this menu.
** It acts the same as the "Area" option in the main editor window, and allows you to toggle between individual chunks.
* To modify a vertex, simply hover your cursor over the desired tile, hold {{ps/circle}}, and press {{ps/up}} or {{ps/down}}.
** You can toggle between vertex face selection with {{ps/l2}} and {{ps/r2}}. This allows for precise modification of the terrain from every angle.

=== Texture ===
TBD

=== Put Character ===
* This option allows you to place actors on the map, and adjust their settings accordingly.
* To setup an actor, simply hover your cursor over the desired tile and press {{ps/x}}.
** A large list of options will present itself as follows.
** The first option determines the actor type. Press {{ps/left}} or {{ps/right}} to toggle between options, of additional note the Actor ID of the selected actor will be displayed to the left of this option (when applicable). Alternatively you can press {{ps/x}} instead, this will present you with a sub-menu that allows you to easily scroll through all available units and their classes.
** The "Lv0001" option should be fairly self explanatory in nature. Simply press {{ps/left}} or {{ps/right}} to increase or decrease the level of your actor.
** The "Enemy1" option determines enemy behavior in battle. "Enemy1" behaves as normal, the unit will be hostile to you and other threats. "Enemy2" however will set the unit to "Neutral" status, here they will not attack the player unprovoked, and instead will focus on the "Enemy1" type actors. "Enemy3" will only attack the player, ignoring all other threats on the map in favor of eliminating the player character.
** The "Direction" option allows you to set the direction the actor is facing at the start of battle. Simply press {{ps/left}} or {{ps/right}} until you find the desired position, then press {{ps/x}} to apply your changes.
** The next option allows you to modify enemy AI behavior. Press {{ps/left}} or {{ps/right}} to toggle between options. "Rush" seems to be default enemy behavior, where they will recklessly rush in with all their bravado. "Fixed Cannon" will force the actor to remain stationary, but it will attack if an appropriate target is in its immediate range. "Do nothing" is pretty self explanatory, the actor will not do anything under any circumstance. "Intercept" prioritizes the protection of its allied units above all else, acting to stop the player or other hostile actor that may pose a threat.
** The "Equip" option will open open a small sub-menu if selected with {{ps/x}}. Here you can use {{ps/left}} or {{ps/right}} to set the desired item to an equipment slot, or press {{ps/up}} and {{ps/down}} to toggle between the slots themselves. If you wish to clear an item from a slot, simply highlight it and press {{ps/triangle}}.
** The following option is a Stats modifier for the current actor. Press {{ps/left}} or {{ps/right}} to toggle between the eight available options. "Common" uses stats derived from the actor database in CHAR.DAT, whereas "BossLv.1" and higher adds some kind of modifier to all stats - increasing their power considerably with each increment.
** The "Move" option is self explanatory. Simply press {{ps/x}} and then move your cursor to the new desired location of the unit, where again you press {{ps/x}} to place it.
** The "Delete" option will delete the actor from the map forever. Beware, for this no way to undo this!
** The "Appear" option determines if an actor is always present on a map or not. "Appear Normal" ensures they are always present. "Absent 2nd" ensures that the actor will not appear if the map is replayed a second time, useful for maps with one-time boss encounters. "Appear 2nd" ensures the actor is not there the first time you visit the map, but will be present every revisit afterward!
** The "Geo" option allows you to modify what kind of Geo Effect property the current actor has. Press {{ps/left}} or {{ps/right}} to toggle between options, and press {{ps/l1}} and {{ps/l2}} to switch between Geo Symbol colors for the effect. While normally this is only ever used on Geo Symbols, this property can be set on any actor!

=== Put Object ===
* This option only works when an individual area is selected for the current map.
** If your map view is set to "All Area" the controls for this function will be disabled.
* {{ps/square}} brings up the Object Select menu.
** Highlight "N000" and toggle through your desired selection with {{ps/left}} and {{ps/right}}.
** Press {{ps/x}} to select and place the desired object. A series of additional options will now display.
* Y modifies the Y Axis of the object. Negative values are higher in height, positive are lower.
* RX, RY, and RZ modify the rotation of the object on the X, Y, and Z axis respectively.
* SX, SY, and SZ modify the scale of the object on the X, Y, and Z axis respectively.
* FlowU and FlowV control horizontal and vertical movement of animated textures. (Where applicable.)

=== Put Event ===
* This option only works when an individual area is selected for the current map.
** If your map view is set to "All Area" the controls for this function will be disabled.
* {{ps/square}} button brings up the Event Select menu.
** Two options should be visible from this menu, both seemingly identical looking, but serving an individual purpose.
** The first "No0000" option is the event tile you're modifying, whereas the second "No0000" option is the actual event you're setting it to.
** As such, you may only have up to 16 event tiles per map, including the base panel event, effectively leaving you with 15 additional event tiles.
** The editor is unfortunately not very descriptive regarding which event you have currently selected, so it may be a good idea to keep notes while editing!
* '''Currently Known Events:'''
** 0000 - Null (Clears Event Tile)
** 0001 - Base Panel
** 0002 - Victory Tile (map is won when a unit walks onto it)

=== Limit Moving ===
* This option allows you to create or remove certain types of collision on the map.
* You can toggle between Collision options with {{ps/square}}.
** Once your selection is made, simply hover over the tile of your choice and press {{ps/x}}.
* The top option represents your current selection, whereas the bottom option represents the collision type on the current tile.
** Unlimited - No Restriction.
** Flying Only - Only units capable of Flight may pass.
** All Disable - Impassable by any means.

=== Item Realm Only ===
TBD

=== Geo Effect ===
* This option allows you to place Geo Effect panels on the map.
* You can toggle between Geo Panel colors with {{ps/l2}} and {{ps/r2}}.
** Once your selection is made, simply hover over the tile of your choice and press {{ps/x}}.
** To remove a Geo Effect tile, simply toggle through the colors until your selection is "Null" and then overwrite the existing tile with "Null" to clear it.

=== Unite MAP ===
TBD

MPD format

2016-09-08T23:24:10Z

FireFly: /* Tile data */

The '''MPD format''' is used to describe map data.

A note on convention: the coordinate system in this article treats positive x as east, positive y as down (that is, "forward"), and positive z as north, if you're looking at the map from above. This makes it a left-hand coordinate system.

== Header ==
<pre>
struct header {
u16 n_chunks; // #chunks in map file
u16 n_actors; // #actors in map file
u16 unknown;
u8 padding[10];
};
</pre>

== Chunk ==
The header is followed by ''n_chunks'' chunks. Each "chunk" is fixed-size, and contains map tiles, objects and event tiles. All map tile data is stored outside the chunks section, whereas objects and event tiles are stored within it (and thus there's a limit to the number of objects/events in a chunk).

<pre>
struct chunk {
struct chunk_header header;
struct chunk_object_entry objects[32];
struct chunk_event_tile_entry event_tiles[16];
struct map_tile weird_special_tile;
};
</pre>

=== Header ===
<pre>
struct chunk_header {
f32 map_offset_x; // (val - 6)/12
f32 unk1_1;
f32 map_offset_z; // (val - 6)/12
f32 unk1_2;
f32 unk1[7];
u16 n_tiles; // #tiles within chunk
u8 unk2, unk3;
u16 index; // index of chunk (starts at 0)
u8 unk4[14];
};
</pre>

The ''map_offset_x'' and ''map_offset_z'' fields warrant some explanation: the map editor allows you to shift the whole map around, and instead of updating all tiles individually, these chunk-wide settings get changed. Actors' coordinates are updated, and are not affected by this offset. Whenever tiles get read, a tile that has stored location ''(x, z)'' effectively ends up at ''(x + map_offset_x, z + map_offset_z)'' instead. Why are they floats, you say? No idea.

=== Object table ===
Each chunk fits up to 32 objects (padded with null bytes if there's fewer).

<pre>
struct chunk_object_entry {
i16 unk1, unk2, unk3, unk4, unk5;
i16 unk6, unk7, unk8, unk9, unk10;
u8 unk11, unk12, unk13, unk14, unk15, unk16;
u8 pad[10];
};
</pre>

=== Event tile table ===
Each chunk fits up to 16 event tiles (padded with null bytes if there's fewer).

<pre>
struct chunk_event_tile_entry {
i8 x, z;
u8 index;
u8 pad1;
};
</pre>

== Tile data ==
The number of tiles in the tile data section is the sum of ''n_tiles'' for all chunks. Presumably the tiles are assigned to chunks in the order they appear, so the first ''chunk[0].header.n_tiles'' tiles belong to chunk 0, etc.

<pre>
struct texdata {
u8 u, v;
u8 unk[6]; // TBD
};

struct map_tile {
struct texdata textures[12]; // N, W, S, E, Top; same repeated with unknown meaning (repeated texture?); 2 unknown textures
i8 corners[4]; // Height in each corner of the tile, negative = up; (SW, SE, NW, NE) (needs verification!)
i8 corners2[4]; // \ Related to bottom corners of tile, somehow. All zero except for "floating platforms" (e.g. mp1302)
i8 corners3[4]; // /
u8 unk2[4]; // TBD
u8 unk3;
i8 x, z;
u8 unk4, unk5, unk6, unk7;
u8 mobility; // 0 = Unlimited, 1 = Fly only, 2 = Impassable
u8 geo_color;
u8 geo_mark; // 0 = No geopanel, 100 = Has geopanel
u8 pad2[6];
};
</pre>

== Actor data ==
The number of actors is given by ''n_actors'' in the file header.

<pre>
struct map_actor {
u16 id; // Class ID
u16 level;
u8 unk2;
i8 x, z;
i8 rotation; // -1 = W, 0 = N, 1 = E, 2 = S
u8 unk4;
u8 ai; // ? verify
u8 unk5, unk6;
u16 items[4];
u8 appearance; // 0 = Appear Normal, 1 = Absent 2nd, 2 = Appear 2nd
u8 unk7;
u16 geo_effect; // Only(?) used for geosymbols, val%10 = color, val/10 = effect
u16 unk8;
u16 magic[4];
i8 unk[30]; // TBD
};
</pre>

[[Category:File formats]]

MPD format

2016-09-08T23:23:51Z

FireFly: /* Tile data */ Update struct map_tile

The '''MPD format''' is used to describe map data.

A note on convention: the coordinate system in this article treats positive x as east, positive y as down (that is, "forward"), and positive z as north, if you're looking at the map from above. This makes it a left-hand coordinate system.

== Header ==
<pre>
struct header {
u16 n_chunks; // #chunks in map file
u16 n_actors; // #actors in map file
u16 unknown;
u8 padding[10];
};
</pre>

== Chunk ==
The header is followed by ''n_chunks'' chunks. Each "chunk" is fixed-size, and contains map tiles, objects and event tiles. All map tile data is stored outside the chunks section, whereas objects and event tiles are stored within it (and thus there's a limit to the number of objects/events in a chunk).

<pre>
struct chunk {
struct chunk_header header;
struct chunk_object_entry objects[32];
struct chunk_event_tile_entry event_tiles[16];
struct map_tile weird_special_tile;
};
</pre>

=== Header ===
<pre>
struct chunk_header {
f32 map_offset_x; // (val - 6)/12
f32 unk1_1;
f32 map_offset_z; // (val - 6)/12
f32 unk1_2;
f32 unk1[7];
u16 n_tiles; // #tiles within chunk
u8 unk2, unk3;
u16 index; // index of chunk (starts at 0)
u8 unk4[14];
};
</pre>

The ''map_offset_x'' and ''map_offset_z'' fields warrant some explanation: the map editor allows you to shift the whole map around, and instead of updating all tiles individually, these chunk-wide settings get changed. Actors' coordinates are updated, and are not affected by this offset. Whenever tiles get read, a tile that has stored location ''(x, z)'' effectively ends up at ''(x + map_offset_x, z + map_offset_z)'' instead. Why are they floats, you say? No idea.

=== Object table ===
Each chunk fits up to 32 objects (padded with null bytes if there's fewer).

<pre>
struct chunk_object_entry {
i16 unk1, unk2, unk3, unk4, unk5;
i16 unk6, unk7, unk8, unk9, unk10;
u8 unk11, unk12, unk13, unk14, unk15, unk16;
u8 pad[10];
};
</pre>

=== Event tile table ===
Each chunk fits up to 16 event tiles (padded with null bytes if there's fewer).

<pre>
struct chunk_event_tile_entry {
i8 x, z;
u8 index;
u8 pad1;
};
</pre>

== Tile data ==
The number of tiles in the tile data section is the sum of ''n_tiles'' for all chunks. Presumably the tiles are assigned to chunks in the order they appear, so the first ''chunk[0].header.n_tiles'' tiles belong to chunk 0, etc.

<pre>
struct texdata {
u8 u, v;
u8 unk[6]; // TBD
};

struct map_tile {
struct texdata textures[12]; 1// N, W, S, E, Top; same repeated with unknown meaning (repeated texture?); 2 unknown textures
i8 corners[4]; // Height in each corner of the tile, negative = up; (SW, SE, NW, NE) (needs verification!)
i8 corners2[4]; // \ Related to bottom corners of tile, somehow. All zero except for "floating platforms" (e.g. mp1302)
i8 corners3[4]; // /
u8 unk2[4]; // TBD
u8 unk3;
i8 x, z;
u8 unk4, unk5, unk6, unk7;
u8 mobility; // 0 = Unlimited, 1 = Fly only, 2 = Impassable
u8 geo_color;
u8 geo_mark; // 0 = No geopanel, 100 = Has geopanel
u8 pad2[6];
};
</pre>

== Actor data ==
The number of actors is given by ''n_actors'' in the file header.

<pre>
struct map_actor {
u16 id; // Class ID
u16 level;
u8 unk2;
i8 x, z;
i8 rotation; // -1 = W, 0 = N, 1 = E, 2 = S
u8 unk4;
u8 ai; // ? verify
u8 unk5, unk6;
u16 items[4];
u8 appearance; // 0 = Appear Normal, 1 = Absent 2nd, 2 = Appear 2nd
u8 unk7;
u16 geo_effect; // Only(?) used for geosymbols, val%10 = color, val/10 = effect
u16 unk8;
u16 magic[4];
i8 unk[30]; // TBD
};
</pre>

[[Category:File formats]]

MPD format

2016-09-08T22:33:40Z

FireFly: /* Header */

The '''MPD format''' is used to describe map data.

A note on convention: the coordinate system in this article treats positive x as east, positive y as down (that is, "forward"), and positive z as north, if you're looking at the map from above. This makes it a left-hand coordinate system.

== Header ==
<pre>
struct header {
u16 n_chunks; // #chunks in map file
u16 n_actors; // #actors in map file
u16 unknown;
u8 padding[10];
};
</pre>

== Chunk ==
The header is followed by ''n_chunks'' chunks. Each "chunk" is fixed-size, and contains map tiles, objects and event tiles. All map tile data is stored outside the chunks section, whereas objects and event tiles are stored within it (and thus there's a limit to the number of objects/events in a chunk).

<pre>
struct chunk {
struct chunk_header header;
struct chunk_object_entry objects[32];
struct chunk_event_tile_entry event_tiles[16];
struct map_tile weird_special_tile;
};
</pre>

=== Header ===
<pre>
struct chunk_header {
f32 map_offset_x; // (val - 6)/12
f32 unk1_1;
f32 map_offset_z; // (val - 6)/12
f32 unk1_2;
f32 unk1[7];
u16 n_tiles; // #tiles within chunk
u8 unk2, unk3;
u16 index; // index of chunk (starts at 0)
u8 unk4[14];
};
</pre>

The ''map_offset_x'' and ''map_offset_z'' fields warrant some explanation: the map editor allows you to shift the whole map around, and instead of updating all tiles individually, these chunk-wide settings get changed. Actors' coordinates are updated, and are not affected by this offset. Whenever tiles get read, a tile that has stored location ''(x, z)'' effectively ends up at ''(x + map_offset_x, z + map_offset_z)'' instead. Why are they floats, you say? No idea.

=== Object table ===
Each chunk fits up to 32 objects (padded with null bytes if there's fewer).

<pre>
struct chunk_object_entry {
i16 unk1, unk2, unk3, unk4, unk5;
i16 unk6, unk7, unk8, unk9, unk10;
u8 unk11, unk12, unk13, unk14, unk15, unk16;
u8 pad[10];
};
</pre>

=== Event tile table ===
Each chunk fits up to 16 event tiles (padded with null bytes if there's fewer).

<pre>
struct chunk_event_tile_entry {
i8 x, z;
u8 index;
u8 pad1;
};
</pre>

== Tile data ==
The number of tiles in the tile data section is the sum of ''n_tiles'' for all chunks. Presumably the tiles are assigned to chunks in the order they appear, so the first ''chunk[0].header.n_tiles'' tiles belong to chunk 0, etc.

<pre>
struct texdata {
u8 u, v;
u8 unk[6]; // TBD
};

struct map_tile {
struct texdata textures[5]; // N, W, S, E, Top
struct texdata textures2[5]; // Same order, unknown meaning (maybe repeated texture)
u8 unk1[0x10]; // TBD
i8 corners[4]; // Height in each corner of the tile, negative = up; (SW, SE, NW, NE) (needs verification!)
u8 unk2[0x0C]; // TBD
u8 unk3;
i8 x, z;
u8 unk4, unk5, unk6, unk7;
u8 mobility; // 0 = Unlimited, 1 = Fly only, 2 = Impassable
u8 geo_color;
u8 geo_mark; // 0 = No geopanel, 100 = Has geopanel
u8 pad2[6];
};
</pre>

== Actor data ==
The number of actors is given by ''n_actors'' in the file header.

<pre>
struct map_actor {
u16 id; // Class ID
u16 level;
u8 unk2;
i8 x, z;
i8 rotation; // -1 = W, 0 = N, 1 = E, 2 = S
u8 unk4;
u8 ai; // ? verify
u8 unk5, unk6;
u16 items[4];
u8 appearance; // 0 = Appear Normal, 1 = Absent 2nd, 2 = Appear 2nd
u8 unk7;
u16 geo_effect; // Only(?) used for geosymbols, val%10 = color, val/10 = effect
u16 unk8;
u16 magic[4];
i8 unk[30]; // TBD
};
</pre>

[[Category:File formats]]

MPD format

2016-09-08T22:31:47Z

FireFly: /* Header */ NIS why

The '''MPD format''' is used to describe map data.

A note on convention: the coordinate system in this article treats positive x as east, positive y as down (that is, "forward"), and positive z as north, if you're looking at the map from above. This makes it a left-hand coordinate system.

== Header ==
<pre>
struct header {
u16 n_chunks; // #chunks in map file
u16 n_actors; // #actors in map file
u16 unknown;
u8 padding[10];
};
</pre>

== Chunk ==
The header is followed by ''n_chunks'' chunks. Each "chunk" is fixed-size, and contains map tiles, objects and event tiles. All map tile data is stored outside the chunks section, whereas objects and event tiles are stored within it (and thus there's a limit to the number of objects/events in a chunk).

<pre>
struct chunk {
struct chunk_header header;
struct chunk_object_entry objects[32];
struct chunk_event_tile_entry event_tiles[16];
struct map_tile weird_special_tile;
};
</pre>

=== Header ===
<pre>
struct chunk_header {
f32 map_offset_x; // (val - 6)/12
f32 unk1_1;
f32 map_offset_z; // (val - 6)/12
f32 unk1_2;
f32 unk1[7];
u16 n_tiles; // #tiles within chunk
u8 unk2, unk3;
u16 index; // index of chunk (starts at 0)
u8 unk4[14];
};
</pre>

The ''map_offset_x'' and ''map_offset_z'' fields warrant some explanation: the map editor allows you to shift the whole map around, and instead of updating all tiles individually, these chunk-wide settings get changed. Actors' coordinates are updated, and are not affected by this offset. Whenever tiles get read, a tile that has stored location ''(x, z)'' effectively ends up at ''(x + map_offset_x, z + map_offset_z)'' instead. Why are they floats, you say? No idea.

=== Object table ===
Each chunk fits up to 32 objects (padded with null bytes if there's fewer).

<pre>
struct chunk_object_entry {
i16 unk1, unk2, unk3, unk4, unk5;
i16 unk6, unk7, unk8, unk9, unk10;
u8 unk11, unk12, unk13, unk14, unk15, unk16;
u8 pad[10];
};
</pre>

=== Event tile table ===
Each chunk fits up to 16 event tiles (padded with null bytes if there's fewer).

<pre>
struct chunk_event_tile_entry {
i8 x, z;
u8 index;
u8 pad1;
};
</pre>

== Tile data ==
The number of tiles in the tile data section is the sum of ''n_tiles'' for all chunks. Presumably the tiles are assigned to chunks in the order they appear, so the first ''chunk[0].header.n_tiles'' tiles belong to chunk 0, etc.

<pre>
struct texdata {
u8 u, v;
u8 unk[6]; // TBD
};

struct map_tile {
struct texdata textures[5]; // N, W, S, E, Top
struct texdata textures2[5]; // Same order, unknown meaning (maybe repeated texture)
u8 unk1[0x10]; // TBD
i8 corners[4]; // Height in each corner of the tile, negative = up; (SW, SE, NW, NE) (needs verification!)
u8 unk2[0x0C]; // TBD
u8 unk3;
i8 x, z;
u8 unk4, unk5, unk6, unk7;
u8 mobility; // 0 = Unlimited, 1 = Fly only, 2 = Impassable
u8 geo_color;
u8 geo_mark; // 0 = No geopanel, 100 = Has geopanel
u8 pad2[6];
};
</pre>

== Actor data ==
The number of actors is given by ''n_actors'' in the file header.

<pre>
struct map_actor {
u16 id; // Class ID
u16 level;
u8 unk2;
i8 x, z;
i8 rotation; // -1 = W, 0 = N, 1 = E, 2 = S
u8 unk4;
u8 ai; // ? verify
u8 unk5, unk6;
u16 items[4];
u8 appearance; // 0 = Appear Normal, 1 = Absent 2nd, 2 = Appear 2nd
u8 unk7;
u16 geo_effect; // Only(?) used for geosymbols, val%10 = color, val/10 = effect
u16 unk8;
u16 magic[4];
i8 unk[30]; // TBD
};
</pre>

[[Category:File formats]]

Main Page

2016-09-08T14:48:50Z

FireFly: Might as well link directly to the DS subpage, too.

A wiki in which we reverse engineer NIS's shit

Spoiler: it often ''is'' shit

We mainly hang out on IRC, in '''#disgaea''' on Badnik (''irc.badnik.zone''). Currently focusing on understanding Disgaea 1 better.

== Games ==
* [[Disgaea 1]] (PS2, PSP, [[Disgaea 1/DS|DS]], PC, TTHM)

== I want to edit ==
PM xkeeper on IRC then.

2016-09-06T20:44:39Z

FireFly: Whee, now we can decompress DS maps

The '''MPDS format''' holds map data in the DS version of Disgaea 1. It is actually just a compressed [[MPD format|MPD file]], with an extra footer appended to the compressed data.

It's fairly likely that this is a known compression that already has a name, in which case the compression part should probably be moved to a separate article. For now, though, it'll be described here.

== Compression ==
There is a very brief header consisting of a 0x10 byte (as "magic number"/to identify compression algorithm), followed by the decompressed size as a 24-bit little-endian integer. Compressed data follows after that.

The compression format is LZ-like, featuring bytes to be copied verbatim as well as backreferences to repeat a string of bytes that has been produced recently.

Before each group of 8 items (verbatim bytes or backrefs) is a byte, its bits acting as flags indicating whether the corresponding item is a verbatim byte (if 0) or a backref (if 1), starting from most down to least significant bit. Thus, ''0x43'' would mean 1 verbatim byte, 1 backref, 4 verbatim bytes, 2 backrefs.

Backrefs are two bytes wide, its bits forming a pattern <code>xxxxyyyy yyyyyyyy</code>. Such a backref represents repeating ''x+3'' bytes from ''y + 1'' bytes back in history.

== Compressed footer ==
At the end of the decompressed data, after the MPD format proper, is a footer consisting of two lists of u32's, both prefixed by a u32 containing the length of the list. It is unknown what these are for.

== C decompressor ==
Here is the source code for a hacky decompressor written in C.

<pre>
#include <assert.h>
#include <stdint.h>
#include <stdio.h>

typedef uint8_t u8;
typedef uint16_t u16;
typedef uint32_t u32;

int decompress(FILE *in, FILE *out, size_t decompressed_size) {
#define CONTEXT 0x1000
#define BIT(n, b) (((n) >> (b)) & 1)

u8 history[CONTEXT];
size_t i = 0,
read = 0,
written = 0;

#define READ() (read++, fgetc(in))
#define WRITE(x) { \
history[i] = (x); \
fputc(history[i], out); \
written++; \
i = (i + 1) & (CONTEXT - 1); \
}

while (written < decompressed_size && !feof(in)) {
u8 flags = READ();
for (int b = 7; b >= 0 && written < decompressed_size; b--) {
if (BIT(flags, b)) {
// Copy from history
u8 x = READ();
size_t count = (x >> 4) + 3;
size_t offset = (((x & 0x0F) << 8) | READ()) + 1;

for (int j = 0; j < count; j++) {
WRITE(history[(i - offset) & (CONTEXT - 1)]);
}

} else {
// Copy input to output
WRITE(READ());
}
}
}

if (written == decompressed_size) {
return written;
} else {
return -1;
}

#undef CONTEXT
#undef BIT
#undef READ
#undef WRITE
}

int main(int argc, char *argv[]) {
if (argc != 2) {
fprintf(stderr, "Usage: %s <file.mpds>\n", argv[0]);
return 1;
}

FILE *f = fopen(argv[1], "r");
if (f == NULL) {
fprintf(stderr, "Couldn't open '%s' for reading.", argv[1]);
return 1;
}

// Read header
u32 header;
fread(&header, sizeof(u32), 1, f);
u8 magic = header & 0xFF;
size_t dec_size = (header >> 8);

// Decompress
int n = decompress(f, stdout, dec_size);
if (n < 0) {
fprintf(stderr, "Error while decompressing.\n");
return 2;
}

return 0;
}
</pre>

MPD format

2016-09-06T17:03:43Z

FireFly: +cat

The '''MPD format''' is used to describe map data.

== Header ==
<pre>
struct header {
u16 n_chunks; // #chunks in map file
u16 n_actors; // #actors in map file
u16 unknown;
u8 padding[10];
};
</pre>

== Chunk ==
The header is followed by ''n_chunks'' chunks. Each "chunk" is fixed-size, and contains map tiles, objects and event tiles. All map tile data is stored outside the chunks section, whereas objects and event tiles are stored within it (and thus there's a limit to the number of objects/events in a chunk).

<pre>
struct chunk {
struct chunk_header header;
struct chunk_object_entry objects[32];
struct chunk_event_tile_entry event_tiles[16];
struct map_tile weird_special_tile;
};
</pre>

=== Header ===
<pre>
struct chunk_header {
u8 unk1[24];
u16 n_tiles; // #tiles within chunk
u8 unk2, unk3;
u16 index; // index of chunk (starts at 0)
u8 unk4[14];
};
</pre>

=== Object table ===
Each chunk fits up to 32 objects (padded with null bytes if there's fewer).

<pre>
struct chunk_object_entry {
i16 unk1, unk2, unk3, unk4, unk5;
i16 unk6, unk7, unk8, unk9, unk10;
u8 unk11, unk12, unk13, unk14, unk15, unk16;
u8 pad[10];
};
</pre>

=== Event tile table ===
Each chunk fits up to 16 event tiles (padded with null bytes if there's fewer).

<pre>
struct chunk_event_tile_entry {
u8 y, x;
u8 index;
u8 pad1;
};
</pre>

== Tile data ==
The number of tiles in the tile data section is the sum of ''n_tiles'' for all chunks. Presumably the tiles are assigned to chunks in the order they appear, so the first ''chunk[0].header.n_tiles'' chunks belong to chunk 0, etc.

<pre>
struct map_tile {
u8 unk1[0x60]; // TBD
i8 corners[4]; // Height in each corner of the tile, negative = up; (NW, NE, SW, SE)
u8 unk2[0x0C]; // TBD
u8 unk3;
u8 y, x;
u8 unk4, unk5, unk6, unk7;
u8 mobility; // 0 = Unlimited, 1 = Fly only, 2 = Impassable
u8 geo_color;
u8 geo_mark; // 0 = No geopanel, 100 = Has geopanel
u8 pad2[6];
};
</pre>

== Actor data ==
The number of actors is given by ''n_actors'' in the file header.

<pre>
struct map_actor {
u16 id; // Class ID
u16 unk1;
u8 unk2;
u8 y, x;
i8 unk3;
u8 unk4, unk5, unk6;

i8 unk[53]; // TBD, various fields
/*
unk[9]: (0:Appear Normal, 1:Absent 2nd, 2:Appear 2nd)
*/
};
</pre>

[[Category:File formats]]

MPD format

2016-09-06T17:03:10Z

FireFly: Describe what is currently known about the MPD format.

The '''MPD format''' is used to describe map data.

== Header ==
<pre>
struct header {
u16 n_chunks; // #chunks in map file
u16 n_actors; // #actors in map file
u16 unknown;
u8 padding[10];
};
</pre>

== Chunk ==
The header is followed by ''n_chunks'' chunks. Each "chunk" is fixed-size, and contains map tiles, objects and event tiles. All map tile data is stored outside the chunks section, whereas objects and event tiles are stored within it (and thus there's a limit to the number of objects/events in a chunk).

<pre>
struct chunk {
struct chunk_header header;
struct chunk_object_entry objects[32];
struct chunk_event_tile_entry event_tiles[16];
struct map_tile weird_special_tile;
};
</pre>

=== Header ===
<pre>
struct chunk_header {
u8 unk1[24];
u16 n_tiles; // #tiles within chunk
u8 unk2, unk3;
u16 index; // index of chunk (starts at 0)
u8 unk4[14];
};
</pre>

=== Object table ===
Each chunk fits up to 32 objects (padded with null bytes if there's fewer).

<pre>
struct chunk_object_entry {
i16 unk1, unk2, unk3, unk4, unk5;
i16 unk6, unk7, unk8, unk9, unk10;
u8 unk11, unk12, unk13, unk14, unk15, unk16;
u8 pad[10];
};
</pre>

=== Event tile table ===
Each chunk fits up to 16 event tiles (padded with null bytes if there's fewer).

<pre>
struct chunk_event_tile_entry {
u8 y, x;
u8 index;
u8 pad1;
};
</pre>

== Tile data ==
The number of tiles in the tile data section is the sum of ''n_tiles'' for all chunks. Presumably the tiles are assigned to chunks in the order they appear, so the first ''chunk[0].header.n_tiles'' chunks belong to chunk 0, etc.

<pre>
struct map_tile {
u8 unk1[0x60]; // TBD
i8 corners[4]; // Height in each corner of the tile, negative = up; (NW, NE, SW, SE)
u8 unk2[0x0C]; // TBD
u8 unk3;
u8 y, x;
u8 unk4, unk5, unk6, unk7;
u8 mobility; // 0 = Unlimited, 1 = Fly only, 2 = Impassable
u8 geo_color;
u8 geo_mark; // 0 = No geopanel, 100 = Has geopanel
u8 pad2[6];
};
</pre>

== Actor data ==
The number of actors is given by ''n_actors'' in the file header.

<pre>
struct map_actor {
u16 id; // Class ID
u16 unk1;
u8 unk2;
u8 y, x;
i8 unk3;
u8 unk4, unk5, unk6;

i8 unk[53]; // TBD, various fields
/*
unk[9]: (0:Appear Normal, 1:Absent 2nd, 2:Appear 2nd)
*/
};
</pre>