Rules Change Log
Date	Section	Rule Change

 

Scope and Agreement

By registering for VR Master League (VRML) or participating in any VRML match, event, or official VRML community space, you agree to follow all VRML rules, guidelines, and policies.

VRML may take action when conduct materially impacts:

• • competitive integrity (cheating, match manipulation, ban evasion),

  • community safety (harassment, threats, doxing),

  • the ability of VRML staff to administer the league.

Definitions

To reduce confusion and ensure consistent enforcement:

• • Harassment: Targeted abuse, repeated unwanted contact, or behavior intended to intimidate or degrade another person.

  • Hate speech / Slurs: Derogatory language targeting protected characteristics (race, ethnicity, nationality, religion, gender, sexual orientation, disability, etc.).

  • Doxing: Sharing or threatening to share private identifying information.

  • Threats: Statements or behavior expressing intent to harm someone or their property.

  • Impersonation: Presenting yourself as another person, staff member, or banned individual.

  • ALT account: Any additional Discord/VRML account used to participate, evade restrictions, or obscure identity.

  • Exploit: Intentionally or recklessly using unintended game behavior/mechanics to gain advantage.

  • Cheating: Any intentional manipulation of game/client/system/network to gain advantage or to access information not intended to be available.

  • Official channels: VRML website, VRML Support Discord ticket system, and designated VRML league servers/channels.

 

1.1 Fair Play and Sportsmanship

• • Play honestly and within VRML rules and the game’s intended mechanics.

  • Cheating, exploiting bugs, or intentionally disrupting gameplay undermines league integrity and may lead to disciplinary action.

  • Win or lose, conduct yourself professionally. Toxic behavior (e.g., targeted insults, harassment, slurs, intimidation) is not tolerated.
    
    

1.2 ALT Accounts and Ban Evasion

• • Using or maintaining multiple VRML or Discord accounts to participate in VRML is prohibited.

  • Assisting, coordinating with, or knowingly concealing ALT use or ban evasion is prohibited.

  • Confidential reports may be submitted via the ticket system.
    
    

1.3 Respect and Safety

Treat all players, League Officials, moderators, casters, and developers with respect.
The following are prohibited:

• • abusive, inflammatory, or discriminatory language (verbal, written, or implied),

  • personal attacks, harassment, threats, doxing, or intimidation,

  • attempts to rally harassment (“brigading”) or targeted call-outs.
    
    

1.4 Inclusive Environment

VRML welcomes participants of all backgrounds, identities, and skill levels.

• • Discrimination is prohibited.

  • Slurs and offensive “jokes” are not acceptable even if claimed to be humorous.
    
    

1.5 False Accusations and Public Drama

• • Good-faith reporting is encouraged through official channels.

  • Knowingly false accusations, fabricated evidence, or coordinated smear campaigns are prohibited.

  • Public call-outs and drama may be moderated when they become harassment, misinformation, or disrupt league operations.
    
    

1.6 Responsibility and Accountability

• • Team Captains are responsible for ensuring their team understands and follows VRML rules.

  • Misconduct by team members may result in consequences for individuals and, where appropriate, the team or captain.

  • Impersonating or representing a banned player (including acting or speaking on their behalf to circumvent a ban) is prohibited.

  • “I didn’t know” is not a defense.
    
    

1.7 Disputes and Reporting

• • Handle disputes respectfully using the ticket system.

  • If you suspect misconduct, submit a report through VRML Support Discord tickets.

  • VRML will handle reports with appropriate confidentiality.
    
    

1.8 Off-Platform Conduct

VRML cannot moderate all private behavior. However, VRML may take action on off-platform conduct when it:

• • targets VRML participants/officials (harassment, threats, doxing),

  • involves cheating/match manipulation,

  • materially impacts competitive integrity or community safety.
    
    

1.9 Streaming and Content

If you stream or post content related to VRML:

• • you must uphold the same standards,

  • content promoting harassment, misinformation, or harmful conduct may result in league action.
    
    

1.10 Live and In-Person Events

Participation in live events is a privilege.
Violations at live events may carry more severe penalties, including:

• • immediate removal/disqualification,

  • forfeiture of prizes/standings,

  • suspension from future events/seasons,

  • permanent bans for egregious or repeated misconduct.
    
    

1.11 Staff Standards and Transparency

League Officials and Moderators are held to the same conduct standards.

• • Official VRML decisions and rulings must be issued through official channels (tickets and/or designated VRML servers).

  • Staff should avoid conducting official VRML business via DMs except for safety/welfare issues, urgent match-day emergencies, or cases requiring privacy. Any outcome must still be summarized and documented in the relevant ticket.
    
    

 

2.1 Eligibility and Age

