Liveon3 Cups

1.0 - Rules
2.0 - Scheduling
3.0 - Servers
4.0 - Match Rules
5.0 - Players
6.0 - Disputing
7.0 - General Cup Rules

1.0 General Rules
1.1 -Round Limits The Lo3 Counter-Strike: Source Cup is played in a best 16 out of 30 format. Players switch sides after 15 played rounds and the game restarts. The first to 16 wins.
1.2 - Teams
To be eligible for play in the Lo3 cup you must register on the website http://www.lo3cup.co.uk and you must have a team of 2 for 2on2, 3 for 3on3, 4 for 4on4 and 5 for 5on5.
1.3 – Lo3 cup Structure
The Lo3 cup is based on individual challenges taking place between teams. Teams must be available till the end of the cup.
1.4 - Forfeit Rules
Teams that have a high percentage of forfeit losses (“No shows”) and are judged to be degrading the quality of the cup may be removed at any time.
1.5 - Game Version
The version used for match play must be the latest version of Counter-Strike: Source that is available on Steam.

Back to top

2.0 - Scheduling
2.1 -Date and Times
You should have your team prepared to play on the date and time that matches are scheduled for. Teams are asked to give common courtesy to each others situations but are not required to.
2.2 - Match Comms
All match communication will be handled through the irc #lo3cup on quakenet. The use of personal E-mail, Instant Messaging, X-fire, or voice chat is not acceptable for exchanging server and match information, this should only be used as a last resort. The host team must PM the match server details (including password) at least 15 minutes before the match. Failure to post this information before the 15 minutes will give the visiting team the oppurtunity to use their server.
2.3 - Sides
The knife fight is always used to decide which team picks sides. It is not optional. If there are players still alive at the end of the round, the team with the most players alive wins. If there an even number of players left alive on each team, you restart and play knives again. The Terrorist that spawns with the bomb MUST drop it. Only knives can be used as a weapon on the knife round.
2.4 - Map List
Teams are to play the map that is set by Lo3 if this is not played then the match does not count. The map list will be on the site before the sign ups are open. You must make sure the maps are on the server and up to date.

Back to top

