How egofree71/wanted-monty-mole works
Project type and purpose
• This is a Unity-based remake of the C64 game “Wanted: Monty Mole” (beta, ~80% complete).
• It consists of Unity scenes, C# scripts, assets (sprites, animations, audio, fonts), and uses Unity’s Mono runtime and TextMeshPro.
File structure to extract high-level modules
• Top-level Unity folders under Assets:
• Animation (Clips, Controllers)
• Prefabs (Entities, Environment, UI)
• Resources (audio, fonts, Levels.json, map data, mods)
• Scenes (Intro, Main, Maze, End)
• Scripts (Entities, Maze, Intro, Tiles, Managers)
• Sprites (Entities, Environment, Fonts, Squares)
• TextMeshPro (shaders, docs, fonts)
• ProjectSettings & Packages hold engine/configuration metadata.
• Build output directories (Monty_Data, maze_Data, monty_mole_Data) contain Unity’s runtime data and Mono files.
README for additional insights
• Game is loaded by opening Main scene (runtime) or Maze scene (pre-generate maze).
• Input via gamepad or keyboard controls.
• Maze generation is a key feature (80% implemented).
a. Main components
• Unity Engine Core (Rendering, Physics2D, Audio, Input, SceneManagement)
• Mono/.NET Scripting Runtime (C# scripts)
• Game Manager Layer
– GameManager, LevelManager, MazeGenerator, ImportMaze
• Entity Module
– Prefabs + Scripts under Scripts/Entities + Animators/Controllers
• Maze Module
– Maze prefabs (TilesMap, BridgeTile, CrusherTile, etc.) + generator scripts
• UI & Intro Module
– IntroManager, TextScroll, ScrollingText, HealthBar, TextMeshPro integration
• Resource Loader
– Resources/Levels.json, map bytes, audio clips, fonts, mods loaded at runtime
• Scenes
– Intro → Maze (optional) → Main → End
b. Relationships & data flow
• Input System → GameManager → LevelManager → Entity Module & Maze Module
• MazeGenerator → Environment prefabs → Scene graph
• Entity Scripts respond to physics events → Animator Controllers → Rendering
• GameManager updates UI Module → HealthBar/TextMeshPro output
• Resources.Load API calls fetch JSON, audio, fonts at start or on demand
• SceneManager loads/unloads Scenes and persists managers where needed
c. Architectural patterns & design principles
• Unity’s component-based architecture (GameObjects + MonoBehaviours)
• Separation of concerns: Maze generation vs. Entities vs. UI vs. Game flow
• Prefab-driven content: reusable environment and entity prefabs
• Data-driven levels: JSON and binary maps in Resources
d. Technologies & frameworks
• Unity 2020.3 LTS
• C# / .NET / Mono runtime
• Unity2D Physics, Audio, Animation systems
• TextMeshPro for rich text in UI
• JSON file I/O for level data
Detail without overthinking
• Major scripts, prefabs, and data sources as separate components.
• Essential flow (input → logic → physics → rendering/audio → UI) and how the maze generation fits in.