1. League Member Code of Conduct
    1. Play fairly and within the rules of the VR Master League.
    2. Treat your fellow gamers, teammates, competitors, spectators, and League officials with respect and dignity.
    3. Discriminatory language, hate speech, threats, doxxing, and other forms of harassment or unlawful behavior will not be tolerated.
    4. Team Captains may be held responsible for their team's behaviour.
    5. Accusations of impropriety or foul play are taken seriously and should be brought to the attention of the League Moderators.
  2. Matches Organization
    1. The League will generate match-ups each week of the regular season.
    2. The matches are generated on Mondays around noon EST/EDT.
    3. When weekly matches are generated, any team with fewer than five (5) rostered players will be turned inactive and not be allowed to play the current week.
    4. Teams are responsible for scheduling their matches.
    5. Players must reach out to the other teams using DISCORDto schedule their matches.
    6. Teams must schedule their assigned match by Friday 1600 UTC of the week it is to take place. A reminder will be sent if teams are late to schedule
    7. The scores must be submitted as soon as the game is over. (See Scoring System below)
    8. All matches must be played and have the scores submitted by 1600 UTC on the following Monday.
    9. Teams will play a minimum of 1 match per week during the season, with exception to the following rules:
      1. Once per season, a team may elect to become inactive (indicated by the team appearing “greyed-out” on the standings page) for one week without penalty. On subsequent inactivity (not necessarily consecutive weeks), said team shall receive a weekly recurrent MMR percentage penalty until it becomes active.
        1. If a team's status is set to “inactive,” they will not be assigned a match on the following Monday and will not receive their allotment of challenges for that week. Inactive teams are still expected to complete matches that have already been assigned and/or scheduled.s
        2. If a team chooses to use their free inactive week, they should open a ticket to let the League Moderators know.
      2. Once per season, when scheduling is deemed to be excessively difficult or impractical, a team can postpone a match without penalty, to be scheduled the following week.
    10. Once a match is scheduled on the VRML website, it may not be rescheduled to another week. It may be rescheduled to a different time within the same week if both teams agree
    11. Occasionally, there may be significant events or circumstances, outside of player control, which affect both teams' ability to play a scheduled match (e.g. a patch is released that makes the game unplayable). In such an event, the match may be rescheduled to the following week, pending League Moderator approval.
    12. In the event that a team becomes inactive or drops out before playing any matches in the current season, and a match was created for that team, the match is cancelled (not forfeited) and their opponent will be allowed an extra challenge match in compensation. The players on the team which dropped out will be on cooldown for 2 weeks.
    13. The scheduled times are according to local time. For example, EST in winter and EDT in summer.
  3. Challenges
    1. The League offers a "Challenge" option which allows players to play an additional match in a given week. Barring special circumstances, teams are not allowed to play more than 1 challenge match per week. Challenges may be rejected without penalty
    2. The website determines home/away side based on team history; it is not based on who initiated the challenge
    3. Barring special circumstances, a team, in order to be able to challenge, must have been active when the weekly matches were generated.
    4. In the event that the League is unable to assign a weekly League match to a team, that team will be permitted additional challenge(s) for that week as replacement(s).
    5. Challenge matches must be scheduled and played no later than 10 days after the challenge is accepted by both teams. The scores must be submitted as soon as the game is over, as usual.
    6. A challenge match may be cancelled, without penalty, after it is scheduled, but only if notification of the cancellation is given to the other team, via Discord, prior to 48 hours before the match is to take place. If a challenge match is cancelled within 48 hours of its scheduled time, it may be considered a forfeit by the team that cancels.
  4. Matches Format
    1. A match consists of 3 maps. All maps must be played, as the overall scores affect traded MMR outcome.
    2. The official game-mode of League matches is "Uplink."
    3. The "Escort" game mode may be played only if both teams fully agree, via Discord text, prior to starting their League match.
    4. The standard round timer for matches is 6 minutes.
      1. Both teams are to check this at the start of the first round of a map and round reset if incorrect (with map rehost).
      2. If a timer error is not identified in the first round, the map is to be played out with rehost for the next map with the correct round timer.
    5. The following are the map pools for Season 11. Some of the maps in the pool will be changed every 5 weeks. Other maps may be played only if both teams fully agree, via Discord text, prior to starting their League match.
      1. Map Pool 1 (Weeks 1-5):
        1. Suburbia Day and Night
        2. Sand
        3. USS Quest
        4. Bazaar Day and Night
        5. Subway
        6. Downfall Day and Night
        7. Quarantine Day and Night
        8. Snowpeak Day and Night
      2. Map Pool 2 (Weeks 6-10):
        1. Sand
        2. Cargo
        3. [TBD (Small)]
        4. Shipyard
        5. Subway
        6. Downfall Day and Night
        7. Quarantine Day and Night
        8. Snowpeak Day and Night
      3. Map Pool 3 (Weeks 11-15):
        1. Suburbia Day and Night
        2. USS Quest
        3. [TBD (Small)]
        4. Bazaar Day and Night
        5. [TBD (Medium)]
        6. Downfall Day and Night
        7. Quarantine Day and Night
        8. Snowpeak Day and Night
    6. A map can not be played twice in the same match. Night variants are considered the same as their day variants for the purpose of this rule.
    7. When a map is banned, all of its variants are also considered banned.
    8. Before the beginning of each match, starting with the Home team, both sides will choose one map to ban from the map pool. A team may decide to not ban any map.
    9. After the ban phase, the Home team picks the map OR chooses their starting side (Volk or Marsoc). The Away team then picks a map OR chooses a starting side. Finally, the Home team has the final pick/choice.
    10. The official player count is 5v5.
      1. When scheduling for their match, teams can mutually decide to play the match 3v3 or 4v4. No teams are obligated to lower their player count for any match.
      2. 5v4 can be played if the team with 4 couldn't find a reservist in time.
      3. 4v3 can be played if the team with 3 couldn't find a reservist in time.
      4. 5v3 is an automatic forfeit if the team with 3 couldn't find a reservist in time.
      5. When both teams need a reservist, no reservist should be used at all. E.g.: A team that was fortunate enough to get a reservist for their match (making it 5 total) cannot play their match against a team of 4 (missing a reservist). In such a case, the match should be played 4v4.
      6. In all cases, a team will be ineligible to play its match where it has fewer than 3 rostered players present.
  5. Gameplay Clarifications and Restrictions
    1. It is forbidden to do "Player-boosting." The term "Player-boosting" refers to the stacking of players on one another (e.g.: a player crouches and another stands on their shoulders).
    2. The M203 and RPG launchers are permitted under the following bounds:
      1. Each team may field, at most, one launcher.
      2. The M203 HE launcher is permitted only on Downfall, Quarantine, Snowpeak, and their variants.
      3. The M203 Smoke launcher is permitted on all maps.
    3. Shields are not allowed on any map.
    4. Volk Drones are not allowed on any map.
    5. Marsoc Drones are only permitted on Downfall, Quarantine, Snowpeak and their variants.
    6. On any map, there shall be no explosions from Frags/C4/RPG/M203 explosives/Molotov before 15 seconds (ie. 5:45 round timer if round is 6 minutes) and no flash detonations before 12 seconds (ie. 5:48 round timer).
      1. Where a violation of the foregoing rule has occurred, the opposing team can request that the round is replayed.
      2. If teams are unable to reach an agreement, the match shall progress as normal and the score will be subject to review by League Moderators.
    7. As Marsoc, it is not allowed to raise your pad more than 6 feet off the ground in order to capture an objective that is located above your head; some exceptions apply and are listed here:
      1. On Suburbia, you can capture the MO, in the middle mansion, only if you have both feet on the stairs.
    8. The following map glitches are banned:
      1. Bazaar: It's not allowed to walk on the side of the buildings on the 2nd storey ledge as shown on this picture HERE. (This is a good example of a general guidance where invisible ledges should not be used)
      2. Bazaar: It's not allowed to walk on the fences like the one in this picture HERE.
      3. Suburbia: It's not allowed to shoot another player if they are glitching through the floor from the uppermost floor of the center building (middle house / open house / mansion) as seen HERE.
      4. Downfall: It is not allowed to enter the cockpit of the helicopter. As seen HERE.
      5. Quarantine: It's not allowed to get up onto the fuselage from the south (which is done by moving along an invisible ledge from east to west, then popping up). As seen HERE.
    9. In offline (LAN) events, it is not permitted to use the "snap-turn" feature.
    10. All official VRML matches are to be played using VRML-approved build(s) only, currently approved builds:
      1. with anti-cheat enabled
  6. Scoring System
    1. Teams enter the score themselves. Both teams need to submit the score for the match results to be accepted.
    2. The website requires users to enter the score for each map individually.
    3. The team winning 2 maps out of 3 is the winning team. All maps must be played as the overall scores affect traded MMR outcome
  7. Matches Forfeits & Timeouts
    1. Teams have a 20 minutes buffer from the scheduled match start time to be in the game lobby with their team members.
    2. If a team is waiting for another team, the waiting team must post a message in Onward VRML's Discord (tagging their opponent) or show other proof to League Moderators that they were ready at the scheduled time.
    3. Once the 20 minutes buffer has elapsed, the team that is responsible for the delay forfeits the first map.
    4. If a further 20 minutes elapses without match commencement, the offending team is officially declared a "no-show" and a score of 12-0 (total) will be awarded to their opponent.
    5. In the case of a forfeit, the "forfeit" option should be selected from the dropdown box under "map" when submitting scores.
    6. Between rounds, a team may call a timeout for any reason
    7. Where a team is delaying a round for more than 2 minutes, the opposing team may notify their opponent that they are forcing them to use a timeout (said 2 minutes counts toward total timeout).
      1. Teams are allotted 2 timeouts each per match.
        1st timeout 15 minutes
        2nd timeout 10 minutes
      2. Once the timeout expires, the match must proceed.
      3. Only one timeout can be used at a time. At least one round must be played between timeouts
      4. In the event a team has no more timeouts remaining and is facing another delay of more than 2 minutes, they must decide immediately to play the round with the players they have or forfeit the match.
      5. Failure to abide by this rule can result in League Moderators reviewing and issuing a penalty to the offending team up to and including forfeiting the match.
  8. Matches Defaults
    1. Where teams miss the match scheduling deadline (Friday 1600 UTC), but the match is organised and played subsequently, a warning will be given to the teams. League Moderators may impose a penalty on one or both of the teams depending on the circumstances.
    2. In the event that a match has not been played during the allotted time frame, the League Moderators will review the circumstances and allocate the match points accordingly. Example resolutions may include the following:
      1. Where neither team made any arrangement efforts, the match will be considered cancelled;
      2. A score of 8-7 may be awarded by default with the "win" attributed to the team determined to have been available on the most days, with a higher weighting given to weekend availability;
      3. A score of 12-0 may be awarded to a team where their opponent has made little/no effort or been objectively determined to have frustrated the organisation of the match; or
      4. Where facts do not permit a clear determination, an 8-7 win may be awarded to the home team.
    3. League Moderators may remove an inactive team from the League if the team has defaulted on 2 or more occasions and the League Moderators have good cause to believe this will continue.
  9. Teams & Players
    1. Players are not allowed to play under more than one account, and must not have more than one account registered with VRML.
    2. Players and teams must play using their registered VRML name. Do not hide your identity under another alias.
      1. Player names, player logos, team names, and team logos are forbidden if they:
        1. Are protected by copyrights/royalties/third-party rights and the user has no written permission;
        2. Resemble or are identical to a brand/trademark no matter whether it's registered or not;
        3. Resemble or are identical to a real person other than themselves;
        4. Resemble or are identical to a VRML representative;
        5. Are deemed too hard to read, distinguish, interpret or have multiple unnecessary characters;
        6. Are nonsense
      2. In addition to the above, any player names, player logos, team names or team logos that are defamatory, pejorative, offensive, vulgar, obscene, anti-Semitic, inciting hatred, or offending against good manners are forbidden. Using alternative spelling or gibberish, in order to avoid the requirements mentioned above, is also prohibited.
      3. Team names must be unique and are first come, first served. Alternative spellings or otherwise attempting to use a name already taken by an active or otherwise occupied team by changing a small detail, whether intentional or incidental, is not permitted, enforceable at Moderator discretion.
      4. The League Moderators reserve the right to suspend or ban the non complying player or team.
      5. Players are forbidden from modifying the display of their names to casters in game (changing colors, adding italics or underscores, etc).
    3. Players are not to falsely represent a team for which they are not a rostered member.
    4. Players acknowledge and follow Onward guidelines on age restrictions.
    5. Players acknowledge and follow their headset's regulations. For example: Oculus Terms of Use and Vive Terms of Use.
    6. Players acknowledge and follow Discord Terms of Use.
    7. Additional regional regulations or guidelines, based on your location, may apply.
    8. The maximum number of players per team is 8.
    9. Players and substitutes rostered on one team cannot substitute for another team.
    10. Only Official Reservists, authorised by the League, can be used to fill empty slots in a match.
      1. When a team needs a Reservist, they must visit the Official Reservists page in order to validate which Reservists are available to them according to their team rank.
    11. Official Reservists cannot play for the same team more than twice per season.
    12. Sister teams are not encouraged. However, an individual can be in a team Discord and not be on the official roster for counseling/friendship/coaching purposes.
    13. Where a player leaves a team for any reason, that player will be subject to a "cooldown" period for the next 2 VRML-weeks (that is the 2nd Monday if a player leaves a Monday-Tuesday and 3rd Monday if a player leaves Wednesday or after). During this period, the player may become a member of the reservists group or another team, but shall be prohibited from participating in a League match.
      1. This rule is inactive during the off-season.
      2. When a team disbands, the cooldowns of the players may, upon request, be waived. League Moderators have complete discretion and may, depending on the situation, decide not to waive said cooldowns
    14. Teams rosters, on the website, cannot change during a match.
    15. If teams have decided to play a match and either one has a roster with fewer than the other (or fewer than standard player team count), any roster changes must result with an even player number count in each team or with the same number of players that was agreed to play the match on. In other words, teams sizes during a match, shouldn't change to become even more unbalanced than it was.
    16. In the event that a team changes the majority of its roster (3/5, 4/6, 4/7, 5/8), within 2 weeks, that team, when ready to continue playing, can, upon request, have its MMR recalculated by averaging each Player-MMRs. In order to prevent abuse (notably when a championship is about to start), that recalculated MMR cannot be higher than what it was before the players had left the team.
    17. In the event that a group of players decide to create a new team from scratch, and most of them are considered "veteran" players, the new team will start with a higher MMR than would normally be attributed. That MMR initialization bonus follows the Player-MMR logic. Note that, like every new team, they will still have to do their mandatory three placement matches before officializing their MMR in the standings
  10. Streaming & Media
    1. The League Moderators and League Casters are responsible for authorizing the spectating or casting of league matches via the game's spectate function.
    2. All teams must permit League sanctioned spectators or casters access to official matches upon request.
    3. Subject to certain exceptions, spectating or casting of an official league match by non-authorized personnel is strictly prohibited.
    4. Official match casting must be streamed via the designated League Twitch channels.
    5. League Casters must abide by the code of conduct maintained by the Casting Coordinator and approved by the League Moderators.
    6. League Moderators may permit a co-caster to stream on another private channel to assist with replay capture.
    7. The League Moderators may, subject to having good cause, require a particular player to stream or record their matches until such a time as specified by the League Moderators.
  11. Bugs & Resets
    1. The native reset function may be triggered to reset a round for any reason. A team shouldn't be using this feature multiple times in a match. Where a team has reset multiple times in a match, the League Moderators reserve the right to forfeit the round(s) in which the reset happened. Their decision will be based on, but not limited to, the reasons and/or the evidence which might have been put forward justifying said resets.
    2. Examples of known prevalent bugs:
      1. In the event the same team (Marsoc or Volk) spawns in 2 different locations, the round is automatically voided and must be replayed.
      2. In the event that all Volk enemies are dead, but the round timer continues (making Volk automatically win) the round point actually goes to Marsoc. Marsoc wins by 1 point (they can't take advantage of the bug to capture the objective).
      3. On Quarantine, for the truck stop objective, if a player spawns underground, the round is automatically voided and must be replayed; unless said player can get to normal height before the spawn countdown ends.
    3. In the event that a game update introduces major bugs experienced by the majority of players, the league may decide to extend the week to play the match.
    4. Sometimes the developers may provide a distinct build to be used by the League. The League Moderators will indicate which default build the matches should be played on. In all cases, when the teams agree to play on a certain build, they cannot decide to change builds within 6 hours of their match (to allow enough time for everyone to re-download another build).
    5. In the event of a bug or round reset which incorrectly awards a point or switches team sides the following should be used as guidance (but may vary - if needing clarification CONTACT A MODERATOR).
      1. If the bug occurs when neither side has played the objective (but the sides are switched) then the lobby should be rehosted before playing the round on any objective which has not been played (does not have to be the same objective as neither side has played it)
      2. If the bug occurs and one team has already played the objective then the lobby should be rehosted on the same objective and the first round should be given to the team who won it previously (have one player from each team load in and shoot the correct person based on who won the round previously - do not volk suicide as two points will be awarded)
  12. Cheating, Exploits & Breaches
    1. Any cheating, exploiting, or contravention of the foregoing rules must be brought to the attention of the League Moderators. League Moderators, with support from League Governors, have complete discretion on penalties imposed for violations. Examples of penalties are: Round forfeit, map forfeit, match forfeit, player suspension, or team suspension.
    2. "Cheating" is intended to include the intentional or reckless manipulation of the game and its code in such a way as to confer an unfair advantage on one side or the other.
    3. "Exploit" is intended to include the intentional or reckless triggering of code, attribute, or in-game function that is otherwise not envisaged as a legitimate feature of the game by Downpour Interactive.
    4. Non-exhaustive examples include:
      1. Going outside of map boundaries;
      2. Clipping, as a deliberate attempt to hide more than half your body inside a solid object in game (rough limit of 50% of one's body shouldn't be clipped in a geometry);
      3. Body glitching (body not following player's viewpoint);
      4. Peeking through solid walls or floors;
      5. Using external communication systems (except to declare a bug (ex: in-game voice not working, game crash to Windows, etc));
      6. "Push To Talk" mode shouldn't be used to communicate or to mute communication;
      7. Kicking a teammate from the game to gain an advantage on a situation;
      8. Self-downing (or have a teammate down one-self), intentionally;
      9. Third Party VR or Desktop overlays/applications that affects gameplay mechanics or aesthetics (Personal system monitoring/diagnostic overlays are allowed, provided they do not affect previously stated mechanics or aesthetics);
      10. Use VPN or any other network manipulation;
      11. Only stick movement is allowed when accessing locations on the map. Using real world playspace movement to access locations on a map that are restricted by thumbstick movement is not allowed. (Example: crawling in the playspace to get under a vehicle is not allowed).
      12. Any other imaginative cheats
    5. Any use of the spectate function by participants during official matches, either directly or indirectly, to obtain an advantage of any kind is classified as cheating.
    6. Any use of external media streaming (stream sniping) which pertains to the circumstances, content or any facts arising from the match is classified as cheating.
  13. Decisions & Sanctions
    1. Contravention of any of the foregoing rules shall be sanctionable on review by League Moderators.
    2. League Moderators reserve the sole right to:
      1. Void or change scores for any match or after it has been played;
      2. Enact disciplinary procedures for any alleged or perceived player misconduct;
      3. Draft, edit, publish, and interpret the rules of the League;
      4. Settle disputes and issue rulings.
    3. Formal disputes amongst League teams and their members are to be lodged directly with League Moderators via Discord.
      1. Unfounded and baseless accusations against players via any public medium are considered to be an act of misconduct.
    4. The League Moderators shall, with regard to developer input, decide issues based on the relevant facts. Due consideration will be given to the accounts of those involved. Amongst these considerations, the League Moderators shall give the most weight to the presence/absence of indicting or exculpatory evidence (e.g. in game footage, chat logs, etc..).
    5. League Moderators will issue decisions via the #sit-room Discord channel and occasionally via #league-talk Discord channel.
    6. Failure to comply with a request for match VODs, stream links, or any other item covered in the above rules will disqualify a player or team from participating in any further League events until they are deemed compliant by the League Moderators.
    7. In relation to any of the above rules, when a majority of the League Moderators reach the conclusion that conduct unbecoming of the League has occurred, the League Moderators have complete discretion to administer the appropriate sanction.
    8. Players may not "block " League Moderators/League Governors.
    9. In the event of a conflict of interest, affected League Moderators shall recuse themselves from deciding or otherwise commenting on an issue in their capacity as League officials.

Updated: 2021-04-26