3.0 - Servers
3.1 - Server Config
Server config is available to download HERE
3.2 - Server Requirements
Matches must be played on servers running the most current version of Counter-Strike: Source and the associated maps. The match must be played on a dedicated server connected to at least a T1 connection. Listen servers are unacceptable.
VAC2 must be enabled and the server must be running the most up to date stable version of zBlock. sv_pure 2 must also be set on the server.
A server capable of handling up to 12 players is necessary for every match, which must be located within the UK. The server must be running in dedicated mode and following all of the necessary rules specified in the Server Config section. The server must be password protected. Please ensure the server's stability and capability to withstand 12 players before the match begins. In the event of excessive lag, another server may be chosen or the match may be re-scheduled.
All server modifications must be disabled.
3.3 - Server Choice
This is posted on irc or website which team is the home team. Whichever side is supplying the server is responsible for posting connection information in the match arrangement system prior to the start time of the match.
3.4 - Major Ping Discrepancy
In the event of a major ping discrepancy (+/- 50 ms average difference between teams), a third-party server can be tried. Otherwise, the best available server must be used, if no server can be found please consult an admin.
3.5 - Server Crashes
In the event of a server crash, the map will be restarted with the remaining rounds and score intact. If the server crashes more than two times the other team’s server should be used. If no such server is available and you can't agree to play on, an admin has to be notified right away to try and find a solution. If no solution can be found the team that provided the server may be forced to lose by forfeit.
3.6 – Dropped Players
If a player drops from play during the process of a match going live, the match is to be stalled until the player returns (within the regular limits mentioned under "failure to appear") at which point the match is restarted. Dropped players during live rounds are considered casualties of war. The match will continue and the team with the dropped player(s) will continue one or more players short until the dropped player returns or they find a substitute to join.
The Pausing in game is set to 5 minutes per team per side.
Abuse of this rule with the intent to ghost, drop weapons, rejoin after a death, etc., will not be tolerated. Penalties for this include the overturning of rounds and/or matches.
3.7 - Substitutions
At anytime during the match a player substitutions are allowed, but they are to join the right side and not sit in spectator. No substitution should ever result in a team having more than 5 players in the server at one given time. Substituted players must begin their x-ray immediately upon connecting to the server.
If a player is substituted in during the first half, the replacement MUST get the required screenshots immediately at the end of the first half. This will mean that there are two screenshot rounds at the half- one for the substituted player and another for the beginning of the second half. If a player is substituted in during the second half, the replacement MUST get the required screenshots at the end of the match. Opposing teams must allow for the extra screenshot round, or they may face unsportsmanlike conduct penalties and risk their ability to dispute that player.
The substituted player must not bring the teams out of the 50ms average ping discrepancy (see 3.4 - Major Ping Discrepancy) or rounds may be overturned.
Once a substitution has been made, both leaders need to get a new "status" or "rcon status" screenshot.
3.8 - SourceTV and IRC Scorebots
SourceTV and IRC Scorebots can be used if both teams agree. If SourceTV is used, the delay must be set to at least 120 seconds. If an IRC scorebot is used, no messagemode (chat) information may be broadcast.
Please post public SourceTV info on the irc (#lo3cup) for everyone's enjoyment. Please also add the SourceTV IP on thewebsite under “Team Management” > “Servers” and select “ScoureTV from the drop-down .

Back to top

4.0 Match rules
4.1 - Pre-Match
Each team should be ready to start the match at 15 minutes past schedule time at the latest. If a team does not have the required amount of members on the server and/or is not ready to start, the match can be considered a no-show.
Each team is allowed a dead round to sort out strategy for the current map. This round is also used to take screenshots of both sides' skins and to start their x-ray anti-cheat.
XAC is compulsory and if unable to be run you must clear it with a Lo3 admin and then POV will have to be done by the player and sent to the admin straight after the match.
4.2 - Net_Graph 3
Players are required to take multiple screenshots throughout the game, therefore net_graph 3 MUST be enabled at all times. This can be done by going to the console and typing "net_graph 3". Any information submitted to Lo3Cup Admins will require this setting to be enabled.
4.3 - Unsportsmanlike Conduct
Unsportsmanlike conduct during matches will not be tolerated by Lo3. If an admin is called in to resolve an issue regarding unsportsmanlike conduct the judgment/punishment will be swift, efficient and final. Sportsmanship issues will result in punishments (except in certain situations that merit further punishment) to be decided by the Head Admin.
Racist or sexist remarks will not be tolerated and may merit harsher penalties.
Simple, straight forward... Play nice.
No custom sprays of any kind are allowed from the moment of joining the server, especially those with pornographic or demeaning content. Players who use custom sprays may be punished according to the unsportsmanlike conduct rules. Tactical use of sprays (such as sprays that resemble an object of the game such as player models, gun models, bomb/grenade models, etc) is seen as exploiting and will be dealt with as other exploits. Since sprays do not always show in demos, you must take a screenshot of sprays if you intend to dispute. If you do not have a screenshot and spray does not show in the demo, your dispute will be thrown out.
Default sprays are legal.
4.4 - Screenshots
Before each half (and any subsequent OT halves), a screenshot round is required to help ensure fair play by both teams. Both teams need to peacefully meet at a location on the map to take the required screenshots. Each player is responsible for taking any number of screenshots which include at least one counter terrorist and terrorist model with a fully developed smoke grenade in the background. Also, the scoreboard (default key is "tab") and net_graph 3 (type "net_graph 3" in console) are both required to be enabled for each these screenshots.
Captains from both teams are required to take additional screenshots. Before the match starts, the hosting team's captain must take an "rcon status" screenshot (type "rcon status" in the console and take a screenshot of it) and the visiting captain must take a status screenshot (type "status" in the console and take a screenshot of it). Additionally, the captain on both teams must take end of half screenshots of the scoreboard.
All screenshots must be taken with the in game "jpeg" command (default key is "F5") and are required to be kept by all players for a minimum of two weeks.
Players who do not submit screenshots or submit altered screenshots when requested by Lo3 staff will be subject to the penalties outlined in Demo Requirements.
Screenshot Summary:
CT and T models with a developed smoke in the background (with the scoreboard enabled)
Console screenshot with status or rcon status (captain)
Scoreboard with final score from each half (captain)
ALL SCREENSHOTS MUST HAVE NET_GRAPH 3 ENABLED
4.5 - Demo Requirement
NOTE: SOURCETV DEMOS ARE NOT REPLACEMENTS FOR PLAYER DEMO'S.
Players are not required to take personal demo unless it is requested so by a admin. If demos are taken they are to be held for a minimum of 3 days after the match date. Demos are to be handed over to a Lo3 admin upon request, where they will be subject to review by Lo3 admins. Demos will not be requested unless you are accused of cheating and the accuser has ample proof that you are cheating. If you are unable to send us your demos when requested, you will be punished as decided by the platform manager whose decision is final.
If players are found in violation of any set rules they will be held accountable for those actions. Punishment for those actions may vary depending on the nature of the issue. Teams where the player competed on will not be subject to any punishment but this may also vary dependant on the severity of the issue.
-Commands:
record demofilename
stop
playdemo demofilename
Demos are saved in a similar directory with the file extension .dem:
\Steam\SteamApps\account_name\counter-strike source\cstrike
4.6 - Match Eligibility
Teams must be signed up by one hour before cup start time or these teams will be replaced to let another team in.
4.7 - Messaging
Only team leaders or captains are allowed to use public in-game messages (messagemode1 or mm1) within a game.
4.8 - Winning the Match
The team that first reaches 16 rounds is considered the winner of the match. If the score result is 15-15, then the match goes into overtime.
Since accurate score reporting affects the playoff seeding, teams incorrectly reporting scores will be punished according to the rules of unsportsmanlike conduct.
4.9 - Overtime
Overtime is a best 4 out of 6 rounds played. The home team chooses which side they would like to start. Three rounds are played and then the teams switch sides. The first team to 4 wins the match. Scores are reported for only the tie-breaking overtime (e.g. – first overtime is 3-3; second overtime is 3-3; third overtime is 4-2; score would be reported as 19-17).
4.10 - Exploits
The intentional use of map and/or game exploits to give your team an advantage during a match is prohibited. Uses of flaws in maps are illegal as determined by the cup admin. Any disputes regarding game play, exploits, cheating or tactics must be submitted via a dispute along with proof of the occurrence and a detailed description including the associated times. If this is not included, the dispute will be thrown out. All Counter-Strike: Source game play in Lo3 is to be perceived as tasteful and fair.
Exploiting the game is illegal and will be considered cheating if used in a match. Do not assume that the use of a bug or game engine flaw is legal. Contact the lead admin if you have any questions.
Boosting or "superman boosting" with any number of players is legal. It is not legal to boost if the map is being exploited by positioning players in locations not within the map. It is not legal to boost a player to the point where he/she remains within the map but is able to view areas not intended to be seen from that location. Smoke (or any other grenade) boosting is NOT legal and will be processed as an exploit.
Planting through the use of boosting is legal if it is possible for the opposing team to defuse with such boosting. If the opposing team does not have enough players to boost to the location of the bomb, this is still legal.
Sripts are considered illegal if they give a player an unfair advantage. An example of a script that does not give an unfair advantage is a buy script. An example of a script that does give an unfair advantage is a bunny-hop script. Any players found to use unfair scripting will be considered cheating.
The use of grenades over walls is legal.
4.11 - Bunnyhopping
Bunnyhopping is permitted during Lo3 matches.
DirectX level, or 'dxlevel' must be at least version 8.0. Other cvars will be added as and when we see fit, it is your responsibility to ensure that you are aware of the rules at all times. Ignorance is no excuse! :)
The cvar blocker zBlock must be installed on your server and be the most recent version. This must be used in ALL Lo3 CSS matches.
Non compliance with these rules may result in a forfeit loss.
4.12 - Spectators
Spectators are not allowed on match servers. Lo3 admins may be required to spectate and referee matches. Requests for a referee should be asked for as early as possible so arrangements can be made. There are no guarantees that an admin will be available to spectate a match, we will try however.
An Lo3 admin reserves the right to observe any Lo3 match without prior notification or approval. The admin's identity can be verified by validating their steam-id. Any attempt to impersonate an Lo3 admin member will result in a permanent site ban.

