Inspiration
Rekindled started from the desire to help fix a real problem in modern society: the collapse of structured fellowship for men and boys — the hollowing-out of institutions like the Scouts, where belonging was once built shoulder-to-shoulder. I didn't want to depict community; I wanted to deliver it. That's the click that made this a Horizon Worlds game and not a 2D systems sim: the platform's one true superpower — real humans co-present in a shared 3D space — is identical to the thematic heart. The need and the platform turned out to be the same thing.
The second spark was recognition that fragility is another modern issue at the heart of many problems: buffers run down, risks get taken, the "middle" gets stretched thin, each decision on it’s own is tactically correct — then a shock hits and the things holding it together can't. I wanted a game that taught resilience not by lecturing, but by letting you feel the buffer you took for granted snap. Reseeding a fallen civilisation — too big a job for any one man — turned out to be the goal that forges the brotherhood and carries the lesson. You rekindle two fires at once: a fallen civilisation, and the kin who rebuild it.
What it does
Rekindled: The Path of Kin is a cooperative Survival & Resource Management game for Meta Horizon Worlds (mobile), given a strategic-RPG treatment. A brotherhood of four to eight real men, embodied as avatars in a shared 3D settlement, gather, craft, and manage scarce resources to survive escalating shocks and reseed civilisation — deciding what to rebuild and in what order across six interdependent "pillars" (Provision, Protection, Construction, Production, Formation, Cohesion).
You lead by influence, not the sword. The signature competence loop — act now · wait · mentor · recruit — turns every task into a live decision about people and time, making interdependence the engine instead of a stat screen. Substitutability is the resilience mechanic: no single strategy is mandatory, and recurring shocks reveal whether the mix you built was wise — a predictable Siege tests robustness, while the apocalyptic climax punishes the optimiser and vindicates the buffer-keeper. A surreal, per-game-seeded world of half-functioning survivors — a granary still keeping a dead world's last harvest, a watchman-golem still calling "all's well" over breached walls — keeps the puzzle fresh every play-through.
How we built it
This submission is a pre-production design package — four coherent artifacts rather than a built game: a Game Design Document, a Player Journey Map (the first 15 minutes, beat by beat), a Visual Concept Package, and a Production Plan.
I designed it the way you'd design a real game — first principles, one decision at a time. Every choice was tested against a single question: what does "you are a body, with others, in a place" unlock that a 2D screen can't? The concept converged from a bare fantasy ("commanding a band on a quest") through dozens of locked decisions into a focused vertical slice that doubles as the MVP. The Visual Concept Package pairs a mood-and-palette study with concept imagery generated via Google Gemini (Nano Banana 2) and a UI mockup built in HTML/CSS. The whole process was run as a structured, AI-assisted design dialogue — used as a sounding board and a discipline, with every design call my own.
Challenges we ran into
The platform pivot. My first concept was a 2D node/network sim — and it fought the platform at every turn. Horizon Worlds went mobile-exclusive (VR retired the day before I started), so I scrapped it and rebuilt from the platform's actual strengths. Painful, but it's why the final concept fits from first principles instead of being bolted on.
Scope versus depth. A "reseed civilisation" premise wants to be enormous, and the page budgets are tiny. The hardest discipline was resisting "a mile wide, an inch deep" — letting a bold full-epic vision coexist with one deep, concrete slice that proves the loop actually turns.
The believability bar. The delivered-community thesis lives or dies on whether the NPC brothers read alive in the most-judged minutes. The challenge wasn't building them — it was arguing, credibly, that they're buildable within Horizon Worlds' real mobile constraints, and designing to that bar rather than over-promising past it.
Accomplishments that we're proud of
The tightest thing in the design: the antifragility lesson is never preached — it's a consequence you walk into. Bracing hard for the visible Siege tempts you to over-specialise; then the random climax breaks exactly the brotherhood that optimised. The game teaches resilience by letting you feel the cost of not keeping slack.
I'm proud that the theme and the platform are the same thing — male fellowship delivered through genuine co-presence, not depicted. And that every ambitious feature ships a Tier-0 floor that stands on its own, so the design is a complete game at the start and an epic in view — bold at the horizon, honest at the ground. Smaller wins I like: the conflicting-reports gem (redundancy becomes a question of judgment, not a free win), and the quorum-tier insight that the waiting itself is the ritual — "we don't start until everyone's here" is an act of belonging.
What we learned
That the strongest concepts come from collapsing two problems into one: the design got dramatically better the moment I stopped treating "what men need" and "what this platform uniquely does" as separate questions. I learned to design to a platform's real constraints instead of around them, and that the honest move under judging pressure is to name your floor and your roadmap separately — feasibility is won by what you don't over-promise. I also relearned an old lesson in a new medium: belonging is forged through shared hardship toward a common goal, never by hanging out — so a co-op game has to engineer the interdependence, not just enable the chat.
What's next for Rekindled: The Path of Kin
The slice proves the loop turns; the full game opens it onto an epic, in three movements. A widening world: the campaign begins before the fall (feel "the middle" snap), it plays the after-the-fall reseed, and opens onto a cyclical story where preparedness itself becomes the meta-game — across a peer network of free-towns that trade, send envoys, and aid one another. A living world: a cloud-backed AI layer that authors plausible events and adjudicates a player's improvised solutions for coherence, plus slow-burn "stretched middle" stressors and a procedural family of uncanny survivors. A shared world: a denser collective life — seasonal feasts, inter-town gatherings, and eventually real brothers taking the field together. None of it asks the player to wait for the epic: every floor is playable in the MVP, and the vision is simply where it grows.
Log in or sign up for Devpost to join the conversation.