News | Rules | Maps

Aussie Custom Fortress Pug Rules


Contents

1. The ACF Pugbot
2. Pugbot Commands
3. Gameplay Rules
       3.1 Class Restrictions
       3.2 Pug Rules
       3.3 Bans
       3.4 Admins
4. Pregame Setup
       4.1 ESEA Mod
       4.2 Captains
       4.3 Gameplay Votes

The ACF Pugbot


Since the begining of the iPGN Team Fortress 2 Pugbots (created by mcky) I have always wanted custom maps to be added. So after many hours and help from many people we decided to setup a system for Custom Map Pugs!

The Pugbot uses a modifed version of the same bot used at #tf2pug and #tf2pug2. This modifications undertaken by bladez includes the removal of the stats and game server connection.

The Pugbot is located on one of the iPGN servers. This bot allows one of the Admins to start a pug and users to join. On filling of the pug a server string is sent to all parties. The player joins the server and an Admin will run the pug.

There is more detailed information about rules and commands setout below.

Hope to see there!

Pugbot Commands


Some of the commands that can be used in IRC are set out below.
!j/!join - Joins active PUG
!l/!leave - Leaves active PUG
!details - Get IP and password for server
!players - See who is playing
!maps - Displays all maps running on the Pugbot
!map (map) - vote for map (!map cp_freight)

Gameplay Rules


Class Restrictions
Class restrictions consists of the 6v6 (CEVO Rules): Maximum of 1 (one) medic, 1 (one) demoman, 1 (one) spy, 1 (one) heavy, 1 (one) engineer and two of everything else.

Pug Rules
-All rules are only 'guidelines' and an admin can alter these and change ban times at their own discretion.

-Breaking a rule WILL result in a ban.

-Players are expected to connect to the server promptly and stay in the server for the entire duration of the pug.

-Players ARE allowed to request a replacement should they need to leave, but they must wait in the server until the replacement has joined the team. Once the replacement is in and playing, the player is able to leave the PUG. Do NOT expect to be able to leave the PUG and have a replacement found for you, doing so will result in a ban. Admin commands are to be used properly, and not to disrupt the pug in progress. You will have to find the replacement yourself.

-When a player is selected as medic by a captain or an admin, they are expected to play the class. Not playing medic after being assigned to the medic class will result in a ban.

-Players being disruptive during the pug (eg. being rude to other players, not adhering to class restrictions) will be warned and then if said player ignores the warning and continues to be disruptive, he or she will be banned.

-Players who sign up for the PUG in the IRC channel and do not join the server will be banned.

-Spamming of any sort, not only limited to !j, !join, !JOIN or !J will result in automatic ban of 1 (one) hour. Players who continue to spam after returning from their 1 (one) hour ban will be dealt a lengthier ban.

-First come first serve to each class. If someone is already playing a class, and the class limits have been reached on that class, it's theirs. Stacking a class, in order to try get a position will not be tolerated and will result in a ban.

-Being abusive or disruptive, ruining the game for other players or being a downright idiot will result in a ban.

-Players may join the server and spectate the pug while in process. If you join the pug and distrupt it you will recieve a ban.

-Spamming +duck (script or manually) in order to exploit hit boxes is not tolerated. Doing so will result in a ban.

Bans
-All ban times are 20 hours, and ANY offence after that may be stacked. For example if you receive your first ban and then you break the rules again you may receive a reasonbly sized ban up to 3 days decided by the admin.

-If a player beleives they have been banned unreasonbly contact one of the admins in the server and if that dosn't work contact Aragon.

Admins
If you need further assistance or questions about the rules, please don't hesitate to contact one of the following people:

-Aragon
-Dpp
-No Mercy

Pregame Setup


ESEA Mod
The ESEA leagues standard mod is installed on this server and can be turned on and off. A vote at the start of the round when at least 10 of the 12 players are in the server will be initiated. You may press 1 or 2 on the keyboard determining your answer when the question arises.

Now a little about the mod:
This plugin removes the on-death freeze cam as well as the random damage range for all weapons in Team Fortress 2. Normally every attack has a +/-50% range in damage it can do, this plugin will force Team Fortress 2 to use the middle value of that range.

Captains
The way teams are determined is decided from a vote at the start. This vote asks wheather you wish for captains to determine teams or scramble. When the captains option wins, it is the responsiblity of the captains to make sure the class's are set for each team. Then it is his/her responsibilty to readyup.

When teams are scrambled a vote may be used to determine wheather players are satisified with teams. Once players are satisified the game will begin.


(An Admin may choose options above without initiated votes at his/her discretion. You will be expected to play. If you leave, it will result in a ban)

GamePlay Votes
Throughout the game votes may be initated for various reasons. Some may include votes for wheather to turn a mod on. Others may include votes about wheather you like a map. It is not compulsory to vote in these but it is suggested as these votes help make your gameing experience more pleasurable.


All of the above rules decisions can be changed/made by one of the admins outlined above in the admins section. If you think one of the decions was unreasonble, PM another admin.

Last Updated: 29/01/2009 at 9:05 pm by Aragon

Copyrights © 2009 Clan Fase | Supporting: IPGN and Ozfortress