Conditions
From EliteWiki
Conditions Whether scripted actions should occur, is determined by a conditions entry. Below is a compilation of used conditions and the proper parameters used.
Contents |
[edit] Player States
[edit] dockedAtMainStation_bool
Checks if player is docked at a proper planet-station. Example: dockedAtMainStation_bool equal YES
[edit] gui_screen_string
Compares the drawn GUI screen to the GUI-screen-parameter. Example: gui_screen_string equal GUI_SCREEN_SYSTEM_DATA
[edit] score_number
Compares the value to the player kill number. Example: score_number greaterthan 1280
[edit] scriptTimer_number
Seconds counted from start of mission? Example: scriptTimer_number lessthan 60
[edit] status_string
Checks on the player-status (see AI-reference.html for more on states). Example: status_string equal STATUS_DOCKED
[edit] mission_yourmission
Compares the mission state of yourmission. Example: mission_conhunt equal MISSION_COMPLETE Parameters can be 'undefined', 'MISSION_COMPLETE' or any other defined (Set) mission state.
[edit] missionChoice_string
Determines a players choice from a setMissionChoices method. Yes or No. Example: missionChoice_string equal YES
[edit] System states
[edit] galaxy_number
Compares with the galaxy number the player is in, numbered from 0 to 7. Example: galaxy_number equal 2
[edit] planet_number
Compares to the players current location. Example: planet_number equal 7
- for Lave.
[edit] sunWillGoNova_bool
Specialised Nova-mission condition
[edit] Search results
[edit] shipsFound_number
Compares the number found by a 'checkForShips: shiptype' method to the parameter. Example: shipsFound_number lessthan 2
[edit] foundEquipment_bool
Compares to message from [testForEquipment] method. Example: foundEquipment_bool equal YES
[edit] Random Numbers
[edit] d100_number
Pseudo random number from 0 to 100. Example: d100_number lessthan 50
[edit] pseudoFixedD100_number
...
This has become redundant. A_H
Better look at methods

