How stevedabartender/milkquest3 works
Project Type and Purpose
• This is a GameMaker Studio 2 game project (“Milk Quest: Half & Half”).
• It’s a monolithic, event-driven game built in GML (.gml/.yy scripts), containing resources (sprites, sounds, shaders, tilesets) and rooms (levels).
• The codebase includes managers for autoscrolling, cutscenes, input, saving/loading, and platform-specific build targets.
Top-Level Architectural Components
a. GameMaker Runtime & Build Targets
• Platform Export Modules: html5, windows, mac, linux, operagx (options/* directories)
b. Resource Manager
• Sprites (sprites/)
• Sounds (sounds/)
• Shaders (shaders/)
• Tilesets & Rooms (tilesets/, rooms/)
• Fonts (fonts/)
• Datafiles (e.g., text script datafiles/dScriptText.txt)
c. Script Library (scripts/)
• Utility scripts (input, collision, GUI drawing)
• Game logic scripts (change_room, save/load, objective checks)
• Character-specific scripts (jump, drive, punch, AI)
d. Object Layer (objects/)
• Manager objects (oPersistent, oCamera, oCutsceneManagerMQ2, oAutoscrollerManager, oSaveDesk)
• Gameplay objects (oPlayer, oEnemy, pickups, traps, NPCs, checkpoints)
e. Room/Level Layer (rooms/)
• Entry-point rooms (rMainMenu, rLevelSelect, rTitle)
• Level rooms (rChristmasLevel1, rFactory2Main, rFezTower, etc.)
• Triggered via change_room scripts
Relationships & Data Flow
1. Startup: Platform Loader → Resource Manager loads assets → Persistent object initializes game state
2. Main Menu Room: oTitleManager handles menu input → invokes change_room script
3. Room Load: change_room → instantiate appropriate room (.yy) → instance creation code → objects spawn
4. Game Loop (per frame):
• Input Manager script (getInput) feeds events to player NPC objects
• Each object’s Step event calls relevant scripts (movement, AI, collisions)
5. Managers coordinate higher-level events: oCutsceneManagerMQ2 runs timelines/timelines/ on triggers → dialogues via call_textbox
6. Save/Load: save_game_data / load_game_data invoked on checkpoints or menu actions
Architectural Patterns & Principles
• Separation of concerns:
• Resource directories vs. logic scripts vs. platform options
• Manager objects encapsulate cross-cutting concerns (camera, saving, cutscenes)
• Reusable script library: Many objects call common scripts (standard_collision, draw_gui).
• Layered Room Design: Backdrops, tile layers, instance layers, GUI overlays