|
|
(3 intermediate revisions by 2 users not shown) |
Line 1: |
Line 1: |
| {{Eras|real}} | | {{Eras|real}} |
| | | {{Gaming}} |
| | |
| The [[Rites of Combat]] (ROC) are the standard gaming rules for all official [[Dark Brotherhood|Brotherhood]] gaming activities, to include normal gaming, Tournaments and [[Vendetta|Vendetta’s]]. All members should familiarize themselves with the general gaming rules, as well as the rules for their platform(s) of choice. | | The [[Rites of Combat]] (ROC) are the standard gaming rules for all official [[Dark Brotherhood|Brotherhood]] gaming activities, to include normal gaming, Tournaments and [[Vendetta|Vendetta’s]]. All members should familiarize themselves with the general gaming rules, as well as the rules for their platform(s) of choice. |
|
| |
|
Line 29: |
Line 28: |
| a. Gaming competitions will follow the rules outlined under the Rites of Combat. | | a. Gaming competitions will follow the rules outlined under the Rites of Combat. |
|
| |
|
| b. Competition organizers may alter rules and guidelines for specific competitions with express approval of the Fist.. | | b. Competition organizers may alter rules and guidelines for specific competitions with express approval of the Fist. |
|
| |
|
| c. Any alterations to rules or guidelines must be made clear prior to the start of any such competition and enforced consistently throughout the entirety of the event. | | c. Any alterations to rules or guidelines must be made clear prior to the start of any such competition and enforced consistently throughout the entirety of the event. |
Line 44: |
Line 43: |
| a. As per Section 1.03 of the Covenant of the Dark Jedi Brotherhood, the Fist reserves the right to amend the Rites of Combat. | | a. As per Section 1.03 of the Covenant of the Dark Jedi Brotherhood, the Fist reserves the right to amend the Rites of Combat. |
|
| |
|
| b. All amendments must be reported to the Membership upon enactment. | | b. All amendments to the Rites of Combat will be reviewed by the Justicar prior to implementation. |
| | |
| | c. All amendments must be reported to the Membership upon enactment. |
|
| |
|
| == Article 2: Setting Up Matches == | | == Article 2: Setting Up Matches == |
Line 50: |
Line 51: |
| === Section 2.1 - DB Gaming Channel === | | === Section 2.1 - DB Gaming Channel === |
|
| |
|
| a. To participate in Brotherhood Gaming for all PvP, [[Vendetta|Vendettas]], and Tournaments members must be present in the DB Gaming Matchmaking Channel on Discord. | | a. To participate in Brotherhood Gaming for [[Vendetta|Vendettas]], and Tournaments members must be present in the DB Gaming Matchmaking Channel on Discord. |
| | |
| b. For PvE and PvO outside of a vendetta, presence in DB Gaming Matchmaking is strongly encouraged but not mandatory.
| |
| | |
| === Section 2.2 - Setting up 1v1 PvP ===
| |
| | |
| a. Members must setup 1v1 matches using the @dbb0t gaming functions on Discord. Members will not set up PvP matches in PM or clan chat at any time.
| |
| | |
| b. If PVP match submissions are found that were not set up using the DB Gaming Matchmaking channel, those matches will be declined, unless they have been approved for exemption by the Fist prior to match submission. Exemptions will be handled on a case-by-case basis, and will be generally limited to Discord @dbb0t issues.
| |
| | |
| c. Members may play twelve (12) matches against a single opponent, on each supported platform, each day. Members may play these twelve (12) matches on an unlimited number of supported platforms.
| |
| | |
| d. Outside of a Great Jedi War or Rite of Supremacy, members are permitted to announce their intention to queue for 1v1 PvP or that they are currently queued for 1v1 PvP but *only* in the DB Gaming Matchmaking channel. Matches cannot be set up in any other chats or by PM.
| |
| | |
| e. During a Great Jedi War or Rite of Supremacy, members will *not* announce in chat that they are in queue for 1v1 PvP at any time.
| |
| | |
| === Section 2.3 - Setting up FFA / Team PvP ===
| |
|
| |
|
| a. Members must use the PvE/O Party Tool to organize their FFA. Members must join this group to receive credit for the FFA activity.
| | b. For PvE and PvP outside of a vendetta, presence in DB Gaming Matchmaking is strongly encouraged but not mandatory. |
|
| |
|
| b. Members may play twelve (12) team matches with the same set of people on a single platform each day.
| | === Section 2.2 - Setting up Gaming Matches and Events === |
|
| |
|
| c. During a Vendetta or Clan Feud, FFA matches may only have one member from each unit. More than one member from a single unit will cause that match to be declined.
| | a. During [[Vendetta|Vendettas]] and DB Wide Gaming Tournaments members must use the “party create” functions on Discord unless specific competition rules say otherwise. |
|
| |
|
| d. A member can not game against members from their same unit during a Vendetta for the purposes of competition.
| | b. For normal gaming outside of a competitive event, members are permitted to set up matches and events in any way they choose. |
|
| |
|
| e. During a Vendetta or Clan Feud, Teams in Team PvP must be from the same unit, unless otherwise specified. Cooperative Events are not subject to this rule.
| | c. Members may play as many games per day as they wish, with the understanding that Clusters of Earth and Fire are managed using a Daily/Weekly cap function. For all Star Wars Games, there is a maximum of 50 Clusters of Fire for PvP modes and 50 Clusters of Fire for PvE modes per day, for a maximum of 350 CFs and 350 CEs per game per week. For non Star Wars games, there is a maximum of 30 Clusters of Fire for PvP Modes and 30 Clusters of Earth for PvE modes, for a maximum of 210 Clusters of Fire and 210 Clusters of Earth per game per week. |
|
| |
|
| === Section 2.4 - Setting up PvE / PvO ===
| | d. During a Great Jedi War or Rite of Supremacy, members will follow all competition specific rules for each competition. If competitions do not have specified rules, members will follow the guidelines in Section 2.2(a) of the Rites of Combat. |
|
| |
|
| a. Members are encouraged, but not required, to announce their intention to play PvE or PvO games in the DB Gaming Matchmaking Channel on Discord.
| | === Section 2.3 - Setting Up During Clan Feuds and Cooperative Events === |
| | |
| b. During a Vendetta, PvE or PvO that is intended to be played for the purposes of a competition must be announced in the DB Gaming Matchmaking Channel on Discord.
| |
| | |
| === Section 2.4 - Setting Up During Clan Feuds and Cooperative Events === | |
|
| |
|
| a. The Rites of Combat are still enforced, along with additional requirements, during Clan Feuds and Cooperative events. Each of these events is unique and may have additional changes to the rules, beyond what is listed here. These details will be listed with the information for each Gaming Competition, so be sure to refer to those rules and guidelines as well. | | a. The Rites of Combat are still enforced, along with additional requirements, during Clan Feuds and Cooperative events. Each of these events is unique and may have additional changes to the rules, beyond what is listed here. These details will be listed with the information for each Gaming Competition, so be sure to refer to those rules and guidelines as well. |
|
| |
|
| b. In a joint or vs. event between two (or more) clans, all gaming submissions must contain at least one player from an opposing team. | | b. In a joint or vs. event between two (or more) clans, all gaming participants must use the “party create” functions on Discord unless specific competition rules say otherwise. |
|
| |
|
| == Article 3 - Rules by Game Type == | | == Article 3 - Rules by Game Type == |
Line 102: |
Line 83: |
| a. Team Matches with less than six (6) players are played until one team reaches 20 points. | | a. Team Matches with less than six (6) players are played until one team reaches 20 points. |
|
| |
|
| b. Team Matches with seven (7) or more players are played until one team reaches 40 points. | | b. Members may choose to raise the points required to win a match of either size if they desire. This should be agreed upon in the DB Gaming Matchmaking Channel on Discord. |
| | |
| c. Members may choose to raise the points required to win a match of either size if they desire. This should be agreed upon in the DB Gaming Matchmaking Channel on Discord.
| |
|
| |
|
| === Section 3.3 - FFA Rules === | | === Section 3.3 - FFA Rules === |
|
| |
|
| a. FFA matches may include up to 10 people. | | a. FFA matches may include up to 10 people. |
| FFA matches are played until one participant reaches twenty-five (25) points.
| |
|
| |
|
| b. FFA Jedi Academy matches will be played up to fifteen (15) points for matches with up to six (6) participants. Matches with seven (7) participants or more will be up to twenty-five (25) points. | | b. FFA matches are played until one participant reaches twenty (20) points. |
|
| |
|
| c. Agree on a map with your opponents prior to the start of the game. Smaller maps are recommended, but not required. | | c. Agree on a map with your opponents prior to the start of the game. Smaller maps are recommended, but not required. |
Line 121: |
Line 99: |
| f. You may use health items to heal at any time during the game. | | f. You may use health items to heal at any time during the game. |
|
| |
|
| === Section 3.4 - PvO/PvE Rules === | | === Section 3.4 - PvE Rules === |
|
| |
|
| a. Player versus Other (PvO) is defined as when members of the DJB team up in a multiplayer match against other players who are not in the DJB. | | a. Player versus Player(PvP) is defined as when members of the DJB team up in a multiplayer match against other players who are not in the DJB, or against other members of the DJB. |
|
| |
|
| b. Player versus Environment (PvE) is defined as when members of the DJB team up against AI controlled enemies. | | b. Player versus Environment (PvE) is defined as when members of the DJB team up against AI controlled enemies. |
Line 131: |
Line 109: |
| === Section 3.5 - Gaming Platform Rules === | | === Section 3.5 - Gaming Platform Rules === |
|
| |
|
| Each individual platform may have specific rules for its use within the Dark Jedi Brotherhood. A full list of these rules can be found in the list of [[Supported Games]]. | | Each individual platform may have specific rules for its use within the Dark Jedi Brotherhood. A full list of these rules can be found in the list of [[Supported Games]]. All rules for specific platforms are considered to be a part of the Rites of Combat and must be followed. |
| All rules for specific platforms are considered to be a part of the Rites of Combat and must be followed. | |
|
| |
|
| == Article 4 - Reporting == | | == Article 4 - Reporting == |
|
| |
|
| === Section 4.1 - 1v1 PvP Reporting === | | === Section 4.4 - PvE / PvP Reporting === |
| | |
| a. All reporting is to be conducted using the @dbb0t functions in the DB Gaming Matchmaking Channel.
| |
| | |
| b. Agree on the final score with your opponent before reporting to avoid any potential issues.
| |
| | |
| c. If there is a disagreement in score, contact the Fist/P:Fist to mediate.
| |
| If there is an error in reporting, inform the Fist/P:Fist immediately.
| |
| | |
| === Section 4.2 - Team PvP Reporting ===
| |
|
| |
|
| a. Use the Submit Gaming Scores page, accessible from a member’s admin page, to report final scores. | | a. Use the Submit Gaming Scores page, accessible from a member’s admin page, to report final scores. |
|
| |
|
| b. Ensure the correct competition is selected for each participant. | | b. Ensure the correct competition is selected for each participant as necessary. |
| | |
| c. Any change of teams requires additional submissions.
| |
| Agree on the final score with your opponent before reporting to avoid any potential issues.
| |
| | |
| d. If there is a disagreement in score, contact the Fist/P:Fist to mediate.
| |
| | |
| e. All matches must be reported to the website within 48 hours of the match conclusion, or 24 hours during a Vendetta or Clan Feud/Co-op. Late submissions will be declined.
| |
| | |
| === Section 4.3 - FFA Reporting ===
| |
| | |
| a. Use the Submit Gaming Scores page, accessible from a member’s admin page, to report final scores.
| |
| | |
| b. Ensure the correct competition is selected for each participant.
| |
| | |
| c. Any change of participants requires additional submissions.
| |
| | |
| d. Ensure that placement is properly recorded after each match for ease of submission.
| |
| | |
| e. Taking screenshots of the final score screen for confirmation is encouraged in case of disagreement.
| |
| | |
| f. All screenshots must be submitted to the website within 48 hours of the match conclusion, or 24 hours during a Vendetta or Clan Feud/Co-op. Late submissions will be declined.
| |
| | |
| g. The Fist will arbitrate all FFA reporting disputes. Members have 48 hours from initial reporting of a FFA match to submit a screenshot disputing any FFA results.
| |
| | |
| === Section 4.4 - PvE / PvO Reporting ===
| |
| | |
| a. Use the Submit Gaming Scores page, accessible from a member’s admin page, to report final scores.
| |
| | |
| b. Ensure the correct competition is selected for each participant.
| |
|
| |
|
| c. Double check screenshots and modifiers prior to submission to prevent delays in proper cluster awarding. | | c. Double check screenshots and modifiers prior to submission to prevent delays in proper cluster awarding. |
Line 215: |
Line 154: |
| === Section 5.3 - Match Dodging === | | === Section 5.3 - Match Dodging === |
|
| |
|
| a. Match Dodging occurs when a member who is actively gaming ignores the queue announcement of a specific person but joins the queue after a subsequent queue announcement. | | a. Match Dodging occurs when a member who is actively gaming in an environment where use of the “party create” functions on Discord are mandatory intentionally avoids or excludes another member or group of members from play. Examples of match dodging include but are not limited to: abruptly ending a party when a certain member joins, leaving a party when a certain member joins, and creating a new party for the same game/mode of another active party with ample open slots. |
|
| |
|
| b. Multiple measures have been implemented to make match dodging a rare occurrence. PvP Leaderboards are hidden for all Vendettas, Clan Feud/Co-op, and Fist Competitions. | | b. Exceptions to the match dodging rule can be granted by the Fist and Justicar for special circumstances such as an ongoing Chamber of Justice mediation. Such exceptions will be issued in writing by the Justicar for particular members and kept on file with the Chamber of Justice. |
| | |
| | |
| | |
| d. During a Great Jedi War or Rite of Supremacy, 1v1 PvP Queue announcements are banned at all times.
| |
|
| |
|
| === Section 5.4 - Dbb0t and DB Gaming Matchmaking System === | | === Section 5.4 - Dbb0t and DB Gaming Matchmaking System === |
|
| |
|
| a. Members are not permitted to idle when signed up for matches. The bot will automatically remove members after three hours of waiting. | | a. Members are not permitted to excessively idle when creating or joining parties in the #gaming-matchmaking discord channel. Members who join parties should be added to in-game groups within a reasonable amount of time. Members who create parties should start gaming within a reasonable amount of time after the first person joins the party. |
| | |
| b. Members must use the /leave command if they are planning on not playing any more matches.
| |
| | |
| c. Repeated confirmation failures will result in the following:
| |
|
| |
|
| *First time: The member will be contacted by a member of the FIST Office through Discord PM or email on the requirements for @dbb0t and DB Gaming Matchmaking utilization.
| | b. Party owners must use the /disband party function when their group is done playing. |
| *Second time: A warning via email will be sent to the member informing them of the violation.
| |
| *Third Time: A warning via email will be sent to the member and their summit informing them of the violation.
| |
| *Fourth time: The member will receive a 24-hour PvP gaming ban.
| |
| *Additional violations: the member will receive additional 24-hour bans for each subsequent violation.
| |
|
| |
|
| d. Warnings will be reset after 90 days of proper adherence.
| | c. Members must use the /leave command if they are planning on not playing any more matches. |
|
| |
|
| === Section 5.5 - Falsifying Matches === | | === Section 5.5 - Falsifying Matches === |
Line 271: |
Line 198: |
| === Section 5.7 - Gaming Bans === | | === Section 5.7 - Gaming Bans === |
|
| |
|
| a. PVP Gaming (1v1, Team, FFA) - No PVP Gaming will be permitted for the duration of the Gaming Ban. | | a. PVE/PVP Gaming - No CFs or CEs will be earned for the duration of the Gaming Ban. The member who has been banned will not count as a second member for others to earn Clusters with when grouped. |
|
| |
|
| b. PVE/PVO Gaming - No CFs or CEs will be earned for the duration of the Gaming Ban. The member who has been banned will not count as a second member for others to earn Clusters with when grouped.
| | [[Category:Fist Policies]] |
The Rites of Combat (ROC) are the standard gaming rules for all official Brotherhood gaming activities, to include normal gaming, Tournaments and Vendetta’s. All members should familiarize themselves with the general gaming rules, as well as the rules for their platform(s) of choice.
The goal of the ROC is to provide a sense of fair play and consistency in how multiplayer competitions operate. Violations of these Rites falls under the jurisdiction of both the Chamber of Justice and the Fist.
If you encounter a member who isn’t following the rules or displays questionable behavior while competing in a multiplayer platform, direct them towards the Rites of Combat. It is also good practice for leaders to point new members to the ROC when they first join a Clan and/or House.
All competitions will follow the rules outlined under the Rites of Combat unless the person(s) running the competition specifically state otherwise in the details of an approved competition. Any alterations to rules or guidelines must be made clear prior to the start of any such competition and enforced consistently throughout the entirety of the event. Any changes made during the course of a competition must be transparently made available to all participating members.
This page is the main page for the Rites of Combat. For a list of supported games please go to the following link:
Article 1 - Rites of Combat
Section 1.1 - Purpose
The Rites of Combat (ROC) are the standard gaming rules for all official Brotherhood gaming activities, competitions, Tournaments, and Vendettas. The goal of the ROC is to provide a sense of fair play and consistency in how multiplayer competitions operate.
Section 1.2 - Application
a. Gaming competitions will follow the rules outlined under the Rites of Combat.
b. Competition organizers may alter rules and guidelines for specific competitions with express approval of the Fist.
c. Any alterations to rules or guidelines must be made clear prior to the start of any such competition and enforced consistently throughout the entirety of the event.
d. Any changes made during the course of a competition must be transparently made available to all participating members, including having them part of the publicly available competition details.
Section 1.3 - Jurisdiction
Violations of these Rites falls under the jurisdiction of both the Chamber of Justice and Fist of the Brotherhood.
Under Section 7.07 of the Covenant members are required to abide by Brotherhood policies.
Section 1.4 - Amendment
a. As per Section 1.03 of the Covenant of the Dark Jedi Brotherhood, the Fist reserves the right to amend the Rites of Combat.
b. All amendments to the Rites of Combat will be reviewed by the Justicar prior to implementation.
c. All amendments must be reported to the Membership upon enactment.
Article 2: Setting Up Matches
Section 2.1 - DB Gaming Channel
a. To participate in Brotherhood Gaming for Vendettas, and Tournaments members must be present in the DB Gaming Matchmaking Channel on Discord.
b. For PvE and PvP outside of a vendetta, presence in DB Gaming Matchmaking is strongly encouraged but not mandatory.
Section 2.2 - Setting up Gaming Matches and Events
a. During Vendettas and DB Wide Gaming Tournaments members must use the “party create” functions on Discord unless specific competition rules say otherwise.
b. For normal gaming outside of a competitive event, members are permitted to set up matches and events in any way they choose.
c. Members may play as many games per day as they wish, with the understanding that Clusters of Earth and Fire are managed using a Daily/Weekly cap function. For all Star Wars Games, there is a maximum of 50 Clusters of Fire for PvP modes and 50 Clusters of Fire for PvE modes per day, for a maximum of 350 CFs and 350 CEs per game per week. For non Star Wars games, there is a maximum of 30 Clusters of Fire for PvP Modes and 30 Clusters of Earth for PvE modes, for a maximum of 210 Clusters of Fire and 210 Clusters of Earth per game per week.
d. During a Great Jedi War or Rite of Supremacy, members will follow all competition specific rules for each competition. If competitions do not have specified rules, members will follow the guidelines in Section 2.2(a) of the Rites of Combat.
Section 2.3 - Setting Up During Clan Feuds and Cooperative Events
a. The Rites of Combat are still enforced, along with additional requirements, during Clan Feuds and Cooperative events. Each of these events is unique and may have additional changes to the rules, beyond what is listed here. These details will be listed with the information for each Gaming Competition, so be sure to refer to those rules and guidelines as well.
b. In a joint or vs. event between two (or more) clans, all gaming participants must use the “party create” functions on Discord unless specific competition rules say otherwise.
Article 3 - Rules by Game Type
Section 3.1 - 1v1 PvP Rules
a. Each 1v1 match will be played until one player reaches three (3) points, or best out of five (5). Exceptions to this rule are listed in Supported Games.
b. In combat based PvP, members may not kill their opponent as soon as they respawn.
Section 3.2 - Team PvP Rules
a. Team Matches with less than six (6) players are played until one team reaches 20 points.
b. Members may choose to raise the points required to win a match of either size if they desire. This should be agreed upon in the DB Gaming Matchmaking Channel on Discord.
Section 3.3 - FFA Rules
a. FFA matches may include up to 10 people.
b. FFA matches are played until one participant reaches twenty (20) points.
c. Agree on a map with your opponents prior to the start of the game. Smaller maps are recommended, but not required.
d. Members may not kill their opponent as soon as they respawn.
e. JA Specific: You may only use a single power weapon at a time.
f. You may use health items to heal at any time during the game.
Section 3.4 - PvE Rules
a. Player versus Player(PvP) is defined as when members of the DJB team up in a multiplayer match against other players who are not in the DJB, or against other members of the DJB.
b. Player versus Environment (PvE) is defined as when members of the DJB team up against AI controlled enemies.
c. There must be a minimum of two (2) DJB members in order to qualify for clusters of fire or earth. Single player submissions are not allowed and will be immediately rejected.
Section 3.5 - Gaming Platform Rules
Each individual platform may have specific rules for its use within the Dark Jedi Brotherhood. A full list of these rules can be found in the list of Supported Games. All rules for specific platforms are considered to be a part of the Rites of Combat and must be followed.
Article 4 - Reporting
Section 4.4 - PvE / PvP Reporting
a. Use the Submit Gaming Scores page, accessible from a member’s admin page, to report final scores.
b. Ensure the correct competition is selected for each participant as necessary.
c. Double check screenshots and modifiers prior to submission to prevent delays in proper cluster awarding.
d. All screenshots must be submitted to the website within 48 hours of the match conclusion, or 24 hours during a Vendetta or Clan Feud/Co-op. Late submissions will be declined.
Article 5 - Rites of Combat Infractions
Section 5.1 - Authority
a. The Fist has the authority under the Covenant to investigate RoC Infractions and mete out punishment for violations of the ROC.
b. The Fist is the first person to investigate possible violations of the ROC.
c. The following are the potential violation punishments:
- Written warning
- Declining of gaming activity.
- Disqualification from an event
- A gaming ban for up to one month
- Loss of progress toward awards related to gaming.
d. These punishments are independent of any action that may be taken by the Chamber of Justice.
e. Under Section 7.07(g) of the Covenant, any punishments administered by the Fist are subject to a review by the Justicar or Appeals Panel if requested by the affected member.
f. All Gaming Platforms are subject to enforcement by the Chamber of Justice. Other infractions that occur during gaming include, but are not limited to: 7.06(d) Cheating and Exploitation, 7.06(g) Crude Behavior, and 7.06(i) Disreputable Behavior.
Section 5.2 - Filing Complaints
a. If you suspect the person you are playing against is cheating or breaking the rules, use an in-game video recording program or take screenshots to record the alleged RoC violation.
b. Send any accusations to the Fist privately. The Fist will judge them on a case-by-case basis.
c. If there is someone verbally abusing another person, provide a screenshot or video of the offense and present it to the Fist. They have the authority to act on the evidence provided to resolve the situation. This extends to the DJB Gaming Matchmaking and DB Gaming Chat Channels on Discord.
Section 5.3 - Match Dodging
a. Match Dodging occurs when a member who is actively gaming in an environment where use of the “party create” functions on Discord are mandatory intentionally avoids or excludes another member or group of members from play. Examples of match dodging include but are not limited to: abruptly ending a party when a certain member joins, leaving a party when a certain member joins, and creating a new party for the same game/mode of another active party with ample open slots.
b. Exceptions to the match dodging rule can be granted by the Fist and Justicar for special circumstances such as an ongoing Chamber of Justice mediation. Such exceptions will be issued in writing by the Justicar for particular members and kept on file with the Chamber of Justice.
Section 5.4 - Dbb0t and DB Gaming Matchmaking System
a. Members are not permitted to excessively idle when creating or joining parties in the #gaming-matchmaking discord channel. Members who join parties should be added to in-game groups within a reasonable amount of time. Members who create parties should start gaming within a reasonable amount of time after the first person joins the party.
b. Party owners must use the /disband party function when their group is done playing.
c. Members must use the /leave command if they are planning on not playing any more matches.
Section 5.5 - Falsifying Matches
a. Falsifying Matches is defined as a member tries to report matches that have not been played for personal gain of Clusters of Fire, Clusters of Earth, to rank up in the GMRG, earn wins in a competition, or earn a higher place on the GMRG Leaderboard.
b. The Fist will remand the member(s) in question to the Chamber of Justice for investigation.
Section 5.6 - Unsportsmanlike Conduct
a. Interpretation of Unsportsmanlike Conduct is at the discretion of the Fist.
b. If a member is acting in an unsportsmanlike manner do not follow in suit with them, remain polite and send screenshots or audio/video recordings of the conversation to the Fist.
c. The following are examples of actions classified as unsportsmanlike conduct, this is not an exhaustive list:
- Cursing at another member (not including cursing in general conversation, which should still be avoided)
- Demeaning talk to another member.
- Talking negatively about a member in public to third parties.
- Clan/House stereotypes being levied against a person.
- Excessive gloating over a match.
d. Unsportsmanlike conduct will result in an initial warning, and may be followed by a ban if it continues.
e. Please note that warnings may carry over from event to event; members are not entitled to multiple warnings simply because you are gaming in a different competition or Vendetta.
f. If a member feels the need to drop out of a current match because of such conduct, they should notify the Fist immediately about the matches that will be reported and the reasons why you felt you needed to drop out of the match.
g. If the actions continue after a gaming ban issued by the Fist, the Chamber of Justice may seek further action.
h. Although unsportsmanlike conduct is prohibited, this policy is not meant to encourage members to report minor infractions. Someone being a sore loser (or winner) is not the same as being unsportsmanlike, and healthy competitive language is not penalized.
Section 5.7 - Gaming Bans
a. PVE/PVP Gaming - No CFs or CEs will be earned for the duration of the Gaming Ban. The member who has been banned will not count as a second member for others to earn Clusters with when grouped.