Topic Rating
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
SPL 2009 Ruleset
Author Message
AC Administrator


Posts: 42
Joined: May 2014
Post: #1
SPL 2009 Ruleset
For reference:


1.1 - The number of clans to participate in SPL is determined by SPL. 

1.2 - Clans will be selected in the manner as seen fit by SPL - whether all participating clans will be admitted straight away, or a tournament held for the final spot(s) - this is the prerogative of the league. 

1.3 - Clans will be chosen by the SPL governing body, whether by consensus or by majority vote in the case of disputes. The primary criteria is skill, however, stability will also be considered. 

1.4 - The league will consist of a regular season, and a post-season (playoffs). The season structure will be predicated on how many clans are admitted into the league, and thus in turn the post-season will be predicated on this. Specifications for season and post-season structure and rules will be specified at the time of clan admissions. 


(to be determined; see 1.4) 


2.1 - Clans are expected to assemble and be organized in the lobby 5 or 10 minutes prior to the scheduled gametime. Before the game starts, both clans must designate a captain. This will be the player who PMs the ref for the password, and refs will now treat this player and ONLY this player as the captain unless he exits the server. See rule 2.2. 

2.2 - Refs should ask for both teams to have their captain PM him for the password 5 minutes before the scheduled gametime. At this time, the captain may and should designate a co-captain to act as the captain in the case that he pings out or has to leave. 

2.3 If the ref starts this process either too early or too late, clans are expected to carry out the game under full authority of the ref and the timeframe, and you may file a grievance with the league afterward. 

2.3 - The captain is responsible for a) handing out the password to his team. b) saying "yes" or "no" when the ref asks if the teams are ready. c) being the team's authority with regard to substitutions. only the captain may request a substitution, or order a substitution for his team. c) calling a timeout for his team. 

2.4 - If for any reason a clan is having an internal argument over which sub wants to come in, or a player refusing to sub out even if asked to by the ref or captain, the ref may grant the captain's request to remove a player from the game. 

2.5 - After the password has been handed out, because of rule 2.2, this gives both clans 5 minutes to get their players in the server and ready to go. At the time of the scheduled gametime, refs will ask if both clans are ready. There will be a 5 minute grace period, for both clans, should EITHER clan opt to take it, for any reason. Even if both clans request grace, it only lasts for 5 minutes. 

2.6 - At 5 minutes past the scheduled gametime, if one or both clans elected to use grace, the ref will now again ask if both teams are ready. By this point clans are expected to have enough players in the game to play, and whatever players they were waiting for to have arrived. Any clan that insists they need more time, risks forfeit. 

2.7* - Refs will use their discretion based on how tight things are running on the league staff's end, and how much the opposing clan is insistent on starting the game or whether they don't mind waiting, with regard to giving a few more minutes of leeway. However, *except for in the event of spark crashing, or the server crashing*, games *must* be started by 10 minutes after the scheduled gametime. Anything more than that is unacceptable. If clans do not have enough players, then the ref will call forfeit. If both clans do not have enough players, the ref will call double-forfeit. 


3.1 - Games will be played 4on4, no more or no less, in the map SPL09GO (401.9). Each clan is allowed to have 2 subs, with an unlimited number of substitutions. ONLY the players in the server at the time of the game's start are eligible to play or substitute. Any referee or staff member that is present in or enters the game for any reason, may NOT speak for their clan or act as a sub for their clan. A clan may not have any players enter the server who were not present at the time of the game's start. 

3.2 - Substitutions must ONLY occur on death or ping-out. When a player dies, he must switch to spectator before the new player may switch in. When a player pings out, it must say "... has left the server" before the new player may switch in. 

3.3** - ANY clan or player deemed by SPL to be intentionally faking or inducing ping-outs to manually time a substitution instead of waiting for a player's death, risks severe penalty such as: player suspension, game forfeiture, clan suspension, clan expulsion. 

3.4 - Games will last for up to 30 minutes(+), and will end if a team achieves 3 caps OR at the end of all flag attempts after time runs out. 

3.5 - If the game is tied at the end of 30 minutes, there will be a continuous 10 minute overtime. In overtime, the game is sudden death. 

3.6 - If a flag run is in play at the end of overtime, the game will continue for the duration of the flag run. After flags are returned to their holders, the ref must declare the game over. Clans may not intentionally avoid ending a flag run for the purpose of perpetuating the game, or they risk severe penalty. Also see rule 3.9 

3.7 - If the game is a 1-cap margin, and the losing team has a flag-run in play at the end of regulation, the game will continue for the duration of this flag run. An active flag run is defined by the enemy team's flag not being in a holder, EVEN IF there are no apparent players around it. So, refs must wait for the winning team to return their flag to holder. Again, the winning team may not intentionally avoid doing this simply for the sake of trying to complete another one of their flag runs or perpetuating the game for any reason, or they risk penalty. Also see rule 3.9 

