Rules
Game: Counter-Strike (Half-Life modifcation)
Version: 1.6
Type: 5 versus 5 Team format (5 persons/team)
System: MR15 (2×15 rounds)
Round time: 1 minute 45 seconds
Start money: 800$
Knife round: Yes
Overtime: MR3 ($10000)
1. Requirements for participation
1.1. Preclusion from the qualification for the Wiggles Regional League – multiple squads
If more than one team per clan qualifies for the Wiggles Regional League relegation, only one of those teams is allowed to play. This has to be the higher seeded team.
1.2. No show
If a team does not show after 20 minutes, the team will lose the match (default loss: 0-1).
1.3. Match Schedules
All matches have to be played before the given deadline. If a match won’t be played in time, the result will be default win.
1.4. Client
1.4.1 Custodia
Each player has to run the latest version of Custodia during the entire match. The files created by Custodia have to be uploaded within 20 minutes (*extended) after the end of the match. If a Custodia file is missing, the team will lose 3 rounds. If more than one Custodia files are missing, one of the parties involved in the match has to protest on the league’s IRC channel. More than one missing, incomplete or manipulated Custodia files lead to default loss (0-1). After the protest was filed it is possible to upload proper Custodia files for another 20 minutes. If proper Custodia files are uploaded within that timeframe the penalty will be reduced to 3 round loss. If even after 20 minutes no proper Custodia files were provided for all players the loser of the match may request a rematch.
1.4.2 Procedures if Custodia is not working
In case Custodia is not working all players have to take a screenshot of the error message given by Custodia. After that, when the players are in-game all have to make a screenshot showing: scoreboard, smoke grenade smoke, a player model and net_graph 3. The screenshots and the in-eye demo then have to be uploaded to the Wiggles Regional League website’s Match Media section within 30 minutes after the match has ended. If any screenshots are missing, incomplete or manipulated, one of the parties involved in the match has to protest on the league’s IRC channel. Missing, incomplete or manipulated match media are punished with default loss (0-1). After the protest was filed it is possible to upload proper screenshots/in-eye demo for another 30 miuntes. If proper screenshots/in-eye demo are uploaded within that timeframe the penalty will be reduced to 3 round loss. If even after those 30 minutes no proper screenshots were provided for all players the loser of the match may request a rematch.
1.4.3. Client Settings
The following values have to be in the configuration file:
cl_movespeedkey 0.52
cl_pitchspeed 225
cl_showevents 0
cl_pmanstats 0
cl_lc 1
cl_lw 1
gl_max_size 128 (or bigger)
gl_monolights 0
gl_picmip 0
gl_polyoffset 0.1 (NVIDIA) / 4 (ATI) (Only values that do not enable an illegal “translucency effect” are allowed)
s_show 0
s_a3d 0
fastsprites 0
lightgamma 2.5
texgamma 2.0
Jumping is only allowed to be bound like this: bind “?Key?” “+jump”
It is not allowed to bind “+duck” to the mouse wheel
Walking is only allowed to be done with “+speed”
All other variables in the configuration files may be changed, as long as they do not give the user a significant unfair advantage (with effects comparable toa cheat). Changes to the game with the help of an external graphics driver or similar tools are not allowed!
1.4.4. Illegal Scripts
The following scripts are prohibited:
turn scripts [180° or similar]
-mlook scripts
stop-shot scripts [Use- or Awp-scripts]
centerview scripts
no-recoil scripts
burstfire scripts
jump- & bunnyhop scripts
duck scripts
1.4.5. Changes to the Configuration – A3D
The use of A3D (2.0) is forbidden and is considered cheating. The use of tools / drivers have the same effect as A3D (2.0) will achieve the use of A3D (2.0) equated.
1.4.6. Changes to the Configuration – Graphics Drivers or similar Tools
Changes to the game graphics or textures using graphics card drivers or other graphics tools are prohibited.
1.4.7. Client Settings – 32 bit
Every player has to set the color depth at Highest (32 bit) in the Counter-Strike settings. If Counter-Strike is played in window mode, the Windows color depth need to be set to 32 bit as well. If a participant does not play with 32 bit graphics the team receives default loss.
1.4.8. Custom Files
Except Steam skins no custom files are allowed. As for Steam skins, only changes to the layout of steam or of the console are allowed. Changing models, Crosshairs, HUD, scoreboard or other files are prohibited. CS: CZ Models, which are sometimes automatically installed due to a steam error, are also not allowed. They have to be replaced with the original models before the start of the match.
1.4.9. Riot Shield
Usage of the riot shield is prohibited. If the shield is used, the team lose 3 rounds. Depending on how it was used the administration may force the match to be replayed.
1.5. Map pool
The map pool of the Counter-Strike Wiggles Regional League consists of the following maps: de_nuke, de_dust2, de_train, de_tuscan, de_inferno
1.6. Server
1.6.1. Server Requirements for the Wiggles Regional League
The Wiggles League matches have to be played on a league server. The teams have to request the server informations from an admin on the league’s IRC channel 24 hours before the start of the match.
1.6.2. Server Settings
All league servers are configured for the matches. Every necessary configs are available on the server. Executing own config file is forbidden. Only the server’s config files allowed to execute. These commands and configs are: rcon exec warmup.cfg / knife.cfg / live.cfg / overtime.cfg. If someone execute an own config, the team will be punished with 3 round loss. The “rcon quit” command is also forbidden. If you have the rcon password, there is no admin on the server and the server need restart, use the “rcon map de_xxxxx” command.
1.6.3. Server plug-ins
No plug-ins may be installed on the game server. Especially the Metamod plug-in is not allowed.
1.6.4. Leaving the Server
All matches have to be completed. Any violation is punished with up to three (3) minor penalties. A match is considered completed when a team won 16 rounds on a map. (At the group stage all the 30 rounds have to be played.)
1.7. Number of players
All matches are to be played with 5 players on each team. A 4 on 5 or other constellations are not possible.
1.8. Choice of team
A knife round has to be played before the match starts. It is up to the winner to choose sides (CT/T). If a team obstructs finishing the knife round before the round ends, the team gets 1 round loss and the opposing team has the right to choose sides.
1.9. Player disconnections
If a player disconnects from the match server before the first kill occurred in the first round, the match is re-started. In the case a player drops after the first kill in the first round, the pause function can be used. If the dropped players are not back by the time the next round starts, the match has to be paused at the start of the round. Maximum waiting time for a dropped player is 10 minutes. If the dropped player does not reconnect and the team is not able to substitute the player, the match is scheduled at a later date. The team, which for the interruption of matches is responsible, lose three rounds.
1.10. Game server or network failure
If a match is interrupted by a network or game server failure within the first 3 rounds of a match, the match will be restarted. If the match is interrupted after the three rounds, all rounds up to that point count. The match will continue with the following settings:
mp_startmoney 5000
all remaining rounds have to be played
The mp_startmoney value has to be reset to 800 after changing sides
1.11. Mandatory demo recording
Each player has to record a demo. Each player has to have one demo per map. HLTV demos are not allowed.
1.11.1. Demo upload requests
If a participant wants to view the demo of a particular player, the demo has to be requested within 20 minutes after the match by filing a protest. The demos then have to be made available within 30 minutes after the end of matches to the website’s match media. Also it needs to be checked whether the demos can be downloaded from the match media section without errors. Missing, incomplete or manipulated demos are punished with default loss. If a demo requested from the winning team is missing, the losing team may request a rematch.
1.12. Exploiting bugs
The deliberate exploitation of all kinds of bugs is punished with 3 rounds loss for each occurrence. The maximum amount per match is 6 rounds loss penalties. Furthermore, the administration may, depending on the situation, force a re-play of parts of the match or the entire match. In very serious cases the administration reserves the right to award higher penalties. Exploiting the following bugs is explicitly prohibited. If any bugs are exploited which are not listed here, the tournament administration decides whether a punishment is necessary or not. Before the match: Bugs caused due to game content failing to load (e.g. missing boxes, ladders and the like) are to be checked for before the start of the match on each map that is played. If such a bug occurs it has to be eliminated by reloading the map. If any bugs were not found prior to the match start or if the player did not check for bugs, the player in question automatically accepts the conditions. Filing a protest because of the playing conditions after the match is not possible.
During the match:
- Pushing players through walls, floors and ceilings (including the outer wall off the map) is prohibited. This also applies on ’skywalking’.
- “Silent bombs” (planting a bomb in a certain way to prevent it from making the intended beeping sounds) are prohibited.
- It’s not allowed to plant the bomb in positions that are impossible to access. It is also not allowed to plant the bomb in places you can’t reach without the help of a teammate!
- Climbing and stacking players in order to do so is allowed. It is forbidden to climb into positions that allow for exploitation of clipping errors in the map design. It’s also not allowed to perform certain moves in some positions that allow for exploitation of the clipping errors (such as a jumping).
- Flash grenade bugs exploits are prohibited.
- Throwing grenades under walls is prohibited. Note: Throwing over roofs and walls is allowed.
- “Map swimming” or “floating” is prohibited.
- “Pixel walking” is forbidden (sitting or standing on invisible ledges).
General: Exploiting any bugs which go against the basic principles of the game are prohibited (e.g. spawn bugs etc.).
1.12.1. Map-specific Bugs
de_dust2: Not allowed positions: [-1-] [-2-] [-3-] / Allowed positions: [-1-]
de_inferno: This roof is illegal.
de_nuke: Walking on this wall and on this roof is illegal.
de_train: Looking through this gap is illegal.
1.13. Match media
All match media files (demos, screenshots, etc) need to be named following the scheme below:
Screenshots:
Errorscreen – Team short handle – Nickname
Smokescreen – Team short handle – Nickname
Custodia: Custodia – Team short handle – Nickname
Demos: Demo – Team short handle – Nickname
All players have to wear the same clan tag. Protest or support tickets because of this will be thrown out. Violations of the clan tag rule will be punished with one round loss.
1.14. In-game Nicknames
All players have to play their matches using the nickname they have provided in their team lineup prior to the start of the season. If this is not the case, the team receives one round loss.
The rules are a guideline and the decisions by admins may differ from them depending on the circumstances.
Subject: Rules ^^ 
Fri Jul 16, 2010 10:50 pm
