How arm-role/rushhour works
Project type and purpose
• This is a Unity‐based multiplayer game (“RushHour”) that uses Photon Fusion for networking, ParrelSync for local multi‐instance testing, and a custom UI/menu layer (PhotonFusionMenu).
• Its purpose: present a start scene, handle login & lobby, allow players to create/join a session, then run a game scene with drag‐and‐drop cooking gameplay.
File structure
• Top‐level Unity folders:
• Assets/Editor – custom build & layout utilities
• Assets/ParrelSync – tooling to spin up multiple editor instances
• Assets/Photon/Fusion – Fusion’s SDK (core, runtime, codegen, editor, plugins)
• Assets/Photon/FusionMenu – FusionMenu UI layer (menus, code, prefabs)
• Assets/Resources – game scenes, scripts, prefabs, scriptable objects
• Scenes under Resources/SceneStart, Resources/Scene (lobby/login/etc.), Resources/SceneGame
• Under SceneGame/Script you see clear sub‐folders representing architecture: Dependency Inject, Event, GameManager, Item, UI, SceneManager, Spawner, etc.
• ProjectSettings and Packages indicate use of Universal Render Pipeline, WebGL target, and multiplayer settings.
Important architectural patterns & design principles
• Dependency Injection container (SceneGame/Script/Dependency Inject)
• Event messaging (SceneGame/Script/Event) for decoupling game systems
• Singleton & MonoSingleton for global managers (SoundManager, ScoreManager, etc.)
• ScriptableObjects for data (items, menu definitions)
• Modular “feature folders” under SceneGame/Script following separation of concerns
• Photon Fusion as the authoritative network layer; FusionMenu as the UI abstraction over Fusion’s lobby/connection APIs
Relationships & interactions
• Unity Client’s Game Logic sends/receives network RPCs & state updates via the Photon Fusion module.
• FusionMenu UI calls Fusion API to create/join sessions, then triggers scene transitions.
• Events emitted by network callbacks (OnPlayerJoined, OnInputReceived) propagate via the Event Bus to GameManager / Item System.
• ScriptableObjects feed data into Game Logic and UI.
• ParrelSync sits outside runtime – only for development to spawn clones of the editor.
Essential elements
• Labels for each component and sub‐component