⚠️ Eco v0.14 is coming — the next major update reworks upgrade modules, so some of these numbers will change. They reflect the current version. What’s changing →
  • Simpler tiers: the 1–4 tiered upgrades become a single Basic / Advanced / Modern upgrade each.
  • Permanent upgrades: a module placed in a workstation is permanent — no more swapping lower tiers out as you progress.
  • Power transitions: a module can change a station’s power type/draw (e.g. a Modern upgrade moves a sawmill from mechanical to electrical power).
  • Talent-integrated: modules now use the same bonus/talent system — any talent benefit (power, labor cost, recipe unlocks) can come from a module.
  • Cheaper to upgrade: with the multi-tier parts gone, fully upgrading a workstation costs significantly less.

We’ll update this calculator shortly after the update releases.

Home › About

About this project

This wiki is the public face of a living Eco server run by an in-world AI steward. Everything you read here is generated from the same game data the steward uses to keep the world turning.

What this is

Under the hood is CarbonMod, a server-side mod for Eco (Strange Loop Games). Eco is a multiplayer game about building a civilization together without wrecking the ecosystem that supports it — every recipe, skill, and harvest has a real cost in the shared world. CarbonMod adds an AI steward, Solomon, who lives on the server and helps that civilization along.

Solomon, the steward

Solomon runs quietly in the background: he scans the world's crafting stations for work that's stuck waiting on missing ingredients, figures out what's sitting in storage versus what still needs to be made, and posts help contracts and quests so players can pitch in and get paid. He keeps a shop with prices that move to match the local economy, remembers what's happened across days, and can even possess a wild animal to wander the world in person.

He also talks. The ✨ Ask Solomon button in the toolbar opens a live chat with that same steward — ask about a recipe, a skill, where an animal lives, or what to build next, and the answer comes from this wiki's data.

How the wiki fits in

This wiki isn't typed up by hand. It's built automatically from the same live game registries Solomon reads — the real items, recipes, skills, animals, plants, and biomes loaded on the server — complete with the game's own icons. The numbers are the engine's numbers; the “Your setup” calculator even recomputes recipe costs and yields against your own character's skills, talents, and upgrades.

The descriptive prose is written by a language model, but only to fill in flavor and gaps — and it runs entirely on local, self-hosted hardware. (The 🌱 Local AI badge in the footer has the details.)

The bigger system

The steward and the wiki are two parts of one integrated system. Behind them sit a public dashboard of server telemetry, the contract-and-quest economy, a tool that can rebuild and migrate the world on the same seed, and governance helpers — all sharing the same live view of the world. The wiki is simply the part of it anyone on the internet can read.

Could this run on your server?

Right now this is built and tuned for one server. But because everything here is generated straight from live game data, the same approach could work anywhere. I'm considering packaging it up as a mod any Eco server could install — so each server would get an accurate, always-current wiki of its own items, recipes, player data, and even custom mods, plus its own steward. No promises yet; it's an idea I'm exploring. If that's something you'd want, that interest is good to know.

About me

Hi — I'm Matt, aka Carbonitex. I've spent 10+ years in full-stack engineering, mostly around email, and helped launch some of the first bots on Discord. CarbonMod is one of my MANY side projects: I first built it back in 2020, then set it aside without taking it any further — and only recently picked it back up, rebuilding it for 2026 Eco+. You can some more of my work at carbonitex.dev.

Contact

Got feedback, found something wrong, or want this on your own server? I'd love to hear from you.