http://sauerbraten.org/README.html = overview
-http://sauerbraten.org/docs/config.html = basic config (cube script)
-http://sauerbraten.org/docs/editref.html = basic map configs (textures, texture blending etc)
-http://sauerbraten.org/docs/models.html = basic model configs (model configs that control how the models operate)

or just look in the docs folder of the current build

there are a few that are not mentioned in there but that about 80% of them. Most of the ones not listed are shader commands, or newer options that have not made it into the read me

chasester

This is one big document. Rather messy, and some of the fonts are unusual.

I think there have been a couple of times when a list of all the commands/variables in Cube 2 were listed. Don't know where or when anymore, but they were a simple list with no explanations.

I CAN though point you to a fairly recent cubescript guide that explains the basics and several commands, but that's about all i can offer.

Thanks for the posts. Will try them both, RaZgRiZ & Skiingpenguins.

Reformatted the doc & reposted it... Doesn't make it any smaller. But, does make it easier to read.

Did a quick scan of your link, RaZgRiZ. Saw some commands, not in my list... Big Thanks.

I don't know if you managed to get there through RaZgRiZ' link, but:
A pretty good list of available commands

Is this actually a node for literally commands used in cubescript or rather a list off all commands? As it seems the second one (change the name of the node if it actually is).

Another reason to redo the wiki sauer already has :)
You can also always cycle through the commands ingame with tabcomplete /a [tab]
not sure if that would help :)
I once saw a complete list of variables and commands by quinn on some pastebin,. Can't find it right now :<

you could get a list of all the commands by doing something like the following to the source code:

in command.cpp at the very top is a vector that holds all the command aliases, etc

hashset idents; // contains ALL vars/commands/aliases
vector identmap;
ident *dummyident = NULL;

so simply writing a COMMAND that exports the names of them would give you a list of all commands in sauer (including ones used in cfg files (so you may have to weed through these, then you could grab the possible variable by:

struct ident
{
    int type;           // one of ID_* above
    const char *name;
    union
    {
        int minval;    // ID_VAR
        float minvalf; // ID_FVAR
        int valtype;   // ID_ALIAS
    };
    union
    {
        int maxval;    // ID_VAR
        float maxvalf; // ID_FVAR
        uint *code;    // ID_ALIAS
    };
    union
    {
        const char *args;    // ID_COMMAND
        identval val;        // ID_ALIAS
        identvalptr storage; // ID_VAR, ID_FVAR, ID_SVAR
    };
    union
    {
        identval overrideval; // ID_VAR, ID_FVAR, ID_SVAR
        identstack *stack;    // ID_ALIAS
        uint argmask;         // ID_COMMAND
    };
    identfun fun; // ID_VAR, ID_FVAR, ID_SVAR, ID_COMMAND 

you could figure out the type then get the mins and maxes, and cur. Then just output this info into a txt file, and add the decriptions.

chasester