TWL Season 6 Rules

[ZeUs!!]

OMG, there had better be a pause for the BWC.

[wadi]

10.21 If a game ends by result of a forfeit, the losing team will be given a score of 0 points for and 100,000 against, and the winning squad will receive a score of 100,000 points for and 20,000 points against. Squads will be allowed to have a total of 2 forfeits per season. If that amount is exceeded, the squad will be removed from participation in their respective league.

I'd suggest 120k-20k for a forfeit win as basing points have inflated since last season. This leaves room both at the bottom and top for truely spectacular, but is better than shafting the winner with a bare 100k.

[Louis XV]

Why not just leave it at 100k-20k, then at the end of the season calculate the average winning score, and adjust the forfeit score appropriately? Point differences in TWL-B don't matter until the end of the season, to break W-L ties, right?

[wadi]

That could also work, but people are going to want a mid-season gauge to rank tied squads, and the 100k is pretty low by today's basing standards.

[Epinephrine]

Hi just a small rule update:
====================

8.12 If a participating player is, in the view of the ref, excessively jittery, blinking in
and out, or otherwise showing signs of lagging that might be the result of an attempt to cheat, the ref may force the player to be subbed. Such a sub should be treated as outlined above depending on the league division. Suspicion of cheating will be followed up and the consequences will be harsh.


Has been changed to:
=====================
8.12 If a participating player is, in the view of the ref, excessively jittery, blinking in
and out, or otherwise showing signs of lagging that might be the result of an attempt to cheat the person will be immediately reported to the upper staff. Further action may be taken in game by upper staff. Suspicion of cheating will be followed up and the consequences will be harsh.



Yes that's right. Refs no longer have the right to spec laggers, although the case may be forwarded to smod+ which can deal with it on a case by case basis. We hope to have tougher lag limits in TWL to enforce stricter lag rules.

-Epi

[THE PUSHER]

Rules Update

The following is a small update to the game rules. They are being revised due to TWBot control over many of the TWL features.

Old Rule:

8.08 Game time roster eligibility will be verified by the game referee and the TWBots.

8.09 All squads must choose a private frequency from which to play from. Only squad members are allowed on the chosen frequency, and referees may join that frequency if the need arises. Squad members who are not playing and wish to join their teams private frequency, can do so by private messaging the attending TWBot with ?!squadfreq?.


Adjusted and Current TWL Rule

8.08 Game time roster eligibility will be verified by the game referee and the TWBots. All squad members must be squadjoined to the squad they are participating with in TWL during league games.

8.09 All squads will be placed on a frequency by the TWBot once the game has begun. Only squad members are allowed on the chosen frequency, and referees may join that frequency if the need arises. Squad members who are not playing and wish to join their teams private frequency, can do so by private messaging the attending TWBot with !myfreq.


This should clear up any confusion there was over these matters.

-PUSH

[Evul Fly]

10.12 All players will start in the referee assigned safety zones. If a player refuses to leave the safety zone after the game starts, the player will be given a warning and a 60 second time limit to leave the safe zone. If the player continues refusal after the 60 second time period, that player will be specced and given a score of 0 points and may be substituted if one is available.

however:

Warp points have been fixed for all 3 leagues, and players will be warped out of the safe zones automatically if they sit there. The TWLB squad captains decided to use the autowarp into the flagroom ear for base games. This should prove to be quite interesting.

[Epinephrine]

Rule change:

Rule 5.01 has been changed so that you can now have 35 players on roster just likd TWD. Since we never got this working on the website, and it's already roster lock, it's time to change this rule


OLD RULE
------------
5.01 All registered Trench Wars League squads may only have a minimum of 10 and a maximum of 30 registered members. Players may only have one name on their squad's roster, and if they have more they may be found in violation of doublesquadding rules (see section III).
------------

NEW RULE
-------------
5.01 All registered Trench Wars League squads may only have a minimum of 10 and a maximum of 35 registered members. Players may only have one name on their squad's roster, and if they have more they may be found in violation of doublesquadding rules (see section III).
-------------

