Announcement

Collapse
No announcement yet.

TWL Rules: revisted

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • TWL Rules: revisted

    Okay I revised Crome's rules and compiled them into one master set, and while there were some good ideas in the rules, I think overall they were poorly written =/. He would switch off between second and third person a lot, and the rules in all three leagues were written as though if I double squadded in TWLJ then I would be breaking a different rule with a different punishment than in TWLD etc.

    It's late because I spent a few hours longer than I had originally planned, so please forgive any glaring spelling or numbering errors.

    Crome these revised rules are for you, but when I wrote them I also added a few new ideas that you can simply disregard if you please, I just hope you add some clarity to the current set of rules and some order to the whole thing =)

    Anyways lets see if I can post this bad boy, or if I need to link to the notepad file...

    1.0 League Rules
    ^^^^^^^^^^^^^^^^^^
    1.01 TWL Games will be refereed by a bot and an appointed Referee. Always obey the Referee. If players have any complaints about the bot or referees, they should contact the Lead TWL Operator.

    1.02 In a case of an unpredictable server crash, router failure etc. that has any impact on the game, the match will be replayed the following week.

    2.0 Scheduling Rules
    ^^^^^^^^^^^^^^^^^^^^^^
    2.01 TWL games will be on Sunday and Saturday at any available time: 1:00pm EST- 6:00pm EST on both days. There is 1 scheduling system for all 3 subdivisions of TWL.

    2.02 All squad captains will email their TWL Op and opposing squadcaptain with the time slot they want. The squadcaptains are given a chance to mutually agree upon an acceptable time for their game. If an agreement is made the captains must email the TWL Op. The deadline for schedules to be agreed upon is Thursday, 3 pm EST. There are no exceptions.

    2.03 All time slots may only contain 3 games. If a time slot that a squad captain requested is already filled, he/she will have no choice but to accept a different time slot.

    2.04 Game times not agreed upon by both squad captains by the deadline will be assigned by the League Operator. The League Operator will assign the game to the earliest least occupired time time slot on Saturday. If both squads email the Operator that it is unacceptable, the game will be assigned to the earliest least occupied time slot on Sunday.
    2.05 If one squad has requested a time to the Operator, but the other did not, the squad who requested a time will be granted it.

    2.06 Squads that do not show up for a scheduled game will lose by default. The no-show squad is assigned a 0-25 loss and the winning squad a 25-0 win.

    2.07 If a squad does not show for 2 games in one division they will be replaced in that division.
    I'd rather be SubSpacing.

  • #2
    3.0 Pre Game Rules
    ^^^^^^^^^^^^^^^^^^^^
    3.01 When the game has been called and the arena assigned, usually by a zone-wide advertisement or a :#squad: message, the squad captain or squad representative has 10 minutes to notify the Referee with the squad's starting players and a possible substitute for their verification to be eligible to play. If the referee does not recieve a lineup from a squad by the end of the 10 minute period that squad forfeits the match.

    3.02 All games will be enforce a blueout.

    3.03 Each player who is playing for his squad should be listed as eligible on the TWL roster (<http://www.twleagues.org>). Players who are not ?squadjoined are considered ineligible by the Referee.

    3.04 Only squad members are allowed to spectate on a squad's frequency during the game, unless specifically asked by the squad captain.

    3.05 If the referee makes an error regarding the rules or a procedure that impacts the outcome of the game, the game will be replayed unless both squadcaptains agree to ignore the error or continue from the point of the error's occurance. Please remember that TWL is just for fun, though while a squad may be "thought less of" for accepting a "shallow victory" it does have the option.

    4.0 Game Play Rules
    ^^^^^^^^^^^^^^^^^^^^^
    4.01 Teams will be assigned a safety by the host and must let the host know their desired game play frequency.

    4.02 Once the game has begun you are not allowed to remain in a safety. a. From the time of GO GO GO. Everyone must leave the safe zone. A player who stays in the safe zone for an unreasonable length of time (determined by the referee) will be warned and given one minute to leave the safe. If the player remains in the safe zone he/she will be substituted by the designated substitute. If there is no pre-determined substitute the player will be specced and counted for 10 deaths. If made, the substitution will be announced by the referee.
    4.03 All players must be on the roster and past the waiting period to be eligible to play (6 days), and the host will check eligibility before the game's start.

    4.04 If it is discovered that an ineligible player had played in a match then the match will be a considered a forfeit and the ineligible team will lose 0-50 (This is different in cases of double squadding, see below). The eligible team will be given credit for the win and however many kills they had in the game that was played. (For example if BackStab beat LAME 50-46 but it is discovered that BackStab was playing with Static Burn who was not eligible until 4 days after the match, LAME will be given a 46-0 victory and BackStab will recieve a 0-50 loss, both squads would be notified of the new game result). This is different for TWLB where the game would be 100k-0 regardless of the original game's result.
    4.05 If staff on a squad talk during a blueout, the squad will be given two warnings, and a third infraction will result in the squad forfeiting that match. Also staff on the participating squads are not allowed to use their powers during a match. The League Operator will be called in to make a ruling if this occurs.
    I'd rather be SubSpacing.

    Comment


    • #3
      5.0 Roster Rules
      ^^^^^^^^^^^^^^^^^^
      5.01 A squad can have maximum of 30 players on their roster.
      5.02 After being added to the roster, a player has to wait for 6 days to become marked as eligible. A player also has to be ?squadjoined in order to be able to play in league games. If a few hours are left before a person is eligible. He/she will not be able to play.

      5.03 A player is only allowed to have one name on one league squad's roster. If these limits are exceeded the player will be determined as a double squadder and the following actions are performed:
      1. The offender is banned from league play for either the remainder of the season plus the next season or one year, whichever comes first.
      2. If it is found that a player is not using a name of his own creation but instead using a friend's name to double squad, they will both be banned.
      3. Games in which the offender played are to remain as they stand.
      5.04 If double squadding causes a squad to dissolve (for instance a squadcaptain being banned for double squadding who dissolves the squad and runs it into the ground), it is the job of the TWL Operator to choose a new squad to take the old squad's place. The TWL Operator is encouraged to choose a squad with a roster that consists of the most players who were on the now-dissolved squad. To bring order to the chaos that double squadding causes, the replacing squad will retain the dissolved squad's record.
      5.05 A player cannot change his name on the roster. Once you put your name on the roster, that is final.

      6.0 Conduct Rules
      ^^^^^^^^^^^^^^^^^^^
      6.01 If a referee feels he/she is receiving unnecessary abuse from a player, he/she may report the player to the League Operator who will review the log and may issue a ban from play in league games up to 3 weeks from league play.

      6.02 A deliberate attempt to distract the referee from the game will result in a ban from the remaining TWL season. TWL Opertators take this very seriously

      6.03 Repeated offenses may result in a ban from TWL permanently.

      7.0 Appeal Rules
      ^^^^^^^^^^^^^^^^^^
      7.01 If a squad feels an outside factor had an effect on the outcome of the game, they have the right to appeal. Appeals will be reviewed by the TWL Operator of that subdivision and his/her ruling is final. This can result in a match being replayed, or if serious enough a squad may be disqualified from that subdivision.

      7.02 Squads must contact the Lead TWL Operator within 24 hours of the appealed game in question to make an appeal. If submitted after 24 hours the appeal will not be handled.
      I'd rather be SubSpacing.

      Comment


      • #4
        8.0 TWLD Rules
        ^^^^^^^^^^^^^^^^^^^
        8.01 All Trench Wars League Dueling games will be played in one of the twld arenas in SSCU Trench Wars: twld, twld2, twld3, twld4, twld5.

        8.02 Each squad is allowed up to five 5 players to participate in league matches.

        8.03 A squad must have at least 4 eligible people to play the game. If less than 4 eligible people are able to start when the 10 minutes have expired, the game will be counted as a no-show and a forfeit will be given. A player who shows up after the end of the 10 minutes or start of the game is ineligible to play as either a starting player or a substitute.

        8.04 Each match will consist of one 30 minute game. Each player will be allowed 10 deaths afterwhich they will be specced. The team with players remaining will be declared the winner and a score will be taken when the last opponent is eliminated. If the 30 minutes are over and both teams will have players, the team with the least amount of deaths will be declared as the winner (In the case of a tie there will be a 5 minute extension and after those 5 minutes the team with the least deaths is the winner, continue these 5 minute extensions until one team wins). No kills after the end of the game will be considered in scoring.

        8.05 All players are allowed 3 lag outs. After lagging out a fourth time the player is either substituted by the substitute or removed from the game. If the player is removed from the game he/she is raised to 10 deaths. The ref will notify when a player lags out, and how many lagouts he/she has left (e.g. "DanyalDenyo has lagged out three times and has no more lagouts allowed").

        8.06 When a player is removed in place of a substitute, the referee counts his kills and allows the substitute to inherit whatever deaths the removed player currently has. The referee should notify the players (via a green arena message) who is being substituted and how many deaths this new player has remaining (Failure of the ref to notify upon lagouts should be reported to the TWL Operator, but will not give grounds for an appeal).

        8.07 If a player lags out of the arena he/she has approximately 5 minutes to return. If the player does not return and the referee knows how many deaths the player had when he lagged out, the player may be substituted at the squad captain's wish. If the referee does not know the player's deaths, the missing player will be raised to 10 deaths and not allowed to play regardless of if he reenters after the 5 minutes.

        8.08 The Most Valueable Player (MVP) is the player with the highest amount of kills minus deaths. If there are multiple players with the same amount, the player with the most kills is MVP.

        9.0 TWLJ Rules
        ^^^^^^^^^^^^^^^^^^^
        9.01 All Trench Wars League Javelin games will be played in one of the TWLJ arenas in SSCU Trench Wars: twlj, twlj2, twlj3, twlj4, twlj5.
        9.02 Each match will consist of one 30 minute game. Each player will be allowed 10 deaths afterwhich they will be specced. The team with players remaining will be declared the winner and a score will be taken when the last opponent is eliminated. If the 30 minutes are over and both teams will have players, the team with the least amount of deaths will be declared as the winner (In the case of a tie there will be a 10 minute extension and after those 10 minutes the team with the least deaths is the winner, continue these 10 minute extensions until one team wins). No kills after the end of the game will be considered in scoring.
        9.03 Each squad is allowed up to five 5 players to participate in league matches.
        9.04 A squad must have at least 4 eligible people to play the game. If less than 4 eligible people are able to start when the 10 minutes have expired, the game will be counted as a no-show and a forfeit will be given. A player who shows up after the end of the 10 minutes or start of the game is ineligible to play as either a starting player or a substitute.

        9.06 Warping is not allowed. Players may only warp at the start of the game. The firs time a player violates this rule he/she will recieve a warning upon the first occurance and removed from the game with no substitute upon a second occurance. His deaths will be raised to 10 upon removal from the game.
        9.07 Players are allowed to fight outside the base, though they must go to the base. Staying outside of the base excessively will result in a warning. If the warning has no effect the player will be substituted by the substitute. If the sub has already been used it will result in the perpetrator being specced and raised to 10 deaths.
        9.08 Players are allowed to skirt along the bottom of the base, though it is illegal to leave the base and delay the game by staying out of the base and loitering in the spawn area. Leaving the base to loiter in the spawn area will result in the player being specced and substituted by the substitute of possible. If the sub has already been used it will result in the perpetrator being specced and raised to 10 deaths.
        9.09 If a player happens to spawn outside of the arena, he/she may either warp back in him/herself, or notify the referee, so that the ref may *shipchange or *warpto you.

        9.10 All players are allowed 3 lag outs. After lagging out a fourth time the player can either be substituted by the substitute or removed from the game. If the player is removed from the game he/she is raised to 10 deaths for scoring purposes. The ref will notify when a player lags out, and how many lagouts he/she has left (e.g. "DanyalDenyo has lagged out three times and has no more lagouts allowed").

        9.11 When a player is removed in place of a substitute, the referee counts his kills and allows the substitute to inherit whatever deaths the removed player currently has. The referee should notify the players (via a green arena message) who is being substituted and how many deaths this new player has remaining (Failure of the ref to notify upon lagouts should be reported to the TWL Operator, but will not give grounds for an appeal).

        9.12 If a player lags out of the arena he/she has approximately 5 minutes to return. If the player does not return and the referee knows how many deaths the player had when he lagged out, the player may be substituted at the squad captain's wish. If the referee does not know the player's deaths, the missing player will be raised to 10 deaths and not allowed to play regardless of if he reenters after the 5 minutes.

        9.13 The Most Valueable Player (MVP) is the player with the highest amount of kills minus deaths. If there are multiple players with the same amount, the player with the most kills is MVP.
        I'd rather be SubSpacing.

        Comment


        • #5
          10.0 TWLB Rules
          ^^^^^^^^^^^^^^^^^^
          10.01 All Trench Wars League Base games will be played in one of the TWLB arenas in SSCU Trench Wars: twlb, twlb2, twlb3, twlb4, twlb5.
          10.02 During a TWLB game, rules in the TWLB portion of the TWL rules have supremacy over previous rules.
          10.03 A squad without 5 eligible members is considered to be a no-show and must forfeit. The winning team will recieve 100k, and the forfeiting team will recieve 0 points.
          10.04 Both teams may have 8 starting players. If a squad starts with less than 8 players, they may add more players (whose eligibility must be checked, and scores reset) after the game has started.
          10.05 Teams are allowed to use three substitutes during a basing game. The player entering the game must be scorerest, and play as the same ship as the player being removed. The player being removed will have his points added to his team's points at the end of the game.
          10.05 The game will last thirty minutes. At the end of the thirty minutes, the squad with the most points is the winner.
          10.06 Only one terrier and two sharks are allowed per team.
          10.07 Ship changes are not allowed during the game, however team members may exchange ships between themselves.
          10.08 Each team's terrier must head to the entrance of the base, failure to do so will result in a warning (unless the time is about to run out in which case it may affect the outcome of the game- an appeal may be nessecary). After the warning, any further occurances will result in the opposing team being awarded 5,000 points.
          10.09 Players are allowed an unlimited number of lagouts per game. Though if a player appears to be lagging abnormally and maintaining an unfair advantage the referee has perogative to have him substituted (the lagging player may be substituted by any eligible player, not just the players who were specified as substitutes), or specced if there is no substitue available.
          I'd rather be SubSpacing.

          Comment


          • #6
            some changes, some from you, some from me.

            2.02 All squad captains will use the scheduling system on www.twleagues.org to mutually agree on a time slot suitable for both teams. If an agreement is made the game will be played as planned. The deadline for schedules to be agreed upon is Thursday, 3 pm EST. There are no exceptions.

            2.04 Game times not agreed upon by both squad captains by the deadline will be assigned by the League Operator. The League Operator will assign the game to the earliest least occupired time time slot on Saturday. If both squads email the Operator that it is unacceptable, the game will be assigned to the earliest least occupied time slot on Sunday.

            3.01 When the game has been called and the arena assigned, usually by a zone-wide advertisement or a :#squad: message, the squad captain or squad representative has 10 minutes to notify the Referee with the squad's starting players and a possible substitute for their verification to be eligible to play. If the referee does not receive a lineup from a squad by the end of the 10 minute period that squad forfeits the match.

            3.02 All games are given the choice of blueout. Once a blueout is called no player not staff member, other than host, will be allowed to talk.

            3.03 Each player who is playing for his squad should be listed as eligible on the TWL roster (<http://www.twleagues.org> ). Players who are not squadjoined may still be able to play. BIG change, tell me what you think.

            4.03 All players must be on the roster and past the waiting period to be eligible to play (1 round) and the host will check eligibility before the game. Changed to 1 round. What do you think?

            4.04 If it is discovered that an ineligible player had played in a match then the match will be a considered a forfeit and the ineligible team will lose 0-50 (This is different in cases of double squadding, see below). The eligible team will be given credit for the win and however many kills they had in the game that was played. (For example if Squad1 beat Squad2 50-46 but it is discovered that Squad1 was playing with John Doe who was playing on Jane Doe’s name, Squad2 will be given a 46-0 victory and Squad1 will recieve a 0-50 loss, both squads would be notified of the new game result). This is different for TWLB where the game would be 100k-0 regardless of the original game's result.

            4.05 If a staff member on a squad, talks during a blueout, the squad will be given two warnings, and a third infraction will result in the squad forfeiting that match. Also staff on the participating squads are not allowed to use their powers during a match. The League Operator will be called in to make a ruling if this occurs.

            Added to all leagues- If a player appears to be lagging abnormally and maintaining an unfair advantage the referee has right to have him substituted (the lagging player may be substituted by any eligible player, not just the players who were specified as substitutes), or specced if there is no substitute available.

            5.03 A player is only allowed to have one name on one league squad's roster. If these limits are exceeded the player will be determined as a double squadder and the following actions are performed:
            1. The offender is banned from league play for either the remainder of the season plus the next season or one year, whichever comes first.
            2. If it is found that a player is not using a name of his own creation but instead using a friend's name to double squad, they will both be banned.
            3. Games in which the offender played are to remain as they stand.
            "The strong move quiet, the weak start riots"

            Comment


            • #7
              about rule 3.03 its no big deal really.. just makes it more convenient for people to play.. will the bots freak out about it?
              Mayo Inc. - We should change god's name to "Tod"... see if there's any followers. - Mattey

              Comment


              • #8
                I appreciate that you read what I worked on Crome, and I agree with Mayo on 3.03, whether or not the rules says to be ?squadjoined or not doesn't matter at least to me. The rule just needs to be concrete with no gray area. =)

                About 4.03- one round is fine the same way as 6 days but I think it needs to be reworded to reduce confusion. How about:

                4.03 When a player joins a squad he/she does not become eligible until one round has passed. This means that a player must sit out during one round's matches before he/she becomes eligible. A player joining on Sunday before the last TWL match may play any matches the following weekend.
                I'd rather be SubSpacing.

                Comment


                • #9
                  I will rewrite it so there is no more gray area. The one round rule was suggested by Nethervoid in a past post because the 6 day rule still promoted squadhopping. With the one round rule, it might make it a little less common. Hopefully. Btw my next step for this upcoming weekend is discussing Playoff and such. Get the system of TWL down so that mistakes that happened this season, don't happen next season.
                  "The strong move quiet, the weak start riots"

                  Comment


                  • #10
                    Re: some changes, some from you, some from me.

                    Originally posted by Crome
                    3.03 Each player who is playing for his squad should be listed as eligible on the TWL roster (<http://www.twleagues.org> ). Players who are not squadjoined may still be able to play. BIG change, tell me what you think.

                    4.03 All players must be on the roster and past the waiting period to be eligible to play (1 round) and the host will check eligibility before the game. Changed to 1 round. What do you think?
                    Personally I don't understand the point of being in a squad if you're not going to be ?squadjoined. But I think the problem here would be the bot thing. I think you should still stay ?squadjoined, because it does add, at least some, extra security as to who can play in a game, and who can't. Also, it's easier to have a bot check if a player is eligible than having the host doing it manually...

                    As for the eligibility period, 1 round is very good. IMHO a better solution than having it set to a certain number of days, especially with the postponements that took place this season....I doubt it will be any better next season.
                    "Disoblige - It's not just a squad, it's a lifestyle" - BermuDa

                    Jonas

                    Comment


                    • #11
                      Thank you Jonas for posting your opinion. I will inform my successor to make sure that the ?squadjoin rule does not interfere with the bot's duty.
                      "The strong move quiet, the weak start riots"

                      Comment


                      • #12
                        Don't know if this was covered before or not since I didn't read most of the shit up there, buuuuut -- this rule should be a good way to prevent a conflict of interest.

                        --



                        ----------------------------------------------------------------------------------


                        Under no circumstance can a leader or captain of a competing squad be allowed to overlook, take command of, or operate a Multi-Squadron League, Tournament, or Competetion which would put him/her in a position of power, influence, or control.











                        Yo crome, sup qt

                        Comment


                        • #13
                          Well if I am gonna exclude competitive squads, I have to exclude all squadleaders of any TWL squad. Which makes our choices very limited. Not only are there very few people who could do a good job but to put that, would make it even harder to find someone with the right qualifications.
                          "The strong move quiet, the weak start riots"

                          Comment


                          • #14
                            D _ A _ N _ T _ A _ X

                            Comment


                            • #15
                              hi annux, how are you doing buddy?
                              Animol> the solution for crimelization is openetion of heartization
                              Moltenrock> STOP TALKING TO MY TEAMMMATE ASSHOLE

                              Comment

                              Working...
                              X