Introduction

Your local documentation (README.html ff.) holds all the commands you can use,
use it as reference for your current release.

With scripting you can achieve a lot more personalized Sauerbraten experience;
in most cases some simple copy-and-paste will do the trick.
But this guide aims at showing some easy techniques to empower gamers and mappers alike.

Any files you find in your game directory (and subdirs) ending in ".cfg" should contain CubeScript.
Check them out to see what the engine already does via scripting ... and how!

To automatically run scripting on engine start you need only place them in a file called *autoexec.cfg* in your base game directory.
If anything /funny/ happens - like key bindings not working anymore - you should be prepared to move (or even delete) your *config.cfg* (also in the base game directory). This file is also executed upon engine start and is useful to keep values from one run to the next, but this may result in bogus data being saved and so can require the mentioned removal to return to a clean setup.
It will be written at every clean exit and if it doesn't exist will contain whatever is in *./data/defaults.cfg* - so never modify _that_ file!

Without being a programmer you might find a lot of this stuff too complicated for your taste,
but do not despair! There are some examples on these pages to help you achieve a lot of goals and there are also quite a few scripts ready for download on quadropolis.

But if you really want to get the most out of the engine it is suggested that you at least getting familiar with some basics of the scripting capabilities!
Try reading this scripting primer to see what fundamental know-how this is and how easy it is.

Syntax

The basic command structures of CubeScript are explained on the syntax page

Map Configuration

Scripting for maps is explained on the Map Configuration page.

Menu Personalization

Scripting for menus is explained on the menu personalization page.