Uros Roleplay · Community standards

Server Rules

These standards apply across the Minecraft server, forums and official Uros community spaces. They protect fair roleplay and the people taking part in it.

Need help?
16+ CommunityUros is intended for players aged 16 and over.
IC is not OOCCharacter conflict must not become personal conflict between players.
Fair play firstIf a mechanic, loophole or piece of information gives an unintended advantage, do not abuse it.
Read the rule, not just the example.

Examples explain the standard but cannot cover every situation. Moderation will consider what happened, the harm caused, intent, relevant history and whether somebody tried to exploit a loophole.

Uros is a roleplay community first. Disagreement between characters is expected; harassment between players is not. Treat the person behind the character with basic respect even when your characters are enemies.

Community conduct

  • No racism, homophobia, sexism, religious hatred or comparable hate speech.
  • No targeted harassment, bullying, threats, dogpiling or sustained attempts to make another player feel unwelcome.
  • Do not deliberately provoke public drama or continue a personal dispute after staff have directed it into the proper support route.
  • Do not impersonate staff or use fabricated evidence to influence a report.

Age requirement

Uros is a 16+ community. Players below the minimum age must not use the server or associated community spaces. Deliberately misrepresenting your age may result in removal.

IC / OOC separation

Insults, arrests, rivalry, political conflict and betrayal can be valid in-character actions. They do not give permission to insult, harass or target the player out-of-character.

Your character may only act on information, abilities and circumstances they can legitimately know or achieve in-character. Roleplay is collaborative: describe attempts where another player reasonably needs a chance to respond.

Metagaming

You read in Discord that an ambush is happening and immediately send your character there prepared for it.

Valid

Your character hears an in-character warning, receives a bird or witnesses something that gives them a reason to investigate.

Powergaming

“Hits the guard and knocks him unconscious instantly.” The outcome is forced onto the other participant.

Valid

“Swings the hilt toward the guard's temple, attempting to knock him unconscious.” The other side can respond.

Characters, alts & lore

  • Alternate characters are separate people. Do not transfer knowledge, political intelligence, items or advantages between them through OOC coordination.
  • Do not create an alt to evade criminal, social, economic or roleplay consequences affecting another character.
  • Approved lore, race traits and magic limits apply. Your character cannot invent powers or exceptional abilities because they are useful in a scene.
  • Do not use nametags, the live map, staff information, streams or other OOC sources as character knowledge.

Combat should arise from roleplay and produce roleplay. It is not a shortcut around interaction or a reason to attack people at random.

InitiationThere must be a clear RP reason and enough context for the other side to understand that conflict is occurring.
No RDMRandom or context-free attacks are not acceptable.
No combat loggingDo not disconnect to avoid capture, injury, death, search, theft or an active staff review.
Respect outcomesFollow the server's unconsciousness, death and permadeath systems and any event/moderation ruling that applies to the scene.
  • Do not force injuries, death, capture or impossible physical outcomes through emotes.
  • Use the server's roll systems when the scene or participants need a neutral uncertain outcome.
  • Do not re-enter an active conflict through an alt or by using OOC information after your character has been removed from the scene.
  • If a rules dispute starts during combat, preserve the scene where reasonably possible and use /modreq rather than turning local/OOC chat into an argument.

Property mechanics establish what can be interacted with mechanically; roleplay establishes why. Do not bypass either through glitches or OOC coordination.

Locks and containers

  • Private locks are private. Do not bypass them through glitches, hoppers, block updates, desync or other unintended behaviour.
  • Public locks intentionally allow normal interaction while protecting ownership.
  • Donation containers are intended for deposits, not unauthorised withdrawals.
  • Password locks may form part of IC security. Do not share passwords OOC to defeat a scene or property system.

Theft and trespass

Theft from accessible property may still be an in-character crime. Mechanical access does not mean an action has no roleplay consequence. Exploiting the plugin to obtain access you should not have is a rules violation, not legitimate theft RP.

