Skip to content

Instantly share code, notes, and snippets.

@danhawkins

danhawkins/rules.html

Created April 17, 2021 16:45
Show Gist options
  • Save danhawkins/e7415270784fa8289e3cd4b02d166661 to your computer and use it in GitHub Desktop.
Save danhawkins/e7415270784fa8289e3cd4b02d166661 to your computer and use it in GitHub Desktop.
Download ZIP
season-11-rules-content
Raw
rules.html
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Document</title>
<link
href="//vrmasterleague.com/css/bootstrap.min.css"
rel="stylesheet"
type="text/css"
/>
<link
href="//vrmasterleague.com/css/custom.css?vrml.2.7.3"
rel="stylesheet"
type="text/css"
/>
<link
href="//vrmasterleague.com/css/theme.css?vrml.2.7.3"
rel="stylesheet"
type="text/css"
/>
<style type="text/css">
@font-face {
font-weight: 400;
font-style: normal;
font-family: 'Circular-Loom';
src: url('//cdn.loom.com/assets/fonts/circular/CircularXXWeb-Book-cd7d2bcec649b1243839a15d5eb8f0a3.woff2')
format('woff2');
}
@font-face {
font-weight: 500;
font-style: normal;
font-family: 'Circular-Loom';
src: url('//cdn.loom.com/assets/fonts/circular/CircularXXWeb-Medium-d74eac43c78bd5852478998ce63dceb3.woff2')
format('woff2');
}
@font-face {
font-weight: 700;
font-style: normal;
font-family: 'Circular-Loom';
src: url('//cdn.loom.com/assets/fonts/circular/CircularXXWeb-Bold-83b8ceaf77f49c7cffa44107561909e4.woff2')
format('woff2');
}
@font-face {
font-weight: 900;
font-style: normal;
font-family: 'Circular-Loom';
src: url('https://cdn.loom.com/assets/fonts/circular/CircularXXWeb-Black-bf067ecb8aa777ceb6df7d72226febca.woff2')
format('woff2');
}
</style>
<style type="text/css">
ol {
counter-reset: item;
}
li {
display: block;
list-style-position: outside;
}
li:before {
content: counters(item, '.') '';
counter-increment: item;
margin-right: 10px;
font-weight: bold;
}
</style>
</head>
<body class="vrmasterleague onward dark">
<ol
class="rules_list vrml_table_container"
style="
list-style-type: none;
padding: 5px 15px 15px 15px;
border-radius: 2px;
"
>
<li class="chapter">
<strong>League Member Code of Conduct</strong>
<ol>
<li>
Play fairly and
<strong>within the rules of the VR Master League.</strong>
</li>
<li>
Treat your fellow gamers, teammates, competitors, spectators, and
League officials with respect and dignity.
</li>
<li>
Discriminatory language, hate speech, threats, doxxing, and other
forms of harassment or unlawful behavior will not be tolerated.
</li>
<li>
Team Captains may be held responsible for their team&#39;s
behaviour.
</li>
<li>
Accusations of impropriety or foul play are taken seriously and
should be brought to the attention of the League Moderators.
</li>
</ol>
</li>
<li class="chapter">
<strong>Matches Organization</strong>
<ol>
<li>
The League will <strong>generate match-ups each week</strong> of the
regular season.
</li>
<li>The matches are <strong>generated on Mondays (US)</strong></li>
<li>
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.
</li>
<li>
<strong>Teams are responsible for scheduling their matches.</strong>
</li>
<li>
<strong
>Players must reach out to the other teams using
<a href="https://discord.gg/jXEjffwx5P" target="_blank"
>DISCORD</a
>
to schedule their matches.</strong
>
</li>
<li>
<strong>Teams must schedule their match by Friday 1600 UTC</strong>
of the week it is to take place. A reminder will be sent if teams
are late to schedule
</li>
<li>
The
<strong
>scores must be submitted as soon as the game is over.
</strong>
(See Scoring System below)
</li>
<li>
All matches must be played and have the scores submitted by 1600 UTC
on the following Monday.
</li>
<li>
Teams will play a minimum of
<strong>1 match per week</strong> during the season, with exception
to the following rules:
<ol>
<li>
Once per season,
<strong>a team may elect to become inactive</strong> (indicated
by the team appearing “greyed-out” on the standings page)
<strong>for one week without penalty</strong>. On subsequent
inactivity (not necessarily consecutive weeks), said team shall
receive a weekly recurrent MMR percentage penalty until it
becomes active.
<ol>
<li>
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.
</li>
<li>
If a team chooses to use their free inactive week, they
should open a ticket to let the League Moderators know.
</li>
</ol>
</li>
<li>
Once per season, when
<strong
>scheduling is deemed to be excessively difficult or
impractical</strong
>, a team can postpone a match without penalty, to be scheduled
the following week.
</li>
</ol>
</li>
<li>
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
</li>
<li>
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.
</li>
<li>
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.
</li>
<li>
The scheduled times are according to <strong>local time</strong>.
For example, EST in winter and EDT in summer.
</li>
</ol>
</li>
<li class="chapter">
<strong>Challenges</strong>
<ol>
<li>
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
</li>
<li>
The website determines home/away side based on team history; it is
not based on who initiated the challenge
</li>
<li>
Barring special circumstances, a team, in order to be able to
challenge, must have been active when the weekly matches were
generated.
</li>
<li>
In the event that the League is unable to assign a weekly league
match to a team, that team will be permitted
<strong>additional challenge(s)</strong> for that week as
replacement(s).
</li>
<li>
Challenge matches must be scheduled, played, and have their scores
recorded on the website no later than the following Monday at 1600
UTC/1200 EDT/0900 PDT.
</li>
<li>
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.
</li>
</ol>
</li>
<li class="chapter">
<strong>Matches Format</strong>
<ol>
<li>
A match consists of
<strong>3 maps. All maps must be played</strong>, as the overall
scores affect traded MMR outcome.
</li>
<li>
The official game-mode of League matches is
&quot;<strong>Uplink.</strong>&quot;
</li>
<li>
The &quot;Escort&quot; game mode may be played
<strong>only</strong> if both teams fully agree, via Discord text,
prior to starting their League match.
</li>
<li>
The standard round timer for matches is 6 minutes
<ol>
<li>
Both teams are to check this at the start of the first round of
a map and round reset if incorrect (with map rehost)
</li>
<li>
If a timer error is not identified in the first round then the
map is to be played out with rehost for the next map with the
correct round timer.
</li>
</ol>
</li>
<li>
The officially supported map pool will be announced in the Onward
VRML server as part of the season 11 map rotations.
<strong>Some</strong> of the maps in pool will be changed every 5
weeks. Other maps may be played <strong>only</strong> if both teams
fully agree, via Discord text, prior to starting their League match.
</li>
<li>
A map can not be played twice in the same match.
<strong>Night</strong> variants are considered the same as their day
variants for the purpose of this rule.
</li>
<li>
When a map is banned, all of its variants are also considered
banned.
</li>
<li>
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.
</li>
<li>
After the ban phase, the <strong>Home team</strong> picks the map
<strong>OR</strong> chooses their starting side (Volk or Marsoc).
The <strong>Away team</strong> then picks a map
<strong>OR</strong> chooses a starting side. Finally, the
<strong>Home team</strong> has the final pick/choice.
</li>
<li>
The official player count is <strong>5v5.</strong>
<ol>
<li>
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.
</li>
<li>
5v4 can be played if the team with 4 couldn't find a reservist
in time.
</li>
<li>
4v3 can be played if the team with 3 couldn't find a reservist
in time.
</li>
<li>
5v3 is an automatic forfeit if the team with 3 couldn't find a
reservist in time.
</li>
<li>
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.
</li>
<li>
In all cases, a team will be ineligible to play its match where
it has fewer than <strong>3 rostered players present.</strong>
</li>
</ol>
</li>
</ol>
</li>
<li class="chapter">
<strong>Gameplay Clarifications and Restrictions</strong>
<ol>
<li>
It is
<strong>forbidden to do &quot;Player-boosting.&quot;</strong> The
term &quot;Player-boosting&quot; refers to the stacking of players
on one another (e.g.: a player crouches and another stands on his
shoulders).
</li>
<li>
The M203 and RPG launchers are permitted under the following bounds.
<ol>
<li>Each team may field at most one launcher.</li>
<li>
The M203 HE launcher is permitted only on Downfall, Quarantine,
Snowpeak, and their variants.
</li>
<li>The M203 Smoke launcher is permitted on all maps.</li>
</ol>
</li>
<li>Shields are not allowed on any map.</li>
<li>Volk Drones are not allowed on any map.</li>
<li>
Marsoc Drones are
<strong
>only permitted on Downfall, Quarantine, Snowpeak and their
variants.</strong
>
</li>
<li>
On any map, there shall be
<strong
>no explosions from Frags/C4/RPG/M203 explosives/Molotov before 15
seconds</strong
>
(ie. 5:45 round timer if round is 6 minutes) and
<strong>no flash detonations before 12 seconds</strong> (ie. 5:48
round timer).
<ol>
<li>
Where a violation of the foregoing rule has occurred, the
opposing team can request that the round is replayed.
</li>
<li>
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.
</li>
</ol>
</li>
<li>
As Marsoc, it is
<strong
>not allowed to raise your pad more than 6 feet off the
ground</strong
>
in order to capture an objective that is located above your head;
some exceptions apply and are listed here:
<ol>
<li>
On Suburbia, you can capture the MO, in the middle mansion, with
your pad pretty high, only if you have both feet on the stairs.
</li>
</ol>
</li>
<li>
The following <strong>map glitches are banned:</strong>
<ol>
<li>
<strong>Bazaar:</strong> It's not allowed to walk on the side of
the buildings on the 2nd storey ledge as shown on this picture
<a
href="../images/maps/Bazaar_ledge.png"
target="_blank"
style="color: red !important"
>HERE</a
>
(This is a good example of a general guidance where invisible
ledges should not be used)
</li>
<li>
<strong>Bazaar:</strong> It's not allowed to walk on the fences
like the one in this picture
<a
href="../images/maps/Bazaar_tree.png"
target="_blank"
style="color: red !important"
>HERE</a
>
</li>
<li>
<strong>Suburbia:</strong> 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
<a href="#" target="_blank" style="color: red !important"
>HERE (needs link)</a
>
</li>
<li>
<strong>Downfall:</strong> It is not allowed to enter the
cockpit of the helicopter. As seen
<a href="#" target="_blank" style="color: red !important"
>HERE (needs link)</a
>
</li>
</ol>
</li>
<li>
In offline (LAN) events, it is not permitted to use the "snap-turn"
feature.
</li>
<li>
All official VRML matches are to be played using VRML approved
build(s) only, currently approved builds:
<ol>
<li><strong>1.8.7.3</strong> with anti-cheat enabled</li>
</ol>
</li>
</ol>
</li>
<li class="chapter">
<strong>Scoring System</strong>
<ol>
<li>
Teams
<strong
>enter the score themselves. Both teams need to submit the
score</strong
>
for the match results to be accepted.
</li>
<li>
The website requires users to
<strong>enter the score for each map</strong>
individually.
</li>
<li>
The team winning
<strong
>2 maps out of 3 is the winning team. All maps must be
played</strong
>
as the overall scores affect traded MMR outcome
</li>
</ol>
</li>
<li class="chapter">
<strong>Matches Forfeits &amp; Timeouts</strong>
<ol>
<li>
Teams have a <strong> 20 minutes buffer</strong> from the scheduled
match start time to be in the game lobby with their team members.
</li>
<li>
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.
</li>
<li>
Once the <strong>20 minutes buffer has elapsed</strong>, the team
that is responsible for the delay forfeits the first map.
</li>
<li>
If a further <strong>20 minutes elapses</strong> without match
commencement, the offending team is officially declared a
&quot;<strong>no-show</strong>&quot; and a score of 12-0 (total)
will be awarded to their opponent.
</li>
<li>
In the case of a forfeit, the &quot;forfeit&quot; option should be
selected from the dropdown box under &quot;map&quot; when submitting
scores.
</li>
<li>
Between rounds, a <strong>team may call a timeout</strong> for any
reason
</li>
<li>
Where a team is
<strong>delaying a round for more than 2 minutes</strong>, the
opposing team may notify their counterpart that they are forcing
them to use a timeout (said 2 minutes counts toward total timeout).
<ol>
<li>
Teams are allotted <strong>2 timeouts each</strong> per match.
<ol>
<li>1st timeout - 15 minutes</li>
<li>2nd timeout - 10 minutes</li>
</ol>
</li>
<li>Once the timeout expires, the match must proceed.</li>
<li>
2 timeouts cannot be called in succession and at least 1 round
must be played between timeouts.
</li>
<li>
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.
</li>
<li>
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.
</li>
</ol>
</li>
</ol>
</li>
<li class="chapter">
<strong>Matches Defaults</strong>
<ol>
<li>
Where teams
<strong>miss the match scheduling deadline (Friday 1600 UTC)</strong
>, 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.
</li>
<li>
In the event that a
<strong
>match has not been played during the allotted time frame</strong
>, the League Moderators will review the circumstances and allocate
the match points accordingly. Example resolutions may include the
following:
<ol>
<li>
Where neither team made any arrangement efforts, the match will
be considered cancelled;
</li>
<li>
A score of 8-7 may be awarded by default with the
&quot;win&quot; attributed to the team determined to have been
available on the most days with a higher weighting given to
weekend availability;
</li>
<li>
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
</li>
<li>
Where facts do not permit a clear determination, a 8-7 win may
be awarded to the home team.
</li>
</ol>
</li>
<li>
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.
</li>
</ol>
</li>
<li class="chapter">
<strong>Teams &amp; Players</strong>
<ol>
<li>
Players are not allowed to play under more than one account, and
must not have more than one account registered with VRML.
</li>
<li>
Players and teams must play using their registered VRML name. Do not
hide your identity under another alias.
<ol>
<li>
Player names, player logos, team names, and team logos are
forbidden if they:
<ol>
<li>
Are protected by copyrights/royalties/third-party rights and
the user has no written permission;
</li>
<li>
Resemble or are identical to a brand/trademark no matter
whether it's registered or not;
</li>
<li>
Resemble or are identical to a real person other than
themselves;
</li>
<li>Resemble or are identical to a VRML representative;</li>
<li>
Are deemed too hard to read, distinguish, interpret or have
multiple unnecessary characters;
</li>
<li>Are nonsense</li>
</ol>
</li>
<li>
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.
</li>
<li>
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.
</li>
<li>
The League Moderators reserve the right to suspend or ban the
non complying player or team.
</li>
<li>
Players are forbidden from modifying the display of their names
to casters in game (changing colors, adding italics or
underscores, etc).
</li>
</ol>
</li>
<li>
Players are not to falsely represent a team for which they are not a
rostered member.
</li>
<li>
Players acknowledge and follow
<a
href="//www.oculus.com/experiences/rift/1216866718419997"
target="_blank"
>Onward guidelines on age restrictions</a
>.
</li>
<li>
Players acknowledge and follow their headset's regulations. For
example:
<a href="//www.oculus.com/legal/terms-of-service/" target="_blank"
>Oculus Terms of Use</a
>
and
<a href="//www.htc.com/us/terms/vive/" target="_blank"
>Vive Terms of Use.</a
>
</li>
<li>
Players acknowledge and follow
<a
href="https://support.discord.com/hc/en-us/articles/360040724612"
target="_blank"
>Discord Terms of Use</a
>.
</li>
<li>
Additional regional regulations or guidelines, based on your
location, may apply.
</li>
<li>The <strong>maximum number of players per team is 8</strong>.</li>
<li>
<strong
>Players and substitutes rostered on one team cannot substitute
for another team</strong
>.
</li>
<li>
Only
<a href="/Onward/Players/Reservists/" target="_blank"
>Official Reservists</a
>, authorised by the League, can be used to fill empty slots in a
match.
<ol>
<li>
When a team needs a Reservist, they must visit the
<a href="/Onward/Players/Reservists/" target="_blank"
>Official Reservists</a
>
page in order to validate which Reservists are available to them
according to their team rank.
</li>
</ol>
</li>
<li>
Official Reservists cannot play for the same team more than twice
per season.
</li>
<li>
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.
</li>
<li>
Where a player leaves a team for any reason, that player will be
subject to a
<strong
>&quot;cooldown&quot; period for the next 2 VRML-weeks</strong
>
(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.
<ol>
<li>This rule is inactive during the off-season.</li>
<li>
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
</li>
</ol>
</li>
<li>
Teams rosters, on the website,
<strong>cannot change during a match.</strong>
</li>
<li>
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.
</li>
<li>
In the event that a
<strong>team changes the majority of its roster</strong> (3/5, 4/6,
4/7, 5/8), within 2 weeks, that team, when ready to continue
playing, can, upon request, have
<strong>its MMR recalculated by averaging each Player-MMRs</strong>.
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.
</li>
<li>
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
</li>
</ol>
</li>
<li class="chapter">
<strong>Streaming &amp; Media</strong>
<ol>
<li>
The League Moderators and League Casters are responsible for
authorizing the spectating or casting of league matches via the
game's spectate function.
</li>
<li>
All teams must permit League sanctioned spectators or casters access
to official matches upon request.
</li>
<li>
Subject to certain exceptions, spectating or casting of an official
league match by non-authorized personnel is strictly prohibited.
</li>
<li>
Official match casting must be streamed via the designated League
Twitch channels.
</li>
<li>
League Casters must abide by the code of conduct maintained by the
Casting Coordinator and approved by the League Moderators.
</li>
<li>
League Moderators may permit a co-caster to stream on another
private channel to assist with replay capture.
</li>
<li>
The League Moderators may, subject to having good cause,
<strong
>require a particular player to stream or record his/her
matches</strong
>
until such a time as specified by the League Moderators.
</li>
</ol>
</li>
<li class="chapter">
<strong>Bugs &amp; Resets</strong>
<ol>
<li>
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.
</li>
<li>
Examples of known prevalent bugs:
<ol>
<li>
In the event the same team (Marsoc or Volk) spawns in 2
different locations, the round is automatically voided and must
be replayed.
</li>
<li>
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).
</li>
<li>
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.
</li>
</ol>
</li>
<li>
In the event that a <strong>game update</strong> introduces major
<strong>bugs experienced by the majority of players</strong>, the
league may decide to extend the week to play the match.
</li>
<li>
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).
</li>
<li>
In the event of a bug or round reset which incorrectly awards a
point or switches team sides the following should be used as
<strong>guidance</strong> (but may vary - if needing clarification
CONTACT A MODERATOR).
<ol>
<li>
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)
</li>
<li>
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)
</li>
</ol>
</li>
</ol>
</li>
<li class="chapter">
<strong>Cheating, Exploits &amp; Breaches</strong>
<ol>
<li>
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.
</li>
<li>
&quot;Cheating&quot; 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.
</li>
<li>
&quot;Exploit&quot; 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.
</li>
<li>
Non-exhaustive examples include:
<ol>
<li>Going outside of map boundaries;</li>
<li>
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);
</li>
<li>Body glitching (body not following player's viewpoint);</li>
<li>Peeking through solid walls or floors;</li>
<li>
Using external communication systems (except to declare a bug
(ex: in-game voice not working, game crash to Windows, etc));
</li>
<li>
&quot;Push To Talk&quot; mode shouldn't be used to communicate
or to mute communication;
</li>
<li>
Kicking a teammate from the game to gain an advantage on a
situation;
</li>
<li>
Self-downing (or have a teammate down one-self), intentionally;
</li>
<li>
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);
</li>
<li>Use VPN or any other network manipulation;</li>
<li>
Going underneath, on top of, or into objects/structures that
were not intended to be used OR where the only way to get to
them is with real world physical movement as only thumbstick
movement is acceptable. (ex: exploiting the corner of an object
to gain access to the top of it or crawling in the playspace to
get under a vehicle.)
</li>
<li>Any other imaginative cheats</li>
</ol>
</li>
<li>
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.
</li>
<li>
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.
</li>
</ol>
</li>
<li class="chapter">
<strong>Decisions &amp; Sanctions</strong>
<ol>
<li>
Contravention of any of the foregoing rules shall be sanctionable on
review by League Moderators.
</li>
<li>
League Moderators reserve the sole right to:
<ol>
<li>
Void or change scores for any match or challenge after it has
been played;
</li>
<li>
Enact disciplinary procedures for any alleged or perceived
player misconduct;
</li>
<li>
Draft, edit, publish, and interpret the rules of the League;
</li>
<li>Settle disputes and issue rulings.</li>
</ol>
</li>
<li>
Formal disputes amongst League teams and their members are to be
lodged directly with League Moderators via Discord.
<ol>
<li>
Unfounded and baseless accusations against players via any
public medium are considered to be an act of misconduct.
</li>
</ol>
</li>
<li>
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..).
</li>
<li>
League Moderators will issue decisions via the #sit-room Discord
channel and occasionally via #league-talk Discord channel.
</li>
<li>
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.
</li>
<li>
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.
</li>
<li>
Players may not &quot;block &quot; league moderators/league
governors.
</li>
<li>
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.
</li>
</ol>
</li>
</ol>
</body>
</html>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment