The RenderFrost code.

Every player deserves to feel welcome and respected within the RenderFrost community.

Prohibited behaviour

• Hate speech, discriminatory remarks and slurs.
• Harassment, targeted abuse, or deliberately humiliating other players.
• Excessive vulgarity or intentionally offensive behaviour directed at others.
• Any conduct intended to make another player’s experience uncomfortable or hostile.

Normal conversations are not actively monitored. However, reported incidents involving abusive or inappropriate behaviour will be taken seriously and reviewed by the moderation team.

Every player’s property, builds and possessions must be respected.

Strictly prohibited

• Breaking, removing or modifying another player’s blocks without permission.
• Stealing items from chests, barrels, shulker boxes or other storage.
• Deliberately damaging or destroying a base, farm, infrastructure or decorations.
• Tampering with another player’s builds to cause damage, inconvenience or disruption.

RenderFrost takes reported griefing and theft seriously. Incidents may be investigated using available evidence, and confirmed violations may result in appropriate moderation action.

Player-versus-player combat is disabled by default. No player should be attacked, trapped or deliberately placed in a harmful situation without their consent.

Prohibited behaviour

• Attempting to kill or damage another player without their agreement.
• Trapping players in enclosed spaces or preventing them from escaping.
• Using lava, dripstone or similar hazards to attack or endanger a player.
• Creating traps intended to cause death or destroy equipment.
• Engineering harm deliberately and disguising it as an accident.

PvP is permitted only when the players involved have agreed to participate. Consent to one fight does not automatically grant permission for unrelated attacks or interference.

Reported violations may be investigated and punished accordingly.

RenderFrost requires fair gameplay. Any client, modification, resource pack, tool or exploit that provides an unfair advantage is prohibited.

Prohibited

• X-Ray resource packs or mods that reveal hidden ores or concealed resources.
• Meteor Client or other hacked clients and cheating tools.
• Seed crackers used to gain an unauthorised gameplay advantage.
• Resource locators or similar tools that reveal hidden resources or locations unfairly.
• Item duplication exploits through unintended game behaviour.
• Any other modification or exploit that bypasses intended mechanics for an unfair advantage.

Permitted modifications must be used responsibly and within their legitimate functionality. Their names alone do not authorise every possible use; any feature used to cheat or gain an unfair advantage remains prohibited. Players must not exploit bugs or unintended mechanics to bypass these rules.

A rollback is a restoration of affected blocks or world changes. It is not an automatic guarantee of compensation.

Rollbacks for world destruction are considered primarily when the damage or loss was directly caused by a verified server-side issue, such as:

• Severe server lag or a server malfunction.
• An unexpected server crash.
• A confirmed server-related disconnection that resulted in the loss or destruction of world data.

Confirmed griefing may also be reviewed for a possible rollback when sufficient evidence is available and staff determine that restoration is appropriate.

The staff team evaluates the circumstances and available evidence before making a decision.

Inventory restoration is considered only when the loss was directly caused by a verified server-side problem.

Potentially eligible

• Severe server lag directly causing the loss.
• A server crash that results in inventory loss.
• An unexpected server-related disconnection that directly causes items to become irrecoverable.

Not eligible

• Normal deaths during gameplay.
• Accidental deaths, including falls, lava incidents or other player mistakes.
• Deaths caused by hostile mobs or other entities under normal conditions.
• Ordinary item loss unrelated to a verified server-side issue.

If you believe your situation qualifies, submit a report to the staff team explaining what happened and when it occurred, and include any available evidence. Final decisions are made by the staff team after reviewing the incident.

Mining directly downward is prohibited on RenderFrost SMP.

This practice can lead to unexpected falls, lava exposure, accidental deaths, and dangerous situations involving other players.

Use a proper mining method that allows you to inspect the blocks and terrain ahead of you.

Keep the world clean and maintain the natural appearance of RenderFrost SMP. Whenever you chop down a tree, remove the remaining logs rather than leaving a partially chopped trunk floating above the ground.

Expected of every player

• Finish cutting down the entire tree.
• Remove any remaining exposed logs.
• Avoid leaving unfinished trees that disrupt the surrounding environment.

