One config file
Every module's settings live in one JSON. A partial install cannot gut another module's saved tuning. Foreign sections survive verbatim.
PlunderEngine 0.1.2Fabric · 26.1.x
PlunderEngine
The core the Link mods run on. It does nothing visible on its own: no wind, no grass, no weather. Install it because WindLink requires it.
Why a separate jar
One config, one settings screen, one command.
Every Link mod registers itself as a module. In exchange it gets config persistence, a settings tab, status reporting and the shader-channel layer for free. And the player gets one place to configure all of them rather than one screen per mod.
One settings screen
Reachable from the mods list, a keybind, and the vanilla Video Settings screen. Three entry paths, because people look in different places.
One status command
/plunderengine reports what actually loaded, which
modules registered, and the per-system timing counters.
The Link suite
One Link ships today.
WindLink
The wind, the terrain flow, blown debris, dust, seasons, and the MCWIND provider.
What it does →More Links
The module system exists so the next world-signal system does not need its own config, its own screen and its own command.
Your Link
Register a module and get persistence, a settings tab and status reporting without writing any of it.