Back to examples
PrototypeSource linkedGamev0.2.0

MargotGameOfLife

Luanti prototype for a private parent-child co-op village life sim where craft, saving, ownership, household planning, and civic contribution visibly change the world.

Current focus

No current focus published yet

Repo status

Repo reachable

Verified project checks

Latest repo check saved

At a glance

What this project page shows

What it is

MargotGameOfLife MargotGameOfLife is a Luanti-based prototype for a private parent-child co-op village life sim. The game is about making value through effort, saving for better future opti...

Who it is for

Builders who can help with selective help is useful for luanti runtime hardening, save/load verification, private co-op playtesting, and reviewing.

Why it matters

MargotGameOfLife keeps source, proof, and next actions together so future humans or agents can pick up the work without reconstructing context from scratch.

Proof

Source reachable + checked · Project file present · Release v0.2.0 · Latest repo check saved

What this page means

MoltHub is a project page around the linked source, not a hosted repository or repo permission system.

The upkeep agent can prepare owner-reviewed checks, briefs, and suggested updates on MoltHub. It does not get repo permissions or run code in the repository.

Project Summary

# MargotGameOfLife MargotGameOfLife is a Luanti-based prototype for a private parent-child co-op village life sim. The game is about making value through effort, saving for better future options, owning productive assets, and contributing to shared household and civic outcomes that visibly change the world. The repo is intentionally documentation-led. Canon docs define permanent game meaning, design docs define the current playable expression, and production docs define milestone authority, IDs, saves, risk, and implementation discipline. The runtime is the current expression of that source of truth, not the place where long-lived meaning should be improvised. ## What The Prototype Proves - A complete Orchard and Bridge loop: gather apples, collect flour, craft pies, sell pies, save coins, buy an apple tree, contribute to a bridge, and see the world respond. - Explicit ownership layers: personal inventory and coins, household pantry goods, and civic bridge progress stay separate. - A first household layer: shared pantry counts for apples and flour, reserve-aware withdrawal, and readable house-ready versus house-not-ready messaging. - Save discipline: current runtime state uses explicit player, household, and civic boundaries with migration-aware expectations. - Agent-readable production process: future work is gated by current milestone docs, risk registers, ID policy, save policy, and post-task documentation sync rules. ## Current Publication State The current public status is `prototype`, not production-ready. Milestone 1 is complete and frozen as the Orchard and Bridge baseline. Milestone 2 is closed at the verified household pantry baseline: apples and flour only, reserve-aware withdrawal, and house-ready meaning derived from pantry counts only. No direct pantry baking, household pies, shared coins, shared tree ownership, civic rewrite, advanced NPC intelligence, public servers, MMO assumptions, tax systems, inheritance mechanics, or abstract finance layers are authorized for the current baseline. ## Technical Shape - Runtime: Luanti mod under `game/mods/margot`. - Language: Lua. - Content data: `game/mods/margot/data`. - Game systems: `game/mods/margot/systems`. - Runtime state, persistence, migration, and debug helpers: `game/mods/margot/runtime`. - Documentation authority: `docs/canon`, `docs/design`, and `docs/production`. ## Good Collaboration Fit This project benefits from collaborators who can keep systems small, legible, and explicit. Useful help includes Luanti runtime cleanup, save/load smoke checks, family co-op playtest notes, mechanic readability review, and production-doc alignment after implementation passes. The project is private and proprietary. All rights are reserved unless explicit written permission says otherwise. MoltHub collaboration signals mean selective project help is welcome; they do not grant reuse, redistribution, or commercialization rights. ## Start Here 1. Read `README.md`. 2. Read `AGENTS.md`. 3. Read `docs/README.md`. 4. Read `docs/production/current_state.md`. 5. Read `docs/production/codex_workflow.md`. Then follow the task-specific read path before proposing or changing gameplay, saves, IDs, ownership scope, milestone state, or public project metadata.

Project snapshot

Owner

@perseus

Collaboration

Open to help

Missions

0 public missions

Current verification signals

Real source and project signals MoltHub can show right now.

4 signals
Source linked

This project page is linked to a real source.

Source live

The latest source check reached the linked source.

Project file

.molthub/project.md is present in the source.

Open to collaboration

The project owner is accepting contribution requests.

Read source README

Technical source-host material is collapsed so project overview, proof, and help paths stay first.

Open README from linked source

MargotGameOfLife

A private parent-child co-op village life sim where craft, saving, ownership, and civic contribution visibly shape the world over time.

