Starsiege: Tribes Community Archive

HaVoC159c

by admin
⤓ Download · 1.5 MB
No file description.
Filename
HaVoC159c.zip
Size
1.5 MB (listed 1.53MB)
Type
ZIP
Version
1.5.7 (from readme)
Developer
admin
Last update
Jun 07, 2008 - 02:13
Format
Zip archive data, at least v1.0 to extract, compression method=store
Readme — HaVoC/readme.txt (from the archive itself)
June 13, 2000.

    ***** HaVoC version 1.5.7 FINAL *****

Thank you for downloading HaVoC 1.5.7.  This will be the
last major release of HaVoC.  This version is filled with 
great new stuff, Duel, grappling  hooks, new teleporters, 
many new maps, and many other things.

This mod has been a project of mine for over 10 months and I 
feel like it is ready to get on every server out there.  I've 
worked hard on not only the mod but on quite a few maps for it.

For information on running a HaVoC 1.5.7 server refer to
the install.txt file that came with this mod.  For 
information on setting the various features of HaVoC, 
refer to the guide.txt file that came with this mod.
Be sure to read the racersetup.txt so you can see the
Racer skins correctly.

While the majority of HaVoC was written solely by myself, 
this mod does contain work from many authors.  No one
but myself ever worked on it, but I used some code from
other's mods.  Why reinvent the wheel?  Many thanks go
out to many people for thier permission to use thier 
code.  Please take a look at the credits.txt file that
came with the mod and acknowledge all the great people
that have contributed to HaVoC.

[HvC]NaTeDoGG
Nathan Sweet
http://havoc.sirris.com
natedone@hotmail.com
Readme — HaVoC/guide.txt (from the archive itself)
This guide and more can be found on the HaVoC website:  http://havoc.sirris.com

For general help on running a server please refer to Tribe's Players (http://tribesplayers.com).

Before reading this please read racersetup.txt.

This guide will teach you how to configure the HaVoC mod to your liking. Click here to download this guide in a text file. When installing the mod a file called HaVoC.cs is put into your Tribes/config folder. In this file are the various server settings. This guide will take you through setting up each one.

Also be sure to check out the features in the HvCUserList.cs file that comes with the mod.


TEAM KILLER FEATURES:

$HaVoC::tkLimit
This determines how many team kills are allowed before action is taken.

$HaVoC::tkClientLvl *
This determines what a TK victim can do to the TKer once $HaVoC::tkLimit has been reached.

If set to 0 the victim will have an option on thier TAB menu to vote to kick the TKer. 
If set to 1 the victim will have an option on thier TAB menu to kick the TKer without a vote. 

$HaVoC::tkServerLvl *
This determines what the server will do to a TKer once $HaVoC::tkLimit has been reached.

If set to 0 just log TKs, never take any action. 
If set to 1 the server initiates a votes to kick a someone every $HaVoC::tkLimit TKs. 
If set to 2 then see $HaVoC::tkMultiple below. 
If set to 3 the server will kick a TKer when $HaVoC::tkLimit is reached. 

$HaVoC::tkMultiple
This is used when $HaVoC::tkServerLvl = 2. The server will vote to kick a player at every multiple of $HaVoC::tkLimit. For example, when $HaVoC::tkLimit = 2 the server will vote to kick anyone when they commit 2 and 4 TKs. But, when someone has committed $HaVoC::tkLimit times $HaVoC::tkMultiple TKs the server will kick them without a vote. For example, when $HaVoC::tkLimit = 2 and $HaVoC::tkMultiple = 3 then the server will vote to kick anyone when they commit 2 and 4 TKs and kick them without vote when they reach 6 TKs (2 * 3 = 6).

$HaVoC::BanKickTime *
This is how long (in seconds) after someone is kicked that they will not be able to reconnect to the server.