• • Minimum age is 13, or the minimum age required by applicable law/platform/game terms—whichever is higher.

  • Players must comply with Discord Terms of Service and headset/platform terms.
    
    

2.2 Team Size and Rosters

• • Maximum roster size: 8 players.

  • Players rostered on one team cannot substitute for another team.

  • Team rosters cannot be changed during a match.
    
    

2.3 One Identity / One Account

• • Players may not play under more than one account and must not maintain more than one VRML account.

  • Players and teams must compete using their registered VRML name and must not hide identity under alternate aliases.

  • If a player may play under multiple platforms/accounts with different names (e.g., Steam/Oculus), a ticket must be opened and names must be submitted before playing.
    
    

2.4 Naming and Branding Standards

Player/team names and logos must not:

• • impersonate staff or other players,

  • be confusingly similar to brands or trademarks in a way likely to cause confusion,

  • be defamatory, hateful, obscene, or intended to evade moderation via altered spelling/gibberish,

  • use excessive characters, unicode spoofing, or formatting designed to mislead or be unreadable.

VRML may require changes to any name/logo that violates these standards.

2.5 Captain Participation in Support

• • Team Captains must join the VRML Support Discord.

  • If a Captain is not present, staff may issue a warning and require them to join within 48 hours after being prompted. Failure to comply may result in AP.
    
    

2.6 Ping Limits and Server Requirements

Players may only participate in matches if their ping is within limits to the required server:

Ping limits

• • North America: 170 ms

  • Europe: 170 ms

  • OCE/ASIA: 270 ms

Mandatory server locations

• • North America: NAE

  • Europe: EUW

Enforcement standard

• • Ping is enforced using ping observed by other players in the lobby (not the player’s own view).

  • If there is a conflict, staff may rule using:

    • multiple observed readings,

    • consistency over time,

    • and an average of credible observations.

  • Consistent fluctuations exceeding 50 ms from established baseline may lead to round/map/match adjustments at moderator discretion.
    
    

 

3.1 Reservist Use

• • Teams may request a reservist to reduce roster imbalance; match sizes must not become more unbalanced.

  • Teams must notify opponents via Discord before the match (or ASAP if mid-match).

  • Reservists used must be listed when submitting match results.
    
    

3.2 Official Reservists and Substitutes

• • Only VRML-authorized Official Reservists may fill empty slots.

  • Substitutes must be validated using the Official Substitute system (MMR rules apply).

  • A team may use at most 1 reservist per match.

  • Official Reservists cannot play for the same team more than twice per season.

  • Official Reservists are not eligible for post-season matches.
    
    

3.3 Minimum Players

• • Teams unable to field at least 3 rostered players are declared a forfeit.
    
    

3.4 Common Scenarios

• • 5v4, 4v3, 5v3 may proceed if a reservist cannot be found in time (one reservist allowed for the short team).

If a player leaves a team for any reason:

• • A cooldown applies for the next 2 VRML weeks (as defined by match generation cycles).

  • During cooldown, the player may join another team or the Reservist group but may not play a league match.

  • This rule is inactive during the off-season.
    
    

5.1 Definitions

• • Standings are defined by team MMR during the season.

  • MMR reflects results to support fair matchmaking.
    
    

5.2 Major Roster Changes

If a team changes the majority of its roster within 2 weeks (e.g., 3/5, 4/6, 4/7, 5/8):

• • the team may request MMR recalculation using Player-MMR averaging,

  • to prevent abuse, recalculated MMR cannot exceed the team’s previous MMR before the roster change.
    
    

5.3 Veteran New Teams

New teams formed primarily from veteran players may receive a higher starting MMR following Player-MMR logic and must still complete required placement matches.

6.1 Weekly Match Generation

• • Match-ups generate weekly on Mondays around 06:00 PM CEST (APAC may experience Tuesday by local time).

  • Teams with fewer than 5 rostered players at generation may be set inactive for the week.
    
    

6.2 Scheduling Responsibilities

• • Teams must schedule assigned matches via Discord.

  • Scheduling deadline: Friday 06:00 PM CEST.

  • Scores must be submitted within 24 hours after the final round and before Monday 15:00 UTC of the next week (except matches under ticket review).

  • Matches must be played and submitted by 06:00 PM CEST the following Monday.
    
    

6.3 Score Corrections

• • Teams must report correct scores.

  • Staff will generally not correct score reporting errors unless the error changes the match winner, or both captains agree in writing within 24 hours.
    
    

6.4 Inactivity and Postponements

• • Once per season, a team may take one inactive week without penalty (ticket required).

  • Additional inactivity may incur recurring MMR penalties until active again.

  • Once per season, a team may postpone one match to the next week without penalty (not allowed in the final week).

  • Matches may not be moved to another week once scheduled, except with moderator approval for major external events (e.g., game-breaking patch).

