In your mission folder, create a text file called ScenarioScript.lua

It has to be complied before the mission will recognise it, you can do that from the timetable editor's script section.

Everytime you call for an event through your scenario it will execute this function and return the event name in "event".
This is your main way of getting your script called.

SysCall is your main way of affecting your mission, but it's syntax is fairly difficult to figure out without documentations, the basic structure is the following:

ScenarioManager allow you to control many aspects if the scenario itself:

Allow you to call an event at a later time

Lock the player's controls.

Unlock the player's controls.

Cause the scenario to end as a failure, showing a popup window with the reason.

Cause the scenario to end as a success, showing a popup window with the reason.

Allow you to show a simple message window.

Allow you to show message windows formatted in HTML, the html files must be placed in a language coded folder subfolder, ex: "En" for english.

Play a video.

Check if the specified video is still playing.

Check if a service is at a specific destination.

Starts a repeating event usually to detect a specific change.

Stop repeating event usually to detect a specific change.

Play a sound file.

Retrieve the season the scenario is currently on.

Get the number of seconds since midnight.

This reference the train driven by the player

Allow you to lock a specific control on the player engine.

Set a control to a specific value. (index is usually zero)

Get the value of a control. (index is usually zero)

Get the player engine speed.

Get tje player's currently effective speed limit.

Used to manipulate the camera.
Turn on one of the stock camera.

Move the camera to a specific coordinate.

Look at an object.