How ameyvibs/run-n-gun works
Main Components Identification
a) Game Core Systems
• Game Manager (obj_game)
• Camera System (obj_camera)
• Transition System (obj_transition)
• Menu System (obj_menu)
b) Player Systems
• Player Controller (obj_player)
• Gun Mechanics (obj_gun)
• Player States (running, air, dead)
c) Enemy Systems
• Skeleton Enemy (obj_skeleton)
• Skeleton Gun (obj_skeleton_gun)
• Enemy Projectiles (obj_skeleton_bullet)
d) Environment Systems
• Ground/Collision (obj_ground)
• Triggers (obj_trigger)
• Signs (obj_sign)
e) Effect Systems
• Particle Effects (obj_dust, obj_hitspark)
• Sound System
• Screen Shake
Component Relationships
[Game Manager]
• [Camera System]
• [Player Systems] ←→ [Gun System]
• [Effect Systems]
• [Enemy Systems] ←→ [AI Controller]
• [Effect Systems]
• [Environment Systems]
Technical Details
• Resource management (sprites, sounds, fonts)
• Input handling system
• Collision system
• Shader system (shd_white)
Implementation Notes
• Annotations for critical scripts like srp_kill_player and srp_slide_transition
Architectural Patterns to Highlight
• Event-driven architecture (GameMaker's event system)
• Object-oriented design (parent-child relationships between objects)
• State machine pattern (player and enemy states)
Room transitions and game flow
This approach will create a comprehensive visualization of the game's architecture while maintaining the specific requirements of a GameMaker Studio 2 project structure.