Beauty in Blocks Server Rules

1. The wilderness is not protected

Outside published protected areas, PvP, theft, traps, sabotage, and destruction of player builds are allowed. This includes offline raids and the complete loss of a base. There are no player land claims or guarantees that your builds or belongings will remain safe.

You do not need to declare war, belong to a clan, obtain the other player's consent, or prove that an attack was profitable. A raid does not need a resource-related motive. Being new, playing alone, or being offline does not create protection.

Players are responsible for their own in-game agreements, alliances, and valuables. Staff do not enforce promises, settle ordinary item-trade disputes, or return items lost through permitted gameplay. Permission for in-game conflict does not authorize real-world fraud, account theft, or other prohibited conduct.

These rules apply equally to new players, established players, supporters, friends of the owners, and owners playing survival. Repeated attacks are not automatically a violation just because the same opponents are involved. A separate violation of another rule is still enforceable.

2. Destroy builds, not the surrounding landscape

Player buildings, farms, walls, roads, and other constructed features may be damaged or demolished, including completely.

During a raid, keep demolition focused on those constructed features. Do not continue blasting the ground after the structure is gone, excavate the surrounding hillside as part of the attack, burn neighboring forests, blanket the landscape in lava or water, or cover it with lava-generated cobblestone.

Aerial carpet bombing, TNT duplication, and using withers as raid weapons are prohibited. These restrictions cannot be bypassed by using a different explosive, mob, machine, or another player to cause the same prohibited damage.

Incidental ground damage from otherwise permitted demolition is accepted. This is not permission to extend an attack into the surrounding landscape or keep excavating beneath a demolished base.

Ordinary mining, access tunnels, construction, and landscaping remain allowed. Calling an attack "mining" or "landscaping" does not exempt it from these restrictions. The size or emotional value of a destroyed building does not, by itself, make its destruction prohibited.

3. Published protected areas must remain usable

Spawn and the travel or event areas specifically listed in the published protected-area register are protected. Their boundaries must be marked in-game and described on the website.

Do not damage, obstruct, trap, or bypass the protections of those areas, including through hazards placed outside their boundaries. Do not trap or obstruct public End portal access, arrival platforms, or exits designated in the register.

A player-built road, shop, farm, or community project is not automatically protected because people use it. Protection applies only to published locations, not private promises or case-by-case player petitions. Any future official addition must be publicly announced before its new protection is enforced.

4. No cheating or interference with server operation

Do not use cheats, X-ray, prohibited automation, exploits, duplication, or methods that bypass server protections. A client-side mod is not automatically allowed just because it can connect. Report vulnerabilities privately rather than using or distributing them.

Normal farms and redstone are allowed unless they use prohibited methods or disrupt server operation. Builds and machines that disrupt the server may be paused or removed. Do not restart or replace a disabled mechanism to recreate the problem before it is resolved.

Attempts to crash the server, compromise accounts, evade bans, or interfere with its services are prohibited. Staff may contain an active technical problem before deciding whether anyone should be punished.

5. Conflict is allowed; personal abuse is not

Swearing, disagreements, criticism, and game-related trash talk are permitted within the applicable platform rules.

Real-world threats, sharing or threatening to share personal information, hateful abuse, sexual harassment, spam, and attempts to bypass communication blocks are prohibited. Harassment of the person behind a character is not protected by the raiding rules.

These boundaries apply to chat, private messages, signs, books, names, builds, and connected Discord spaces. Minecraft/Xbox and Discord rules still apply on their respective platforms.

Blocking or ignoring someone does not give you immunity from ordinary gameplay. It does mean they must not use alternate accounts, other communication channels, or other people to force continued unwanted personal contact.

A permitted raid, rivalry, or critical opinion is not automatically harassment. Equally, an otherwise permitted raid does not excuse separately evidenced threats, doxxing, hateful conduct, or a personal harassment campaign.

6. Staff enforce boundaries, not outcomes

Staff review suspected rule violations, safety concerns, and technical problems. Staff do not decide who deserved to win a feud, negotiate peace, require apologies, or compensate players for permitted losses.

Use the designated private reporting route for rule violations and sensitive evidence. Report the behavior, the players involved, the approximate time and timezone, the dimension and coordinates when relevant, and any available evidence. You do not need to identify an exact rule number to report a safety concern.

Rollbacks and compensation are reserved for confirmed prohibited activity or technical failures when recovery is feasible. Recovery is not guaranteed. A violation during a raid does not automatically invalidate every otherwise permitted action in that raid.

Enforcement depends on evidence and severity. Minor, correctable violations may receive a warning; repeated or serious violations may receive restrictions or bans. Serious misconduct can result in immediate action without a warning. An accusation alone is not proof.

One appeal per decision may identify a factual mistake, relevant new evidence, or a misapplied rule. Ordinary disagreement does not require repeated reviews. Genuinely new information can still be added to the existing case.

Supporter status, friendships, time played, and owner participation do not change the rules. An owner directly involved in a dispute should not be its sole decision-maker. Genuine policy ambiguities will normally be clarified publicly for future play rather than resolved by inventing a new rule after the event.

7. This is a two-owner hobby server, not an on-demand support service

Beauty in Blocks is run by two owners in their spare time. We both have jobs, responsibilities, other hobbies, and lives outside the server. We review reports, bugs, appeals, and other issues when we have time available.

A response or resolution may take days or weeks, and sometimes longer, depending on our availability and the issue. There is no guaranteed response time, investigation, fix, rollback, or outcome. An owner being online, chatting, or playing does not mean they are available for support.

Submit one clear report through the designated route and add genuinely new information to that report. Repeated messages, owner pings, duplicate reports, or public pressure do not move an issue ahead. Supporter purchases do not buy priority moderation or guaranteed turnaround.

Active threats, security incidents, and problems affecting server operation may be prioritized when noticed, but the server is not continuously monitored. Use platform blocking and reporting tools for immediate personal control. For an immediate real-world danger, contact appropriate emergency services rather than waiting for a server response.

A delayed response is not approval of prohibited behavior. Thank you for respecting our time and helping keep the server sustainable.