View source for Styctap/Console Commands

<b>[[styctap|<- Back]]</b>

The commands listed below are some of the active and working commands, mostly ones that can only be found in sty+ct+ap.<br />
To view the full list of available commands, see [http://durf.cf/tools/ConsoleSearch+ap/0.1/ list of commands]

= ADMIN_LOG =

Enabling this will ensure that all admin commands will be written to ./var/adminlog.txt file.

= ARENA_BOUNDARY Commands =

== ARENA_BOUNDARY ==

This is the distance players can travel outside the arena boundary.

== ARENA_BOUNDARY_KILL ==

If set to 1, Players beyond the ARENA_BOUNDARY will be killed.

= BANNED_WORDS_* Commands =

== BANNED_WORDS ==

This command stores all the bad words you want filtered out or censored in your server/client depending on <code>BANNED_WORDS_OPTIONS</code> setting you chose.

clean example: <code>BANNED_WORDS stupid;idiot;dumb;</code>

LOVER$BOY included an array of bad words by default. You may wish to use BANNED_WORDS_ADD and BANNED_WORDS_REMOVE

== BANNED_WORDS_OPTIONS [0|1|2] ==

<code>BANNED_WORDS_OPTIONS 0</code>

The available options. are 0, 1 and 2. Default value is set to 0 which disables the activation of checking bad words in message.

Normally this allows users to easily send messages to each other. If this setting is set to 1 or 2, different actions will be triggered.

If setting is set to 1, the message will get blocked. Along with that, a message of warning will be sent to the user, their message contained one or many bad words. Due to that their message is blocked. This message will be different if each server owner decides to write something different.

If setting is set to 2, the message will get parsed. While parsing, the found bad words will get replaced by the selected characters placed in english_base.txt

== BANNED_WORDS_ADD [word] ==

<code>BANNED_WORDS_ADD [word]</code>

This command allows users to add a new word. If the word already exists in the container, then the word to add will be ignored.

== BANNED_WORDS_REMOVE [word] ==

<code>BANNED_WORDS_REMOVE [word]</code>

This command allows users to remove the entered word. If the word exists in the container, then the word will be removed. If it doesn’t, then it will get ignored.

== BANNED_WORDS_LIST ==

This command allows users to list the words that exist in the banned words container. The <id>is a number area which only accepts number values from 0 to 9.

If the <id>area is given blank, then it will display words from 0 to 9 ids. Otherwise you can give the number of id to view the word and the ten from that <id>will appear on your chat display.

= CHATTERS_ Commands =

=== CHATTERS_KILL ===

If this command has been executed, all players in chat mode and are playing on the grid, are killed!

=== CHATTERS_SUSPEND [rounds] ===

Suspends all players that were in chat mode for the following rounds.

=== CHATTERS_SILENCE ===

Silences all chatters during play. This command is closely linked with

<code>SILENCE_ALL</code>

To give their voices back, simply do

<code>VOICE_ALL</code>

=== CHATTERS_LIST ===

Displays the list of currently chatting or players who have entered idle mode up on your screen.

= CLEAR_ Commands =

<code>CLEAR_LADDERLOG Clear all data from ladderlog.txt located in ./var folder.</code><br />
<code>CLEAR_SCORELOG Clear all data from scorelog.txt located in ./var folder.</code><br />
<code>CLEAR_CHATLOG Clear all data from chatlog.txt located in ./var folder.</code>

= COLLAPSE | DESTROY Commands =

<code>COLLAPSE_ZONE [zone_name]</code>

This command causes the selected zone(s) to shrink in size and disappear smoothly.

<code>DESTROY_ZONE [zone_name]</code>

This command causes the selected zone(s) to vanish instantly.

<code>COLLAPSE_ZONE_ID [zone_id]</code>

This command is similar to <code>COLLAPSE_ZONE</code> but uses the zone’s ID instead to locate and make that zone disappear smoothly.

<code>DESTROY_ZONE_ID [zone_id]</code>

This command is similar to <code>DESTROY_ZONE</code> but uses the zone’s ID instead to locate zone and make it disappear instantly.

= CUSTOM_ Commands =

== CUSTOM_MESSAGE ==

Calls upon the string located within your language file

<code>CUSTOM_MESSAGE hello_world</code>

If “hello_world” exists within the language file, it loads the string.<br />
Inside Language File: hello_world Hello World!The output will be displayed on the client’s screen as:<br />
Hello World!

Example 1:

<code>CUSTOM_MESSAGE player_reach_race</code>

Output Similar to: 1 finished with 10 points in seconds

Example 2:

<code>CUSTOM_MESSAGE player_reach_race lover$boy 5 15.5432</code>

Output : lover<math display="inline">boy finished with 5 points in 15.5432 seconds This command not only loads in the language string command, it also replaces those \1, \2, \3 indicators. In example 2 you see those indicators as: Language String Command: player_reach_race \1 0xfffffffinished with \2 points in \3 seconds.\n **\1 = lover</math>boy**<br />
'''\2 = 5'''<br />
'''\3 = 15.5432'''

So to speak, it looks like this: CUSTOM_MESSAGE player_reach_race '''\1''' '''\2''' '''\3''' …

They can go on depending on your choosing of calling this command.

== CUSTOM_PLAYER_MESSAGE ==

<code>CUSTOM_PLAYER_MESSAGE player_name language_command parameters...</code>

This command works similarly to the <code>CUSTOM_MESSAGE</code> but the message will be sent to the given player and the sender only. Similar to how <code>PLAYER_MESSAGE</code> and <code>/msg</code> work.

= CUSTOM_SHORTHAND commands =

=== CUSTOM_SHORTHAND_ENABLED [0|1] ===

If set to 1 and CUSTOM_SHORTHAND is found, then CUSTOM_SHORTHAND_CONNECTION will be used to connect.

=== CUSTOM_SHORTHAND<authority> ===

The custom authority to trigger when a player tries to login.

=== CUSTOM_SHORTHAND_CONNECTION ===

The link to connect to when using custom shorthand. Do not include [http:// <code>http://</code>].

= CYCLE_RUBBER_DEPLETE_ Commands =

The following commands are the very core of rubber reduction behavior in client and server alike.

<code>CYCLE_RUBBER_DEPLETE_SELF # if set to 0, it will not reduce rubber like normal when you hit your own tail; Default 1.</code><br />
<code>CYCLE_RUBBER_DEPLETE_ENEMY # if set to 0, it will not reduce rubber like normal when you hit enemy's tail; Default 1.</code><br />
<code>CYCLE_RUBBER_DEPLETE_TEAM # if set to 0, it will not reduce rubber like normal when you hit team's tail; Default 1.</code><br />
<code>CYCLE_RUBBER_DEPLETE_RIM # if set to 0, it will not reduce rubber like normal when you hit the rim wall; Default 1.</code>

While it these will indeed work on any game client, this is only implemented in sty+ct+ap currently. This essentially just means that on most clients the rubber meter will appear to be using rubber, but jump back down to the correct rubber every sync.

= DEADLY_ Commands =

=== DEADLY_EXPLOSIONS [0|1] ===

If set to 1, cycles in the blast radius of an explosion will be destroyed.

=== SCORE_EXPLOSION_OWNER [points] ===

Points the owner of an explosion gains for destroying another enemy cycle.

=== SCORE_EXPLOSION [points] ===

Points the enemy cycle destroyed in an explosion gains.

= DEATHZONE_RANDOM_COLORS [0|1] =

Default: 0; If set to 1, deathzones will have their colors by randomness for each round.

Don’t let your eyes bleed too much :P

= DECLARE_ROUND_WINNER =

<code>DECLARE_ROUND_WINNER [player_name | team_name]</code>

This command declares a winner of the round depending on the player name given or the team they belonged to at the time.<br />
Command can only be used once per round and there’s no taking back after declaring someone a winner. So, choose wisely.

= DELAY_COMMAND =

<code>DELAY_COMMAND [r&lt;delay&gt;] [+]&lt;time&gt; &lt;string&gt;</code>

The intent was to allow use of timing things asynchronously without having to script it. As all delay commands will be cleared between rounds, it may be most effective used in the map settings or used within everytime.cfg, to sort of “script” things happening.

The optional r<delay> allows repetitive commands executed in an interval. The optional + before time indicates to the server that you want it to happen that amount of seconds from now.

For example:

<code>DELAY_COMMAND +3 SAY hello!</code> Executes <code>say hello!</code> (Admin: hello!) 3 seconds later.

<code>DELAY_COMMAND 30 center_message Stage 2</code> will show a center message “Stage 2” when the round’s timer reaches 30 seconds.

<code>DELAY_COMMAND r10 +3 Say hello</code> will result in “Admin: Hello” every ten seconds starting in 3 seconds from now

<code>DELAY_COMMAND r10 30 Say hello</code> starting at 30 seconds and every 10 seconds after it says “Admin: Hello”

== DELAY_COMMAND_CLEAR ==

Clears all stored commands in DELAY_COMMAND

= DISPLAY_MAP_ Commands =

== DISPLAY_MAP_DETAILS ==

<code>DISPLAY_MAP_DETAILS [0|1]</code>

If set to 1, then map details will appear in everyone’s clients and it will show the name, author, version and axes for it. This however is dependent on the following commands

== DISPLAY_MAP_NAME ==

<code>DISPLAY_MAP_NAME [0|1]</code>

If set to 1, map’s name will be displayed at the beginning of each round.

== DISPLAY_MAP_AUTHOR ==

<code>DISPLAY_MAP_AUTHOR[0|1]</code>

If set to 1, map’s author will be displayed at the beginning of each round.

== DISPLAY_MAP_VERSION ==

<code>DISPLAY_MAP_VERSION [0|1]</code>

If set to 1, map’s version will be displayed at the beginning of each round.

== DISPLAY_MAP_AXES ==

<code>DISPLAY_MAP_AXES[0|1]</code>

If set to 1, map’s axes will be displayed at the beginning of each round.

= ENABLE_MATES_CASING =

<code>ENABLE_MATES_CASING [0|1]</code>

Enabling this is a personal choice.

It is clear of irregular letters in name causes some hassle for server but this choice setting will be good for those preferred to search for mates use that kind of name.

= DISPLAY_SCORES_DURING_CHAT [0|1] =

Tabbing during chat gets annoying when the scores keep appearing and disappearing. This command works individually and is enabled right now but you can choose to disable it and have a good time tabbing names without having to worry about appearing score board.

= _GRIDPOS Commands =

== PLAYER_GRIDPOS_INTERVAL ==

<code>PLAYER_GRIDPOS_INTERVAL</code>

Set the number of seconds of interval between each ladderlog output of <code>PLAYER_GRTIDPOS</code>

== ZONE_GRIDPOS_INTERVAL ==

<code>ZONE_GRIDPOS_INTERVAL</code>

Set the number of seconds of interval between each ladderlog output of <code>ZONE_GRTIDPOS</code>.

= HIDE_CYCLES =

The following commands can only be executed from within a client.

== HIDE_CYCLES 0|1 ==

<code>HIDE_CYCLES 0|1</code>

If set to 1, all cycles on the grid will vanish from view. This will only work while you are alive.

== HIDE_CYCLE_WALLS 0|1 ==

<code>HIDE_CYCLE_WALLS 0|1</code>

If set to 1, the tails of all cycles will vanish from view. This will only work while you are alive.

= HIGHLIGHT_NAME =

If set to 1, your name will get highlited in string.

= QUEUE Commands =

=== QUEUE_MAP <name> ===

<code>QUEUE_MAP MAP_FILE.xml</code>

Stores map that exist in MAP_ROTATION. Stops rotation temporarily to complete the listed maps.

=== QUEUE_CONFIG <name> ===

<code>QUEUE_CONFIG config.cfg</code>

Stores config that exists in CONFIG_ROTATION. Stops rotation temporarly to complete the listed maps.

=== RESET_MAP_QUEUEING ===

Resets all the maps in the queue.

=== RESET_CONFIG_QUEUEING ===

Resets all the configs in the queue.

=== QUEUE_LIMIT_ENABLED [0|1] ===

<code>QUEUE_LIMIT_ENABLED 0</code>

Should the people have limits when queueing?

=== QUEUE_LIMIT [number] ===

<code>QUEUE_LIMIT 20</code>

This is the amount that players can use up for queueing maps or configs.

=== QUEUE_LIMIT_EXCEMPT [access level] ===

<code>QUEUE_LIMIT_EXCEMPT 2</code>

Access level equal to or below this do not have queue limit.

=== QUEUE_INCREMENT [number] ===

<code>QUEUE_INCREMENT 0</code>

If set to &gt;0, players will get their queues increased during refill by this amount.

=== QUEUE_REFILL_TIME [time in seconds] ===

<code>QUEUE_REFILL_TIME 2400</code>

How long each time should players refill take? This is measured in hours.

=== QUEUE_REFILL_ACTIVE [0|1] ===

<code>QUEUE_REFILL_ACTIVE 0</code>

Should players be in server to have their queue refill active?

=== QUEUE_MAX [number] ===

<code>QUEUE_MAX 30</code>

The maximum queues allowed due to the increase in their slots.

=== QUEUE_LOG [0|1] ===

<code>QUEUE_LOG 0</code>

If set to 1, players queueing maps/configs will get written to queuelog.txt

=== QUEUE_REFILL <name> ===

<code>QUEUE_REFILL &lt;player name=&quot;&quot;&gt;</code>

Refill the queue fuel of the given player’s name. Usage: <code>QUEUE_REFILL &lt;name&gt;</code>

=== QUEUE_GIVE <player> ===

<code>QUEUE_GIVE &lt;player&gt;</code>

Give a set of queues to the given player’s name. Usage: <code>QUEUE_GIVE &lt;name&gt; &lt;amount&gt;</code>

=== QUEUERS_LIST ===

Displays the list of queuers and their queues.

= Racing Commands =

=== RACE_CHANCES [no_of_times] ===

This command is pretty simple. This gives each and every player on grid to continue to race, from the start, each time they die. Of-course, their chances deplete but this gives them extra chances to race and try to complete the course.

=== RACE_END_DELAY [seconds] ===

If there was only one play still alive on the grid, this timer activates. Depending on this set, they get that many amount of seconds to try and cross the finish line.

=== RACE_CHECKPOINT_COUNTDOWN [seconds] ===

Number of seconds to give individual racers to complete the race.

=== RACE_CHECKPOINT_REQUIRE_HIT [0|1|2] ===

<code>RACE_CHECKPOINT_REQUIRE_HIT 1</code>

Explanation:

<code>0 : Will let you finish regarless of doing the checkpoints</code><br />
<code>1 : MUST complete all checkpoints but not in order</code><br />
<code>2 : MUST complete all checkpoints in order;</code>

=== RACE_CHECKPOINT_LAPS [0|1] ===

<code>RACE_CHECKPOINT_LAPS 1</code>

Explanation:

<code>0 : Won't do anything</code><br />
<code>1 : After each completed lap, your completed checkpoints data is cleared to do again.</code>

=== RACE_LAPS [number] ===

<code>RACE_LAPS 1</code>

If set to &gt;1, these are the number of laps to complete to finish the race.

=== RACE_SAFE_ANGLES [angle,angle,…] ===

<code>RACE_SAFE_ANGLES 0,45,90,135,180,225,270,315</code>

These are the angles that are safe to travel in. Anything else and your dead. Usage: degrees1,degrees2,degrees3,…

=== RACE_UNSAFE_ANGLES_KILL [0|1] ===

<code>RACE_UNSAFE_ANGLES_KILL 0</code>

If set to 1, kills all players that are in the unsafe angles as they finish the race.

=== RACE_FINISH_KILL [0|1] ===

If set to 1, players crossing the finish lines will get killed!

=== RACE_FINISH_COLLAPSE [0|1] ===

If set to 1, all zones will collapse/disappear at the end of round.

=== RACE_IDLE_KILL [0|1] ===

If set to 1, kills players that are idle for RACE_IDLE_TIME seconds.

=== RACE_IDLE_TIME [seconds] ===

Number of seconds a player is idle on grid before being warned and then killed.<br />


=== RACE_IDLE_SPEED [speed] ===

Set to &gt;= 0, idle activates if players stay for RACE_IDLE_TIME under the set idle speed.

=== RACE_LOG_LOGIN [0|1] ===

If enabled, it will only log the time records of players that have logged in.

=== RACE_LOG_TIME [0|1] ===

If enabled, it displays the reached time and the position of arrival.

=== RACE_LOG_UNFINISHED [0|1] ===

It set to 1, logs in the players that have not yet finished that racing course. Time values will be set to -1.

=== RACE_POINTS_TYPE [0|1] ===

If set to 0, players receive points depending on SCORE_RACE_FINISH<br />
If set to 1, players receive points depending on RACE_SCORE_DEPLETE

=== RACE_SCORE_DEPLETE [points] ===

<code>RACE_SCORE_DEPLETE 1</code>

The number of points the race score deplete every time someone crosses the finish line. The points giver will remain at 1 if it were to reach 1.

=== RACE_SMART_TIMER [0|1] ===

The smart timer is set to 0 by default. If it were to be enabled, smart timer loads the first 1/2/3 player’s time ranks and then make a timer from that! If there are not ranks yet, it resorts to using RACE_END_DELAY timer instead.

=== RACE_SMART_TIMER_FACTOR [number] ===

<code>RACE_SMART_TIMER_FACTOR 0.15</code>

The factor by which countdown is multiplied when smart timer is enabled.

=== RACE_SMART_TIMER_NUM [number] ===

<code>RACE_SMART_TIMER_FACTOR 3</code>

The number of records to look to obtain the average time for the countdown.

=== RACE_TIMER_ENABLED [0|1] ===

<code>RACE_TIMER_ENABLED 0</code>

By default, this is disabled. The only way to enable this is for everyone to spectate or enable it in your config files.

=== SCORE_RACE [points] ===

<code>SCORE_RACE 10</code>

The points you receive for being the first to cross the finish line. Default is set to 10.

=== SCORE_RACE_FINISH [points] ===

<code>SCORE_RACE_FINISH 1</code>

The points players receive for crossing the finish line.

=== RACE_RANKS_SHOW_START [0|1|2] ===

This command is for ranks to be shown at the beginning of the round.

Default: 1. Set to 0 to disable records shown at the beginning of the round.

If set to 1, ranks from top RACE_NUM_RANKS_SHOW_START will appear to all players.

If set to 2, shows the relative position of the player above and below them and their current rank with respect to their position.

=== RACE_RANKS_SHOW_END [0|1|2] ===

This command is for ranks to be shown at the end of the round.

Default: 2. Set to 0 to disable records shown at the end of the round.

If set to 1, ranks from top RACE_NUM_RANKS_SHOW_END will appear to all players.

If set to 2, shows the relative position of the player above and below them and their current rank with respect to their position.

=== RACE_NUM_RANKS_SHOW_START [number] ===

<code>RACE_NUM_RANKS_SHOW_START 3</code>

The number of ranks to display at the start of round.

=== RACE_NUM_RANKS_SHOW_END [number] ===

<code>RACE_NUM_RANKS_SHOW_END 3</code>

The number of ranks to display at the end of round.

=== RACE_RANK_SHOW_PLAYER_LENGTH [number] ===

<code>RACE_RANK_SHOW_PLAYER_LENGTH 15</code>

The limit length of players to display in the display of ranks.

=== RACE_RANK_SHOW_LENGTH [number] ===

<code>RACE_RANK_SHOW_LENGTH 7</code>

The length of the name of the rank should the rank be aligned by.

=== RACE_RANK_HEADER_ORDER [number] ===

<code>RACE_RANK_HEADER_ORDER 1</code>

The order in which the “rank” header will appear. Default: 1.

=== RACE_RANK_HEADER_PLAYER_ORDER [number] ===

<code>RACE_RANK_HEADER_PLAYER_ORDER 2</code>

The order in which the “player” header will appear. Default: 2.

=== RACE_RANK_HEADER_TIME_ORDER [number] ===

<code>RACE_RANK_HEADER_TIME_ORDER 3</code>

The order in which the “time” header will appear. Default: 3.

=== RACE_RANK_HEADER_LENGTH [number] ===

<code>RACE_RANK_HEADER_LENGTH 8</code>

The length of the header “rank” should be.

=== RACE_RANK_HEADER_PLAYER_LENGTH [number] ===

<code>RACE_RANK_HEADER_PLAYER_LENGTH 16</code>

The length of the header “player” should be.

=== RACE_RANK_HEADER_TIME_LENGTH [number] ===

<code>RACE_RANK_HEADER_TIME_LENGTH 0</code>

The length of the header “time” should be.

= ROTATION Settings =

== MAP_ROTATION ==

<code>MAP_ROTATION map1.aamap.xml|&lt;round&gt;;map2.aamap.xml|&lt;round&gt;;</code>

As you have seen above, this command works like a rotation script that causes the stored maps to change every round or match, depending on how you set ROTATION_TYPE to.<br />
Also, as you can see from

<code>map1.aamap.xml|&lt;round&gt;;</code>

You can also set which <round>you want that map to load in. However, this can only be activated if '''ROTATION_TYPE 6''' is set.

'''Setting the <round> is optional!'''

== CONFIG_ROTATION ==

<code>CONFIG_ROTATION config.cfg1|&lt;round&gt;;config2.cfg|&lt;round&gt;;</code>

As you have seen above, this command works like a rotation script that causes the stored config files to change every round or match, depending on how you set ROTATION_TYPE to.<br />
Also, as you can see from

<code>config.cfg1|&gt;&lt;round&gt;;</code>

You can also set which <round>you want that map to load in. However, this can only be activated if '''ROTATION_TYPE 6''' is set.

'''Setting the <round> is optional!'''

== CONFIG_ROTATION_TYPE ==

<code>CONFIG_ROTATION_TYPE [0|1]</code>

How should the configs from the config_rotation be loaded?

<code>0 # INCLUDE</code><br />
<code>1 # RINCLUDE</code>

== ROTATION_TYPE ==

<code>ROTATION_TYPE [0|1|2|3|4|5|6]</code>

This command is quite nice. It controls how to <code>MAP/CONFIG_ROTATION</code> setting works.<br />
Bellow are the list of each of it’s values. Th values are restricted, so don’t bother trying to go higher than 4 or below then 0.<br />
* 0 = This value ensures no rotation will take place.

* 1 = This value ensures maps are rotated in their respective order every round
* 2 = This value ensures maps are rotated in their respective order every match
* 3 = This value ensures maps are rotated randomly every round
* 4 = This value ensures maps are rotated randomly every match
* 5 = Activates ROTATION_MAX.
* 6 = Activates for rotation where maps and configs load depending on the round they are set for.

== ROTATION_MAX ==

<code>ROTATION_MAX 3</code>

If set to &gt;0 and rotation is enabled, current rotation item will remain the same until till ROTATION_MAX. After which, the rotation will activate ORDERLY type and change map/config.

== MAP_STORAGE ==

<code>MAP_STORAGE map1;map2;map3; ...</code>

=== Similarities ===

* <code>MAP_ROTATION</code>
* Each map separated by the <code>;</code>

=== Differences ===

* Cannot specify a round
* Is to be used for non-rotation. Only for queueing.

== CONFIG_STORAGE ==

<code>CONFIG_STORAGE config1;config2;config3; ...</code>

=== Similarities ===

* <code>CONFIG_ROTATION</code>
* Each config separated by the <code>;</code>

=== Differences ===

* Cannot specify a round
* Is to be used for non-rotation. Only for queueing.

== COMMANDS ==

<code>/mr &lt;id&gt; # Shows list of maps by either leaving &lt;id&gt; blank or &lt;id_number&gt; from the mao_rotation. Shows only ten maps per call.</code><br />
<code>/cr &lt;id&gt; # Shows list of configs by either leaving &lt;id&gt; blank or &lt;id_number&gt; from the config_rotation. Shows only ten configs per call.</code>

<code>/mq &lt;add|remove|list&gt; # add &lt;map_file&gt;| adds the corresponding map to the map queue if that map exists within MAP_ROTATION</code><br />
<code># remove &lt;map_file&gt;| if map exists in the queue, it will be removed</code><br />
<code># list | shows the list of all maps in queue</code>

<code>/cq &lt;add|remove|list&gt; # add &lt;config_file&gt;| adds the corresponding config to the queue if that config exists within CONFIG_ROTATION</code><br />
<code># remove &lt;config_file&gt;| if config exists in the queue, it will be removed</code><br />
<code># list | shows the list of all configs in queue</code>

<code>/ms &lt;add|remove|list&gt; # add &lt;map_file&gt;| adds the corresponding map to the map queue if that map exists within MAP_STORAGE</code><br />
<code># remove &lt;map_file&gt;| if map exists in the queue, it will be removed</code><br />
<code># list | shows the list of all maps in queue</code>

<code>/cs &lt;add|remove|list&gt; # add &lt;config_file&gt;| adds the corresponding config to the queue if that config exists within CONFIG_STORAGE</code><br />
<code># remove &lt;config_file&gt;| if config exists in the queue, it will be removed</code><br />
<code># list | shows the list of all configs in queue</code>

= Custom TEAMNAME Commands =

** Not to be confused with TEAM_NAME_* commands !!! **

These are the custom team name commands that have been recently added as a new feature. This has been taken directly from 0.4 Trunk version of Armagetron Advanced.

<code>TEAMNAME_1 Team 1</code><br />
<code>TEAMNAME_2 Team 2</code><br />
<code>TEAMNAME_3 Team 3</code><br />
<code>TEAMNAME_4 Team 4</code>

This feature will only work on servers that support it and are not using a team configuration that blocks the use of it. Clients that do not support it may also use the chat command /teamname to accomplish the same thing.

= SET_ZONE Commands =

SET_ZONE_* and SET_ZONE_ID_* commands are identical, except SET_ZONE_* commands accept a name which can be defined when you spawn a zone, and SET_ZONE_ID_* only accepts zone IDs.

<code>SET_ZONE_ID_COLOR &lt;id&gt; {r} {g} {b} # Change the color of a zone</code><br />
<code>SET_ZONE_ID_EXPANSION &lt;id&gt; &lt;expansion&gt; # Change the Expansion rate of a zone</code><br />
<code>SET_ZONE_ID_POSITION &lt;id&gt; &lt;x&gt; &lt;y&gt; # Look at COORD and ROUTE instead.</code><br />
<code>SET_ZONE_ID_COORD &lt;id&gt; &lt;x&gt; &lt;y&gt; # Hard-set the position of a zone.</code><br />
<code>SET_ZONE_ID_ROUTE &lt;id&gt; &lt;x1&gt; &lt;y1&gt; &lt;x2&gt; &lt;y2&gt; &lt;x3&gt; &lt;y3&gt; ... # Makes a new route the zone will follow. The zone will stop moving if two coordinates in a row are the same or the last coordinate is the same as the first.</code><br />
<code>SET_ZONE_ID_RADIUS &lt;id&gt; &lt;radius&gt; # Change zones radius</code><br />
<code>SET_ZONE_ID_ROTATION &lt;id&gt; &lt;rotation&gt; # Change the rotation speed of a zone</code><br />
<code>SET_ZONE_ID_SPEED &lt;id&gt; &lt;speed&gt; # Change a zones speed</code>

= SHOT_ Commands =

== SHOT_BASE_RESPAWN ==

<code>SHOT_BASE_RESPAWN 1</code>

If set to 1, when you shoot at your team base, your teammates will be revived.

== SHOT_BASE_ENEMY_RESPAWN ==

<code>SHOT_BASE_ENEMY_RESPAWN 1</code>

If set to 1, when you shoot at your enemy team’s base, your enemies will be revived.

== SHOT_PENETRATE_WALLS ==

<code>SHOT_PENETRATE_WALLS 0</code>

If set to 1, when you shoot, your zone will go through the walls. Once it reaches the boundary of the arena, it will disappear if bouncing is either not enabled or finished.

= SPAWN_* Commands =

== SPAWN_ZONE ==

The ability to spawn all different types of zones via the command line or a script.<br />
These zones no longer are required to be specified in the map and can be spawned either via the console using /admin SPAWN_ZONE, <setting> … elements in the map or by using a script.

=== Types of zones ===

=== Command Usage ===

<code>SPAWN_ZONE &lt;win|death|ball|target|blast|object|koh&gt; &lt;x&gt; &lt;y&gt; &lt;size&gt; &lt;growth&gt; &lt;xdir&gt; &lt;ydir&gt; &lt;interactive&gt; &lt;r&gt; &lt;g&gt; &lt;b&gt; &lt;target_size&gt; &lt;penetrate&gt;</code><br />
<code>SPAWN_ZONE &lt;acceleration|speed&gt; &lt;speed&gt; &lt;x&gt; &lt;y&gt; &lt;size&gt; &lt;growth&gt; &lt;xdir&gt; &lt;ydir&gt; &lt;interactive&gt; &lt;r&gt; &lt;g&gt; &lt;b&gt; &lt;target_size&gt; &lt;penetrate&gt;</code><br />
<code>SPAWN_ZONE &lt;rubber|rubberadjust&gt; &lt;x&gt; &lt;y&gt; &lt;size&gt; &lt;growth&gt; &lt;xdir&gt; &lt;ydir&gt; &lt;rubber&gt; &lt;interactive&gt; &lt;r&gt; &lt;g&gt; &lt;b&gt; &lt;target_size&gt; &lt;penetrate&gt;</code><br />
<code>SPAWN_ZONE teleport &lt;x&gt; &lt;y&gt; &lt;size&gt; &lt;growth&gt; &lt;xdir&gt; &lt;ydir&gt; [&lt;xjump&gt; &lt;yjump&gt; &lt;rel|abs&gt; [&lt;xdir&gt; &lt;ydir&gt; &lt;reloc&gt;]] &lt;interactive=true|false&gt; &lt;r&gt; &lt;g&gt; &lt;b&gt; &lt;target_size&gt; &lt;penetrate&gt;</code><br />
<code>SPAWN_ZONE &lt;fortress|flag|deathTeam|ballTeam&gt; &lt;team&gt; &lt;x&gt; &lt;y&gt; &lt;size&gt; &lt;growth&gt; &lt;xdir&gt; &lt;ydir&gt; &lt;interactive&gt; &lt;r&gt; &lt;g&gt; &lt;b&gt; &lt;target_size&gt; &lt;penetrate&gt;</code><br />
<code>SPAWN_ZONE sumo &lt;x&gt; &lt;y&gt; &lt;size&gt; &lt;growth&gt; &lt;xdir&gt; &lt;ydir&gt; &lt;interactive&gt; &lt;r&gt; &lt;g&gt; &lt;b&gt; &lt;target_size&gt; &lt;penetrate&gt;</code><br />
<code>SPAWN_ZONE zombie &lt;player&gt; &lt;x&gt; &lt;y&gt; &lt;size&gt; &lt;growth&gt; &lt;xdir&gt; &lt;ydir&gt; &lt;interactive&gt; &lt;r&gt; &lt;g&gt; &lt;b&gt; &lt;target_size&gt; &lt;penetrate&gt;</code><br />
<code>SPAWN_ZONE zombieOwner &lt;player&gt; &lt;owner&gt; &lt;x&gt; &lt;y&gt; &lt;size&gt; &lt;growth&gt; &lt;xdir&gt; &lt;ydir&gt; &lt;interactive&gt; &lt;r&gt; &lt;g&gt; &lt;b&gt; &lt;target_size&gt; &lt;penetrate&gt;</code>

Please see [[styctap/zones]] for a more complete explanation on most zone types, as well as what you can do after spawning them, including zone routes.

=== Abbreviations ===

<code>team</code> - team name. team_blue would match Team Blue.

<code>x</code>, <code>y</code> - zone position

<code>size</code> - zone’s radius

<code>growth</code> - How quickly, if at all, a zone grows or shrinks.

<code>xdir</code>, <code>ydir</code> - What direction and where the zone moves.

<code>interactive</code> - If the zone bounces on walls. true if it should, false if it shouldn’t.

<code>r</code>, <code>g</code>, <code>b</code> - The amount of color a zone has, from 0-15 (values outside of this range are allowed too, though negative numbers only help make it invisible)

<code>rel|abs</code> - abs{{!}}cycle|rel and abs are relative or absolute using the map basis. cycle is relative using the cycle basis. it means 100 10 is a jump of 100 forward then 10 left (as trigonometric angles, left is +, right is -). This is to be understand before any direction change.that means depending of the direction you entering the zone, you are teleported in a different direction - Default value is rel.}}