This rule helps preserve the server’s appearance and makes the world more enjoyable for everyone.

The Spawn Village is a protected area that serves as an important shared location for the RenderFrost community.

Without explicit staff permission, you must not

• Break, remove or damage existing blocks or structures.
• Place blocks that modify or obstruct the protected area.
• Build over, alter or replace existing structures.
• Remove decorations or modify the village’s appearance.
• Make any other change to the spawn environment.

Even seemingly minor modifications can affect the shared appearance and functionality of the area. If you believe a change is necessary, contact a staff member and obtain permission before proceeding.

Each player may own a maximum of 3 Elytras on RenderFrost SMP. This limit prevents excessive accumulation and preserves a reasonable distribution of Elytras throughout the community.

• You may not keep more than three Elytras in your possession.
• You may not hoard additional Elytras beyond the permitted limit.
• You may not trade or transfer extra Elytras in a way that bypasses the ownership restriction.

Channeling-enchanted tridents can cause lightning strikes during suitable thunderstorms. Using them carelessly around important structures can create unnecessary damage and disruption.

Players must avoid using Channeling tridents near another player’s base, house or other important structure when doing so could cause damage or disturbance.

Prohibited

• Deliberately using Channeling to damage or disrupt another player’s property.
• Intentionally causing damage and dismissing it as a joke.
• Using Channeling to provoke other players or interfere with their builds.

Always consider the potential consequences before using Channeling near another player’s property.

RenderFrost encourages creativity, ambitious projects and impressive builds. However, everyone must build responsibly and consider the effect their constructions may have on server performance.

Players should avoid creating excessively resource-intensive structures that cause unnecessary lag or negatively affect the gameplay experience of others.

Builds that may require attention

• Excessively lag-inducing automatic farms.
• Overly large or inefficient redstone systems.
• Machines or mechanisms that generate excessive entity or processing load.
• Other constructions that significantly degrade server performance.

Large projects should be designed and maintained with reasonable performance in mind. Players should also maintain a reasonable distance between large builds when necessary, to reduce interference, preserve the surrounding environment and support server performance.

If a build is found to be causing significant problems, cooperate with the staff team to address the issue.

RenderFrost SMP operates with a whitelist system to maintain a trusted and controlled community.

Want a friend to join?

Follow the official process:

1. Contact a staff member and explain whom you would like to invite.
2. Ensure the prospective player follows the required verification process.
3. Wait for staff approval and official whitelist access.

Do not assume that sharing server information or receiving a personal invitation automatically authorises someone to join. All whitelist additions are subject to staff verification and approval.

Every player’s private storage and designated restricted areas must be respected.

Staff-only storage halls

Staff-only storage halls are strictly restricted to authorised staff members. Players must not:

• Enter restricted storage halls without authorisation.
• Access or remove items from staff storage.
• Interfere with stored materials, organised resources or restricted equipment.
• Use unauthorised access to obtain items or information.

Unauthorised access to another player’s storage, taking their belongings, or interfering with their property may be treated as griefing or stealing, depending on the circumstances.

Respect all private and restricted areas, even when access appears physically possible.

When players are participating in an agreed-upon friendly PvP session, allow them to complete their fight without unnecessary interference.

You do not need to participate, fight or provide assistance. Simply respect the ongoing activity.

Players must not deliberately:

• Run into the fight to disrupt the participants.
• Interfere with the fight or distract those involved.
• Obstruct the participants or otherwise prevent the agreed session from continuing normally.

This rule applies to intentional disruption; merely being nearby or passing through is not automatically a violation.

New players must spend at least 15 days on RenderFrost SMP from their first login before they can recommend another player for whitelist consideration.

This waiting period allows the staff team to become familiar with new members, establish trust, and maintain the quality and security of the community.

How the 15-day requirement works

• Before completing 15 days, you cannot recommend or request another player’s addition based on your invitation.
• After completing the required period, you may request that another player be considered for the whitelist.
• The recommended player must still complete the required verification process.
• Meeting the 15-day requirement does not guarantee approval.