|
|

|
Q3CTFS Headlines Missing Week + Fixtures Season 17 Starts Season 17 sign ups open Season 16 Finished Season 16 Fixtures Savage Headlines Web Server Maintenance .. Game server move complete Game server move Happy Christmas Clocks go back an hour |
Latest Demos |
Latest Reports |
|
|
Rules for The SavageUK Q3 CaptureStrike League1. The Savage Council and Match AdminsCouncil Chairman - Slave Council Members - Are as follows:
League Admin - NoMercy Match Admins - Appointed by League Admin, on weekly basis. At NO point will you verbally abuse any of the Savage Council or Admins, if you do you will receive a 2 Match ban and if that does not stop the abuse then your clan will be removed from the league. 2. GrievancesGrievances will only be listened to via email. If, for whatever reason, you have a grievance against a Match Admin then please email it to The Savage Council If, for whatever reason, you have a grievance against a Council Member then please email it to The Savage Council Chairman Please do not expect problems to be sorted out on match days. Once you have mailed your grievance you should expect a reply within a week. If you are experiencing problems with connecting to a SavageUK (Match or Public) Server from any ISP, please perform a DOS tracert to the IP of the server you are experiencing problems with and post the results to the server forum and the problem will be investigated. 3. Match Format and Game Rules3.1 Server Settings
3.2 Clan TagsPlayers are expected to wear their clan tag and a name which has to be registered on CAPS during matches, anyone not wearing their clan tag WILL be asked to put it on, if the player does not respond or put the tag on that player will be kicked from the server. Subsequent violations will see the player excluded from his match.
3.3 PunkbusterSavage servers use Punkbuster Anti-Cheat Software,you must make sure you have Punkbuster enabled to join a Match server. Players will be responsible for ensuring their Punkbuster installation is up-to-date. Games will not be delayed for any players whose Punkbuster is not accepted by the servers due to outdated installations. If a player is kicked by Punkbuster for any reason other than a Punkbuster Server issue then the game will not be delayed to accommodate this player, though the player will be allowed to enter the game after a mandatory lockout period of around 2 minutes. Genuine problems caused by Punkbuster that affects the Savage Community as a whole will be considered on a case by case basis and the league admin will resolve such matters using personal discretion. Players kicked by Punkbuster for cheating will be banned from the league. GUID's will be stored to ensure said players do not attempt to rejoin the league under an alias. Aliasing will not be tolerated and in such incidents GUID's will be used to determine the identity of the protagonist. The league admin will take random Punkbuster Screenshots. Whilst we know this may cause some lag for players, it is felt this is a vital tool in combating cheats such as wallhacks. Savage take no responsibility for any problems that Punkbuster might cause and suggest Players consult EvenBalance.com with any technical issues that might arise. 3.4 Punkbuster Server settingsThe following settings are applied to league servers, players that do not conform to these settings will be kicked until they are adjusted accordingly.
3.5 PausingThere will be a maximum 1 minute pause allowed per team per map. Use it wisely. 3.6 Season Length5 weeks (this may change based on the number of teams per Division) 3.7 MapsMaps will be publicised before the commencement of each season on the Savage Q3 CTFS fixtures page. It is up to you to have the correct maps, downloads of maps for the season are mirrored on the Savage Q3 CTFS page. 3.8 Match TimesDuring a Season Matches are played once a week on a Sunday Afternoon. Start times are dependent on your Division and are as follows: Division 1: 4pm (subject to change) All times are current UK time (GMT or with daylight savings BST), please add one hour if you are in the CET timezone. 3.9 Rescheduling of MatchesA clan should only reschedule one Match a season, BUT the other clan must agree first and may, if they wish, turn you down therefore receiving a Default win. Please use the Reschedule button on the fixtures page for the relevant match you wish to reschedule. Rescheduled games should be played within one week of the original fixture, and the times should be agreed with the league admin so that a server and league admin may be provided for the game. 3.10 Match LengthA match consists of 2x18 Minute games. Games will start as near to the Match Time as possible. The latest a game will start is as follows: First game start: 5 Minutes after the hour. If players and game admin are willing, games may start before these times. At the admins discretion 5 more minutes may be added to these times in order for late players to arrive. If both clans aggree, break time may be sacrificed to grant up to an aditional 7 minutes waiting time for late players. The first game should start no later than 17 minutes past the hour, the 2nd game should start no later than 40 minutes past the hour. At the league admins discretion these time limits may be waved. It is up to players to be on the Match Server in time for the game. If both clans fail to have the required number of players on server, the game will be a default draw, unless a rescheduled game time is arranged. When the server enters Match Mode, please join your team. When the teams indicate readiness or the maximum start time is reached, the admin will start the match. After this point the rules regarding conduct are strictly enforced. 3.11 Match ColoursFrom the fixtures page the team on the LEFT should go BLUE for the first game, and thus the team on the RIGHT sould go RED for the first game. For the 2nd game, the teams should change colours 3.12 Team size6 (SIX) players. If a Clan turns up with less than 4 (FOUR) players by the latest starting time then the Match Admin will default the game to the other clan. If during a game a Clan drops below 4 (FOUR) players a Default will be awarded to the other Clan - overflows are of course excluded from this rule. If during a game a clan drops a player to even teams, that player will be allowed to stay on the server provided they use the "specred/specblue" command to spectate their own team only. At NO time other than pause time may a clan have more than 6 (SIX) players on a match server, if a player is to be replaced, they should drop from the server before the replacement connects. 3.13 Player Ping TimesThere is NO lower limit on pings (No LPB Limit), high ping players will be removed from the server if they cause disruption to the running of the server, eg game pauses 3.14 Frames per SecondThere is NO FPS Limit at this time. 4. League Rules & Information4.1 DefaultsIn the occurrence of a default being given the following will be awarded per game defaulted: 3 game points/12 Caps If a Clan should miss/default 2 league Matches in a season then
they may be removed from the League at the League Admin's discretion. 4.2 Match ScoringEach game is classed as a separate entity. Points will be given out per game as follows: 3 points for a win If each Clan has the same amount of points by the end of a game it will be classed as a Draw. If, at the end of the Season, two Clans end up with the same score for first place or the second promotion spot in divisions 2,3 and 4 a 'decider' will be played in 'week 8'. 4.3 Internet Relay ChatDetails are as follows: Server: irc.quakenet.eu.org Match Server details will be given out 5 minutes before a Match Starting time in the Match Channel and will not be given out any earlier so please do not ask. Please make sure a Clan representative is in #savage.q3 to collect server details. Please wear your Clan Tag if you are in #savage.q3 If you do not wear your Clan Tag you may be kicked. Match details will only be given out in this channel. Please do NOT join the Match Server until instructed to do so by an Admin. Usually this instruction is given with the match details, but if it isn't wait until it is given. Please do NOT join #admins unless you are requested to do so by a Council Member or league Admin or unless you are a Match Admin. If you do then you WILL be kicked. If the IRC server crashes or in event of a netsplit please use the following server: irc.b0rk.co.uk 4.4 Match Server CrashesThis, unfortunately, does sometimes happen. If it does please go to IRC #savage.q3 and await your new Match Server details. If a spare Match Server cannot be found then the Match will be replayed at a later, mutually convenient date to be decided by the Savage Council. Following a Server Crash the game will be played with the following game Length: Time remaining Between 15 and 18 Minutes: 18 minutes It is understandable that a Clan might feel aggrieved due to positions held on the map. This cannot be taken into account in a replay. If the Match Server crashes before 5 minutes of game has been played then it will be classed as a new game and any Cap score will be lost. If a game has been playing for more than 5 minutes then the Cap score at the time of the Match Server crash will be carried forward to the replay. 4.4 Clan WhoringWill NOT be tolerated. A player cannot play for more than one team within the Savage q3ctfs League. If a player changes Clan there must be a gap of 8 days between their last appearance for their old Clan and their first appearance for their new Clan. If it is found that a player has broken this rule the Match they played in will be classed as a Default in favour of the opposing Clan (if the other clan chooses to accept the default score - otherwise the game results stand as played). The offending clan will also be docked 3 points per incident. The player will also receive a 2 match Ban. If a Clan breaks this rule twice they will be kicked from the League. It is up to the Clan to make sure they know who is playing for them. A player may play for more than one Clan if it is for another MOD. In order to field a new player, SavageUK q3ctfs clans must ensure that they abide by the following:
As long as the opposition team and the match admin are satisfied that the player is who they say they are, then a match may proceed, but there will be no scope for complaint after the match UNLESS the player is found out not to be who it was claimed he was. The match admin has the power to over-rule a clan. If the match admin is satisfied, the match may proceed. If a clan wants to complain about a player name, they must do it before the game starts, and if they let the game proceed it is taken as read that they have accepted who they are facing as opposition. If a clan is found to be fielding a player who is not confirmed on their members list, or within the two week tied period, that clan will be awarded a default loss [if their opponents wish to accept the default score] and penalised by a three point deduction per incident. A player may still not play for two clans within SavageUK q3ctfs, so if the player's original clan also join the SavageUK q3ctfs League, that player must chose which clan he will play for. He may change his mind, but will be subject to the two match period during which he may not play. 5 CheatingEvidence of cheating during league games may be shared with other leagues to protect the gaming community. 5.1 BotsBots will NOT be tolerated. Bots are easy to spot. If a player is found to be using a Bot they will be banned for LIFE. Bots include Speed, auto-aim bots, health bots, etc... 5.2 ProxiesProxies will NOT be tolerated. If a player joins a Match Server with a Non-default port they WILL be kicked. It is up to the player to make sure they connect using the default port. 5.3 Hacked Game Binaries/exe filesHacked game binaries/.exe files will NOT be tolerated. If a player is found to be using a hacked .exe file they will be banned for LIFE. 5.4 SpectatorsAre NOT allowed on to the Match server, this does not include people in team-spectator mode /specred /specblue. If a member of a Clan joins a Match Server and is not playing they will be asked to leave by the Match Admin. If they do not leave they WILL be kicked. 5.5 SubsAre NOT allowed on to the server unless: Their Clan drops a player due to disconnection. Once the dropped player rejoins the Sub should drop. 5.6 Voice CommunicationReal-time voice programs such as Teamspeak2, Battlefield Communicator and Roger Wilco are not considered cheating and are permitted. 5. Conduct of PlayersThese rules apply to any communication relating to the league between people involved with the league, though disciplinary measures will only be enacted against those who break them in relevant savage controlled IRC rooms (#admins, #savage.q3), savage forums, and game servers. 5.1 Disruptive BehaviourSwearing, spamming or anything else classed as disruptive is not permitted; you WILL be kicked/banned if you do so. 5.2 Spamming the serverSpamming the server or players Will NOT be tolerated. Messagemode 1 Text or Radio spam is not permitted. Anyone spamming text or radio messages in MM1 will be warned by the match Admin. If MM1 spam continues after a warning is issued, you will be kicked from the server for the remainder of the match. Please keep all messages to 'Messagemode 2' (team messages). It is up to you to find out how to do this. If a player repeatedly uses 'Messagemode 1' to Spam the Match Server they WILL be kicked/banned. 5.3 The Q3 CTFS ForumIs there for you to say what's on your mind. However it is NOT there to verbally abuse any of the Savage Council or Admins, if you do you will receive a 2-Match ban and if that does not stop the abuse then your clan will be removed from the league unless significant disciplinary action is taken against the player by the clan. If you have a grievance do NOT use the Boardroom. Instead please use the grievance procedures as detailed in section 2. The Savage Council reserves the right to delete posts that are felt to bring the Savage q3ctfs League into disrepute. 6. GeneralThe Savage UK q3ctfs League reserves the right to change these rules as and when it feels it necessary. Feedback on these rules in particular regarding mistakes in the text, should be emailed to nomercy (at) tomb.org.uk |
|