Respect other players
Keep the community welcoming. Slurs, degrading ableist language, hate speech, threats, sexual harassment, targeted abuse, and disruptive spam are not acceptable.
Community funded. No paid power. Never pay-to-win.
Our promiseClear expectations protect the world, the community, and everyone’s time.
Direct answer
AshRun is not a profanity-free server. Ordinary, untargeted profanity and mature conversation are generally allowed. Slurs, degrading ableist language, hate speech, targeted degradation, threats, sexual harassment, and attempts to evade community-safety filters are not acceptable in Minecraft or AshRun Discord spaces. Minecraft private messages sent with /m, /msg, /w, /tell, /r, or /reply—including offline inbox messages—are covered by the same rules and AutoMod review as public in-game chat.
Keep the community welcoming. Slurs, degrading ableist language, hate speech, threats, sexual harassment, targeted abuse, and disruptive spam are not acceptable.
Other players' builds, claims, containers, Pokémon, and items are off-limits without permission.
Do not use hacks, dupes, automation exploits, or bugs for an unfair advantage. Report problems instead.
Do not intentionally crash, lag, or stress the server. Build farms and machines responsibly.
Stay out of claimed areas unless invited and leave reasonable room around neighboring bases.
PvP belongs in approved areas or between players who have clearly agreed to it.
Staff decisions apply in the moment. Use Discord for calm questions or appeals rather than arguing in public chat.
Do not scam, misrepresent items, manipulate players, or abuse market systems.
Staff may clarify rules to protect the community. Material changes should be posted through official channels.
Follow the Minecraft EULA, Microsoft Services Agreement and Code of Conduct, and Minecraft Community Standards. Credible, evidence-supported violations can and will be reported to Microsoft or Mojang.
You must follow the Minecraft EULA, Microsoft Services Agreement and Code of Conduct, and Minecraft Community Standards. When staff determine there is credible, reviewable evidence of a violation, it can and will be reported to Microsoft or Mojang through an official reporting channel.
A platform report is separate from AshRun moderation and does not predetermine the outcome: Microsoft or Mojang decides any Microsoft-account or Minecraft-platform action. Knowingly false reports and fabricated evidence are themselves AshRun rule violations.
The standard focuses on the effect and context of public community language while giving ordinary conversation room to sound natural.
Ordinary, non-targeted profanity, mature conversation, and good-faith disagreement are generally allowed. AshRun is not an 18+ or explicit-content space: graphic sexual content in shared channels, sexual targeting, harassment, intimidation, and repeated disruption are not protected as ordinary mature conversation.
Ableist slurs and degrading disability language are filtered even when they are not aimed at a specific person. Do not use slurs or dehumanizing language about disability, race, ethnicity, nationality, religion, sex, sexual orientation, or gender identity. Threats, encouragement of harm, sexual harassment, and targeted degradation are also prohibited.
Do not post a prohibited word or phrase to “test” AutoMod. Testing, quoting, misspelling, spacing out, or disguising it still puts the same harmful content into a community space. It is blocked, recorded, alerted, and placed on the same enforcement slope as saying it ordinarily. Report a suspected false positive privately through help or appeals without reposting the term in public.
Discord and Minecraft stop harmful language differently. These are the published automatic baselines, not a substitute for context or staff review.
The message is blocked before posting and a private staff alert is created. Discord language AutoMod does not automatically warn, time out, kick, or ban the member. Repetition, targeting, or filter evasion may lead to a separate staff-reviewed action.
| In-game match | First automatic response | Repeat slope | Lookback |
|---|---|---|---|
| Non-targeted degrading or ableist language | Message blocked | Kick, then a 24-hour temporary restriction | 7 days |
| Targeted abuse, sexual harassment, or suicide encouragement | Message blocked and player kicked | 24-hour, then 7-day temporary restriction | 30 days |
| Hateful slur or explicit hate slogan | Message blocked and player kicked | 24-hour, then 7-day temporary restriction | 90 days |
| Hate incitement, credible real-world threat/doxing, or child exploitation | Message blocked and 7-day temporary hold | Immediate staff review; never an automatic permanent ban | 365-day safety record |
| Ambiguous safety language or child-safety reference | Message blocked | Kick if repeated | 10 minutes |
| Rapid or duplicate flooding | Matching messages blocked; continued burst causes a kick | 1-hour, then at most 24-hour temporary restriction | 24 hours |
Ordinary profanity and non-targeted mature conversation have no punishment by themselves. A filtered message never reaches its intended recipients. Calling a post a test does not excuse it or reset the slope; testing and deliberate evasion receive the same automatic treatment as an ordinary match. Failed enforcement does not add an escalation strike, and when staff overturn a false positive its exact strike is removed from future escalation. Staff may reduce, reverse, or strengthen a manual action when surrounding context, credible safety risk, history, or technical error warrants it. AutoMod never permanently bans; permanent sanctions require staff judgment and remain appealable.
This baseline covers conduct such as griefing, theft, scams, exploiting, harassment, evasion, and server harm when staff—not language automation—decide the response.
| Reviewed situation | Normal response range |
|---|---|
| Low-impact first incident | A private instruction or warning, plus removal, repair, return, or correction of the immediate harm. |
| Continued or deliberate conduct | A channel, content, or gameplay restriction; a kick; reversal or restoration; or removal of unfair gains. |
| Repeated or material harm | Usually a 1-to-7-day temporary restriction, with repair, restitution, or loss of unfair gains where practical. |
| Severe safety harm, major exploitation, or evasion | May begin at a stronger or longer temporary restriction while staff review the evidence. |
| Persistent pattern or exceptional severe harm | A longer temporary or permanent sanction only after staff judgment and review. |
This is a slope, not a rigid price list. Context, intent, actual impact, history, cooperation, restitution, evasion, and credible safety risk can move an action up or down. Staff should use the least restrictive response that reasonably protects players and the server. Every AshRun warning or sanction can be questioned privately and appealed; a separate Microsoft/Mojang report may still be made under Rule 10 when supported by credible evidence.
Slurs and targeted abuse push people out of public conversation even when the speaker describes them as a joke. The language policy protects a varied community without pretending every swear word carries the same risk.
The same core standard applies to in-game public chat, bridged server chat, Discord community channels, names, and other player-facing surfaces controlled by AshRun.
Discord AutoMod may block a matching language message before it appears and privately alert staff. Discord language automation does not itself kick, time out, or ban a member.
In-game AutoMod may block a public or private in-game message, kick a player, or apply a temporary restriction based on severity and recent repeats. Every trigger privately tells the sender that AutoMod activated, that the message was blocked, the exact automatic action taken, the incident reference when one was saved, and where to appeal; kick and temporary-restriction disconnect screens retain that explanation. Every successfully recorded in-game AutoMod event—including a blocked direct message or reply—captures the matched message and, when available, its intended in-game recipient name for authorized staff review, then queues a private Discord alert to staff. If secure evidence recording fails, the message remains blocked, no automatic punitive action is applied, the sender is told no incident ID exists, and online staff receive an immediate in-game warning. Discord delivery is monitored but cannot be guaranteed during a Discord or network outage. Automation cannot issue a permanent ban; any permanent ban requires staff judgment and review.
Hateful slurs, targeted abuse, threats, severe hate, or child-safety concerns can trigger stronger temporary protection and staff review. Ambiguous safety-related language may be blocked or cause a kick while context is reviewed. Flooding and filter evasion can also escalate, but automated outcomes remain temporary.
An automated match is evidence, not an infallible final judgment. Staff can consider context, history, severity, and technical error. Authorized staff may review Minecraft DMs carried by AshRun’s server; they do not inspect private Discord messages. Linking your account does not give AshRun access to private Discord direct messages.
Check the current item restriction list, use Discord to clarify edge cases, or report a player privately. If you believe a warning, kick, timeout, or ban was mistaken or disproportionate, use the structured appeal process instead of arguing in public chat.