Supervisor Based Programming

For new developers to Synapse X, most will be confused on how to fully utilize the power of the Synapse X environment. For you to understand where Synapse X scripts extracts its abilities from, we must first show where most Synapse X scripts insert themselves.

Shown below is a diagram of a normal game instance:

Now, we will show a diagram after a Synapse X script fully utilizing Synapse X's supervisor programming model:

As you can see, Synapse X extracts its abilities from being able to intercept API calls and event invocations from both the native game engine, and game scripts. Once an interception function is called, Synapse X scripts have full control over arguments, return values, and can modify calls as needed by that script. This allows Synapse X scripts to act as supervisors of game logic, alas the term 'supervisor-based programming'.

Supervisor based programming allows a powerful programming model much unlike most other forms of systems programming. If the native game engine were the OS kernel and game scripts were user mode programs, Synapse X scripts would act as the 'drivers' for such a system under this analogy.