Back to top

5.0 – Players
5.1 - Steam ID's
ALL players must have a valid Steam ID number and must be displayed on the team page on the lo3cup.co.uk website.
5.2 – Player Info
All players must use the default player and weapon models/skins. The default hostages, bombs, grenades and all items must be the default ones. The same applies to sounds.
Custom Huds are allowed as in font, font color, font size, and hud arrangement. If at any time cup finds that something can be coded into a custom hud to give a player an ingame advantage, we will revert back to stock huds.
Players must use the default sprite files.
The in game variable r_drawviewmodel must be set to 1 (on).

Back to top

6.1 - Disputing
Whether you are disputing or being disputed, be prepared to produce all requested materials. Demos, server logs, player screenshots, status screenshots, and score screenshots may all be requested at the admin's discretion. To resolve disputes in a timely manner, once requested, all materials must be produced in under 48 hours (for matches rescheduled after default date, the deadline is reduced to 24 hours).
Cheating disputes must be accompanied by the specifics of the accusation. The disputing team needs to provide the following information:
* Who is suspected of cheating
* When did the events take place, i.e. Side, round, etc.
* What is the suspected cheat, e.g. wallhack, aimbot, etc.
Teams are encouraged to take the hour immediately after the match to review their own demos before filing a cheating dispute. Log the round number, side, and time that they believe the opponent was cheating and provide that information with the dispute. Cheating disputes without specifics may be thrown out.