• • Teams may play up to 1 challenge match per week (unless staff grants exceptions).

  • Challenges may be rejected without penalty.

  • Challenge matches must be completed by 06:00 PM CEST the following Monday.

  • Challenge cancellations:

    • may be canceled without penalty if the opponent is notified in writing 48+ hours before match time,

    • cancellations inside 48 hours may be treated as a forfeit.
      
      

8.1 Missed Scheduling Deadline

If teams miss the scheduling deadline but play later, warnings may be issued and penalties may apply based on circumstances.

8.2 Unplayed Matches

If a match is not played in the allotted time, staff will review efforts and may:

• • cancel the match if neither team made reasonable efforts,

  • award a default score (e.g., 27–21 or 27–0) based on demonstrated availability and cooperation,

  • cancel without MMR change when facts are insufficient.

Availability weighting may be applied:

• • Monday–Thursday = 1.0

  • Friday–Sunday = 1.3
    
    

8.3 No-Show Procedure

• • Teams have a 10-minute buffer from scheduled start to be in the lobby.

  • The waiting team must post proof they were ready (e.g., message tagging opponent in the relevant VRML Discord channel or other verifiable evidence).

  • After 10 minutes: offending team forfeits the first map.

  • After 20 minutes: match may be declared a no-show and scored 27–0.
    
    

8.4 Penalty Enforcement

• • Forfeits and penalties (AP and other actions) may only be issued by League Moderators/Lead Moderators.

  • Captains may not pressure opponents into penalties; suspected violations must be reported via tickets.
    
    

• • Each team receives 2 timeouts per match, each lasting 10 minutes.

  • Only one timeout may occur between maps.

  • A timeout runs the full 10 minutes unless both teams agree to resume earlier.

  • A 1-minute cooldown occurs automatically between maps unless both teams agree to start immediately.
    
    

10.1 Registration and Roll Call

• • Registration opens the first Monday after the prior season concludes.

  • Registration indicates intent but is not entry.

  • Teams become official participants only after Roll Call begins 1 hour prior to the scheduled start.
    
    

10.2 Eligibility

• • Teams must complete at least 50% of regular season matches.

  • Teams must remain active during the final two weeks of the season.

  • Challenges are locked during the final two weeks of the regular season.
    
    

10.3 Recording and VOD Policy 

All post-season players must record or stream their matches.

• • Retention: Keep VODs for 14 days minimum.

  • If requested by staff: Provide VOD(s) within 24 hours of the request.

  • If you cannot meet the deadline due to technical limitations, you must respond within 12 hours explaining why and providing the soonest possible delivery time.

  • VODs must include full, uncut gameplay with audio. Editing that materially alters evidence (removing segments, cutting rounds, desyncing, or selectively removing comms) is prohibited.

  • Minimum quality: 480p.

  • Overlays that obstruct gameplay visibility are prohibited.
    
    

10.4 Structure 

Post-season consists of 3 stages:

• • Challenger Cup — Swiss (1 round) + CC Final between top 2

  • Quarterfinals — Single elimination (Bo3)

  • Grand Finals — Single elimination (Semis Bo3, Bronze Bo3, Finals Bo5)

Published start times:

• • Challenger Cup: 07:00 PM CEST (EU) | 00:00 AM CEST (NA)

  • Quarterfinals: 06:00 PM CEST (EU) | 11:00 PM CEST (NA)

  • Grand Finals: 06:00 PM CEST (EU) | 11:00 PM CEST (NA)
    
    

11.1 Reporting

Cheating/exploits must be reported to League Moderators via tickets.

11.2 Definitions

• • Cheating includes intentional or reckless manipulation of the game/client/system/network to gain advantage.

  • Exploits include intentional or reckless use of unintended mechanics not envisaged by the developer as legitimate.
    
    

11.3 Non-Exhaustive Examples (Prohibited)

Includes, but is not limited to:

• • going outside map boundaries,

  • using ziplines/geometry to breach boundaries or reach unintended locations,

  • clipping the torso or significant body volume into solid objects to gain advantage,

  • peeking through solid floors/walls,

  • third-party overlays/apps that affect gameplay mechanics or visibility (system performance overlays allowed if they do not affect gameplay/visibility),

  • VPN or network manipulation intended to evade ping limits, bans, or restrictions,

  • altering SteamVR World Scale outside default 100%,

  • planting the scanner in ways that prevent or unreasonably obstruct interruption,

  • planting while not on the same plane as the artifact (standing on the artifact or objects to plant is not allowed),

  • using bugs/exploits to relocate an active scanner,

  • using spectate or external media (stream sniping) to gain advantage,

  • using chat of an active cast while playing in the match.

Rejoin edge case:

