Server rules

1. Scope

These rules apply in every world and all server-related areas. Accepting confirms that you have read and understood them. Ask the server team before acting if anything is unclear.

2. Conduct

Treat other players respectfully. Insults, discrimination, harassment, threats, targeted provocation and spam are prohibited.

Privacy and disputes

Do not publish other people's personal information or impersonate team members. Resolve disputes calmly or report them to the team.

3. Property and claims

Protect your land with a claim. Respect others' property and leave their items alone out of courtesy. Damaging or dismantling others' structures and machines without permission remains prohibited even without a claim.

Request a claim

Only the admin team creates claims, through Discord tickets. Claim permissions and changes also go exclusively through admins. Request expansions there too. Discord

Without a claim

Taking items from unprotected storage on unclaimed land is not pursued by the team as a theft violation. There is no restoration or compensation for this. Bypassing protection and looting death inventories remain prohibited.

Claims and equipment

Do not bypass or exploit claims, locks or protection systems. Only the team may release or remove abandoned installations.

Plot centre

Without a claim, your existing base provides the reference for your plot centre. Ask before expanding if uncertain. When creating the claim, admins define and communicate its centre chunk. Later claims or expansions do not automatically move it.

Mines and farms

Mines, resource farms and comparable equipment in the main world must stay within twelve chunks in every horizontal direction from the centre chunk: a 25 × 25 chunk square including the centre. Without a claim, use your base as reference and ask the team about boundary cases. Mining restrictions apply additionally.

Distance and expansion

Claims must not surround other plots, deliberately block them or prevent reasonable expansion. New plots and large extensions need adequate distance. The team decides doubtful cases.

Death inventories

Death inventories, gravestones and clearly lost items remain the affected player's property. Do not loot, open or remove them without permission.

Abandoned plots

Admins assess abandonment individually. An explicit statement that someone no longer plays is one clear example. Do not independently loot or remove abandoned equipment; the team must release it.

4. Create infrastructure

Do not damage, dismantle, modify, move or obstruct other players', public or team-managed Create installations without permission. This especially includes trains, carriages, tracks, switches, signals, stations and contraptions.

Your own equipment

You may change your equipment provided public routes and others' installations are unaffected. Agree connections to the public rail network with the team beforehand.

Trains in the Nether

Create trains must not travel through the Nether. Do not build or use rail routes or portal connections through the Nether for this purpose.

Vaults on ME systems

Each ME system may connect at most six Create Item Vaults without filters through Storage Buses. Each Vault may be at most 3 × 3 × 9 blocks. Count connected Vault multiblocks regardless of the number of Storage Buses. Six maximum-size Vaults contain 486 Vault blocks in total.

Local Create logistics

Create logistics with Frogports, Chain Conveyors, Packagers and comparable components is allowed for small local transport within a single production facility, for example supplying ingredients to a line or removing its finished products.

No central logistics network

Do not use this as a base's central storage, distribution or main transport system, or as an overarching logistics network between independent farms or factories.

Package congestion and faults

Prevent packages from accumulating indefinitely or circulating when storage is full, routes are blocked or destinations are missing. Stop the affected supply during these faults. Equipment proven to cause significant server lag must remain shut down until fixed.

5. PvP and traps

PvP, traps and intentional killing or obstruction of other players require prior consent from everyone involved. Traps and combat areas must not endanger uninvolved players.

Safe zones

Configured protection around world spawn prevents PvP within 250 blocks and mob spawning within 260 blocks. Protected spawn and spawn-portal areas are safe zones for everyone. Mob-spawn protection does not automatically prevent all other hazards.

Dimension portals

Other dimensions also have safe zones at designated spawn portals. Other portals do not have that protection. General PvP rules still apply outside safe zones: lack of protection does not permit attacks without consent.

Accidents and damage

After an unintended incident, return lost items and repair damage caused.

Mobs and events

Boss summoning and dangerous events, particularly Wither summoning, are allowed only in the Farming world. They must not endanger spawn, portals, public installations or others' plots. Inform affected players beforehand.

Create Mechanical Spawner

As an exception, Create Mechanical Spawner resource production is allowed outside the Farming world in specially secured rooms. Mobs and their effects must remain safely contained, without endangering players or surroundings.

Keep safe zones clear

