The map, evidence, and shared knowledge behind a Valheim project fleet
Baseline is the hub. NetworkSense, Quest, the service platform, and the MCP kernel each keep their implementation in a sovereign repository.
The communities this is for already do this work — with mods, spreadsheets, Discord bots, checklists, screenshots. The fleet doesn't replace any of that. It is meant to let people spend less time on paperwork and tracking, and more time making things.
One corpus, several useful views
Choose the question closest to yours. These are tailored tables of contents, not gates: every view keeps a route to everything outside its lane.
The platform-owned Community Workbench
A catalog of tools you can download and run on your own machine tonight. Every card says what the thing actually does today — not what it's going to do.
Quest Picker
Turns a guild's real quest tracker into a page where a player checks off what they're chasing — and the game mod reads the result.
ComfyStewardView
Reads a Valheim world file and answers what stops being walkable once a server gets big: where is everyone building, and who owns this.
Community Telemetry
An aggregates-only telemetry API with privacy tests that fail if a player ID, name or position ever shows up — plus the whole stack, runnable locally.
Steam Self-Service Join
An invite, a Steam sign-in, and a mod-pack zip with your credentials already in it.
What the tools turn up
Photographing a world nobody had time to look at
Three million building pieces and one person. Clustering a save file into 1,833 structures, then placing a camera at every one of them from its geometry — 1,411 photographs, none of them framed by hand.
the arithmetic, the file contracts, and what each stage emits
From a leader's spreadsheet to a killing blow, and back with proof
A guild master keeps their tracker exactly as it is. The absorption engine harvests it verbatim, a player picks quests on a web page, and the game itself notices the completing blow and starts the paperwork — with a provenance page showing the leader every cell's journey.
the loop drawn end to end, the auto-capture machinery, and the seam that is not baked yet
Running one of these once is a complete contribution
Every tool has its own thread. Saying what happened when you ran it — including that it broke — is the contribution.
What is not open yet
The game server is not open. You can run every tool above on your own machine, but this is not yet an invitation to come play on the live world — the volunteer platform isn't ready, and saying otherwise would waste your evening. That work is tracked in the open on the roadmap. This is a solo-operator project in alpha, and it is written down honestly rather than dressed up.
Designed for extraction
People are expected to read this code, and if you take pieces of it and use them yourself, that's the highest compliment.