Server Logistics

One button for all your server’s tools, and the shared ground they stand on. Server Logistics is the base that PrankLevels, Factions&Wars, ServerRegister and ServerWhitelist require: a single «Server Logistics» button in the inventory with one tab per tool, the tools to choose land in the world and on the map, the aurora that shows where land begins, and the protection engine that keeps that land safe from players, mobs, fluids, explosions and other mods’ machines.

It is also what every player’s game uses to tell the server what it carries — mods, the active shader pack, the selected resource packs — so that ServerWhitelist can judge players who do not have ServerWhitelist. And it knows who is behind every creature: a villager farming in a base is nobody’s attack, a dragon a player rides or owns is that player.

Forge, Minecraft 1.20.1. Required on the server and on every player’s game. MIT licence. Author: puercoalopecico.

Commands

Server Logistics adds no command of its own. Each tool that uses it has the same access commands under its own name (serverregister, serverwhitelist, pranklevels, factions):

Being a server operator gives nothing by itself: the console names who administers each tool.

Before you install

• On the server and on every player’s game, same version. A game without it, or with another protocol, is refused at login and told which mods to install. Version 1.0.1 changed the protocol (the game report): update the server and the players’ pack together.
• Update the tools with it. PrankLevels 1.0.1, Factions&Wars 1.1.0, ServerRegister 1.0.1 and ServerWhitelist 1.0.1 require Server Logistics 1.0.1.

What it does

• The button and the tabs. One button in the inventory; each tool is a tab. Closing a tool returns to where the visit started.
• Choosing land. Selection tools in the hotbar (corners, height, undo), or by drawing on Xaero’s World Map or JourneyMap. Several boxes make one piece of land.
• The aurora and the messages. A glow on the edges of land, near you, and a line when you enter or leave it — each player chooses what they see.
• Protection. Every block written into the world is asked about to the tool that owns that land, whoever writes it: a player, their arrow or their pet, fire and fluids, explosions, pistons, other mods’ machines.
• Villagers live in bases. A villager or a wandering trader (and the types you list in protection.npcEntities) with nobody behind it may farm, open doors and take beds on protected land. Any creature may open or close a door: refusing it only made it try again forever.
• Who is behind a creature. A creature counts as its player when a player rides it (any seat, any vehicle in the chain), owns it, threw or made it, or holds its lead. So a ridden or tamed dragon follows its player’s rules; a wild one, the land’s rules for mobs.
• The game report. Asked by ServerWhitelist, every game sends its jars (with hashes and the code inside), its shader packs (and which one is active) and its resource packs (and which are selected), in pieces, only when asked.
• Wide help boxes. Every tool’s «i» opens a box wider than the game’s own, beside what it explains and always inside the screen.

Settings

config/serverlogistics-common.toml holds what the tools share (the aurora, the messages, the protection of land, the kill counter). New in 1.0.1: protection.npcEntities — extra entity types treated as villagers (for example another mod’s villagers), empty by default.

Compatibility

• Xaero’s World Map and JourneyMap are optional (choosing land on the map).
• Works with other protection mods: each one is asked only about its own land.
• Languages: English, Spanish, French, Portuguese and German (and their regional variants); the rest in English.