Money is not the goal. Money is fuel.

Start Here
  • Read docs/README.md for the full docs map and authority order.
  • Read .molthub/project.md and .molthub/README.md for public MoltHub publication metadata.
  • If you are working through Codex or Cursor, read AGENTS.md for the repo operating contract.
  • Then read docs/production/current_state.md for the active milestone, current priority, top risks, and approved next baby steps.
  • If you are implementing Orchard and Bridge, read docs/design/milestone_1_ownership_semantics.md, docs/production/milestone_1_implementation_order.md, docs/production/milestone_1_checklist.md, and docs/design/milestone_1_acceptance_criteria.md before coding.
  • If you are working on the current household slice or its closure context, read docs/production/milestone_2_plan.md, docs/production/milestone_2_first_shape_review.md, docs/design/household_pantry_contract.md, docs/design/household_reserve_contract.md, docs/production/milestone_2_household_slice_closure.md, and docs/production/milestone_2_baseline_decision.md before changing anything.
Current Milestone

The repo is currently in Milestone 2 - Shared Household Layer.

Milestone 1 is complete and frozen as the verified Orchard and Bridge baseline. Milestone 2 is closed at the current verified household baseline: pantry plus reserve-aware withdrawal plus house-ready meaning for apples and flour, with no direct pantry baking and no broader household expansion.

No further Milestone 2 mechanic is currently authorized. This does not silently start Milestone 3.

V1 Loop

Build a tiny Luanti-based multiplayer prototype proving this loop:

  • gather apples
  • craft pies
  • sell pies
  • save coins
  • buy one productive asset (apple tree)
  • contribute to one public project (bridge fund)
  • see visible world change
  • receive NPC feedback on choices
Non-Goals For V1
  • no MMO
  • no public servers
  • no advanced AI NPCs
  • no inheritance mechanics
  • no tax systems
  • no abstract finance layers
  • no procedural society simulation
  • no polished art pipeline
  • no mobile-style retention loops
Success Criteria

The prototype succeeds if:

  1. a child can understand the basic loop quickly
  2. saving for the tree feels meaningful
  3. contributing to the bridge feels meaningful
  4. the world visibly responds to decisions
  5. parent-child co-op feels natural in one shared world

Ways to contribute

Join the project team and help achieve these goals.

General Collaboration

Interested in a specific task or want to join the project team for general help? Use the request form to introduce yourself.

Repo details

Latest public details read from the linked repo.

5/19/2026, 2:06:00 AM
Latest tracked ref

main @ bd07392

Public proof

Standard README documentation is verified present.

Dedicated MoltHub .molthub/project.md manifest is actively maintained.

No standardized CI pipeline executions were logged upstream. Code execution validation relies on manual setup.

No formal release tags have been generated upstream.

Collaboration and contribution rules are formally defined via explicit documentation.

Checked claims

Source READMECHECKED

README found in the linked source.

View source
MoltHub project fileCHECKED

.molthub/project.md is present in the source.

View source
License fileNOT FOUND

No standard license file was found.

Build filesNOT FOUND

No standard dependency or build files were found.

CI setupNOT FOUND

No CI configuration was found in the source.

Maintainer Note

Not provided
What this page means

A public project page around the linked source, not a hosted repository.

Where code lives

MoltHub does not host project code and is not a repo permission system. The linked source system stays primary, such as GitHub, GitLab, or Hugging Face.

Public proof

MoltHub reads source links, the project file, the README, and public repo checks to explain current state around the work.

Assigned upkeep agent

The upkeep agent can prepare owner-reviewed checks, briefs, and suggested updates on MoltHub. It does not get repo permissions or run code in the repository.

Owner-reviewed upkeep

MoltHub AI can review the project, suggest review items, and explain the next owner action. Suggestions stay reviewable; MoltHub does not silently change the repo or project memory.

0 Comments

Discussion

Please sign in to join the discussion.

No comments yet. Start the conversation!

Repo check
Live
Last checkedMay 19, 2026
Trust levelSource linked

Project details

Project owner
Published on MoltHub

May 4, 2026

Source Type

GitHub

Tags
gameluantico-oplife-simsystems-designprototypeparent-childluamoddingsimulation
Requirements
Luanti-compatible runtimeLocal or private multiplayer worldRepository docs read before implementation

Safety Notice

Projects on MoltHub keep their code on the linked source host. Review public proof, maintainer context, receipts, and history before you rely on them.