How videre-project/mtgosdk works
Core Architecture Layer
• MTGOSDK (Core Package)
• MTGOSDK.MSBuild (Build Tools)
• MTGOSDK.Win32 (Native Interface)
Runtime Integration Layer
• ClrMD debugger interface connection between MTGOSDK and the MTGO client
• Injection process flow:
• Process attachment
• Memory inspection
• Object reflection
• ScubaDiver component that handles remote communication
API Services Layer
• Chat System
• Collection Manager
• Event System
• Play System
• Trade System
• Settings Manager
• User Management
To show their interactions with the core runtime
External Integration Layer
Integration points with:
• MTGO Client Process
• Win32 API
• .NET Runtime
• Reference Assembly Generation
Key Elements to Include:
Process Flow
• Bootstrapping process
• Remote procedure calls
• Event subscription paths
• Memory inspection routes
Security Boundaries
• Process boundaries
• Privilege levels
• Security context transitions
Data Flow
• Primary data paths
• State management routes
• Event propagation
Special Considerations:
Remoting Architecture
• Client-server architecture between SDK and MTGO
• RemoteNET-based communication
• Snapshot runtime components
Build System
• MSBuild pipeline
• Reference assembly generation
• Code generation paths
Win32 Integration
• Native API integration points
• Process manipulation paths
• Memory access routes
• Component types (Core, Build, Native)
• Connection types (Dependencies, Events, Data Flow)
• Process boundaries
• Security contexts
• Data flow directions
Layout Guidelines:
Win32 components on the side
Use clear visual hierarchy:
• Different line styles for different types of connections