A little world with a lot of state.

A collaborative 2D cat simulation combining minigames, changing needs, random events, and persistent player state.

Unity
C#
UML
Unity Cloud Save

THE CONTEXT

A closer look.

The problem

A simulation game needs consistent behavior across player actions, minigames, random events, and saved state. Team development also needs clear responsibilities and a shared model of the application.

What I built

I led a four-person team developing a 2D cat simulation in Unity and C#. I authored UML diagrams and requirements analysis, and worked on minigames, dynamic cat AI, random events, authentication, and persistence.

HOW IT FITS TOGETHER

The architecture.

01
Unity scenes present the cat simulation and minigames.
02
C# gameplay logic updates cat needs and responds to player actions.
03
Random events introduce changes in the simulation.
04
Unity Cloud Save supports persistent player state.

ENGINEERING DETAILS

Decisions that matter.

A shared design

Requirements analysis and UML diagrams defined system architecture, gameplay logic, and team responsibilities.

Interconnected behavior

Minigames and random events interact with cat needs and game currency, connecting separate features through shared state.

An honest prototype

The public README documents an incomplete Flappy Fish minigame caused by differing Unity versions. This is presented as a team prototype, not a fully released product.

Public MeowVerse README and résumé. Illustration is conceptual; no credentials or private contact information from the repository are reproduced.

UP NEXTpH Measurement System