<code>xdirdest</code>, <code>ydirdest</code> - the direction the player is sent when teleported, 0 will be current

<code>relocation_factor</code> - the relocation factor multiplied by the zone’s radius, typically 0-1. Basically, how far away you are teleported from the destination. Used for making you leave a zone of the same size at destination, as well as enabling default teleport zone behavior (1) of just teleporting from one side of the zone to the other.

<code>target_size</code> - The final size of a zone after shrinking or growing from another size.

=== Examples ===

<code>SPAWN_ZONE death 100 100 10 0 0 0 false 15 0 0 10 false</code>

This spawns a death zone with the following attributes:

<code>coordinates : x=100 and y=100</code><br />
<code>size/radius : 10</code><br />
<code>growth rate : 0</code><br />
<code>speed/velocity: xdir=0 and ydir=0</code><br />
<code>bounce of wall: false</code><br />
<code>color of zone : red=15 and green=0 and blue=0</code><br />
<code>target size : 10</code><br />
<code>penetrate wall: false</code>

== SPAWN_OBJECTZONE ==

=== Usage ===

<code>SPAWN_OBJECTZONE &lt;x&gt; &lt;y&gt; &lt;size&gt; &lt;growth&gt; &lt;xdir&gt; &lt;ydir&gt; &lt;interactive&gt; &lt;r&gt; &lt;g&gt; &lt;b&gt; &lt;target_size&gt; &lt;seek_owner&gt; &lt;seek_speed&gt; &lt;seek_update_time&gt;</code>