-Epi

[Sufficient]

Next season will it go back down to 30? And if so, can you make TWD's roster limit to 30? To me 30 seems more than enough.

[Bosshawk]

Originally posted by Sufficient
Next season will it go back down to 30? And if so, can you make TWD's roster limit to 30? To me 30 seems more than enough.

it almost seems.... Sufficient!

[Epinephrine]

The rules have been updated again. References to GMT have been taken out. Please note that all times are in EST, and that EST changes by 1 hour during daylight savings time.

Also the 48 hour rule has been changed to 60 hours. If one squad puts in a proposed time and the second squad does not respond within 60 hours (assuming that no other times were inputted) then the time that the first squad suggested will be used.

Finally there is a limit of 4 base games per hour. This is because of host limitations.

Updated rules:


NEW RULES
---------------
7.02 There will be a total of five (5) available games per time slot. If a time slot is filled,
another must be negotiated and chosen. There is a maximum of 4 base games allowed per slot.

7.07 If the second Captain replies to an offered time more than 60 hours after the initial
proposal, the first Captain is automatically rewarded the proposed time. This is assuming there were no times proposed by the second captain at all.

7.08 If the second Captain replies to the proposed time within the 60 hour time period, but no time was agreed to, the League Operator will choose a time slot in between the two suggested times. If the squads agree to times on different days, the League Operators will chose a time based on rule 7.05.





OLD RULES
--------------
7.02 There will be a total of five (5) available games per time slot. If a time slot is filled,
another must be negotiated and chosen.

7.07 If the second Captain replies to an offered time more than 48 hours after the initial
proposal, the first Captain is automatically rewarded the proposed time.

7.08 If the second Captain replies to the proposed time within the 48 hour time period, but no time was agreed to, the League Operator will choose a time slot in between the two suggested times. If the squads agree to times on different days, the League Operators will chose a time based on rule 7.05.



-Epi

[Malladrin]

I'm writing this becasue of what happened in the match whiterabbits vs No Surrender in TWLB round 5.
Host: Cpt.Guano<ER>

This is what happened:

According to Magoo they sent in a 9 man roster. Guano must have added the first 8 or something, either way he didn't notice it. Guano pm's the captains the lineups before he starts the game and asks them to confirm it. NS and wr confirm the lineups and the game starts.

10 min into the game...someone in NS messages Guano about NS's wrong lineup, they've realized they've only got one shark in.

Guano thinks he made a mistake, and with no shipchanges allowed by the bot, Guano restarts the game after 15 min(!) of play. That's half the match!!

Now, I don't know which rule I should press this issue on because there ain't noone good to this situation. However I don't think you should be allowed take this long before you realize something is wrong and then expect the host to make it "right". After all, Guano did send them the line-up he gave the bot and NS confirmed it was the right one. Something like rule 10.3 should be implemented for these kind of things. I guess you didn't think anyone would be this stupid when you made the rules.

Epinephrine's reply to why a 5 min deadline on rule 10.3:

5 minutes as a deadline for people who arrive late because if a squad isn't going to bother showing players to the right time, that's their penalty.

Edit: I don't know what good it would do to apply for this thing, since the scores from the first match haven't been saved. The best thing we would get is a rematch and we already have had too many rematches of this match. (IMO) This leads me to the question why the scores before a restart of a game isn't saved. The way it is now we can't restart the game from the point it was cancelled, which is very debatable when restarts are made on these kind of wierd grounds.

[Jason]

Yeah, Guano really screwed the pooch on this one. WR was up 90k-2.5k before the restart. We were well on our way to a near 200k game.

[Depili]

Well I think that it would not have been a nice nor honest victory, but restarting after the game had been going for so long for something like that...

[Malladrin]

I just want to add something else to this story. If the host had been able to shipchange the player with the wrong ship this match wouldn't have been restarted in the first place.

So, add the possibility for hosts to shipchange people to the bot for instances like this. (The ability and legacy of shipchanges don't have to be changed in the rules though)