Old Server Cvars Command List

This site is best viewed in a modern browser with JavaScript enabled.

duelist

Please keep in mind this information is Very very old.
I apologize if this is available somewhere else. I have not been able to find a copy of this old resource. So I am reposting this verbatim from an archive. Please note that some of this might be out of date.
Source: https://web.archive.org/web/20160809170408/http://forum.mechlivinglegends.net/index.php?topic=16687.0

Admin, players, cannon fodder! Lend me your eyes! (this is the internet, ears would be foolish!) I have noticed a need, and gentleman I have the solution. A thread dedicated to providing as many of the useful variables as I can think of! It can all be yours just for suffering through this obnoxious intro.

First some general tips

Each of these is to be typed into the console as written ex. sv_password Hustle would make the server

password Hustle (case sensitive).

If you are adding these variables to your server.cfg file for

autorun at startup, you will need to have an = between the cvar and the variable. sv_password=Hustle

I do not recommend playing with the variables that will not have an affect on the

style of game you trying to run.

I have not included variables for those cvars as they are whatever you want them to be.

Default values can be found in a clean server.cfg found in your \crysis wars\Mods\mwll folder.

Some documentation regarding variables in this guide can be found in your

\crysis wars\Mods\mwll\Documentation folder. This documentation includes additional server specific commands
and information regarding those commands beyond the scope of this guide.

Variables that require a yes or no answer are 1 for ON (enabling that  cvar) and 0 for OFF (disabling that cvar)

I have not played around with Time Limit or respawn settings sorry don't know the format, if you do post here and tell me! [/li]

And now the star of our thread...

These variables can be applied to most games modes.
sv_password
sv_maxplayers
g_timelimit
g_minteamlimit
g_revivetime
g_autoteambalance
g_tk_punish
g_tk_punish_limit
ban_timeout
g_timelimit
g_fraglimit
g_pp_scale_income
g_roundlimit
g_preroundtime
g_scorelimit

General Commands
sv_is_vs_clan
0 is off
1 is on, Clan vs IS
2 is on, IS vs IS
3 is on, Clan vs Clan

sv_gamemode (Enter gamemode with proper caps and spaces ex. sv_gamemode TestofStrength)
g_nextlevel
map MAPNAMEHERE

Terrain Control
Additional Information regarding Terrain Control variables and how some of these values affect your game check this Sticky Dead Link https://web.archive.org/web/20120811095215/http://forum.mechlivinglegends.net:80/index.php?topic=11608.0
sv_team_tickets
sv_player_tickets
sv_ticket_decrement_rate
sv_capturing_rate
sv_null_ticket_wait_time

Test of Strength
sv_starting_cbills

Last Man Standing
sv_fixed_spawn_cbills
sv_leaguemode_commentator This shuts Duncan up

League Mode
sv_leaguemode_enabled
sv_leaguemode_aerorearm
sv_leaguemode_turrets
sv_leaguemode_ams
sv_leaguemode_cbtx (cbill exchange)
sv_leaguemode_repair
sv_leaguemode_vsale
sv_leaguemode_purchasemode
sv_leaguemode_purchasetimer
sv_leaguemode_exittimer
sv_leaguemode_jointimer
sv_leaguemode_joinmode
sv_leaguemode_activeeject
sv_leaguemode_aerorearm
sv_leaguemode_commentator

This guide is not all encompassing but does include the everyday settings needed to run custom games.

duelist

And terrain Control. Souce
https://web.archive.org/web/20120811095215/http://forum.mechlivinglegends.net:80/index.php?topic=11608.0
The following should be considered work in progress, but I wanted you guys to have it sooner rather than later:

MechWarrior: Living Legends Terrain Control Server Administrators Guide

Purpose This guide is intended to clarify some of the new features and concepts of the MechWarrior: Living Legends game mode Terrain Control. This document contains content that references the state of the game as of release 0.4.2

Terrain Control Overview
The Terrain Control game mode is a team-based objective capture-and-hold scenario that centers around the decrementing of Team Tickets from the opposing team. There are two methods to deduct Tickets from a team:

Controlling a greater number of capture points than the opposing team.
Destroying enemy vehicles and player kills.

Server Side Control Variables (CVARS)

Round Time
The time allotted for each session can be controlled using the following cvar:

g_timelimit n

Where n is a positive integer value that represents the number of minutes for the session.

Team Tickets Setting
Each team will start out with the same number of Team Tickets. The starting number may be set by the server administrator using the following cvar:

sv_team_tickets n

Where n is a positive integer value. The value of this setting will be dependent upon the selected match time duration, number of players and ticket decrement rate.

Assuming a 45 minute round time with 0.1 decrement rate:
Up to 10 players: 500
10 – 16 players: 750
16+ players: 1000

Capture bases present on the map have an author set weight that denotes their relative strategic value. Once one team holds more capture points than the opposing team Team Tickets will being to be decremented from the team that holds fewer capture points.

Ticket Decrement Rate
The rate of ticket debit is set using the following cvar:

sv_ticket_decrement_rate  n

Where n is a positive decimal value.
During the development testing period values between 0.3 – 0.5 where found to yield a reasonable ticket decrement rate.

The greater the disparity in number of held capture points, the faster the ticket decrement rate will go.

If sv_ticket_decrement_rate is set to 0 or is not present then base captures will not have any affect on Team Tickets.

Capturing Rate
The amount of time it takes to capture a strategic point can be controlled using the following cvar:

sv_capturing_rate n

Where n is a positive decimal value. Increasing the value of this number will result in faster capturing rates, lowering it will make captures take longer. If sv_capturing_rate is set to 0 or is omitted bases cannot be captured.

Note that if there are multiple players standing on a capture point their capture rate is additive (2 players can capture a point faster than 1 lone player).

Null Ticket Wait Time
If one team is able to completely deprive the opposing team of their Team Tickets then a challenge interval is invoked if it has been configured by the server administrator via the following cvar:

sv_null_ticket_wait_time n

Where n is an integer value in seconds.

Setting this interval allows for the team that has run out of Team Tickets to potentially deprive their opponent of their remaining Team Tickets resulting in a draw if such a state can be achieved within the time allotted. Once a team is out of Team Tickets, any players in the respawn queue will be unable to respawn.

For example, if sv_null_ticket_wait_time is set to 120, then a 2 minute timer will be displayed for both teams once one team (A) has deprived the other team ( of Team Tickets. If team ( is able to decrement all of the team (A) tickets within the 2 minute interval, the match will be declared a draw.

If sv_null_ticket_wait_time is set to 0 or is not included, the match will immediately end when one team deprives the other of Team Tickets.

Ticket Notifications
Audible notifications are made when the ticket value of a team is below 10% of their starting Team Ticket total. Another warning will be played when the Team Ticket value is 0.