How thereisnousername1/comp3000-final-year-project works
Project type and purpose
• This is a Unity-based standalone game (final-year project) consisting of scenes, assets, scripts, and render pipeline settings. It has no external backend or server components—everything lives within the Unity Editor and the built player.
File structure
• Top-level directories:
• Assets – all game assets (scenes, scripts, graphics, input actions, render settings, tutorial data).
• Packages – Unity Package Manager dependencies (manifest.json).
• ProjectSettings – build and engine configuration (URP settings, input manager, audio, quality, XR, etc.).
• README.md – high-level description.
• Notice the “Assets/Scenes” folder indicating multiple game levels, “Assets/Scripts” for gameplay logic, “Assets/Settings” for render pipeline assets, and “Assets/TutorialInfo” for tutorial content plus an Editor extension under Scripts/Editor.
README for additional insights
• The README confirms it’s a Unity game in active development, with branching strategy (development → main) and no mention of external data stores or networked services. The Trello link points to feature tracking.
1. Unity Editor & Build System
2. Render Pipeline (URP)
3. Game Runtime – subdivided into:
• Scene Manager (Assets/Scenes)
• Gameplay Scripts (Assets/Scripts + TutorialInfo/Scripts/Readme.cs)
• Input System (Assets/InputSystem_Actions.inputactions)
4. Project Settings (configuration assets)
5. Packages (external libraries)
• User Input → Input System → Gameplay Scripts
• Gameplay Scripts → Scene Manager (SceneSwap.cs) → Load/Unload Scenes
• Scenes → GameObjects → Scripts & Assets
• Render Pipeline reads project settings & scene camera data → Renders frames
• Editor scripts (ReadmeEditor.cs) → Unity Editor UI (designer-time only)
c. Architectural patterns/design principles:
• Modular scene-based architecture: each level/scene encapsulates its own content.
• Separation of concerns: Input System, Scene Management, Rendering Configuration, and Tutorial Logic are kept in distinct folders.
d. Key technologies/frameworks:
• Unity Engine & Editor (C# runtime)
• Universal Render Pipeline (URP) assets in Assets/Settings & ProjectSettings/URPProjectSettings.asset
• Unity Input System package (manifest.json dependency)
• Custom Editor extension (ReadmeEditor.cs)