No shared library
Convention over dependency: shared standards and design tokens, zero shared runtime jars. No mod inherits another's release cadence.
The Vision
Four independent overhauls of the vanilla systems Minecraft shipped shallow — and the loop they form together.
One session, four verbs
Survive, enchant, trade, discover are the four verbs of a single survival session, in the order a player actually lives them. The world threatens you — Tribulation. You grow stronger to meet it — Meridian. You convert your surplus into what you lack — Mercantile. You push outward for more — Prosperity — which raises the threat, and closes the loop.
Install all four and survival Minecraft gains the escalation arc of a roguelike, laid over unmodified vanilla. Install any one and it stands entirely on its own.
Overhaul, not add-on
Each mod takes one vanilla system the game left shallow and overhauls it — going as deep as that domain needs, whether that means deepening a mechanic, replacing it, or running a new system in parallel with vanilla's. What a mod does not do is wander: one domain per mod, no new dimension, and nothing another member has to load.
À-la-carte by principle
The collection is independently installable mods, not a modpack — and that shape is deliberate. A modpack can hide a weak member inside the bundle; a suite where every mod is its own download cannot. Each one has to justify itself alone, which keeps all of them honest.
Optional integration
Siblings light up together through guarded, read-only APIs — and degrade gracefully to working solo the moment one is absent.
Open to anyone
The integration pattern is public. Any third-party mod can plug into a member the same way the siblings do.
The cast
Concord — agreement and harmony between independent parties — is the architecture thesis as a name. Its members share the register: one weighty abstract noun apiece, naming the system each one finishes.
Meet them on the home page.