3.8 - If the losing team ties the game in the above scenario, overtime will begin upon the flag cap, with no interruption or pause. Note that the time required to finish the flag run during regulation does NOT count as "overtime-time". 

3.9 - With regard to flags being out of holders, and returning flags to holder, the following specifications apply. NOTE that these three clauses MUST be judged and understood all togther, in context of each other. 

-A clan may not purposefully neglect to return an active flag to their team's flag holder, either for sake of padding stats or to try and gain an advantage by leaving the flag in a specific position in their base.

-The standard reasons for a clan or player's decision to not return the flag right away would be if an enemy is in or approaching their base, or if one of their teammates is making or is about to make a flag attempt. 

-Refs are expected to monitor the situation and give a lot of leeway for the above mentioned examples, and use their discretion to determine if a clan is purposefully neglecting to return a flag for some advantage or abuse. In this case, the offending clan risks penalty including the possibility of match forfeit. 

3.10 - Each clan is allowed 1 timeout per game. Timeouts can only be taken after a flag cap occurs. A captain must say "timeout" following the flag cap, in which case the ref will lock the game for 120 seconds. ONLY the captain may call a timeout - anyone else saying this must be disregarded. During timeouts, clans may perform substitutions. After 90 seconds have passed, the ref should let clans know that the game will resume in 30 seconds. After the timeout is over, the /start command will be used to resume play. The 2 minutes of timeout-time is SEPARATE from the gametime. 


4.1 - Clans are expected to stay in the server until the ref has all the stats he needs and tells you that you may go. Any clan or player that does not do this will receive 0 for any stat that was not recorded by the ref. 

4.2 - SPL's policy with regard to sportsmanship and in-game behavior is the following. 

4.3 - Anything you are not allowed to say in spark generically, you are not allowed to say in a league game. Players who violate this risk penalty. 

4.4 - Any kind of moderate trash talk that would be accepted in a normal public GO game, is acceptable. To whatever extent a clan wishes to damage its credibility with other clans is its own prerogative. Given that any clan or player has the ability to mute the opposing team's players, SPL's view is that any chatter from a clan can only serve to hurt them by taking their focus off of the game, and that anything excessive or bothersome to an opposing clan simply renders the opposing clan expected to mute the offenders. 

4.5 - If you know a clan talks trash, or rather, if you don't know that they don't talk trash, and it is a problem for you, then you are advised to mute them at the start of the game. 

4.6 - The only communication that is mandatory - and it is indeed mandatory - is between an individual clan and the ref(s). 

4.7 - Spectators MUST REMAIN SILENT AT ALL TIMES except in a player's response to a team's captain asking if they are ready/able to sub. Any player who violates this must be warned immediately by the ref, and if he violates this again the ref must eject him from the server for the remainder of the match. 

4.8 - Any player from either clan who is asked to leave the server by the ref, MUST DO SO. If it is a wrongful request, a grievance with the league may be filed afterward. 

4.9 - The same goes for journalists or broadcasters - they must not talk out of team chat. 

4.10 - Even spectator chat must be kept in check, since chat flooding will hinder the ability of the ref(s) to communicate with the clans/players. It is the ref's discretion as to whether someone is being excessive with their chat, and all players must adhere to the ref's requests or demands to minimize or eliminate their chatting. 


5.1 - After the game, the ref(s) MAY OR MAY NOT choose an MVP. There is a new system for MVP's and this is how it will work: at the end of a game, IF there is a player who stands out as having played a notch above everyone else in the game, he will be awarded an MVP for that game. If there is no one who stood out, no MVP award will be given. Further, the ref(s) will not come to an impulsive decision and announce this in the server after a game, but will think about it for 5 minutes and mark it on the scoresheet that they submit. 

5.2 - Refs will record points, frags, deaths, frag to death ratio, flag attempts, and flag caps. These stats will also be recorded for individuals as well as the teams themselves. 

5.3 - If a flag attempt is started, and a player drops, and a new player picks it up, this will be recorded as a separate flag attempt for each player, but only 1 flag attempt for the team. If the flag is returned, however, the next picking up of the flag will be a new flag attempt for the team. 

5.4 - Refs will record +/- statistic. Any time a team caps, the players on the capping team get +1, and the players on the opposing team get -1. Through a series of games and caps, players will have a + score or a - score that will be kept track of. 

5.5 - At the end of the regular season, SPL will give out numerous awards to be announced later. 


6.1 - Clans may have an active league roster of up to 30 people. Only these 30 people, under the precisely listed aliases, are eligible for league play. Each week there will be a roster update thread in which clans may post roster changes. Clans can remove or add players or change a listed alias. Roster changes, in particular alias changes, are to be kept at a reasonable minimum. Individual players may have up to 3 alias changes per season. An example of when you will need to do this is if an alias gets banned or is no longer accessible to you, so, use an alias change at your own risk. Any clan deemed by SPL to be abusing the lack of limit on roster updates purely for the sake of antics risks having their roster frozen for that week or longer. 

