01
IN-GAME CONDUCT
Minecraft Gameplay Rules
1.1 Raiding, Griefing, and PvP
The following activities are permitted:
- Attacking and eliminating other players.
- Stealing items from other players.
- Raiding bases and structures.
- Destroying or modifying other players’ builds.
- Setting traps and defending territory.
Restrictions- These activities must not intentionally damage server performance.
- Deliberately crashing, freezing, or disrupting the server is prohibited.
- Raiding and griefing do not excuse cheating, harassment, or other rule violations.
- Players are not entitled to compensation for items or builds lost through permitted gameplay.
Large-scale destruction is allowed provided it does not violate the server performance rules.
1.2 Cheating and Unauthorized Modifications
Cheating is strictly prohibited. This includes using any of the following features:
- Hacked clients.
- X-ray and resource-revealing modifications.
- Freecam.
- Autoclickers.
- Combat, movement, or gameplay macros.
- Unauthorized gameplay bots.
- AutoPlace and automatic building modifications.
- No-fog modifications.
- Minimap features that reveal hidden structures, caves, players, or entities.
- Other modifications providing comparable prohibited advantages.
Prohibited features are prohibited even if you claim you did not gain an advantage from them.
Permitted features: Normal minimaps without prohibited information-revealing features; automatic reconnection for AFK farming, without additional prohibited gameplay automation.
A modification is not automatically permitted simply because it works in vanilla Minecraft. Cheating punishments depend on the severity, evidence, impact, and previous violations. Permanent bans are not automatic.
1.3 Duplication Exploits
ALL duplication glitches and exploits are prohibited. There are zero exceptions.
This includes:
- TNT duplication.
- Carpet duplication.
- String duplication.
- Gravity-block duplication.
- Dragon egg duplication.
- Any other unintended item or block duplication exploit.
- Intentionally using duplication glitches is prohibited.
- Creating or operating duplication machines is prohibited.
- Sharing duplication methods for the purpose of exploiting the server is prohibited.
- Accidentally discovering a duplication glitch is not automatically punishable.
- Players who discover a duplication glitch must stop exploiting it and report it.
- Ordinary intended item production, such as normal crafting and farming, is not considered duplication.
No duplication glitch is permitted, regardless of the item or method involved.
1.4 Bugs and Exploits
- Intentionally abusing bugs to gain unfair advantages is prohibited.
- Players must report potentially exploitable bugs through the official bug-reporting channel.
- Deliberately repeating or exploiting a discovered bug is prohibited.
- Using bugs to generate unauthorized items, money, resources, or other benefits is prohibited.
- Sharing exploit instructions to help other players violate the rules is prohibited.
- Accidentally encountering a bug is not automatically punishable.
Staff must have reasonable evidence of intentional exploitation before issuing an exploit-related punishment.
1.5 AFK Farming
AFK farming is permitted under the following conditions:
- Automatic reconnection is allowed.
- Autoclickers are prohibited.
- Gameplay macros and bots are prohibited.
- Automatic gameplay actions using unauthorized software are prohibited.
- AFK farms must comply with the server performance rules.
Automatic reconnection is an exception to the automation restrictions, not permission to automate gameplay.
1.6 Server Performance and Lag Machines
Players may build farms and redstone mechanisms as long as they do not cause unacceptable server performance issues.
A farm or mechanism may violate this rule when:
- Server TPS falls below 18.5 while it operates.
- Staff can reasonably confirm that the mechanism caused or materially contributed to the performance problem.
A low TPS reading alone is not proof that a particular farm caused the issue.
Enforcement- Staff may temporarily disable mechanisms that threaten server stability.
- Accidental performance problems will generally receive a warning and an opportunity to fix the issue.
- Repeatedly operating a mechanism after being instructed to fix it may result in punishment.
- Deliberately creating lag machines or attempting to crash the server may result in an immediate ban.
- Punishments depend on severity, intent, evidence, and impact.
1.7 Advertising
Advertising other Minecraft servers or competing communities without authorization is prohibited. Examples include:
- Posting competing server IP addresses to recruit players.
- Sending unsolicited promotional messages.
- Repeatedly encouraging players to leave CheeseySMP for another server.
Ordinary discussion about other games or communities is not automatically advertising.
1.8 Account Responsibility
Players are responsible for activity conducted through their Minecraft accounts. Claims that a friend, sibling, or family member used the account do not automatically invalidate a punishment. Staff must still have reasonable evidence that the account was involved in a violation.
1.9 Alternative Accounts and Punishment Evasion
Players may not use alternative accounts to bypass active bans or restrictions. Players may not arrange for others to evade restrictions or improperly pressure staff on their behalf. Legitimate appeals through the designated appeal process are permitted.
03FAIR, CONSISTENT MODERATION
Punishments and Enforcement
3.1 Punishment Types
Staff may issue:
- Warnings.
- Message removals.
- Temporary mutes.
- Temporary restrictions.
- Temporary bans.
- Permanent bans.
3.2 Punishment Severity
Punishments are based on:
- The rule violated.
- Severity of the behavior.
- Available evidence.
- Whether the violation was intentional.
- Impact on other players or the server.
- Previous confirmed violations.
- Repeated behavior after warnings.
Minor first-time violations generally receive a warning. Serious or deliberate violations may result in immediate punishment without a warning. Confirmed cheating does not automatically require a permanent ban.
3.3 Evidence Requirements
Significant punishments must be supported by reasonable, documented evidence. Acceptable evidence may include:
- Server logs.
- Plugin logs.
- Screenshots.
- Video recordings.
- Chat records.
- Verified technical findings.
- Other relevant, reliable information.
Staff should consider the context and reliability of evidence.
Suspicion alone is insufficient for a cheating ban.
Staff should record the violated rule and reason for the punishment.
3.4 Appeals
Players may appeal through the designated official appeal system. An appeal should include:
- Minecraft or Discord username.
- Punishment reason.
- Explanation of the appeal.
- Supporting evidence, if available.
Appeals should be reviewed fairly, preferably by a staff member who did not issue the original punishment. Submitting an appeal does not guarantee that a punishment will be reversed. Players may not evade their punishment while awaiting an appeal decision.
3.5 Staff Accountability
Staff must enforce rules fairly and consistently. Staff members may not issue punishments based on personal disagreements, favoritism, or retaliation. Punishments found to be incorrect should be reviewed and corrected.
3.6 Emergency Moderation
Staff may temporarily restrict accounts or disable mechanisms when necessary to protect the server or community from an immediate threat. Such action must be documented and reviewed. Temporary protective action does not automatically establish guilt.
3.7 Rule Changes
Rule changes take effect when officially published. Players will not be punished retroactively for behavior that was permitted when it occurred. Players are responsible for reviewing announced rule updates.