product software
Bloom
A Unity 6 PvE co-op extraction game with a large procedural world, multiplayer systems, and a defined playtest path.
No public links are recorded for this case study.
Challenge and constraints
The project needs a coherent player experience while world generation, networking, performance, and content direction evolve together.
Constraints
- World generation, networking, performance, and content direction evolve together
- The project remains in development
- Public evidence cannot expose the private repository
What I owned
Product ownership, systems design direction, technical planning, AI-assisted implementation review, and playtest quality assurance.
Ownership
- Define product milestones
- Review multiplayer and world-system contracts
- Prioritize player-facing risks
- Maintain playtest evidence
Decisions and implementation
The decisions define the boundary; the implementation records what was delivered inside it.
Decisions
- Keep multiplayer state server-authoritative
- Treat procedural-world performance as a validation gate
Implementation
- Server-authoritative multiplayer foundation
- Procedural-world systems
- Playtest planning
- Performance and launch-preparation gates
Validation
Evidence is checked against the surface it is meant to demonstrate.
Checks
- Unity EditMode test guidance
- Multiplayer foundation review
- Performance and launch-preparation checklists
Evidence-backed outcomes
Each delivered result is paired with the public proof basis that supports it.
- Documented technical directionBasis: Recorded in reviewed product milestones and system contracts.
- Defined the multiplayer foundationBasis: Supported by multiplayer foundation review.
- Prioritized playtest and performance workBasis: Recorded in performance and launch-preparation checklists.
Evidence gallery
Each artifact is selected for what it explains and reviewed for public safety.
No public-safe media is available for this case study. The validation and outcomes above are the available public record.
Related projects
No public project relationships are recorded for this case study.