LEB

LEB is a custom format used to store room data in Link's Awakening.

This format is still in the process of being reverse engineered and so this page is currently incomplete.

Format

LEB files are in a FixedHash format, with the data for actors stored in the data section and the names section. There is consistency in how the FixedHash is built for LEB files, with the exception of Lv07EagleTower_05E (the lower part of the Eagle boss room), which for some reason is different than all other rooms. Aside from this room, LEBs always have 0x17 hash table buckets and 0x4 child FixedHash nodes. The buckets are always the same, so the start of LEB files always look like:

3d01 1700 0400 0000 ffff ffff 0000 0000

2000 0000 ffff ffff ffff ffff ffff ffff

ffff ffff ffff ffff 4000 0000 ffff ffff

ffff ffff 5000 0000 ffff ffff 3000 0000

ffff ffff ffff ffff ffff ffff ffff ffff

ffff ffff

Entries Section

There are 6 entries in most LEB files.


Node Index	Name Offset	Name Hash	Next entry offset	Data Offset
0xFFF0	Offset of `version`in the names section	Hash of `version`	0xFFFFFFFF	Offset to version section
0xFFF0	Offset of `infomation`in the names section [sic]	Hash of `infomation`	0xFFFFFFFF	Offset to infomation
0x0	Offset of `point`in the names section	Hash of `point`	0xFFFFFFFF	Offset to point section
0x1	Offset of `rail`in the names section	Hash of `rail`	0xFFFFFFFF	Offset to rail section
0x2	Offset of `actor`in the names section	Hash of `actor`	0x10	Offset to actor section
0x3	Offset of `grid`in the names section	Hash of `grid`	0xFFFFFFFF	Offset to grid secion

Data Section

The data section contains one subsection for each entry (usually six).

Version Section

This section holds a u64 with the value 0x3 (specifying 3 bytes of data), followed by the 3 bytes of data, which seem to always be 0x1001D4. Whether it has a purpose is unclear. Given the name, it could just be a version marker. Following this is five empty bytes.

Infomation Section

This section holds a u64 with the value 0x4 (specifying 4 bytes of data), followed by the 4 bytes of data. Its purpose is unknown. Following this is four empty bytes.

Point Section

This is a FixedHash child. It's usually empty and has 1 bucket and no child nodes. The names section is empty. Purpose unknown.

An example of a room which has a non-empty FixedHash here is Lv01TailCave_04G (Moldorm boss room).

Rail Section

This is another FixedHash child. Usually it's empty and has 1 bucket and no child nodes. The names section is empty. Purpose unknown.

An example of a room which has a non-empty FixedHash here is Lv01TailCave_04G (Moldorm boss room).

Actor Section

This section is a FixedHash which holds actor data. Each entry corresponds to one actor. Every entry points to non-node data, usually blocks of 0x90 bytes, but sometimes longer. The names section is empty. The data block for each actor is formatted as follows:


