Redstone

Redstone often works differently for Java multiplayer servers compared to vanilla Minecraft. Here's where we try to keep you informed of how this affects training, gameplay, and mob farms.

This page has been marked as incomplete. Some content may not yet be available on this page, and some embedded images or features may not work correctly.

Redstone mechanics are incredibly useful for a variety of functions inside Minecraft. From automatic doors to monster farms and functional calculators, players who are interested in a puzzle can experiment with wiring almost any contraption they can think of.

Here's what you might not know: each block containing redstone dust runs more than 20 individual checks of its surroundings each time the current changes! For long wires, this means hundreds or thousands of checks per-contraption, per-second! Other blocks, such as pistons, are even less CPU efficient. The problem is that redstone on Java Edition was initially designed for singleplayer, so our game has to run these checks on a single CPU thread. To combat the lag associated with vanilla redstone, server admins are left either to alter redstone behavior to remove superfluous block checks, or to restrict its use by capping the quantity of redstone-sensitive blocks in an area.

In the interest of avoiding both lag and an unreasonable hard cap on redstone, Dormcraft makes use of Eigencraft redstone. This is a free rework of the vanilla redstone mechanics for Minecraft: Java Edition which chopped redstone lag down by more than 60% in our testing. Using reworked redstone allows us to "break" some of the least CPU-efficient vanilla contraptions without affecting the majority of players making simple redstone setups. Using Eigencraft Redstone, players can still create nearly every automated farm in the vanilla game, but they're encouraged to use more CPU-efficient designs.

For transparency (and to avoid headaches), here's a list of the ways in which Dormcraft's redstone mechanics differ from the vanilla game. Being familiar with these changes can be quite important if you have a big machine planned. If you know of a detail that isn't listed here, please contact staff in our Discord server and we'll add it. Your farm or redstone contraption can likely still be created on Dormcraft despite these changes, so feel free to try things out.

OPTIMIZATIONS	EXPLOIT PATCHES
Many 1 and 0-tick machines (carpet & TNT duplication machines, certain flying machine designs, etc.) have been disabled due to their CPU performance impact.	Pistons will not push blocks across land claim boundaries, even if the builder of the machine has permission within the current claims. This is done to enforce our anti-griefing measures.
Hopper transfer speed has been decreased from every tick to every 8 ticks.