Pressing Control+T while in the development tools will load Cash_Out to test the level pack.
There are three major aspects of the level pack testing window...
| Section | Description |
|---|---|
| Framerate | The current (real) framerate that the game is running at. The framerate shown here isn't totally accurate, as the actual ingame framerate is still locked to whatever framerate option you selected. The colour of the bar represents how stable the framerate is, if it drops too low it'll become red. |
| Profile | This section shows how much of a frame is being dedicated to one script. Clicking on the bar will give even more detail by breaking up each script into functions. Due to how this works, it may not be 100% accurate, it can only update when the script is called, so it may appear much larger or smaller than it really is. Along with that, game-engine actions (such as creating explosions using then(createexplosion)) are also accounted for, inflating the count. |
| Console | The console. Errors will appear in this box, along with messages sent with then(debugmessage). You can enter commands (see table below) to interact directly with the debugger and the game. |
Here are some console commands that can be used...
| Command | Description |
|---|---|
| ppause | Pauses the profiler. |
| pstart | Starts the profiler. |
| pclear | Clears the current profiler and framerate data. |
| clear | Clears the console. |
| data | Spits out some minor data about the level pack. |
| restart | Restarts the level pack and mod. |
| object [object] | Creates the object at the player's feet. |
| particle [particle] | Creates the particle at the player's feet. |
| sound [sound] | Plays the sound. |