Collaborative Game Development
My Baby Pooped a Mythic
A collaborative Roblox project where an intentionally absurd progression loop is backed by explicit ownership, integration gates, and QA.
- Role
- Systems · Integration · QA
- Status
- Active development
- Stack
- Luau · Roblox Studio · Git
- Provenance
- Collaborative project · Van, Aian, Jericko
Built with Aian and Jericko, the game revolves around gathering food, feeding or planting it, babies producing poop/gems, selling or fertilizing the result, and reinvesting into progression such as Backpack capacity, Poop Basket capacity, Nursery Luck, garden systems, collections, and rarity/RNG reveals. Ownership rotates by phase and the portfolio keeps collaboration visible.
00 / System
How the work connects.
- 01Gather→
- 02Feed / Plant→
- 03Baby→
- 04Poop / Gem→
- 05Sell / Fertilize→
- 06Upgrade→
- 07Collect→
- 08Verify
The case study is about shared development, not solo ownership.
Work is divided by phase and responsibility, then brought back together through shared profile data, integration gates, review, and QA. The roles are not treated as permanent individual ownership of the whole game.
One major assigned phase centered on baby systems, the Crib Machine, and collections.
That phase covered baby RNG, ownership and storage, active babies, guarantee behavior, Baby Index, Poopdex, networking, profile migration, and related UI/world integration. Other phases rotate responsibility across the team.
Systems are designed to survive contact with everyone else’s systems.
The project uses explicit phase ownership, shared persistence boundaries, Script Sync checks, integration tests, exploit/security review, and release-candidate QA rather than assuming an isolated feature is complete because it works alone.
Testing and fairness rules are part of the game design.
Deterministic checks, integration verification, manual QA, migration review, and correction follow feature work. Monetization is kept deterministic and separate from core Luck/RNG odds so paid systems do not quietly redefine the progression rules.
Media / Selected Evidence
Evidence from the work.
The strongest project surfaces, system artifacts, QA output, and technical evidence stay curated here.
A real gameplay screenshot showing the gather → feed/plant → poop → sell/fertilize → upgrade loop.
Real baby RNG / Crib Machine work from the assigned development phase.
Collections, ownership, guarantees, and index UI.
Real world, nursery, garden, progression, or upgrade work.
Script Sync, profile migration, shared-data, or team integration evidence.
Deterministic/manual QA or integrated verification evidence without unsupported test-count claims.