Object List file

From RRU Knowledge Base
Revision as of 03:49, 15 September 2017 by Jessietail (talk | contribs)

This article is an unfinished work in progress or contains transferred information that needs to be rewritten or reformatted to fit our standards. Please excuse the mess and do not mark for deletion.

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. The configuration data in them is unencrypted and can easily be edited with even Notepad.

Each entry in the OL File 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. The maximum number of objects that can be present in the OL file at a time is 200 (anymore would exceed its memory pool, causing the level to crash). While the allotted name of the object in the can be anything, it typically is in the format "Object#" using a number "#" to keep track of the amount of Objects used. Any special objects that are used in script are referred to using this allotted name.

Typical Ol File Format:

Lego* {

	Object1 {
		type	[ObjectName]
		xPos	[X-Coordinate Location]
		yPos	[Y-Coordinate Location]
		heading	[Facing Angle]
	}

}

Where ObjectName is an object as it is defined in the ObjectNames or MiscObjects lists in the Main LEGO Config file.

If an object list is missing a camera, the game will crash on startup. If an object list has a camera but lacks any exposed units, the game will run up to Chief's briefing in that level, where it will softlock.