• • if placed on the opposing team, the player must immediately suicide at round start and swap teams.

  • the player must not communicate with their team or use spectate displays.

  • opponents must not pick up items dropped by the affected player; leave them in spawn.
    
    

11.4 Allowed Clarification

• • Shooting limbs that clip through walls/floors is permitted; players are responsible for not exposing limbs through geometry.
    
    

12.1 Official Casting

• • League Moderators and League Casters authorize spectating/casting via the game’s spectate function.

  • Teams must permit league-sanctioned spectators/casters upon request.

  • Official casting must be streamed on designated League channels unless otherwise approved.
    
    

12.2 Community Casting

Community casters may cast official matches only if:

• • both teams agree in writing,

  • the caster follows #community-cast requirements and streams publicly,

  • the stream has a 3-minute delay,

  • the caster has a VRML account in good standing and a linked Discord account,

  • the caster has the community caster role.

VRML may override a community cast at any time.

12.3 Recording Mandate (General)

• • Captains are responsible for ensuring the team complies with recording/VOD rules where applicable.

  • VRML may require a player to submit recordings for a defined period if good cause exists.
    
    

 

• • AP is issued when a rule listed in the AP Table or official rules is violated.

  • AP is assigned to the responsible person(s) and tracked on the website.

  • AP may trigger cooldowns or disciplinary actions when thresholds are reached.

  • AP expires 180 days after the infraction.

  • AP tracks across VRML leagues.

  • AP may only be issued by League Moderators and Lead Moderators.
    
    

14.1 Authority and Documentation

League Moderators may:

• • void or change match outcomes where rules/evidence require,

  • administer discipline for misconduct,

  • interpret and update rules.

Decisions must be documented in the relevant ticket and should include:

• • rule basis,

  • evidence reviewed,

  • reasoning for the chosen penalty level.
    
    

14.2 Evidence Standard

Moderators evaluate evidence using a “more likely than not” standard. Stronger penalties may require stronger evidence.

14.3 Conflicts of Interest

Moderators must recuse themselves from decisions where a conflict of interest exists.

14.4 Communication Requirement

Players must maintain at least one functional communication method with VRML staff (the ticket system). Blocking individual staff members is permitted only if it is not used to evade investigations and the player remains reachable via tickets.

14.5 Appeals

• • Appeals must be submitted via a VRML Support ticket.

  • AP may be appealed immediately and at any time after being applied.

  • If you believe AP was applied in error, appeal as soon as possible so it can be reviewed before any suspension is triggered.

14.6 Suspension Timing

Suspensions are generally applied weekly in the 24-hour window before match generation, except when timing is necessary to protect competitive integrity. Suspensions normally end before match generation in the week they expire. Exceptions may apply when appeals/reviews are pending.

 

 

1. 1. A match consists of 3 maps. All maps must be played, as the overall scores affect traded MMR outcomes.
   2. The official game mode of League matches is “Artifact”
   3. The official player count is 5v5.
   4. Maps may be played at any time of day (Daylight, Dusk, or Night). The team selecting the map determines the time-of-day setting.

 

Map Pool:   Suna Khidi Miru Cliffside Frio   The same map can not be played twice within a match. Match Setup: Prior to match start, teams should reach out to each other in DM’s on discord with picks. Starting with the Home team. Both teams will choose a map to be banned. A team may elect not to ban a map. The home team must declare before start if they intend to choose Map or Side first. If they choose Side first then Away chooses Map. When a team chooses a side or map first, they must make the choice known before the other team picks. For example, if Home chooses to pick Map, they must choose the map before Away choosing which side. Upon completion of a map, a new server can be created and code shared with the opposing team (and caster if casted). [Home] Team: May Ban a Map [Away] Team: May Ban a Map Map 1: [Home] Chooses Server Location | Chooses map or side.  Map 2: [Away] Chooses Server Location | Chooses map or side. Map 3: [Home] Chooses Server Location | Chooses map or side. The team selecting the map determines the time-of-day setting. Server Region alternates every map unless teams agree to remain on the current server.

Gameplay Clarifications and Restrictions. Global In offline (LAN) events, it is not permitted to use the "Snap-turn" feature. Mandatory Recording Players are now mandated to record. Rules can be found within rule 15.8 . Player Skin Cosmetics Player body skin must be the Standard Issue skin. Colonist: Standard Issue Coat / Standard Issue Bracer.  Reyab: Standard Issue Coat Players are allowed to use any head skin. Players are allowed to use any hand skin. Players are allowed to use any weapon skins. Utility Limitations Players are limited to equipping a maximum of 1 frag grenade per round, but may receive a second frag grenade from a teammate after the round starts. Equipping a frag grenade with an impact frag is allowed. The only permitted utilities for matches are Frag Grenades, Impact Grenades, Flash-bangs, Smoke Grenades and Thermites. Players are not allowed to use the Vortex Mine