Kickback Kingdom - Discord
Navigation
Community Policy

Kickback Kingdom Dissident Protocol

The Dissident Protocol is our promise to protect fair games, good-faith competition, and welcoming community spaces.

Need help now?

Start a moderation action

Use these shortcuts during disputes, then add details and evidence in the ticket.

What it protects
  • Fair play
  • Respectful spaces
  • Community trust
How it works
  • Reports and evidence
  • Moderator review
  • Strikes and Dissident flag
How to recover
  • Positive behavior
  • Strike expiration
  • Support ticket appeals

The Dissident Protocol applies to both ranked play and Kickback community spaces. Our goal is simple: protect fair matches, keep conversations respectful, and offer a clear path back when mistakes happen.

Overview

Protocol at a Glance

Quick Answers

What do I need to know?

Jump to the details behind the most common moderation questions.

Learn more about the Dissident Protocol

Start with the overview, review strike-eligible conduct, or jump to consequences and recovery.


Overview

Review & Enforcement Flow

How the Dissident Protocol Works

The Dissident Protocol is designed to be careful, consistent, and fair. Each concern is reviewed with context so community members understand what happened, what action may be needed, and how to move forward.

Report received

Reports and context are gathered before action is considered.

Moderator review

Moderators weigh evidence, history, and impact fairly.

Arbiter of Truth review

Disputed cases can escalate to the Arbiter of Truth.

Outcome/recovery

Members receive the outcome and any recovery path.

Community standard

Core Community Values

Kickback Kingdom is built for friends, fair competition, creativity, streams, chill hangouts, and deep discussions. These values explain what we protect before moderation ever becomes necessary.

Respect the people

Banter, debate, and rivalry are welcome when people still feel safe to queue up, speak, create, and return tomorrow.

Compete with integrity

Wins should come from skill, teamwork, preparation, and creativity—not cheating, sabotage, harassment, or manipulation. Competitors must read the rules for each event before playing; the agreed-upon written rules are always what will be upheld.

Speak with context

Different spaces have different tones. Read the room, follow posted expectations, and move disagreements toward clarity instead of escalation.

Leave a path back

Accountability should repair trust where possible. Members who understand the issue and stop the harm can work back toward good standing.

Our moderation goal is simple: protect the room so good people can play hard, speak freely, grow together, and recover when mistakes happen.

Reports are judged by behavior, context, impact, and willingness to correct course—not popularity, rank, donor status, or personal grudges.

“Everything can be solved with patience and understanding.”

Conduct

Strike-Eligible Conduct

Conduct Watchlist

Strike-Eligible Conduct

These conduct types can threaten fair play or community trust. Open each item for examples, possible consequences, and the evidence moderators may consider across web spaces, voice chats, games, streams, meetups, and official events.

Context
Intent and impact matter.
Evidence
Logs, clips, and reports help.
Escalation
Repeat issues raise risk.

What it means: Treat other members, creators, competitors, staff, guests, and event attendees with respect in every Kingdom space.

Examples: Extremely disrespectful behavior, hateful or racist remarks, hostile personal attacks, threats, slurs, demeaning someone in voice chat, or escalating a disagreement into abuse.

Possible consequences: Reminder, mute, kick, strike eligibility, official-space restrictions, Dissident flag escalation, or immediate bans for severe hate, threats, or targeted abuse.

Evidence moderators may consider: Screenshots, clips, chat logs, voice moderation notes, eyewitness reports, event staff notes, prior warnings, deleted-message records, and whether the conduct stopped when corrected.

What it means: Different Kingdom spaces may allow different levels of competitive banter, mature debate, roleplay, strategy critique, or high-energy commentary. Know the expectations before joining and step away from spaces that are not a fit.

Examples: Repeatedly derailing an intense debate, demanding that an event or game lobby change its posted tone for you, escalating after staff explains the space expectations, or turning normal competition into repeated complaints about allowed banter.

Possible consequences: Reminder, temporary mute, removal from the specific space, event or lobby restriction, strike eligibility when disruption repeats after correction, or stronger action if paired with harassment or threats.

Evidence moderators may consider: Posted space expectations, staff instructions, chat or voice logs, event context, prior reminders, whether the member was offered another space, and whether the disruption continued after correction.

What it means: Do not flood conversations, event spaces, game lobbies, support systems, streams, or gameplay systems in ways that make participation difficult for everyone else.

Examples: Repeated small messages, excessive pings, copy-paste walls, mic spam, repeated low-effort reports, lobby invite spam, trade spam, or repeated in-game actions intended to drown out normal play.

Possible consequences: Message removal, mute, kick, rate limits, event removal, support restrictions, strike eligibility for repeated or coordinated spam, or stronger action when spam is used for harassment or evasion.

