The following list shows you the TSW-specific commands and the default keys they are bound to.
command |
description |
default key |
observermode |
toggles between action-mode (1st-person) and tactical-mode (freefloat-3rd-person) |
o |
sattelitemode |
switches between strategy-mode (top-down-view) and tactical-mode |
i |
mouse_mode |
switches the way, the mouse behaves; you can either use it for angle-turning (in case you use the freelook-mode) or for mouse-cursor-movement, then your crosshair will be moveable over your screen like a normal mouse-cursor |
TAB |
print_vecs |
prints your current position and angles to the console, use this command if you need coordinates in a map (e.g. script-coding) |
<none> |
If you execute tsw.cfg, the default bindings will be set for you.
TSW has been designed to be played with a mouse-keyboard-combo, where the mouse turns your angles (freelook-mode) and you move with your keys. Since the mouse-buttons will have different functions in the different movement-modes, we recommend to have the firing-function set to the first mouse-button and jump/move up on the second mouse-button. Other control-sets are possible, but may cause problems when switching between the movement-modes. You should also have a key bound to the walk/run-command, as this one is also used in multiple movement-modes.
The following list shows you the TSW-specific cvars and their default values. You can set these cvars with the command seta <cvar> <value> or ask for the current value with <cvar>.
cvar |
description |
default value |
g_modelscale |
Scale the relation between the units and all other objects to the world they are presented in, the value is calculated in percent, a value of 50 will make everything just half as big and move half as fast as it would normally, thus increasing the world's size by factor two. |
100 |
g_limitvis |
Determines how the lines-of-sight are calculated. If set to 1, your units will only be able to see objects over a certain distance, beyond that they are invisble. If set to 0, your units will be able to look until their view is blocked by a wall or a large object. You cannot disable the lines-of-sight at all. |
0 |
g_tsw_start_credits |
Specify how many credits each team will get at the start of the game. |
2000 |
g_useini |
If this cvar is enabled (1), the server is forced to read the map's ini-file to determine which teams are playing and where the teams start. If this cvar is not set, the ini-file is ignored in case the map contains proper information on how to start the game. The ini-file will always be used for TSW:Mission-games. |
0 |
sv_mapini |
Load an ini-file that's name is different than the map's name (e.g. e1m1.bsp and e1m1b.ini). This allows you to play different situations on a single map. Learn more about this at the modify-part. |
<empty> |
sv_minclients |
Define how many clients are needed to start the game. The desired number of players has to choose the team and signal their ready-state, then the game will start. This cvar is also auto-set by the start-server-menu, so setting it is only needed for a manual server-launch. |
<auto-set> |
There are some other settings you need to set if you are launching a server manually.
The units in TSW are bots. This means each unit requires a client-slot. The more clients you can run on your machine, the more units you will be able to have in the game. The number of clients your machine can afford depends on the physical RAM you have. With 128MB of physical RAM you are able to allow around 40 clients without problems. To set this, use the cvar 'sv_maxclients'. You may set this one also in the startserver-menu.
This list shows you the commands that can be executed by the server-operator to manually start a game. All these commands are auto-executed if you are using the startserver-menu.
command |
paramters |
description |
reg_team |
<name> <number> |
Register the team at the server. Only registered teams can be accessed by the players, so you need to register at least two teams. "name" holds the name of the team, "number" tells the team-number ( 1 = red, 2 = blue, 3 = yellow, 4 = green ). Warning, at the moment TSW only supports skins in red and blue. Specifying other teams will give the units their default skins, so avoid registering green and yellow together! |
reg_ip |
<IP> <team> |
Register a certain client to a team. "IP" holds the IP-Adress of the client, "team" the name of the team he shall be assigned to. |
tsw_finalize_init |
no paramters |
This executes the final settings and prepares the whole game for the clients. Before this command is executed, the players can't choose their teams or prepare the launch of the game. This command has to be the last one of the whole list! |
website design : images : screenshots are copyrighted by "shattered wings" © 2000
Quake(tm), Quake 2(tm) and Quake 3: Arena(tm) symbols (the stylized 'Q's) copyright © 1996-99 Id Software, Inc.
Quake(tm), Quake 2(tm) and Quake 3: Arena(tm) are registered trademarks of Id Software, Inc. All rights reserved
|