Concord
Concord logo

Concord

Four independent Minecraft mods. One escalating survival loop.

Concord takes the vanilla systems the game shipped shallow — enchanting, villagers, difficulty, loot — and gives each its own mod to overhaul it. Install one. Install all. Every mod stands alone, and together they light each other up — never a hard dependency.

One loop, four verbs

Survive, enchant, trade, discover — the four verbs of a single survival session, each owned by one mod, in the order a player actually lives them.

Survive

The world pushes back the longer and farther you survive. — Tribulation

Enchant

Enchanting becomes a system you build toward, not a slot machine. — Meridian

Trade

Villagers become people you have a history with. — Mercantile

Discover

Every chest is worth opening, for every player who finds it. — Prosperity

The four mods

Each completes one vanilla system. Each ships and updates on its own.

Tribulation

Survive what comes next.

A difficulty overhaul: mobs grow stronger as you play longer, venture farther, and descend deeper.

tribulation.rfizzle.com →

Meridian

Chart your enchantments.

An enchanting overhaul: a deep, buildable progression in place of the vanilla slot machine.

meridian.rfizzle.com →

Mercantile

Every villager remembers.

A villager & trade overhaul: reputation, named traders, and trades worth returning for.

mercantile.rfizzle.com →

Prosperity

Every chest, yours to discover.

A loot overhaul: per-player instanced loot scaled by how far you roam.

prosperity.rfizzle.com →

Built to be modular

À-la-carte is the whole point. A modpack can paper over a weak mod; a suite of independently installable ones cannot — so every mod has to earn its place alone.

Independent

Every mod is fully functional on its own. Remove one and you lose exactly its features — nothing else breaks. A server can adopt the collection one mod at a time.

Interoperable

Installed together, siblings detect each other and light up extra integration through read-only public APIs and Fabric events — never a hard dependency, never a shared jar.

No bloat

Each mod overhauls one domain and stays in its lane: no new dimension, nothing another mod must load, and multiplayer-fair by design.

For developers

Every member publishes a small, stable, read-only com.rfizzle.<mod>.api package plus a Fabric event surface. Integration is soft-dependency only — modCompileOnly + isModLoaded guards — so a third-party mod can integrate with any member using the exact pattern the siblings use. There are no private handshakes.

The shared API and HUD standards, the design system, and the build tooling all live in the concord repository.