Evidence moderators may consider: Message volume, timestamps, voice moderation notes, invite or report logs, stream chat records, gameplay telemetry, prior warnings, and whether multiple members or systems were disrupted.

What it means: Stay cool, play in good faith, and respect the integrity of games, quests, tournaments, streams, and official events.

Examples: Poor sportsmanship includes sabotaging teammates, cheating, trolling, stream sniping, harassment, griefing, refusing basic event instructions, or retaliating after a loss.

Possible consequences: Match kick, event disqualification, reward removal, ranked restrictions, strike eligibility, Dissident flag escalation, or stronger action for coordinated or repeated misconduct.

Evidence moderators may consider: Match logs, event staff notes, replay clips, stream VODs, team communications, objective participation, witness reports, and prior similar incidents.

What it means: Intentionally harming your own team, leaking strategy, throwing matches, or betraying a declared alliance without first ending that alliance clearly and officially.

Examples: Feeding opponents on purpose, refusing objectives to force a loss, giving enemy players team callouts, or turning on an alliance while still claiming to honor it.

Possible consequences: Match removal, ranked restrictions, a strike, Dissident flag escalation, or longer action for coordinated match manipulation.

Evidence moderators may consider: Match logs, replay clips, team chat, voice reports, objective participation, alliance declarations, repeat patterns, and statements from affected teammates.

What it means: Using hacks, exploit abuse, scripts, unauthorized automation, account sharing for unfair ranked advantage, or outside tools that create an unfair competitive edge.

Examples: Aim or movement assistance, map or hidden-information overlays, macro abuse, duplicated resources from an exploit, or intentionally queuing with a cheater.

Possible consequences: Immediate ranked removal, strike or severe-offense handling, loss of rewards, temporary or long-term bans, and action against alternate accounts used to evade penalties.

Evidence moderators may consider: Anti-cheat signals, server telemetry, replay review, impossible input patterns, exploit reproduction steps, inventory or economy logs, reports from multiple players, and prior warnings.

What it means: Deliberately provoking players, derailing matches or discussions, or continuing disruptive behavior after being asked to stop.

Examples: Baiting arguments in chat, repeatedly interrupting voice chats, fake-report threats, queue dodging to annoy a group, or dragging disputes into unrelated spaces.

Possible consequences: Moderator reminders, temporary mute or kick, strike eligibility for repeated disruption, or broader restrictions when trolling targets specific members.

Evidence moderators may consider: Chat logs, voice moderation notes, timing of repeated disruptions, prior warnings, deleted-message records, user reports, and whether the conduct stopped when corrected.

What it means: Using livestream information, creator delay gaps, or spectator knowledge to gain an unfair in-game advantage or target a streamer.

Examples: Rotating based on a visible stream map, targeting hidden bases shown on stream, sharing stream-only callouts with teammates, or repeatedly queueing into a creator to disrupt them.

Possible consequences: Match removal, strike eligibility, ranked restrictions, event disqualification, or escalation for coordinated targeting.

Evidence moderators may consider: Stream VOD timestamps, queue timing, player movement patterns, chat admissions, teammate communications, repeated match history, and whether stream-only information was acted on.

What it means: Verbal abuse, hostile direct messages, stalking behavior, targeted offensive messages, or repeated unwanted contact that makes a member feel unsafe or unwelcome.

Examples: Insults aimed at protected traits, threats, repeated direct messages after being told to stop, brigading a player across Kingdom spaces, or encouraging others to dogpile a target.

Possible consequences: Mutes, kicks, strikes, official-space restrictions, Dissident flag escalation, or immediate bans for threats, doxxing, or coordinated harassment.

Evidence moderators may consider: Screenshots, message links, direct-message records, timestamps, witness reports, moderation logs, prior boundary-setting, deleted-message records, and cross-space behavior patterns.

What it means: Intentionally ruining gameplay by blocking progress, stealing key resources, teamkilling, trapping players, or destroying shared work without a legitimate gameplay reason.

Examples: Blocking quest turn-ins, breaking team defenses at the worst moment, hoarding required items to stall a group, or repeatedly killing allies outside agreed rules.

Possible consequences: Match kick, resource or reward removal, temporary server restrictions, strike eligibility, or stronger action for repeated destructive behavior.

Evidence moderators may consider: Server logs, replay clips, inventory changes, build or destruction history, objective timing, team communications, affected-player reports, and prior similar incidents.

Recovery

Consequences & Recovery

Severity Guide

Consequences & Recovery at a Glance

These examples are not fixed punishments or promises for every case. Moderators consider intent, evidence, impact, prior history, and whether behavior stops when corrected.