Offset	Type	Description
0x0	u64	Actor key. This value must match the hex value of the corresponding actor label in the (top-level) names section.
0x8	u32	Names section offset. This stores the offset in the (top-level) names section for the start of the label that corresponds to this actor.
0xC	u16	Actor ID
0xE	u16	Padding?
0x10	u32	Room ID. The actor loads when entering the specified room and unloads when leaving it. Generally this should be consistent across all actors in the file, since each room has its own file.
0x14	u32	X coordinate. One “tile” is 0xC0000 units, so using the lower 2 bytes here is going to generally be pretty insignificant. Hence them usually being 0
0x18	u32	Appears to be Z coordinate (height). However it scales very strangely, maybe not linear?
0x1C	u32	Y coordinate. One “tile” is 0xC0000 units, so using the lower 2 bytes here is going to generally be pretty insignificant. Hence them usually being 0
0x20	u32	Unknown
0x24	u32	Unknown
0x28	u32	Unknown. Mostly only used on lighting actors
0x2C	u32	Unknown. Commonly 0x3F800000
0x30	u32	Unknown. Commonly 0x3F800000
0x34	u32	Unknown. Commonly 0x3F800000
0x38	u32[16]	Parameters. This section contains 16 u32's, which are grouped into 8 pairs of [parameter, parameter type]. For any pair, the first 4 bytes make up the value of the parameter. This can be basically anything (will include some known parameters for certain actor types below). The second 4 bytes indicate what the purpose of the parameter is. There are only 3 observed values so far: 0x0, which indicates the parameter is not used? 0x2, unknown purpose. Observable on the small key in Lv04AnglersTunnel_06A among other rooms, but the parameters appear to not do anything. 0x3, which indicates that the parameter is an integer parameter, taken as just the value of the first u32. 0x4, which indicates that the parameter is a string parameter specified in the names section. The value in the previous u32 is the offset in the names section for this parameter. Most actors have "blank " parameters filled in as offsets to the 2nd null byte after the first label in the names section; however, this seems to be functionally equivalent to leaving the parameter as 0.
0x78		Actor Switches. Defines 4 actor switches for the event. These are used for the behavior of many things like small keys, chests, NPCs, loading zones, doors, blocks, etc. First there is 4 bytes which define the usage of actor switches 0-3 respectively: 0: Appears to define an index in set a of local flags for the room. For example, whether a torch is lit or not, a bush is cut or not, etc. 1: The actor switch is the index of a global flag. 2: Defines a hardcoded value for the switch, usually 1. For example, while some treasure chests appear based on a global flag being set, some don't; these ones would just use this hardcoded 1 instead of a flag index. 3: Used only on actors in panel dungeon rooms. Appears to be an index for a flag system specific to panel dungeons. 4: The switch is unused. Following this are the four actor switch definitions, each 2 bytes (u16).
0x84		Actor Relationships. Defines the relationship this actor has with other actors in the room, primarily for use with events. This section uses a lot of actor indexes, which are the based on the order the actors are defined in the room. That is, the first defined actor is 0, the second is 1, etc. The sections starts with 8 bytes which define the structure and purpose of the data in the section, followed by 4 null bytes, and then followed by 3 sections of data. xx bb kk ee 00 00 yy zz 00 00 00 00 x indicates the number of actors in section 1. y indicates the number of actors in section 2. z indicates the number of actors in section 3. b appears to be 01 if the enemy appears from the +enemies tile in a chamber dungeon and 00 otherwise. k is 01 only for TagHolocaustChecker actors. Probably indicates looking at enemy spawns/kills. e is 01 for all enemies and 00 for anything else. Section 1 defines which other actors have behaviors controlled by this actor. This includes actors which get used by this actor's event, enemies that a TagHolocaustChecker watches for, that an AreaEventBox/AreaLevelOpen/etc will trigger this actor, and possibly other uses. It consists of a sequence of 20-byte structures, which are each 2 parameters (8 bytes each, same format as parameter section) and a 4-byte actor index. Section 2's purpose is not yet known. It consists of a sequence of 24-byte structures, which are each 2 parameters (8 bytes each), and 2 u32's. Section 3 defines which actors can call upon use of this actor. It is simply a sequence of 4-byte actor indexes. This should line up with section 1 of other actors. As an example, if actor[2] defines control of actor[5] in its section 1, then actor[5]'s section 3 should contain 0x02.

Grid Section

Another child FixedHash. It has a name section which usually contains two strings: data and info. Some have other strings in between, such as Lv08TurtleRock_01H (right half of the sidescroller leading to the boss). This FixedHash has one Entry for each of these strings in the names section. Each entry holds a block of data. It seems like the block of data for the info entry is also 0x10 bytes, and the data for the data section is almost always 0x500 bytes, except in some cases (like the aforementioned room with an extra entry in this fixed hash).

The data in the data section contains 80 blocks 0x10 bytes each which define some properties for every tile on the screen (which is 10 by 8). The exact format is still unknown.

Names Section

The names section contains a list of actors by name, followed by a hyphen (-), followed by a 16-digit hexadecimal number. This also includes some plaintext parameters for some objects, such as the contents of a chest (ObjTreasureBox) or the destination of a loading zone (AreaLevelOpen). Note that these do not define what actors exist, in fact it seems like the actual labels here are meaningless aside from the aforementioned parameters.

All labels in the names section are separated by null bytes. Of note, there seems to always be one separator that 2 null bytes instead of 1. Depending on the file, this is either between point and rail at the start of the names section, or between the 1st and 2nd listed actors (it is more commonly the latter).