Click on "Help/Contents/How To Use FPI EditPad/Add Commands to FPI List" This will give you help on adding commands.
I posted this on the first page: but will post it here once more.
You can manually add any subsequent commands that Lee provides yourself.
There are two files for each of the action and condition commands:
The ".lst" files are divided into categories.
[PLAYER], [ENTITY MOVEMENT], [ENTITYPLAYER INTERACTION], [ENTITY/TARGET INTERACTION], [ENTITY], [SOUND], [VARIABLES], [ANIMATION], [MULTIPLAYER], [HUDS], [LIGHTSAMBIENCE], [GAME], [MISC]
[PLAYER], [ENTITY], [COLLISION], [HUDS], [ANIMATION], [VARIABLES], [MISC]
When adding an action or condition into the list be sure and place it into the correct category. The definition for that command can be in any order. Just place the newest one at the top.
How to place an action or condition command into the list and definition files.
The command that goes into the ".lst" file is lowercase. If there is a required variable assigned to it you should follow the command with an equal sign.
The command that goes into the ".def" file is uppercase. If there is a required variable assigned to it you should follow the command with an equal sign and an X. Also the definition shall also be placed in this file after the X.
PLRDISABLE - Freezes player and disables camera and gun.
INCVAR=X - Increases the value of the current variable by X
Us the tilde (~) for a new line within the definition.
ACTIVATED=X - This is true when the activation value of the entity equals X.~The action "Activate" will set the activation value for the entity within the same script.~However, the "Activateifused" action will reset the activation value from another entity's script.~Whatever the current acivation value is it will be used to check the "X" value of the condition.~
Notice the use of the tildes. The tilde on the end will cause a blank line.
The past has a lot of memories to hold onto; but, today is chock full of new adventures, and, the future shouts out, "The best is yet to come!" -- TerryC