=== Abbreviations ===

<code>seek_owner</code> - Who the zone is targeting <code>seek_speed</code> - The speed factor the zone moves towards the player, relative to the player’s speed. <code>seek_update_time</code> - How often the zone updates its movement. Lower values may allow more accuracy, but cause the server to resync the zone with the client more often which may also increase lag.

== SPAWN_SOCCER ==

=== Usage ===

<code>SPAWN_SOCCER ball &lt;x&gt; &lt;y&gt; &lt;size&gt; &lt;growth&gt; &lt;xdir&gt; &lt;ydir&gt; &lt;interactive&gt; &lt;r&gt; &lt;g&gt; &lt;b&gt; &lt;target_size&gt;</code> <code>SPAWN_SOCCER goal &lt;team&gt; &lt;x&gt; &lt;y&gt; &lt;size&gt; &lt;growth&gt; &lt;xdir&gt; &lt;ydir&gt; &lt;interactive&gt; &lt;r&gt; &lt;g&gt; &lt;b&gt; &lt;target_size&gt;</code>

It is like the traditional fortress/ball combination in styball, but uses it’s own separate class and its own commands.

Other primary differences are * scoring is done by team instead of by player * zone wall and player wall interaction happening at once is different, players can actually (usually) keep control of the ball even near a wall. * speed decay is it’s own separate thing and is enabled by default.

