Difference between revisions of "PTL file"

From RRU Knowledge Base
Line 1: Line 1:
{{WIP}}
{{WIP}}
One of several [[level files]] located in a Mission's level folder, the '''PTL File''' controls the [[artificial intelligence]] of the Rock Raiders. It designates what actions the Rock Raider is capable of doing, and the default order of preference. Every game [[level]] uses basically the same contents.  Tutorial levels, however, disable certain actions by not including them in the PTL.  It is suggested that you leave this file alone, as it can seriously and adversely affect the behavior of the Rock Raiders.
'''PTL files''' are [[File formats in LEGO Rock Raiders|configuration files]] used in the Windows version of [[LEGO Rock Raiders (video game)|''LEGO Rock Raiders'']] to control artificial intelligence. They designate cause and effect in game events, what actions [[Rock Raider]]s and [[Rock Raiders creatures]] are capable of doing, and the default order of preference. Every [[LEGO Rock Raiders missions|mission]] has its own PTL file located in its level folder, and will crash while loading if one does not exist. All default PTL files are identical, (with the exception of training missions, which disable certain actions), but they can be individually modified to change the AI in any mission.
 
Further research has revealed that it not only controls the AI of the Rock Raiders, but also of other creatures.
It even is possible to alter game events using the '''PTL File'''. Such as clearing [[rubble]] causing [[rock monsters]] to emerge.


Below is a complete list of "messages" as the exe calls them
Below is a complete list of "messages" as the exe calls them

Revision as of 14:53, 9 June 2018

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.

PTL files are configuration files used in the Windows version of LEGO Rock Raiders to control artificial intelligence. They designate cause and effect in game events, what actions Rock Raiders and Rock Raiders creatures are capable of doing, and the default order of preference. Every mission has its own PTL file located in its level folder, and will crash while loading if one does not exist. All default PTL files are identical, (with the exception of training missions, which disable certain actions), but they can be individually modified to change the AI in any mission.

Below is a complete list of "messages" as the exe calls them

I have no idea how to arrange this, or what to call properties vs their "answers", especially the ones that can be used as both

Property Action
Debug_DestroyAll
ClearRemovePathComplete
ClearRemovePath
ClearInitialComplete
ClearInitial
ClearBuildingComplete
ClearBuilding
UpgradeComplete
Upgrade
GenerateFromCryOreComplete
GenerateFromCryOre
GenerateCrystalAndOreComplete
GenerateCrystalAndOre
TrainComplete
Train
BuildPathComplete
BuildPath
ReduceSelection
CollectTool
FollowAttack
ManSelectedAndMonsterClicked
GetIn
AttackBuildingComplete
AttackBuilding
PickRandomFloorComplete
PickRandomFloor
GatherRockComplete
GatherRock
GenerateRockMonsterComplete
GenerateRockMonster
ClearFallInComplete
ClearFallIn
ClearComplete
Clear
CollectOreComplete
CollectOre
GenerateOreComplete
GenerateOre
CrystalToRefineryComplete
CrystalToRefinery
CollectCrystalComplete
CollectCrystal
GenerateCrystalComplete
GenerateCrystal
RockFallComplete
RockFall
ReinforceComplete
Reinforce
RepairComplete
Repair
DigComplete
Dig
PlaySample
TopView
TrackObject
FirstPerson
UserGoto
RockMonsterGotoComplete
RockMonsterGoto
Goto
Deselect
ClearSelection
Selected
Select
Null

Properties

Property Action
DigComplete Defines what to do after a Rock Raider has finished digging a wall. It is usually set to RockFall.
GatherRockComplete Defines what to do after a monster has gathered a boulder. It is usually set to AttackBuilding.
GenerateRockMonsterComplete Defines what to do after a monster has emerged.

Messages

Property Action
GenerateRockMonster Causes a monster to emerge. The location is completely random on any valid wall (not a corner, not solid rock, and not blocked by water, lava, or a building) rather than defined by the emerge map.