MineColonies Unofficial Fabric

0.0.51 makes the warehouse storage upgrade work, and stops a full warehouse deadlocking couriers. Buying the upgrade grew the racks but never recomputed how many slots were free, so a warehouse with 450 genuinely empty slots reported none and refused everything a courier brought — until something was taken out by hand or the chunk reloaded. And a courier the warehouse refused went back to the warehouse, over and over, in 80 % of samples; because it never reached its delivery states it never carried anything out either, so a full warehouse could not even be drained by the workers asking for its contents. Now a refused courier warns you, naming the warehouse, and gets on with the deliveries it can make. The full-warehouse chat message also carries real numbers — slots taken and how much of that is fragmentation, side by side.

0.0.50 gives every hostile territory its own border colour. They all drew in the same red before, so a second territory was ground you could see but not tell from the first. /mc colony territory create \[\] \[\] takes a colour, and without one it picks from twelve, preferring a colour no other territory in that dimension is wearing. /mc colony territory colour recolours one later. White is deliberately not among them — that is the colour your own colony draws in — which is also why territories made before this release keep drawing in the old red.

0.0.49 keeps hostile pilots' aircraft out of your sky — by routing, not by force. With Simple Planes 5.3.9 or newer installed, an aircraft under that mod's autopilot prefers a heading that does not cross a colony where its pilot holds the hostile rank. It is advice weighed against the terrain, not a no-fly zone: it is asked only while the autopilot is flying, so hand-flying is untouched, and it cannot refuse a route, so an aircraft launched from inside a claim flies straight out. Neutral does not count as hostile — that would detour aircraft around every colony their pilot is not a member of. Without the aircraft mod, or with an older version, nothing here runs.

0.0.48 lets a colony hold the sanity cleanup back while it is being rescued. That cleanup deletes every building whose chunk is loaded and whose anchor is no longer the right block — correct when a player mines a hut, destructive when the blocks are missing because the world was opened without the mod. /mc colony keepbuildings on suspends the removal for that colony, saved with the colony, off by default, logging what it spares instead of destroying it. The rescue order is keepbuildings on → load the backup → restorehuts confirm → repairall → keepbuildings off; restoring a backup without the switch loses buildings before restorehuts can reach them, and a building the cleanup has already deleted cannot be recovered — a hut block placed where the colony has no building registers a fresh one at level 0.

0.0.47 puts the hut blocks back after a world has been opened without the mod. Load a save once with the jar missing and vanilla drops every one of the mod's block entities — Skipping block entity with invalid type in the log — and the hut blocks go with them. The colony save is a separate file and survives whole, so the town still exists in the colony's memory while the world holds nothing. That state destroys itself: the sanity cleanup deletes from the colony every building whose chunk is loaded and whose anchor is no longer the right block, so each session erases more of the town for good. /mc colony restorehuts counts what is missing; adding confirm places one hut block per building, at its recorded position and facing, in a single server tick with the chunks pulled in explicitly — so the cleanup never gets a look in. The blocks bind to the buildings that are already there, at the levels they already have; nothing is registered fresh at level 0. The structures themselves are then the builders' job, through /mc colony repairall.

0.0.46 fixes a levitation icon that nothing could remove. A player denied eleven times in ten seconds gets ten seconds of levitation — upstream's punishment, and intended. But the permission handler's bookkeeping was running client-side as well as server-side, because most Fabric callbacks fire on both, so the effect landed on the client's own copy of the player where the server could never clear it. It stuck at 00:00, ignored /effect clear and milk, and needed a relog. Now server-side only.