• 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.
    6. Use this form to report a VRML rule violation: https://forms.gle/jUnwWALM3HxGvQRXA
  • Matches Organization
    1. The League will generate match-ups each week of the regular season.
    2. The matches are generated on Mondays.
    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 DISCORD to schedule their matches.
    6. Teams must schedule their 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.
    8. Teams will play a minimum of 1 match per week during the season (subject to the following rules).
    9. Once per season, a team may elect to become inactive for one week (greyed-out in standings) without penalty. On subsequent inactivity (not necessarily consecutive weeks), said team shall receive a recurrent MMR percentage penalty until it becomes active again.
      • The only effects of this inactive status is that a team will not be assigned matches on Monday and will not receive their allotment of challenges for that week. Inactive teams can still complete matches that have already been assigned.
    10. Twice per season, when scheduling is deemed to be excessively difficult or impractical, a team can push (postpone) a match without penalty. That match will have to be scheduled the following week.
    11. When a match is scheduled between parties, IT MUST BE PLAYED. No pushes (postponements) (previous rule) are possible.
    12. When both teams schedule and attempt to play a scheduled match only to find out that the match is unplayable (e.g.: game is broken), they can both push (postpone) it. This rule does not apply to individuals experiencing technical or scheduling difficulties.
    13. 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). The players on the team which dropped out will be on cooldowns for 2 weeks.
    14. The scheduled times are according to local time. For example, EST in winter and EDT in summer.
  • Challenges
    1. The league offers a "Challenge" option which allows players to play an additional match in a given week. Limit of 1 challenge per week.
      • Those challenges can be scheduled at any time. The website limits it from being scheduled too far in the future.
      • Challenges can be rejected without penalty.
      • The website determines home/away side based on team history. Whoever initiated the challenge is irrelevant.
    2. 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 until it reaches the same number of allowed matches as the other teams.
  • 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 in the league is Search & Destroy.
    3. The officially supported map pool is listed below. Comp versions of the maps. Other maps can be played only if both teams fully agree:
      • Cache (by Tarmac)
      • de_seaside (by Maverick)
      • Dust II (by Tarmac)
      • Inferno (by Tarmac)
      • Manor (by voxie)
      • Mirage (by KENNITHH)
      • Oil rig (by Reimus)
      • Overpass (by Tarmac)
      • Pipes (by JingleJosh)
      • Reachsky (by Crackers)
      A map can not be played twice.
    4. At the beginning of each match, the following phases must be arranged between team captains:
      INTRA-REGIONAL MATCH INTER-REGIONAL MATCH
      1. Away team bans a map
      2. Home team bans a map
      3. Home teams picks map
      4. Away team picks side (blue or red)
      -- on next map --
      5. Away team picks map
      6. Home team picks side (blue or red)
      -- on next map --
      7. Home team picks map
      8. Away team picks side (blue or red)
      1. Home team bans a map
      2. Away team bans a map
      3. Away team picks map
      4. Home team picks server and side (blue or red)
      -- on next map --
      5. Home team picks map
      6. Away team picks server and side (blue or red)
      -- on next map --
      7. Away team picks map
      8. Home team picks server and side (blue or red)
      • When a match is NA West vs EU, the match is played on NA East servers and standard INTRA-REGIONAL MATCH map/side choice applies. Teams registering as NA West shall have a majority of players west of the Mississippi and/or south of Texas.
      • Games are generally expected to be played on the official servers. VRML moderated servers with root access by at least two VRML mods or their delegates may be made available. These are valid servers if both team captains agree on their use.
    5. The official player count is 5v5.
      • 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.
      • 5v4 can be played if the team with 4 couldn't find a ringer in time.
      • 4v3 can be played if the team with 3 couldn't find a ringer in time.
      • 5v3 is an automatic forfeit.
      • When both teams need a ringer, no ringer should be used at all. E.g.: A team that was fortunate enough to get a ringer for their match (making it 5 total) cannot play their match against a team of 4 (missing a ringer). In such a case, the match should be played 4v4.
      • In all cases, a team will be ineligible to play its match where it has fewer than 3 rostered players present.
  • Gameplay Clarifications and Restrictions
    1. Full 3rd party communications is allowed while playing.
    2. In-game mic may be muted via pavlov’s steamVR push to talk binding or other 3rd party means.
    3. Players and team coaches are forbidden from communicating in any way with in-game players during a match. In between maps, and during timeouts, coaches, players and spectators may communicate with in-game players freely.
    4. The AWP sniper and the 50 Cal may only be used with the default scope attachment, and/or a suppressor and the scope must be left in the default position. The red dot, acog, and holo sight attachments are forbidden for this weapon. If a forbidden sight is purchased, the default scope must immediately be replaced, or if no player on the team can afford replacement, the awp or 50 Cal must be discarded. Carrying an improper awp or 50 Cal around or otherwise using it in combat will result in a map forfeit. Picking up an improperly attached awp or 50 Cal for the next round is also a map forfeit.
    5. Only publicly available skins on the workshop that only change the color "skin" of the gun and do not effect any other game files are allowed.
    6. When dual wielding guns, it is not allowed to fire one gun through another attempting to stack up the sights of both, or using a physical stock with two guns at once.
    7. Between maps, a team may call a timeout for any reason.
    8. Where a team is delaying a round for more than 2 minutes, the opposing team may notify their counterpart that they are forcing them to use a timeout (said 5 minutes counts toward total timeout).
      • Teams are allotted 2 timeouts each per match.
        1st timeout 15 minutes
        2nd timeout 10 minutes
      • Once the timeout expires, the match must proceed.
      • 2 timeouts cannot be called in succession and at least 1 round must be played between timeouts.
      • 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.
      • 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.
  • Scoring System
    1. Teams enter the score themselves (or ask an admin). Both teams need to submit the score for the match to be compiled.
    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.
  • Matches Forfeits
    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 write down a message in Discord (tagging their opponent) or show proof to League Moderators that they were indeed ready at their scheduled time.
    3. Once the 20 minutes buffer has elapsed, the team that is not ready (or 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 30-0 (total) will be awarded to their opponent.
  • Matches Defaults
    1. Where teams miss the match scheduling deadline, 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 facts.
    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:
      • Where neither team made any arrangement efforts, the match will be considered cancelled;
      • A score of 2-1 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;
      • A score of 3-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
      • Where facts do not permit a clear determination, the match is cancelled and neither team gains or loses MMR.
    3. League Moderators may remove an inactive team from the League where they have defaulted on 2 or more occasions and have good cause to believe this will continue.
  • 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. One must not hide their identity under another alias.
      • Player names, player logos, team names or team logos are forbidden if they:
        • Are protected by copyrights/royalties/third-party rights and the user has no written permission;
        • Resemble or are identical to a brand/trademark no matter whether it's registered or not;
        • Resemble or are identical to a real person other than themselves;
        • Resemble or are identical to a VRML representative (excluding the VRML representatives themselves using the name);
        • Are deemed too hard to read, distinguish, interpret or have multiple unnecessary characters;
        • Are nonsense
      • 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, gibberish or wrong spelling in order to avoid the requirements mentioned above is forbidden.
      • The League Moderators reserve the right to suspend or ban the non complying player or team.
    3. Players acknowledge and follow Pavlov VR guidelines on age restrictions.
    4. Players acknowledge and follow their headset's regulations. For example: Oculus Terms of Use and Vive Terms of Use.
    5. Players acknowledge and follow Discord Terms of Use.
    6. Additional regional regulations or guidelines, based on your location, may apply.
    7. The maximum number of players per team is 8.
    8. Substitute players from other teams are prohibited in standard or challenge matches.
    9. Only Official Ringers authorised by the League can be used to fill empty slots in a team.
      • When a team needs a Ringer, they must visit the Official Ringers page in order to validate which Ringers are available to them according to their team rank.
    10. Official Ringers can not play for the same team more than twice per season.
    11. 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.
    12. 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 ringers group or another team, but shall be prohibited from participating in a league match.
      • This rule is inactive during the off-season.
      • 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.
      • As a courtesy, the captain of the opposing team may allow the cooldown to be waived for a player who is otherwise ineligible to play due to cooldown. Note that this is a courtesy only and teams are not obligated to allow their opponents to field an otherwise ineligible player.
    13. Teams rosters, on the website, cannot change during a match.
    14. 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.
    15. 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.
    16. 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.
  • Streaming & Media
    1. At least 1 player per team must be streaming or at least recording the match.
    2. The recording must include full video and audio. It must be available before Monday of the following week and remain accessible for 2 weeks.
    3. Recording must be posted in the match-vods channel in DISCORD.
    4. Failure to provide a recording may result in forfeit.
    5. The League Moderators may, subject to having good cause, require a particular player to stream or record his/her matches until such a time as specified by the League Moderators.
  • Bugs
    1. In the event that someone crashes out or encounters a bug (be it advantageous or disadvantageous); that is unfortunate but the round still counts. Note that advantageous bugs could be considered exploits, see below.
    2. 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.
    3. Sometimes the devs 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 change idea 6 hours prior to their match (to allow enough time for everyone to re-download another build).
  • Cheating, Exploits & Breaches
    1. Any cheating, exploiting, or contravention of the foregoing rules must be brought to the attention of the League Moderators who have complete discretion on how to impose a penalty. 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. The term exploit is intended to include the intentional or reckless triggering of code, attribute or function in game that is otherwise not envisaged as a legitimate feature of the game.
    4. Non-exhaustive examples include:
      • Going outside of map boundaries;
      • Clipping inside solid objects/floors (using room-scale or not);
      • Body glitching (body not following player's viewpoint);
      • Peeking through solid walls;
      • Use VPN or any other network manipulation;
      • Any other imaginative cheats
    5. 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.
    6. Everyone is responsible to have a connection (ping) as good as possible for their region and technical situation. All downloads and other programs which are not necessary for the match have to be turned off, and use of VPNs or other tools to manipulate connection speed or fidelity are forbidden. Teams may be disqualified for use of such tools.
  • 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:
      • Void or change scores for any match or challenge after it has been played;
      • Enact disciplinary procedures for any alleged or perceived player misconduct;
      • Draft, publish and interpret the rules of the league;
      • Settle disputes and issue rulings.
    3. Formal disputes amongst league teams and their members are to be lodged directly with League Moderators via Discord.
      • 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 on the balance of probabilities based on the relevant facts and giving due consideration 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 Captains Room 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: 2020-09-14