Case-by-case
No automatic scripts.
Recovery
Positive behavior counts.
Severe cases
May bypass strikes.
Severity Examples General treatment
Reminder or warning One-off off-topic spam, heated but non-targeted trash talk, accidental disruption, or minor rule confusion that stops when corrected. Usually handled with a reminder, warning, or moderator note so the player can correct course before it escalates.
Temporary mute or kick Continuing an argument after a warning, flooding chat, disrupting voice, refusing to leave a tense discussion, or short-term griefing that can be stopped immediately. Often handled by cooling down the space with a temporary mute, space removal, match kick, or server kick.
Strike Verified harassment, targeted offensive messages, deliberate griefing, team sabotage, stream sniping, match throwing, or repeated disruption after staff intervention. Typically becomes strike-eligible when the conduct is intentional, targeted, affects match integrity, or repeats after clear correction.
Dissident flag Three active strikes, repeated ranked misconduct, a pattern of evading moderation boundaries, or ongoing disruption across multiple official spaces. Can temporarily restrict ranked queues, official servers, trading, marketplace access, and stores while the player demonstrates improved behavior.
Severe offense Cheating tools, exploit abuse, match manipulation, ban evasion, alternate accounts used to bypass penalties, threats, doxxing, or coordinated harassment. May bypass normal strike progression and lead to long-term or permanent restrictions when needed to protect players and competitive integrity.

How Strikes Work

  • Verified misconduct in ranked play or official Kickback spaces can issue a strike.
  • At 3 active strikes , an account receives a Dissident flag .
  • Strike duration may vary by offense type and can expire after sustained positive behavior.
  • Reviews may include reports from multiple members, moderator logs, interviews, and match evidence.

Dissident Flag Effects

  • Temporary removal from ranked queues.
  • Temporary removal from Kickback official servers.
  • Temporary suspension from player trading, marketplace access, and stores.
  • Penalty length depends on offense severity and prior history.
  • Violations during the penalty window can escalate consequences.

The Path Back

Recovery starts with showing the community that the issue is understood and will not repeat. Use the steps below to move from a strike, restriction, or Dissident flag back toward good standing.

Acknowledge the issue

Review the moderation notice, match report, or community concern and identify the specific behavior that caused harm. A useful response focuses on what happened, what rule or expectation was missed, and what you will do differently instead of blaming other players or moderators.

Avoid repeat incidents

During any strike or penalty window, avoid ranked disputes, hostile direct messages, retaliation, evasion attempts, and edge-case behavior that could look like the same issue again. If a situation is heated, step away, mute, report, or ask staff for guidance before it escalates.

Let strikes expire or request review

Some strikes expire after the listed duration when there are no new related incidents and account behavior stays positive. If you believe a strike, restriction, or Dissident flag was issued in error, you can request a high-level review through support rather than arguing the case in public spaces.

Bring helpful appeal context

The best appeal evidence is specific and verifiable: match, server, or event names, dates, approximate times, usernames involved, screenshots, clips, chat logs, prior reports, and a short explanation of what context you think was missed. Do not edit evidence or pressure other players to support an appeal.

Know what happens after a ticket

After you submit a support ticket, the team reviews the account history, available evidence, and the context you provided. You should expect a written response when the review is complete; staff may uphold the action, reduce it, remove it, or ask for more information. Submitting duplicate tickets or reopening the dispute in community spaces can slow the process.

Final Authority

Authority & Final Review

Final Authority

Authority & Final Review

Most disputes are settled by the Arbiter of Truth. Admins only step in when policy oversight or final review is needed.

  1. Moderator Review
    Initial evidence and context review.
  2. Arbiter of Truth
    Settles disputes using Kingdom principles.
  3. Admin Final Review
    Only for escalations, policy issues, or final authority.
Arbiter of Truth:
No Arbiter of Truth accounts are currently listed.
Policy version: 2026.05.14 Last reviewed: May 14, 2026
Request Moderation Review

Need a Review?

If you believe a moderation action was incorrect, request a review through a support ticket. Include the action you want reviewed, relevant dates, and any context or evidence that can help the team make a fair decision.

Evidence checklist:

  • Moderation action, strike, restriction, or message you want reviewed.
  • Date of the action and any related match, server, event, quest, or community space.
  • Context, screenshots, clips, logs, witnesses, or other missing details.
Open Support Ticket

Report Misconduct

If you witnessed harassment, cheating, match disruption, or other conduct that may violate the Protocol, submit a report with specific details so moderators can review it efficiently.

Evidence checklist:

  • Account/usernames involved and when it happened.
  • Match, server, event, quest, or community space where it occurred.
  • Screenshots, clips, logs, report IDs, or witnesses.
Report Misconduct