Back to top

7.0 - General Cup Rules
7.1 - Server Crashes
In the event of a server crash, if both teams can agree upon the remaining time and score, the map will be restarted with the remaining time and score intact. If there is a dispute the entire map will be restarted. In the event that a team loses a player due to connectivity issues, the team may substitute the player immediately with someone from their roster. Substitute players brought in during match that are not eligible players will force an immediate forfeiture on the part of the team they were playing for.
7.2 - Punctuality
Teams are expected to be on the server and ready to play with the minimum number of players at the scheduled or agreed upon time. Any team that fails to be present with the minimum amount of players and ready to play on a server 15 minutes after the match start time will forfeit the match.
7.3 - Sportsmanship and Cheating
Un-sportsmanlike conduct during matches will not be tolerated by the Lo3. If an admin is called in to resolve an issue regarding un-sportsmanlike conduct the judgment/punishment will be swift, efficient and final. We here at the Lo3 suggest you conduct yourselves accordingly.
Racist or sexist remarks will not be tolerated.

Simple, straight forward... Play nice.

Match results or disputes must be told to the admin within 10 minutes of match end.
By reporting the results, teams waive their rights to protest (ultimately decided by Lo3 staff).
Failure to Appear
To compete in the match there is a minimum number of players needed to proceed with a match. Teams should have the minimum number of players on the appropriate server no later than 15 minutes after the scheduled match time. Failure to meet this requirement will result in an immediate forfeit against the non-compliant party. Both teams should be ready to play no later than 30 minutes from the scheduled match time (Unless agreed upon by both parties). Failure to agree to start the match at this time will result in forfeiture by the non-compliant party. An Lo3 admin should be contacted immediately for a ruling to be made.

Server Choice

****ANY SERVER USED MUST be running MATCH CFG to be considered eligible servers, unless agreed upon by both teams and approved by an admin.****

Complaints about servers are waived after a match is completed.

7.4 - HACKING
Lo3 has a ZERO tolerance policy regarding game hacking. This rule covers players who use code to manipulate a particular game for the purpose of gaining an unfair advantage over other teams and players. Wallhacks, speedhacks and aimbots are just examples of the types of cheats covered by this rule.

"Testing" or "Trying out" Hack Programs will not be accepted excuses. Simply put, "Do Not Install Hacks for any reason"

1. Hacker caught in Lo3 Match:
- forfeiture of the existing game
- Player Permanently banned from Lo3.
- Team will forfeit any match (for the present season) that the offending player was *proven to have played in.

Back to top

Many Thanks Management of Lo3 Servers and Cups.