$HaVoC::Eye4anEye *
When this is true and a player has reached $HaVoC::tkLimit number of TKs, then any damage this player does to a teammate is also done to himself. If a player exceeds twice $HaVoC::tkLimit number of TKs then twice the damage this player does to a teammate is also done to himself.

$HaVoC::BaseKillWarning *
This is the number of Base Kills (destroying your own team's deployables) required before admins will be warned. For example, if $HaVoC::BaseKillWarning = 3 then when a player has destroyed 3 of his own team's turrets, all admins will be warned that the player is Base Killing. Destroying a turret you deployed yourself is not considered a BK. Set to "0" (zero) to disable.

$HaVoC::BaseKillLimit *
This is the number of Base Kills required before the player is kicked. The Base Killer will be warned when they reach $HaVoC::BaseKillLimit number of BKs that one more BK and they will be kicked. Set to "0" (zero) to disable. 


SUPER ADMIN FEATURES

You can set up to 100 Super Admin passwords. Here is an example of how to set up new super admin passwords:

$HaVoC::SADPassword[1] = "evil";
$HaVoC::SADPassword[2] = "die";
$HaVoC::SADPassword[3] = "renegades";
$HaVoC::SADPassword[4] = "stupid";

Any one of those passwords used with the SAD(""); command will grant the user Super Admin Status. 

You can set up to 100 Master Super Admin passwords. Here is an example of how to set up new master super admin passwords:

$HaVoC::MasterSADPassword[1] = "always";
$HaVoC::MasterSADPassword[2] = "kill";
$HaVoC::MasterSADPassword[3] = "smurfing";
$HaVoC::MasterSADPassword[4] = "bums";

Any one of those passwords used with the SAD(""); command will grant the user Master Super Admin Status. Being a Master Super Admin allows you to strip any non-master admin of thier powers. 


PUBLIC ADMIN FEATURES

You can set up to 100 public admin passwords and each can have thier own special abilities. Here is an exaple of how to set up new public admin passwords:

$HaVoC::PAPassword[1] = "secret";
$HaVoC::PAPassword[2] = "ruplstiltskin";
$HaVoC::PAPassword[3] = "tree";
$HaVoC::PAPassword[4] = "cheerios";

Any one of those passwords used with the SAD(""); command will grant the player public admin status. 

To restrict a certain password from specific features, you first must enable it by using the number in the brackets of the corresponding password above:

$HaVoC::PASpecial[3] = TRUE;

This will give password number 3 ($HaVoC::PAPassword[3]) special lockouts as specified with these: 

$Special::PATimelimit[3]: Ability to change the time limit. 
$Special::PAMission[3]: Ability to change the mission. 
$Special::PATeamDamage[3]: Ability to enable/disable team damage. 
$Special::PAKick[3]: Ability to kick players. 
$Special::PABan[3]: Ability to ban players. 
$Special::PATorture[3]: Ability to access the Torture menu. 
$Special::PATeamChange[3]: Ability to change a players team. 
$Special::PAServerOptions[3]: Ability to change $HaVoC::tkServerLvl and $HaVoC::tkClientLvl. 
$Special::PAFairTeams[3]: Ability to enable/disable Fair Teams. 
$Special::PATourneyMode[3]: Ability to enter/leave Tournament mode. 
$Special::PAStartMatch[3]: Ability to start the match in Tournament mode. 

Set these to true or false according to what you want to give password number 3 access to. Repeat using different password numbers to set up any password with special lockouts.

If you do not set up special lockouts on a password then the default lockouts are used. The default lockouts also apply to admins appointed by public vote and players given admin status by another admin. To set up the default lockouts, set the following to what you want to give default public admins access: 

$HaVoC::PATimelimit: Ability to change the time limit. 
$HaVoC::PAMission: Ability to ch
Contents — 228 files (inside the archive)
Source: The Exiled — Tribes Repository
Original page: https://library.theexiled.pwnageservers.com/file.php?id=195
Archived source HTML: _source/file/195.html