System design
Gameplay responsibilities are separated into focused components.
← All projects
Software Engineering · Game Systems
Stud Safari
A Roblox zoo-management project using Lua to explore modular gameplay systems, player interaction and maintainable game logic.
01
Overview
Stud Safari extends the portfolio beyond notebooks into an interactive, stateful software project.
The concept centres on building and managing a virtual zoo. Development involves connecting player actions to habitat, animal, economy and progression systems while keeping the code organised enough for features to evolve independently.
02
Technologies
03
Key Results
Player state
Actions update the world, economy and progression state.
Delivery
No player-count or engagement claims are made before release.
04
Architecture
The intended structure separates user interaction from domain logic and persistence concerns, reducing tight coupling between game objects.
Player input
Interaction layer
Game services
World state
UI feedback
05
Visuals
Gameplay media pending
Screenshots will be added when representative gameplay and interface states are ready to publish.
06
Challenges
State coordination
Keeping world, player and interface state synchronised as actions occur.
Module boundaries
Separating responsibilities without fragmenting simple gameplay logic unnecessarily.
Event lifecycle
Managing connections and updates so repeated interactions remain predictable.
Iterative design
Balancing technical structure with frequent gameplay changes.
07
What I Learned
- How event-driven game logic differs from sequential notebook workflows.
- Why clear module ownership makes interactive systems easier to extend.
- How player feedback must stay aligned with underlying state changes.
- How version control supports iterative development outside conventional web or data projects.
08
Repository Links
A public repository or Roblox experience URL has not been provided.