Use communication systems for their intended purpose. The fact that a message is private does not make harassment or rule-breaking acceptable.

  • Keep IC and OOC channels separate and follow channel-specific restrictions.
  • Do not spam chat, birds, private messages, help channels or staff requests.
  • Birds are an in-character communication system. Their content and delivery should be treated as part of the world.
  • Do not use DMs to continue harassment or pressure somebody who has disengaged from a dispute.
  • Use /modreq for in-game moderation support and #need-help for appropriate community support. Do not knowingly submit false or malicious reports.
  • Do not edit, crop or present evidence in a deliberately misleading way.

Uros is a shared world. Your actions should respect active settlements, server systems and the visual/lore standards of the setting.

  • Build within the medieval-fantasy setting and any settlement/build guidance that applies to your area.
  • Do not grief, deliberately scar terrain or damage another player's work without an authorised game mechanic or staff-backed roleplay context.
  • Do not manipulate shops, treasuries, crafting stations, professions, storage or currency systems in ways clearly outside their intended use.
  • If a system produces an obviously unintended reward, duplication or permission result, stop using it and report it.
  • Staff may restore, roll back or remove gains caused by bugs or abuse even where the system technically allowed the action.

Do not use software, bugs or unintended mechanics to obtain information, movement, items, access or other advantages that normal players are not meant to have.

  • No hacked clients, x-ray, fly hacks, dupes, packet abuse or comparable cheats.
  • No intentional exploitation of locks, shops, treasuries, combat, crafting, professions, inventories or custom systems.
  • Cosmetic or accessibility modifications are acceptable only where they do not reveal hidden information or automate/alter gameplay in an unfair way.
  • If you discover a bug, report enough to reproduce it safely. Do not repeatedly test it on the live server for profit or advantage.
  • Items, currency or progress gained through an exploit may be removed regardless of whether a separate sanction is imposed.

Dark or difficult stories can exist without ignoring participant boundaries or community safety.

  • No ERP or explicit sexual roleplay/content.
  • Sexual violence roleplay is prohibited.
  • Graphic torture, self-harm/suicide themes or similarly intense material must not be sprung on unwilling participants. Use staff/event guidance where a planned story needs unusually sensitive material.
  • Do not publish, threaten to publish or seek another player's private identifying information.
  • Do not share private staff or player communications for harassment, doxxing or targeted abuse.
  • If somebody asks to step away from an OOC-sensitive discussion, respect that boundary and use staff support if the underlying RP issue still needs resolution.
Enforcement

How moderation decisions work

Sanctions are guidance, not an automatic five-strike tariff. Moderators should apply the response that is proportionate to the actual incident and escalate serious cases for senior review.

Low impactMinor disruption, first-time channel misuse, low-level RP mistakes.

Guidance, verbal/formal warning, scene correction, short mute or kick where needed.

Moderate / repeatedRepeated rule-breaking, material metagaming/powergaming, harassment, property or economy abuse.

Formal warning, rollback/confiscation, temporary mute or temporary ban, plus relevant RP correction.

SeriousMajor griefing, exploit abuse, serious harassment, deliberate evidence manipulation, significant evasion.

Longer temporary ban, substantial rollback/confiscation and senior Moderation or Administration review.

CriticalSevere hate speech, doxxing, serious threats, major cheating/exploit chains, safeguarding or security risks.

Immediate protective action up to permanent removal may be appropriate. Serious outcomes are recorded and reviewed under the Moderation SOP.

Context matters. Severity, intent, harm, relevant history, cooperation, evasion and attempts to exploit loopholes may all affect the outcome.

Follow immediate directions first. A moderator may temporarily pause a scene or remove somebody to stabilise an incident. That protective action is not automatically the final finding.

Significant decisions can be reviewed. Use the proper appeal/support route rather than reopening the case through public arguments or repeated tickets.

Unsure whether something is allowed? Ask before doing something difficult to reverse. In game use /modreq; for wider support use #need-help.