39
edits
LEB: Difference between revisions
m
no edit summary
(Filled in more info) |
mNo edit summary |
||
| Line 40: | Line 40: | ||
|0x18 | |0x18 | ||
|u32 | |u32 | ||
|'''Room ID'''. The actor loads when entering the specified room and unloads when leaving it. | |'''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. | ||
|- | |- | ||
|0x1C | |0x1C | ||
| Line 65: | Line 65: | ||
The second 4 bytes indicate what the purpose of the parameter is. There are only 3 observed values so far: | 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? | *0x0, which indicates the parameter is not used? | ||
* 0x3, which indicates that the parameter is a direct parameter. e.g., the parameter 0x1 is used to indicate being able to push a block actor. | *0x3, which indicates that the parameter is a direct parameter. e.g., the parameter 0x1 is used to indicate being able to push a block actor. | ||
* 0x4, which indicates that the parameter is a plaintext parameter specified in the names section. The value in the previous u32 is the offset in the names section for this parameter. | *0x4, which indicates that the parameter is a plaintext 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 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. | 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. | ||
|- | |- | ||
|0x80-0x97 | |0x80-0x97 | ||