gameinfo
{
    ...

    scoreboard
    {
        key = value(s)
    }

    ...
}

alignment = left, right, center
customcolumn1..5 = <string>
headercolor = <integer enumeration for color, like CR_RED>
order = POINTS, FRAGS (KILLS), DEATHS, NAME, TIME, PING, MONSTERS_KILLED, CAPTURES, LIVES_LEFT, WINS, CUSTOMCOLUMN1/2/3/4/5
sorting = POINTS, FRAGS (KILLS), DEATHS, NAME, TIME, PING, MONSTERS_KILLED, CAPTURES, LIVES_LEFT, WINS, CUSTOMCOLUMN1/2/3/4/5
truncatenames = <boolean>

1) alignment
Where the board aligns. Left means it aligns on the left hand side (plus some buffer), center means it lines up always from the center, right means it aligns from the right, with preference given to whatever is on the left of the 'order' key (since those are considered important fields)


2) customcolumn1, customcolumn2, customcolumn3, customcolumn4, customcolumn5
The custom columns that users can set with data via ACS. Any changes are sent at the end of the gametic (to save bandwidth/stop spam) to the clients. They will render this data if it is present. The header of the column is the provided name
Ex: customcolumn1 = "mana" would render a column with the header 'mana'


3) headercolor = <integer enumeration for color, like CR_RED>
Sets the header color to be something else, default is Red as per normal.


4) order = [list of items]
Order is how the columns will be rendered from left to right.
Ex: order = kills, name, ping
Would draw kills on the left, then name, and then ping. All possible values are in the above code box.

5) sorting = [list of items]
Like order, left to right determines the priority of sorting.
Ex: sorting = kills, deaths
That means that people will be sorted by kills, in the event of ties... then deaths. If two have the same death, it then sorts by default with the player number. This is the bottom case for every sorted list.
I chose this because its deterministic, right now on the scoreboard people change positions for no reason (thank you Carn).
NOTE: Spectators are always sorted by player index only.

6) truncatenames = <boolean>
Since people use low resolutions, sometimes obnoxious names screw up the table, like a name called asdoijsadid1j289dnmjdo9nas.
This will truncate any names longer than 16 chars with a '...', color codes do not count to name length
Ex: MyNameIsReallyLong -> MyNameIsReall...
Pseudo code: If name > 16 chars and truncatenames = true, write chars 0-12, and append '...'.

typedef enum
{
    SCOREBOARDTYPE_KILLS = 0,
    SCOREBOARDTYPE_DEATHS,
    SCOREBOARDTYPE_DAMAGE,
    SCOREBOARDTYPE_POINTS,
    SCOREBOARDTYPE_LIVESLEFT,
    SCOREBOARDTYPE_FLAGDEFENSE,
    SCOREBOARDTYPE_WINS,
    SCOREBOARDTYPE_PING,
    SCOREBOARDTYPE_TIME,
    SCOREBOARDTYPE_VOTE, // (Yes) or (No) column
    SCOREBOARDTYPE_ISREADY, // If the player is ready to go on
    SCOREBOARDTYPE_NAME,
    SCOREBOARDTYPE_CUSTOM_0, // Custom fields set by ACS
    SCOREBOARDTYPE_CUSTOM_1,
    SCOREBOARDTYPE_CUSTOM_2,
    SCOREBOARDTYPE_CUSTOM_3,
    SCOREBOARDTYPE_CUSTOM_4,
    
    SCOREBOARDTYPE_MAX
} e_ScoreboardScoreType;