=== Abbreviations ===

Please see SPAWN_ZONE’s list of abbreviations above.

= SOCCER Commands =

=== SOCCER_GOAL_KILL_ENEMIES [0|1] ===

If set to 1, enemies entering other team’s goal will be killed.

=== SOCCER_GOAL_SCORE [points] ===

Number of points scoring team gains for shooting the soccer ball through the other team’s goal.

=== SOCCER_GOAL_RESPAWN_ALLIES [0|1] ===

If set to 1, team mates will respawn after entering their own goal

=== SOCCER_GOAL_RESPAWN_ENEMIES [0|1] ===

If set to 1, enemies will respawn if the other team enters their goal

=== SOCCER_BALL_FIRST_WIN [0|1] ===

If set to 1, first goal made by a team will be declared the winners of that round.

=== SOCCER_BALL_SHOTS_WIN [0|1] ===

If set &gt; 0, the number of times the ball must enter other team’s goal. Sending the ball in their own goal does not count.<br />
Once these many shots have been accounted for, the round winner will be decided by the team with the leading score.<br />
Comparing the score between the shooting team and the team owner of the goal.

=== SOCCER_BALL_SLOWDOWN [0|1] ===

If set to 1, soccer balls slow down.

=== SOCCER_BALL_SLOWDOWN_SPEED [slowness] ===