Do not endanger safe zones with lured mobs, traps, fluids or other damage sources. Keep entrances and spawn portals clear. Do not use machinery to bypass protection.

6. Server performance and machinery

Do not intentionally cause lag. Farms, machines and logistics must be reasonably limited and switchable when needed. Avoid unnecessary entities, loose items, backed-up storage outputs and permanently running machinery.

Multiblock construction

Each individual multiblock structure must be built entirely within one chunk and must not cross a chunk boundary. This applies to multiblocks from every mod, including Create, Mekanism and Applied Energistics 2 (AE2). All blocks belonging to a given multiblock structure must be in the same chunk.

Separate multiblocks

Separate multiblocks in one installation may stand in different chunks, provided each individual multiblock stays entirely within one chunk.

Multiblocks crossing chunk boundaries can cause performance problems in some circumstances. Plan for chunk boundaries before building.

Continuous load

AFK farms and factories operating while you are absent or offline are generally allowed. If equipment causes lag, admins will discuss and explain necessary changes. Limits and measures are set individually.

Automated mining

Mining machines such as Digital Miners and Create drills used to farm ores or other natural resources may operate only in the Mining world/Mining Dimension. Such resource farming is prohibited in every other dimension, even inside a claim.

Mining rigs

Each person may operate at most one drilling rig in the Farming world/Mining Dimension. Its drilling area must not exceed 16 × 16 blocks.

Excavation examples

Outside the Mining world, Create drills and mining contraptions may excavate for a specific construction project, such as your factory. Limit excavation to that purpose. Resource farming must not be disguised as construction. Factories and production are expressly permitted.

Overflow and shutdown

Automated equipment needs reasonable shutdown or overflow protection. It must not continuously generate items, fluids, entities or other resources when they can no longer be processed or stored.

Hazardous installations

Secure reactors, radiation sources, explosives and other equipment with wide-area effects adequately. They must not endanger others' plots or public areas.

Damage and safeguards

Report radiation, explosions and other damage immediately and eliminate it where possible. The team may require another location or additional safeguards for hazardous equipment.

Temporary equipment

Remove temporary mining rigs, contraptions, chunk loaders and construction-site equipment after use. Do not leave dangerous holes, running machines or abandoned entities.

World resets

The Mining world in particular may be reset depending on depletion. Nether and End are generally not reset unless genuinely necessary. Agree long-term installations and storage in resettable worlds with the team beforehand.

7. Fair play

Exploits, duplication and bypassing protection are prohibited. Commands, scripts and automation must not bypass safeguards or provide an unfair advantage.

Bugs and public areas

Report bugs privately to the team. Do not publish abuse instructions. Protect spawn, portals, paths and other public installations.

Bypassing limits

Do not evade server limits with alternate accounts, fake players, extra teams, distributed claims or multiple chunk loaders. A mod's technical capabilities do not automatically make an action permitted.

8. Team and consequences

Follow reasonable instructions from the server team. The team decides unclear situations and may temporarily disable disruptive or dangerous installations. Measures depend on severity, intent and repeated violations.

Possible measures

Measures may include warnings, return/restoration, temporary restrictions, jail, and temporary or permanent exclusion. Severe intentional violations do not require every stage to be applied in sequence.

Rule changes

When a new rules version is activated, read and accept it again. If you are online, TDRules saves your position and holds you there with normal actions restricted until acceptance.

Logging out and returning

If you log out first, you are restricted at spawn on your next login. Your original position stays saved. After acceptance, TDRules tries to return you there safely. Accepting again does not grant another starter kit.

Help and reports

Report questions, disputes and technical problems to the team. Open a Discord ticket for claims, reimbursements or complaints. Provide your player name, time, dimension, coordinates and a precise account of events. Discord

Sensitive reports

Report exploits and sensitive information privately in a ticket only. Do not publish instructions for abuse. Complaints about team decisions are discussed with a neutral team member.

Loss and reimbursement

For losses caused by bugs, the team reviews each case using your account and available tracking records. Admins decide whether and how to reimburse. Reimbursement is not automatic. The property rule applies to items taken from unprotected storage without a claim.

Logging

TDRules logs rule-related events including display, acceptance, refusal, blocked actions and administrative changes. Passwords are not logged. Its own TDRules log files are automatically deleted after 30 days.