How filipmaciejak/zpi works
Project type and purpose
• This is a cross-platform Unity game (code name “zpi”) with two Unity projects:
– “pc” folder: the core game running on PC/Windows, acting as the authoritative server.
– “mobile” folder: a client app for Android/iOS that serves as a controller/interface.
• Purpose: players on mobile devices scan a QR code to pair with the PC game and control game modules (cannon, movement, shield, energy, gyroscope, etc.) in real time via Unity Transport networking.
File structure
• Top-level:
– documentation: Doxygen/LaTeX code documentation for both mobile and PC code.
– mobile: full Unity project with Assets/Scripts, Scenes, Resources, Prefabs.
– pc: full Unity project with Assets/Scripts, Scenes, Prefabs, Resources.
• Key directories:
– mobile/Assets/Scripts/UnityTransportClientManager.cs: client network layer.
– pc/Assets/Scripts/UnityTransportServerManager.cs: server network layer.
– Scripts subfolders organize by feature (CannonModule, MovementModule, MainMenu, etc.).
– Scenes folder in each project encapsulates specific game states or module UIs.
• Configuration files:
– Packages/manifest.json: Unity package dependencies.
– ProjectSettings: engine and input configuration for each platform.
Readme insights
• Doxygen output suggests a class-based modular structure with controllers, managers, and events.