If SOCCER_BALL_SLOWDOWN is set to 1, then the soccer ball will slow down depending on the value set for this command.<br />
Cannot have values over 1 or less than 0.

= SILENCE_ Commands =

== SILENCE_ALL ==

Silence everyone in the game.

== UNSILENCE_ALL ==

Reverts the SILENCE_ALL command. Meaning, give voices back to all of those who lost their ability to chat.

== VOICE_ALL ==

Similar to UNSILENCE_ALL. Gives the ability to chat again to everyone.

== SILENCE_ENEMIES ==

If set to 1, chat sent from enemies is not displayed on your client if you are alive. If you are dead all chat is displayed. This is a client setting.

= TAB_COMPLETION =

== TAB_COMPLETION [0|1] ==

If set to 1, the tab completion of names or commands will be enabled.

== TAB_COMPLETION_WITH_COLORS [0|1] ==

If set to 1, the tab completion of names or commands will be in colors.

= TIMER_ Settings =

=== TIMER_START [seconds] ===

Starts a ingame timer, giving players <seconds> to do something before getting killed.

=== TIMER_STOP ===

Perfectly stops the ingame timer.

=== TIMER_RESUME ===

If the timer was previously stopped, it resumes from where it last stopped.

=== TIMER_RESET ===

Resets the ingame timer back to default.

=== TIMER_MODE ===

* If set to 0, TIMER will count downwards until it reaches <code>TIMER_MIN</code>
* If set to 1, TIMER will count upwards until it reaches <code>TIMER_MAX</code>
* If set to 2, TIMER will count up or down, depending on the <code>target_time</code> given.

=== TIMER_TYPE ===

* If set to 0, TIMER will do nothing once the min or max is reached.
* If set to 1, TIMER will kill all active cycles on the grid.
* If set to 2, TIMER will destroy all active zones on the grid.
* If set to 3, TIMER will kill all active cycles and destroys all zones.

=== TIMER_MIN ===

<code>TIMER_MIN 0</code>

This is the minimal time for the timer to reach.

=== TIMER_MAX ===

<code>TIMER_MAX 80</code>

This is the maximum time for the timer to reach.