HyperSphere

HyperSphere is a Unity 3D game built around structured progression rather than a single endless loop: a main menu, player selection, eight levels and six discrete missions, each with its own scene, objectives and scoring. The engineering interest is not in any one level — it is in the manager layer that keeps fourteen separate scenes behaving like one continuous game.

Every scene you add is another place the game can forget itself

A single-scene arcade game is straightforward: everything that matters lives in one place and nothing has to survive anything. HyperSphere has more than fourteen scenes — menus, player selection, eight levels and six missions — and score, chosen character, unlocked progress and audio state all have to cross every one of those boundaries intact.

Get it wrong and the symptoms are unmistakable: the score resets on level load, the selected character reverts to default, a mission counts the same pickup twice. None of those are hard bugs to fix individually; they are hard to stop recurring, which makes it an architecture problem rather than a gameplay one.

• Unity destroys everything in a scene on load, so cross-scene state needs an explicit owner
• Mission rules differ per mission, but the shared game loop must not fork into six copies
• Level content has to be authored in the editor, or every new level becomes a code change
• The performance budget is a mobile one — draw calls and runtime instantiation both matter

A persistent manager layer over prefab-driven, scene-authored content

A single persistent game manager owns the state that must survive scene changes — selected player, score, progression. Per-scene managers own only what belongs to their own scene and nothing more, which keeps the boundary between "the game knows this" and "this level knows this" explicit rather than implied.

Mission scripts implement only their own objective and completion condition, consuming shared score and timer services instead of re-implementing them. Six missions therefore share one game loop rather than six near-identical copies of it.

Level content is assembled from prefabs — platforms, coins, score boosters — placed in the editor. Building a new level is authoring work, not programming. UI flow runs through its own controllers for the menu, player selection and game-over states, with TextMesh Pro keeping typography readable at every resolution.

The problems that took real work to solve. Tap any one to read how.

• A published, playable build on itch.io with a complete menu → selection → level → mission → game-over flow.
• Fourteen playable scenes sharing one persistent state layer, one score service and one timer service.
• A content pipeline where adding a level is scene authoring rather than programming.
• A documented import path so any reviewer can get the project running from a clean Unity installation.