6.2 - At some point in the season, and certainly before the post-season, rosters will be frozen, after which no additions may be had. 

6.3 - SPL's policy with regard to smurfing: 

Smurfing of *any* nature is absolutely prohibited. This includes playing for more than one clan, players playing under more than one alias, playing on someone else's alias, the switching of aliases between established identities, or any action with regard to deceit or multitude of identity. SPL will review any incidents or accusations of smurfing on a case-by-case basis. Also, even though refs should check to make sure all players in game are aliases listed on the clan roster, clans are also accountable for their players playing on the correct names. 

-If a player is in a clan, which is not participating in SPL, wants to join and play with an SPL clan, he may do so if he is up front about it and both parties are aware of and ok with it. The player must have officially left the former clan on the spark clan website. The main points are that A) you must not be on two different clan rosters B) you must not be attempting to perpetrate deceit by establishing multiple active and league-playable aliases. 

6.4 - SPL's policy with regard to cheating: 

Cheating is prohibited, and SPL classifies cheating under two categories - intentional game-altering behavior, and non-intentional game altering. 

Game-altering behavior includes but is not limited to: extreme lag, constant spikes, a series of spikes or a prominent spike during a critical play, or godmode-like behavior (damage immunity). 

Any player or clan found to be exhibiting game-altering behavior is subject to protest. 

SPL will review accusations of game-altering behavior on a case-by-case basis. The only difference between intentional and non-intentional game-altering behavior is, obviously, if the league has sufficient reason to believe a player or clan (or both) had intent behind the exhibited behavior. 

*Sufficient reason can exist without concrete proof*. Things such as behavior, patterns, circumstantial evidence, player credibility, testimony as to the nature of the occurences, etc., will all be examined and the league will decide whether or not there is enough reasonable doubt as to A) whether signfiicant game-altering behavior in fact occured B) whether there is strong enough likelihood that there was intent behind it. 

6.5 - If a player is exhibiting any kind of game-altering behavior, he is expected to sub out immediately upon death. One of the refs should notice it and ask the player to sub out on death, and if not the opposing clan may urge the ref(s) to observe said player and request he sub-out. A clan's captain is also expected to urge his teammate to sub out if he starts spiking or exhibiting game-altering behavior, because his clan will be held accountable for this player's game-altering behavior, and clans are expected to have any players sub-out if the majority of other players in game including the refs notice this (sometimes a player is smooth on his own screen, but everyone else sees them spiking). 

6.6 - SPL reserves the right to modify these rules if there is revealed to be a flaw or a differently desired policy on an issue. Obviously, clans will be judged based on the rules as they exist at the time of their actions. 

6.7 - SPL reserves the right to take whatever action necessary to preserve the integrity of the league. By participating in this league, you agree to adhere to all rules and suffer whatever consequences deemed appropriate should your clan or a player in your clan violate the rules. 

6.8 - Generally, what the referee says goes. You may politely correct a ref if he is not following rules or procedure, but ultimately he is the authority of the game and must be obeyed; grievance may be filed afterward. 

6.9 - In the event of a protest, submit your case via private message to me (Fordus) to be reviewed by the board of representatives. All decisions are majority vote/consensus after careful and sufficient discussion and argument. If a case is strong, the player/clan will be contacted and have the opportunity to give a defense/counter-case. By participating in SPL, you agree to abide by whatever decision the board comes to. 

6.10 - In the event of a server crash, the following principles govern how to proceed: 

-The game will restart/resume with whatever amount of time was remaining. The score will be as it was at the time of the crash. 

-If there was a flag run in progress, but the other team had a possibility of stopping the flag run, regardless of how unlikely, the flag run is considered dead. An example would be if the enemy team had a player in front who had a chance of killing or delaying the flagger for his team to arrive and possibly recover the flag. 

-If there was a flag run in progress that was a virtual inevitability, i.e. both flags were in or coming into base and no enemies were close enough to even have a chance to make the flagger drop, and it would've 99.9999% been a successful flag run had the server not crashed...then this flag cap will be counted. 

-In the event of a flag run being in progress at the time of a server crash, clans may protest the game either to get the cap counted, not counted, or have the entire game replayed, and the board will make a decision. 

-The reason the flag run is to be counted in the aforementioned scenario is because this might affect things such as overtime, extending play if a flag attempt is in progress and the game is a 1 cap margin, etc. If it was a near-certain cap, the safe thing to do is to play the game assuming the cap counted (since in all likelihood the ruling will end up being that the cap was indeed achieved) so that in the event of a tied or 1-cap margin game, the clan does not get robbed of the opportunity for OT or for play extending while a flag is in play.
08-23-2019, 02:57 PM
Find Quote

Forum Jump:
Options +

Users browsing this thread: 1 Guest(s)

About Critical Headquarters

Armor Critical is a top down multiplayer PvP shooter. Armor Critical is and has always been 100% free..

© Critical Headquarters - 2021