All events are iterated through  &  their respective script parsers execute one more step.
When an event is first encountered, its script parser fills its internal script list.
The parser script list is built before any event commands are executed.

Basically, each event has 2 script lists.
- The one made by the level editor.  (cannot change during run-time)
- The one that's built during run-time.  (CAN change during run-time)
	(this is done to allow "Condition" statements to insert code when they're evaluated)



Scripts are stored in objects & can also be stored within other objects
(condition statements)

When a condition statement is reached, the script parser inserts the statement's selected commands list into the parser's script list.
In other words, upon execution, a condition statement is replaced by its chosen code.
- Code added, then Condition removed.

Given this behavior, each time an event script repeats, it is cleared and reloaded from the LevelData.
