How pgmdev/pgm works
High-Level Architecture Overview
a. Core System
• PGM Plugin Core (central component)
• Match Management System
• Management System
• Player Management System
b. Module System
• Game Modes (e.g., Blitz, CTF, Control Points)
• Features (e.g., Spawns, Teams, Filters)
• Utilities (e.g., Commands, Events)
c. Platform Layer
• Modern Platform Implementation
• SportPaper Platform Implementation
Key Components
a. Core Components:
[PGMPlugin] --> [MatchManager]
[MatchManager] --> [MapLibrary]
[MatchManager] --> [PlayerManager]
b. Match System:
[Match] <--> [MatchModules]
[Match] <--> [Teams/Parties]
[Match] <--> [Players]
c. System:
[MapLibrary] --> [MapContext]
[MapContext] --> [MapModules]
[MapContext] --> [Features]
Module Integration
How different modules interact:
[Core] <--> [Filters]
[Core] <--> [Regions]
[Core] <--> [Goals]
Platform Abstraction
Demonstrate the platform independence:
[PGM Core] <--> [Platform API]
[Platform API] --> [Modern Platform]
[Platform API] --> [SportPaper Platform]
Important Relationships to Highlight
• Match Lifecycle Management:
[MatchManager] --> [Match States]
[Match States]: Loading -> Running -> Finished
• Player Management:
[MatchPlayer] --> [Party/Team]
[MatchPlayer] --> [Statistics]
[MatchPlayer] --> [Settings]
Implementation Details to Note
• Separation between API interfaces and implementations
• Async vs sync operations
• Extension points for custom modules
[Platform Layer]
• ↑
[Core Systems]
• ↑
[Game Modules]
• ↑
[Utilities/Support]