Bowen
OP
Deputy Administrator
🛡️ x1
🔱
🥉
Clique CO
Oct 9, 2024 11:12 AM
Hey guys,
I wanted to post the same information here as what is on the discord for full visibility as recommended by a captain in the league, plus I agree, Champ has put a lot of work here and this site should be used to relay information as much as the discord :).
Base line rules have been adjusted to account for some attempts to find loopholes in the current format. Next season, all rules, not just base line rules, will be compressed and simplified...base line rules themselves will most likely reflect being unable to cross into them once you exit on either side...which might require some map tweaks.
Rules are listed below, changes in bold.
7.7 A player may only cross an enemy's base line for an angle or ammo. Squads that try to hide or waste time behind the enemy base lines <b>will be warned. If ignored, offending squad will have their location revealed to the opposing squad and base lines will be voided for engagement.</b> A player CANNOT fire any weapon when beyond the enemy's base line(unless voided see 7.6). If a player does fire, the player will be specced immediately and can be put in again at the Captain's request. If the player fires when beyond a base line a second time in a match, the player will be specced for the rest of the game. The player's team will also lose that player slot for 5 minutes.
<b>7.8 A player may not avoid death by crossing into either side's base lines. At the ref's discretion, offending players will be specced and the kill will be awarded to the opposing team's total.
Further attempts to avoid death by crossing into base lines will result in a loss of that player slot for 5 minutes</b>
S
SKCAB
⭐ x1
Oct 9, 2024 11:53 AM
There shouldn’t even be a warning in my opinion. If a player does go over them, spec them for five minutes. If they do it again, or another player on the same team does it, spec and award a kill. Simple as that. We’ve already seen the consequences from having to warn a player with Leak. By the time he received the warning the damage was already done.
Bowen
OP
Deputy Administrator
🛡️ x1
🔱
🥉
Clique CO
Oct 9, 2024 12:27 PM
SKCAB wrote:
There shouldn’t even be a warning in my opinion. If a player does go over them, spec them for five minutes. If they do it again, or another player on the same team does it, spec and award a kill. Simple as that. We’ve already seen the consequences from having to warn a player with Leak. By the t ...
Yep, actually that's already included in my thoughts for the rewrite. Someone goes into base lines on either side and will get specced immediately, and if they did it to avoid a death, the opposing team will get a kill. That way people don't just run into base lines to avoid dying :)
1st offense will be a spec, 2nd offense will be loss of a player slot for 5 minutes.
Edited Oct 9, 2024
L
Lunar Tick
🛡️ x1
Oct 9, 2024 6:30 PM
recalling a certain incident. Rule 7.7 seems to be a bit vague still. "If a player does fire, the player will be specced immediately and can be put in again at the Captain's request".. what if the offending player's captain request the unspecc Immediately? Right now that rule basically has 0 consequences.
Basically a whole team can go into the rape lines for a massacre, get specced in the event they were all seen by ref, then the captain can immediately ask for the whole team to be unspecc. And in the unlikely chance it was the weaker team that does this, they can STAY in specc until the end then ask to be put back in.
Joking aside, it feels like there ought to be a clause in there where if player fire, while in enemy rape line and those lines are not voided, they ought to be specced for the rest of the game or a very specific amount of... penalty minutes for a lack of a better term. And during this penalty period, no one is allowed to replace them, forcing a penalty situation like in Hockey for example. Or, perhaps forcing a permanent replacement for the rest of the game.
Champion
Webmaster
👑 x24
👑
Gentlemen CO
Oct 9, 2024 6:46 PM
Lunar Tick wrote:
recalling a certain incident. Rule 7.7 seems to be a bit vague still. "If a player does fire, the player will be specced immediately and can be put in again at the Captain's request".. what if the offending player's captain request the unspecc Immediately? Right now that rule basically has 0 conseq ...
wouldn't work because of this rule:
5.1 Each squad must show at least 8 players for a match at the minimum. Refer to rule 3.5. If at any point during a match a team has 0 players unspecced by their own actions, or rule violations, they will forfeit the match.
Bowen
OP
Deputy Administrator
🛡️ x1
🔱
🥉
Clique CO
Oct 9, 2024 6:52 PM
Lunar Tick wrote:
recalling a certain incident. Rule 7.7 seems to be a bit vague still. "If a player does fire, the player will be specced immediately and can be put in again at the Captain's request".. what if the offending player's captain request the unspecc Immediately? Right now that rule basically has 0 conseq ...
What champ said. Also, we'll call this sort of a band-aid for now to just close the loop so we're not messing with a ton during the season. But yea, next season loss of player slots will be a more immediate thing. Also, clarity from rule 7.8 currently, any squad that goes into base lines to avoid death will see the offending player get specced and a kill will be awarded to their opponent. This rule is legit going to be treated like goaltending in basketball. If it might have gotten a kill, it will give a kill.
L
Lunar Tick
🛡️ x1
Oct 9, 2024 7:53 PM
Bowen wrote:
What champ said. Also, we'll call this sort of a band-aid for now to just close the loop so we're not messing with a ton during the season. But yea, next season loss of player slots will be a more immediate thing. Also, clarity from rule 7.8 currently, any squad that goes into base lines to avoid ...
to quote rule 5.1 is missing my point Champ, what if it was just 7 of them that violated? The captain will remain outside and circumvent that 8 player unspecced condition? Plus rule 7.7 says the captain can ask for their unspecc (with no time specified here so it can be immediately). So it's home free for the offenders.
Here's just an edit of 7.7 as an example:
7.7 A player may only cross an enemy's base line for an angle or ammo. Squads that try to hide or waste time behind the enemy base lines will be warned. If ignored, offending squad will have their location revealed to the opposing squad and base lines will be voided for engagement. A player CANNOT fire any weapon when beyond the enemy's base line(unless voided see 7.6). If a player does fire, the player will be specced immediately <b>for 5 minutes. After 5 minutes the player may be put in again at the offending team captain's request or another player from the team can be request to replace the offending player. </b>If the player fires when beyond a base line a second time in a match, the player will be specced for the rest of the game. The player's team will also lose that player slot for 5 minutes.
m
Referee
⭐ x4
💎
Kays Krew 3
Oct 10, 2024 8:21 PM
Remove the lines, take yer beatin
D
Dracolich
Commentator
🥉
Clique
Oct 11, 2024 8:43 AM
Aside from the rule(s)...the base lines for Titan need to be pushed back a bit.
D
Daddy
Commentator
💎 x8
Kays Krew 3 CO
Oct 12, 2024 2:03 PM
m wrote:
Remove the lines, take yer beatin
Remove the lines. How can you expect a ref to keep an eye on 8 players when fighting next to the base? Make the rules human proof.
As long as you allow 70% of all active rings on one squad people will find a way to be desperate enough to find any loop hole.
Backs idea of a one way trench is better than not allowing a team to enter their own base, if a ref isn’t paying attention. Better for a team to die on a trench wall than find themselves down a player. Remove the chance to play down a man.
D
Daddy
Commentator
💎 x8
Kays Krew 3 CO
Oct 12, 2024 2:15 PM
Any rule in place that results in a team playing down a man outside of a disconnect or lag needs some rework.