Difference between revisions of "Object List file"
Jessietail (talk | contribs) |
Jessietail (talk | contribs) |
||
| Line 3: | Line 3: | ||
They use the filename extension <code>.ol</code>, though any extension can be used as long as its internal formatting remains the same. | They use the filename extension <code>.ol</code>, though any extension can be used as long as its internal formatting remains the same. | ||
== | == Coding == | ||
{{todo|Rewrite first paragraph here}} | {{todo|Rewrite first paragraph here}} | ||
Each entry in an Object List designates the coordinates and facing angle of a certain object. | Each entry in an Object List designates the coordinates and facing angle of a certain object. | ||
Revision as of 05:36, 15 September 2017
Object List files are configuration files used in the Windows PC version of LEGO Rock Raiders to designate the starting locations of Rock Raiders, buildings, vehicles, creatures, building materials, webs, and the game camera within levels.
Each level's Object List is linked to in that level's section in Lego.cfg using the line OListFile, and is by default located within that level's folder.
They use the filename extension .ol, though any extension can be used as long as its internal formatting remains the same.
Coding
To do: Rewrite first paragraph here
Each entry in an Object List designates the coordinates and facing angle of a certain object. Buildings are often placed with the main part of the construction in the center of a block (ex: 7.5, 8.5), with the Power Path part of the construction pointing towards the facing angle. The facing angle or heading is in degrees in typical compass format, with 0 degrees pointing to the top of the map, and 90 degrees pointing to the right side of the map.
An Object List can have a maximum of 200 entries; going over this limit exceeds its memory pool, causing the level to crash[verify]. While the allotted name of an object can be anything, it's typically in the format Object# (using a number in place of #) to keep track of the amount of objects used. Any special objects that are used in script are referred to using this allotted name.
If an Object List doesn't have a camera defined, the game will crash while loading at startup. If there is a camera but no non-hidden controllable units, the game will run up through the briefing for that mission, at which point it will softlock.
Example
Lego* {
Object1 {
type [ObjectName]
xPos [X-Coordinate Location]
yPos [Y-Coordinate Location]
heading [Facing Angle]
}
Object2 {
type [ObjectName]
xPos [X-Coordinate Location]
yPos [Y-Coordinate Location]
heading [Facing Angle]
}
}
Modding
Object List files are unencrypted and can easily be edited with even Notepad.
To do: write editing OL files after forums are back up
