> For the complete documentation index, see [llms.txt](https://coppercore-smp.gitbook.io/coppercore-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coppercore-smp.gitbook.io/coppercore-wiki/rules/builds-and-server-performance.md). # ✦ ─ Builds & Server Performance Players are free to build creatively on Coppercore, but builds must not harm server performance, disrupt other players, or create unsafe or offensive spaces. Staff may ask for a build, farm, redstone system, or collection of entities to be changed when it causes problems. *** ### Lag Machines Lag machines are strictly prohibited. Do not create or operate anything intended to: * reduce server performance * freeze or crash the server * overwhelm chunks * create excessive calculations * generate huge numbers of entities or items * interfere with other players’ connections Claiming something was a “test” or a joke does not make it acceptable. *** ### Redstone Builds Redstone is allowed, but it must be built responsibly. Avoid: * permanently running clocks with no off switch * extremely fast clocks * large numbers of pistons firing constantly * machines that repeatedly update large areas * unnecessary hopper chains * redstone systems left running while not in use * builds designed to create excessive block updates Large redstone builds should include an easy way to switch them off. *** ### Farms Automatic and semi-automatic farms are allowed as long as they do not cause excessive lag or violate other server rules. Staff may require changes to farms that contain: * excessive mobs or entities * large numbers of minecarts * huge hopper systems * constantly running redstone * excessive dropped items * large amounts of flowing water or lava * mechanics that behave unpredictably across chunk borders Farms should be switched off when they are not needed where possible. *** ### Mobs, Animals and Villagers Do not keep excessive numbers of animals, villagers, mobs, armour stands, boats, minecarts, or other entities in one area. Coppercore uses **FarmControl**, which automatically limits the number of certain mobs that can exist within the same area. Any mobs exceeding the configured limit may be removed automatically without warning. Because of this: * spread large farms across separate areas * avoid overcrowding animals or villagers * do not rely on excessive mob stacking for storage or production * keep valuable named or tamed mobs away from overcrowded farms where possible * regularly check and manage breeding systems to prevent populations growing beyond the limit Staff may also reduce or remove excessive entities when they affect server performance or are being used to bypass FarmControl’s limits. *** ### Dropped Items Do not intentionally leave large numbers of items on the ground. This includes: * dumping unwanted items in bulk * allowing farms to overflow * repeatedly breaking large storage systems without collecting the contents * creating item fountains Use containers, disposal commands, lava, or other safe methods instead. *** ### Chunk Loaders Chunk loaders are **not allowed** on Coppercore. Do not create, use, or attempt to maintain any system designed to keep chunks loaded while no player is present. This includes: * Nether portal chunk loaders * redstone-based chunk-loading machines * entity or minecart chunk loaders * plugin, mod, or exploit-based chunk loading * designs intended to keep farms or machines running unattended Any chunk loader found may be disabled or removed by staff. *** ### Offensive Builds Builds, map art, banners, statues, signs, or decorations containing offensive or inappropriate content are not allowed. This includes content involving: * hate symbols * slurs * explicit sexual imagery * graphic violence * harassment of another player * real-world extremist material * content designed to shock or upset others Something being inside a private claim does not exempt it from serious content rules. *** ### Disruptive Builds Do not create builds intended to inconvenience, obstruct, or disturb other players. Examples include: * walls around another player’s claim * structures blocking roads or public access * excessive noise machines * bright flashing redstone * builds designed to block views or access * giant structures placed deliberately close to another player * traps disguised as normal public builds The **200-block claim distance rule** still applies. *** ### Public Builds Public farms, shops, warps, roads, portals, and community areas should be safe and clearly marked. Dangerous features such as lava, deep drops, hostile mobs, or traps must be secured or clearly warned about. Public builds should not mislead players about where entrances, exits, or teleport points lead. *** ### Unfinished and Abandoned Builds Unfinished or inactive builds are not automatically abandoned. Do not remove, claim over, or reuse someone else’s build without staff approval. Staff may clear genuinely abandoned builds when necessary, particularly when they obstruct expansion, affect performance, or occupy important areas. *** ### Server Limits Some farms, redstone systems, entities, hoppers, spawners, or other mechanics may have specific server limits. These limits may change as the server develops or performance needs change. Players are responsible for following any limits listed in the wiki, announcements, or in-game information. *** ### Staff Intervention Staff may inspect, disable, modify, reduce, move, or remove a build when it: * harms server performance * breaks a rule * creates a safety issue * interferes with another player * affects protected or public areas * exceeds a server limit Where practical, staff will contact the owner first and explain what needs to change. {% hint style="warning" %} **Important:** Being able to build something does not automatically mean it is safe or permitted. When in doubt, ask before creating a large farm or redstone project. {% endhint %}