Staff
| The DGL team. For any questions or problems contact these people, either on IRC #dystopia-league @ gamesurge, or on the forums. |
| Admin | |
| .obj | Head admin. Responsible for running the league, enforcing the ladder rules and more. |
| Taara | US admin |
| Whiteknight | US Admin |
| Public | |
| Warsprite | Dystopia Team liason, public relations |
| ocun | DGL public relations, website |
| Server | |
| Dredhorse | Hosting of the official DGL Dystopia server (eu). |
| dirker | Web server hosting, technical support |
General
| Rules that apply to all divisions. |
| Cheating | |
| Cheat-1 | Any cheats, including but not limited to 3rd party programs, editing of protected game files to exploit holes, or the exploitation of any bugs (see below) is regarded as illegal. |
| Cheat-2 | Use of cheats or exploits will result in the involved player(s) being immediately banned from the league once a decision has been made concerning the matter. Resolution may involve more than one administrator and all decisions are final. |
| Cheat-3 | If a player is found using cheats all previous clan matches in which that player played are null-and-void. |
| Cheat-4 | Use of command scripts is not considered cheating as long as they do not exploit the game. Scripts are legal. If you are unsure what is legal or not, consult an administrator. |
| Cheat-5 | Any map exploits used (such as traveling to parts of maps that are not meant to be traveled to; the use of weapons, implants or any other qualities that are not designed in-game for a particular class) are illegal. |
| Cheat-6 | Any action or exploit that hinders game play can and will be considered illegal pending the decision of the administrator(s) assigned to the matter. |
| Cheat-7 | Abnormal situations in both the game and map, like boosting (allowing a player to climb on you) and use of furniture (to block, etc) are legal. |
| Cheat-8 | For any extenuating circumstances and further decisions, an administrator will be consulted. |
| Comms | |
| Comm-1 | All forms of team-only communication, including message mode 2, vox communications (not including globals), in-server voice communication and all third-party communication programs such as IRC, Ventrilo or TeamSpeak, are unregulated. |
| Comm-2 | Players are allowed to use message mode 1 (MM1) only before the first, and after the last minute of a match. Between these times, only the team leader may use MM1. |
| Comm-3 | Spamming or excessive taunting may lead to administrator action. |
| Comm-4 | Messages will be limited to comments that reflect good sportsmanship and/or the conveyance of necessary information. |
| Comm-5 | No one is allowed to spectate at any given time with the exception of league administrators assigned to the match. Others may be allowed to spectate as approved by an administrator on a case-by-case basis. |
| Conduct | |
| Con-1 | All members must maintain respect for each admin or fellow competing member, in-game and out. Openly causing another member of the league unnecessary grief can lead to a suspension from the league for an amount of time deemed fit by an administrator. |
| Con-2 | A team/player is perfectly welcome to disagree with any ruling by the league administrators, however, the league administrators descision will be considered final. |
| Con-3 | Rules are subject to change at any time. Therefore it is the duty of the team leaders and organizers to keep their respective teams informed concerning an updates to the rules listing. |
| Disputes | |
| Disp-1 | Disputes will be resolved by one or more neutral league administrators. Disputes are to be reported by team leaders only and within 24 hours of the match in question. Evidence must be presented and available for the league administrators to resolve the issue. No dispute submittal will be honored without the proper proof to substantiate it. |
| Disp-2 | Screenshots and demo evidence will by expected immediately by league administrators, although 24 hours may be given in extreme cases. In the event that server logs are required, 24 hours will be given for the presentation of those requested logs. |
| Disp-3 | Decisions made by league administrators are final. |
| Player | |
| Pl-1 | Players are advised to record a demo of their play during each match that they play. In case of disputes, demo's will be a primary source of information - throwing out accusations without demo's or other proof to back them is highly discouraged. |
| Pl-2 | If a SourceTV proxy is recording the match, individual players do not need to record demos. This demo is to be made public on the Battle Hub forums. |
| Pl-3 | It is the responsibility of each individual player in the league to be aware of the league rules as posted. Claiming ignorance of the rules will not be accepted as an excuse for a violation. |
| Pl-4 | Each member must supply his correct STEAMID in his profile. |
| Season winner | |
| Seas-1 | The duration of a running season is stated in the description of a division.
A season is won by the team with the most played matches on rank 1 when the season is closed. In other words, assuming that all teams play an equal amount of matches a week, this is the team that was the longest on rank 1. At the end of a season stats are gathered and the winner is announced on the awards page. |
Server configs
| Server settings, per division. |
| All divisions | |
| Serv-1 | Any variable not specified in the official config must be at the default setting. |
| Global 5vs5 | |
| Serv-2 | All servers used for a match will be set to the following configuration:
sv_pure 1; sv_cheats 0; mp_stopwatch 1; mp_startdelay 15; mp_timelimit 20; mp_rounds 2; mp_friendlyfire 1; mp_autoteambalance 0; mp_punishvotes 0; mp_chattime 45; tv_allow_camera_man 0; tv_delay 30; sv_turbophysics 0; sv_maxspeed 320; sv_maxcmdrate 100; sv_mincmdrate 30; sv_maxupdaterate 100; sv_minupdaterate 30; sv_client_cmdrate_difference 20; sv_gravity 600; sv_friction 4; sv_accelerate 10; sv_airaccelerate 10; sv_minrate 10000; sv_maxrate 0; |
| Phistball | |
| Serv-3 | All servers used for a phistball match will be set to the following configuration:
mp_stopwatch 0 mp_startdelay 15 mp_timelimit 10 mp_rounds 2 mp_friendlyfire 1 mp_autoteambalance 0 |
Matches
| Everything concerning challenges and matches. |
| Challenge | |
| Chal-1 | Once a challenge has been made, teams have 8 days to play the match. Failing to do so will result in a double forfeit forced by an admin. Some flexibility may be expected on special ocasions. |
| Chal-2 | Teams are allowed to reschedule a match until 8 days after the challenge was made. |
| Chal-3 | The winning team will report the outcome of the match.
In the event of a tie, the challenging team (attacker) will report the match as a draw. |
| Chal-4 | Match results must be reported by no later than 23:59 UTC the day following the match. |
| Forfeit | |
| FF-1 | Any team that presents 3 or more consecutive forfeits will have to leave their division. |
| Match | |
| Mat-1 | A forfeit will be recorded for the team that does not appear and are ready to play within 30 minutes of the scheduled start time. |
| Mat-2 | The challenged team (defender) will choose the side which they wish to start. |
| Mat-3 | If a player from a clan uses means to restart a map once the match has started, that offending clan forfeits. The only exception will be if both teams agree that the server performance is unsatisfactory and the restart of the server is necessary. In the event that server performance cannot be restored to a satisfactory level, an alternate server may be used within reasonable time. Both teams must agree upon this condition prior to taking contingency action. |
| Mat-4 | It is permissible for matches to be broadcast via SourceTV. SourceTV must be set with a minimum delay of 90 seconds and a maximum delay of 2:30 (two minutes and thirty seconds). |
| Mat-5 | VAC (Valve Anti-Cheat) measure, while advised, is not required for a server hosting match play. VAC, if used, is to be set to "Alert" and not ban any player found to have raised that alert. The player(s) in question will then submit their demos and evidence for review by league administrators to determine whether it was a valid detection. Review will take place by no less than three league administrators and a conclusive decision will be brought forth to two senior league administrators for final analysis. |
| Mat-6 | In the event that the server which the match is played may crash, the game will be continued once the server is restored. The half in progress will be reset and the game will continue from the beginning of that half. In the event of a second crash, a new and acceptable server must be chosen. |
| Mat-7 | All players must play with their listed STEAMIDs from the official league roster. |
| Mat-8 | All players must play with their listed name and clan tag from the official league roster. |
| Mat-9 | A player may only play for the team for which they are registered with league. |
Rosters
| Rules concerning team rosters. |
| Ingame | |
| Ing-1 | Each team must have a minimum 4 players to begin a match. It is suggested that a team have one or more backups outside of the server ready to enter in the case of any circumstances where there are not 5 players. |
| Ing-2 | If a team does not present the minimum of 4 players (3 for phistball) to begin a match, that team forfeits the match. |
| Ing-3 | In the event that a team loses a player or players once the match begins, a legal substitute may enter to replace the dropped player to bring the team total to the maximum of 5 players (3 for phistball). A legal replacement is a player listed on the league roster for that team. |
| Roster | |
| Ros-1 | Teams are expected to maintain at least 6 players on their respective league rosters. |
| Ros-2 | The team leader or team scheduler must make sure all its team members on the league roster have supplied the correct STEAMID. |
| Ros-3 | Players are discouraged from "team-hopping" and any suspected of such can be brought under review and suspended from the league indefinitely. |
| Ros-4 | A player may only register for play with one team per division, but may administer more than one team per division as a pure admin.
A player marked as 'admin' on the roster, can both admin and play for the team. A player marked as 'pure_admin' on the roster, can admin the team but may not play in matches. |
| Ros-5 | No team may carry more than 16 players at any time on their league roster. |
| Ros-6 | When a team has an upcoming challenge any player that joins the team one or more days after, may not play in this upcoming challenge. New members are only allowed to play in challenges that were placed on the same day or after they joined the team.
The only exception is when a team is new to a division and playing its first match. |
Scoring, 5vs5 obj gametype
| Scoring for Dystopia 5vs5. |
| Score | |
| [1] | The team that completed the most objectives by the end of the game, wins |
| [2] | If both teams captured the same objectives, the team that captured the last objective the fastest, wins. |
| [3] | The only objectives that count, are the ones that a team possesses by the end of the round.
Example: Vaccine, Team A vs Team B. ---round 1--- Team A captures the docks at 5 mins. Team A then captures objective 2, at 10 mins. Team B recaptures objective 2 at 12 minutes. ---round 2--- Team B captures the docks at 2 mins. => Team A and B had the same amount of objectives at the end of the game, but team B captured faster => Team B wins |
| [4] | Objectives that involve starting a timer do not count (unless the timer is successfully completed)
Example: -starting the rocket launch sequence on silo does not count as an objective |
| [5] | When neither team captures any objectives, the match is to be reported as a draw. |
Scoring, Phistball
