How bosh/trogdor-pinball works
Main Components
a) Core Game Components:
• MPF Framework Layer
• FAST Neuron Hardware Interface
• Godot-based GMC (Game Media Controller)
• Ruby-based Build System (Trogbuild)
b) Configuration Layer:
• Base Configurations (/config)
• Mode Configurations (/modes)
• Hardware Definitions
• Generated Configurations
c) Game Elements:
• Mode System
• Controller
• Sound System
• Light Controller
• Switch Management
• Ball Device Management
┌─────────────────────────────────────────────────────┐
• Physical Layer │
• (FAST Neuron Hardware, Switches, Lights, etc) │
• ┘
• ↕
┌─────────────────────────────────────────────────────┐
• Hardware Interface Layer │
• (MPF Hardware Abstractions, Drivers) │
• ┘
• ↕
┌─────────────────────────────────────────────────────┐
• Game Logic Layer │
• ┬─────────────────────┬────────────────┤
• Mode │ Base Game │ Show │
• System │ Controller │ Controller │
• ┴─────────────────────┴────────────────┘
• ↕
┌─────────────────────────────────────────────────────┐
• Presentation Layer │
• (Godot-based GMC, Display, Audio) │
• ┘
Key Relationships to Highlight
• Build pipeline from Ruby-based Trogbuild to generated configurations
• Mode hierarchy and relationships
• Demonstrate the audio system's integration with game events
• Interaction between physical inputs and game logic
• Configuration flow from YAML files to runtime systems
Build System Integration
How trogbuild.rb generates:
• Mode configurations
• Sound hooks
• Achievement systems
• Definitions
Monitoring and Debug
Monitoring system's architecture showing:
• Monitor interface
• Debug connections
• Live state observation
Remember to:
• Keep hardware abstraction layers clear
• Notes for key architectural decisions
• Configuration file relationships
This architecture should emphasize the real-time nature of the pinball system while showing how the various components interact to create the game experience.