1.1.1. Don’t be a jerk and don’t be immature.
1.1.2. Remember the server is for ages 13 and up. Strong language is fine, though don’t direct it at others; slurs, in any form, are not okay.
1.1.3. Don’t spam.
1.1.4. Stick to the right channels for the topic you want to discuss.
1.1.5. Speak English.
1.1.6. Use pings appropriately; never ping pointlessly. Don’t ping between midnight and noon ET unless it’s an individual who was online within the last few minutes.
1.1.7. If you are in an event, don’t leave the server; don’t leave during the season at all if you are a member of a league.
1.1.8. Don’t spoil media that has been released within the last month.
1.2.1. I Just Want To See The Rules
1.2.2. I Want To Know How The Mods Are Going To Moderate
1.2.3. I Want To Complain About Something
1.2.4. I Want To Find The Introduction Section
1.3.1. Breakdowns
1.3.2. Explanations
1.3.3. Philosophies
1.3.4. Moderator Manual And Training Guide
2.1.1. Summary
2.1.2. RSC is for everyone. That does not mean that everyone will enjoy every part of RSC’s events. That does not mean that everyone will enjoy even a single RSC event. That does not mean that everyone will be friends, or even that everyone will get along. It does mean that RSC will endeavor to not turn people away when they have given us no cause to do so. It does mean that RSC will endeavor to make people feel welcome. It does mean that we will punish or ban individuals as needed if they harm this cause. It does not mean we will punish or ban an individual because a single other person does not want them there.
2.1.3. RSC does not discriminate against individuals based on their age, parental status, career/employment status, hobbies, disabilities, gender identity, sex, sexual orientation, lawful sexual activity, marital status, physical features, political beliefs or activity, physical conditions, race, ethnicity, religious beliefs or activities, social class, origins, or association with others based on any of the above characteristics. We may place limits on participation in specific events based on some of these characteristics, such as age (example: a tournament for those 30 and up, or those under 18). We will only ever do so in a polite, respectful, and fair way, when possible seeking to help some group through additional opportunities for them.
2.1.4. RSC should be a safe space, in the sense that people should not fear discrimination in any of the above categories, nor should they fear personal attacks. It does not mean that people will be shielded from new ideas, nor does it mean that we can prevent individuals from being put in situations that may affect them negatively due to their own history. It does not mean that RSC is opposed to freedom of speech. It does mean that we will not respect any “right” that individuals may feel they have to harm others through words or actions. It does mean that there should be rules of behavior to indicate what individuals should be prepared to encounter, and what they should expect to see punished.
2.1.5. RSC does not discriminate based on age, but it does reserve the right to discriminate based on maturity level. Some individuals, be they five or fifty-five, may act immaturely with great enough frequency that RSC may block them from taking up certain roles or participating in certain events. Maturity of an individual will be judged primarily based on two things: their ability to follow rules and their interactions with members of RSC.
2.1.6. RSC should pay attention to the concerns of its members, particularly in regards to the behaviors of others. If a member reports a concern about another member’s behavior, regardless of who the behavior was directed at or the severity of the offense, RSC should not forget the matter. RSC should endeavor to follow up with concerns according to the behavior rules and guidelines.
2.2.1. Moderation should be done confidently. Moderators should feel empowered to enforce the rules. They should not feel like they will have their every action questioned.
2.2.2. Moderators should not be expected to be perfect, by the staff or the community. Mistakes happen. Apologies will need to be delivered, by the individual in question when possible and by the staff as a whole when needed.
2.2.3. Moderation should be as swift as is reasonably possible. Delayed consequences lead to lesser effect, and more disconnect between the event and the consequences. They can also lead to a snowballing effect in the community, leading to more trouble and encouraging others to commit similar misbehaviors.
2.2.4. Moderators should present a united front. Moderators may not always agree, but public argument leads to a reduction of faith in RSC staff. Disagreement should be handled in staff-only channels, and a final resolution be presented to the public as needed. Should moderation be recognized as probably problematic by the staff, lesser punishments (such as temporary mutes) should stay while greater punishments (such as match suspensions) should be lifted until a consensus is reached. Public statements should be minimal until a final official statement can be made.
2.2.5. Moderators should be as clear as possible when moderating. Specific rules should be referenced when broken. Catch-all misbehavior categories may be used when others do not fit, with several strikes delivered if needed. Members should be able to DM and ask questions. They are not entitled to more than one clear explanation, however, nor is a moderator expected to deal with a debate for every punished misbehavior. Not debating does not make the moderator’s decision wrong. If a player wishes to make a formal complaint or have a moderator’s behavior looked at by others, they should contact the Mod Committee head, or use the RSC Modmail bot to contact RSC staff.
2.2.6. Moderators should not expect discussion before every moderation call. Any discussion should happen after the first moderator to respond chooses to take action or chooses not to. A moderator who chooses to not take action may change their mind.
2.2.7. For moderation calls of lesser consequence (where the punishments are things like simple timeouts, or where there are levels of warnings built into the system), moderators should lean towards preferring more decisive moderation. For moderation calls of greater consequence (suspensions or other cases where the individual is missing out on events of great importance to RSC), moderators should act with caution. For cases of permanent or difficult-to-undo moderation (bans), there should always be a reasonable amount of discussion first, except in rare cases (such as blatant spammers). This should never lead to someone not receiving punishment for rules they’ve broken in accordance with currently set-out consequences.
2.2.8. Moderators who are still being trained or otherwise limited should always defer to full moderators. Moderators should defer to admins. Any other set indicators of hierarchy in the staff should be obeyed. This does not mean silent acceptance, but it does mean not going against their final declarations on matters. Defiance of the set hierarchy in a non-constructive manner (such as making public references in a disrespectful manner) is an indication that an individual is too immature to moderate fairly and reasonably.
2.2.9. Moderators are not beholden to understanding the full context of a situation. Context of a misbehavior that reaches outside of the RSC Discord should be ignored by moderators, except as is made clear inside of the RSC Discord by members shortly before or after the misbehavior. (Note that videos, GIFs, long texts, or other material that takes some effort to absorb does not count as providing clear context.) Moderators are not expected to understand every reference made by members, and will have to judge each situation without external references except in rare cases. Even in the case of a moderator understanding a reference, they should consider how members who do not know the reference would see it, and if it breaks a rule without that context. Moderators should pay attention to misbehaviors in the context of past misbehaviors only in how they might make a misbehavior more severe.
2.2.10. Moderators should go outside of the set structure of consequences as rarely as possible. Leniency should be set by the structure and the rules, and further leniency should be given only very rarely. Harsher consequences than set forth in the rules should be given even more rarely. (Cases of multiple strikes for a single action, when following the guidelines given, do not count as going outside of the rules.)
2.2.11. Moderators are not the parents of the community. They have no obligation to try and teach you morality or improve your attitude in your out-of-RSC life. We are trying to run a community that is pleasant to be in. Therefore, there is a cut-off point where it is highly unlikely that a trouble-causing individual will improve their behavior, and they should be banned if the trouble is severe enough or occurred frequently enough. Likewise, there is a cut-off point for moderators taking time to ensure members understand the rules.
2.2.12. Moderators of both the RSCC and RSCSC(1v1) servers will moderate collaboratively. Strikes will accumulate collectively across both servers. Any member of either server that is struck in one league will serve punishments in both league servers.
2.2.13. If you leave either server while you have a contract in progress, you will be suspended from playing for both the current seasons. This only applies if you are on contract when you leave the server, it does not apply if you leave as a free agent or in offseason.
2.3.1. Clearer rules are better than vague rules. Moderator discretion is an important part of moderation, but the community should not have to rely on learning the personalities and tolerance levels of moderators in order to avoid breaking rules and receiving consequences.
2.3.2. Simpler rules are better than more complex rules. More complex rules are better than rules that are frequently misinterpreted.
2.3.3. Doing a misbehavior twice is worse than doing it once. Consequences should follow a logical scaling with repetition.
2.3.4. Consequences should be set in advance whenever possible.
2.3.5. Cases of bans should always be reviewed before an actual ban occurs (barring rare cases, usually related to spam or non-person members); they should instead receive an alternative severe punishment if the ban does not occur.
2.3.6. How consequences scale should reflect the severity of the misbehavior committed. Consequences may scale both in the severity of the starting and ending punishments, and by the linearity of the increase in severity as repetition of a misbehavior increases (that is, how quickly the punishments get worse).
2.3.7. When a misbehavior happens, a player’s general manager will be notified of the misbehavior and where the member stands with their strikes.
3.1.1. Being generally disrespectful, rude or toxic to community members
3.1.2. Explicit Conversations
3.1.3. Excessively spamming text chat with text or reactions
3.1.4. Spamming voice chat/spam joining voice
3.1.5. Misuse of channels
3.1.6. Non-English text in chat
3.1.7. Misusing group/staff pings or pinging staff as a joke
3.1.8. Asking for specific punishments for yourself or another
3.1.9. Baiting other community members
3.2.1. Conduct detrimental to RSC
3.2.2. NSFW images or descriptions
3.2.3. Swearing directed at another member
3.2.4. Lying to staff
3.2.5. False accusations of serious offense
3.2.6. Falsely/incorrectly reporting scores
3.2.7. Spoiling recent media
3.2.8. Discussing politics, religion, or other serious real-life topics in bad faith or an offensive manner
3.2.9. Testing or baiting mods
3.2.10. Attempting to time misbehaviors to minimize punishments
3.2.11. Encouraging drama or rule-breaking, or promising to do so
3.2.12. Pinging @everyone
3.2.13. Abusing members of the community
3.3.1. Posting scam/spam links
3.3.2. Using slurs or bigoted speech
3.3.3. Impersonating members or staff
3.3.4. Serious (death/assault) threats
3.3.5. Other cheating
3.3.6. False accusations of serious offense towards staff
3.3.7. Attempting to bypass punishments
3.3.8. Retaliating against staff or members
3.4.1. Throwing Combine games or combine sandbagging
3.4.2. Breaking Rocket League TOS
3.4.3. Throwing a match or fixing matches
3.4.4. Rage quitting
3.4.5. Leaving the server while mid-event (including RSCC)
3.4.6. Collaborating to commit misbehaviors
3.4.7. Committing misbehaviors within 24 hours after a timeout
3.4.8. Bot Abuse
3.4.9. Using incorrect in-game names
3.4.10. Spam or chains in tier chats
3.5.1. Upon receiving a sufficient report of toxicity in the RSC 6mans/4mans queues, players will be given a verbal or written warning.
3.5.2. After a second report, the player will be removed from all applicable 6mans/4mans queues for one week.
3.5.3. After a third report, the player will be permanently removed from all applicable 6mans/4mans queues.
3.5.4. The Moderation Committee reserves the right to skip any of these steps depending on the severity of the misbehavior.
4.1.1. Abusing player trust
4.1.2. Misleading players
4.1.3. Failing to respond to player concerns
4.1.4. Breaking other GM guidelines
4.1.5. Committing misbehaviors in the Meta category
4.1.6. Committing other misbehaviors
4.1.7. Toxic/unpleasant team Discord
4.2.1. Abusing player trust
4.2.2. Misleading players
4.2.3. Failing to respond to player/GM concerns
4.2.4. Breaking other staff guidelines
4.2.5. Committing misbehaviors in the Meta category
4.2.6. Committing other misbehaviors
4.3.1. How GMs And Staff Members Are Punished
4.3.2. Stages
5.2.1. Multi-Rule Breaking
5.2.2. Multiple Strikes
6.1.1. Appealing moderator actions refers to going to a higher authority in RSC (than the individual moderator who took the actions in question) in order to have moderator actions partially or fully overturned.
6.1.2. Requesting a moderator review refers to asking a higher authority in RSC, usually the Arbiters to examine whether or not a moderator’s actions and behavior is in line with RSC’s views and the behavior rules and guidelines.
6.2.1. You should appeal a moderator’s actions when you believe you did not commit one or more of the misbehaviors you were given consequences for, or if you believe the punishment was out of line or inconsistent with the current behavior rules and guidelines.
6.2.2. You should not do it if you simply disagree with the behavior rules and guidelines. Just because you think a rule should not exist does not give you the freedom to break it whenever and wherever you wish.
6.2.3. You should request a moderator review if you feel they acted rudely or otherwise inappropriately for a moderator and representative of RSC. You can also request a moderator review if you believe a moderator is clearly acting with bias towards or against some individual or group.
6.2.4. You should not request a moderator review if you have no reason beyond personally not liking the moderator or because another individual asked you to.
6.3.1. You can appeal the actions of a moderator by contacting the Mod Committee Head and stating that you would like to appeal. Please specify what strike you were given that you’d like to appeal.
6.3.2. The Mod Committee Head will be responsible for setting up the appeal channel in the RSC Appeals Server. One channel will outline relevant rules that apply in the case, as well as evidence. Another channel will be created so the member who is making the appeal can put forth their case for why they are appealing.
6.4.1. Players will be allotted two appeals per season. This appeal limit will reset with the Forgiveness cycle each season.
6.4.2. The Mod Committee reserves the right to deny any player an appeal that is deemed abusive of the system or egregious in nature.
6.5.1. The Arbiter Process is Outlined in the Arbiter Handbook, which can be found here:
6.5.2. RSC Arbiter Handbook
7.2.1. Any minor offenses give the player a single point on their record.
7.2.2. Any normal offenses give the player two points on their record.
7.2.3. Any serious offenses give the player three points on their record.
7.2.4. The accrual of 5 points leaves the member open for a ban from the mod committee, regardless of where they stand on the regular punishment scales.
7.4.1. The member, upon reaching 5 total points, will be placed on enforced break.
7.4.2. The mod committee will examine the offences and have two weeks to determine if a ban is justified.
7.4.3. If the mod committee determines a ban is not justified, the player will still serve the appropriate punishment for the strike, and be placed back at 4 points, unless the first week has passed, in which case, the new player period is over.
7.4.4. If the two weeks has passed and the committee could not reach a decision, the player cannot be banned under the new player period, and the new player period will have passed.
8.1.1. The Purpose of this section is to explain when an arbiter decision clarifies how a rule is to be enforced, and only when that occurs. Not every arbiter decision will be listed here, only those that impact the enforcement of rules in the future.
8.2. Regarding “3.1.3 Abusing members of the community” the Arbiters clarified that the mod committee has the right to strike instances of abuse outside of the RSC discord in any RSC context.
8.3. Regarding: 3.5.4 Attempting to bypass punishments: The Arbiters clarified that so long as it is disclosed before the punishment is up so strikes can be properly applied to the main account, simply using an alt and breaking rules is not an instance of “attempting to bypass punishment.”
8.4. Regarding 3.1.10: Arbiters ruled inconsistent application of this rule had been taken place, as suggested by an arbiter, an announcement was made that stricter enforcement will be taking place.
9.3.1. Upon being reinstated following a ban, the individual will enter into a Probationary Period. This period will last one calendar month from the day they rejoin the server. During this one month period, any strike received by the individual will result in an automatic and permanent (unappealable) ban from RSCC and RSCSC.
9.3.2. If the individual receives a strike after the initial Probationary Period has ended, they will automatically be placed under another Probationary Period lasting a calendar month. If the individual gets another strike during this period, they will be automatically and permanently banned from RSCC and RSCSC. This cycle will repeat indefinitely for three seasons (one year), after which the individual will be subject to the same moderation as the rest of the members of the servers.