How edo9300/edopro works
Project type and purpose
• Project Ignis: EDOPro is a cross-platform, C++-based automatic duel simulator client for the Yu-Gi-Oh! Official Card Game. It ties together a game-logic core (ocgcore), a custom GUI framework (gframe + Irrlicht), networking, scripting, resource managers, audio backends, and auxiliary tools (updater, bot, repo manager, Discord integration).
File structure
• Top-level modules:
• discord-launcher (macOS Discord RPC stub)
• gframe (monolithic GUI + platform abstraction + game client logic)
• irrlicht (embedded 3D engine)
• ocgcore (external core engine submodule for rule scripting)
• sfAudio & SoundBackends (audio abstraction + multiple backend implementations)
• overwrites (custom patches for mingw and other toolchains)
• ios-assets, android, iOS subfolders under gframe (mobile platform ports)
• tools (scripts for embedding binary assets)
• travis, .github (CI/deployment pipelines)
• config, notices, LICENSE/COPYING (docs and licensing)
README for additional insights
• The README confirms:
• It is the game client only (no server core)
• It uses an automated scripting engine (ocgcore fork)
• Integrates open-source card/script repos via Git
Main components
a. User Interface Layer
• gframe GUI modules + Irrlicht renderer
• EventHandler → translates user input to game commands
b. Game Logic Core
• ocgcore (card rule engine, duel simulator)
• GenericDuel, DuelClient classes orchestrating matches
c. Resource & Data Management
• DataManager, ImageManager, RepoManager (card scripts, databases)
• Updater, ClientUpdater (downloads assets via Curl, Git2)
d. Audio Subsystem
• SoundManager → selects SoundBackend (irrklang, miniaudio, sdlmixer, sfml)
e. Networking & Multiplayer
• NetServer (host lobbies), DuelClient (client-side networking), Network abstraction
f. Auxiliary Services
• Discord integration (discord_wrapper, discord_register)
• WindBot AI plugin (windbot_panel, windbot)
g. Build & Deployment
• Premake5 scripts, Travis/GitHub Actions pipelines, platform port modules (Android/iOS)
Relationships & Interactions
• UI Layer ←→ Game Logic (commands, state updates)
• Game Logic ←→ Resource Manager (load card data, images, scripts)
• Game Logic ←→ Audio Subsystem (play sound effects, music)
• Game Logic ←→ Networking (send turn data, receive opponent moves)
• Updater & RepoManager → Resource Manager (update local script/db repositories)
• DiscordWrapper ←→ Game Logic & UI (rich presence updates)
• WindBot plugin ←→ Game Logic (automated commands)
Architectural patterns & design principles
• Layered architecture: separates UI, core logic, I/O, network, audio
• Strategy pattern for audio backends (SoundBackend interface + multiple implementations)
• Plugin/extension points: dllinterface, repo-based script loading
• Platform abstraction for OS-specific operations (COSAndroidOperator, COSiOSOperator)
• CI/CD orchestration with premake and Travis/GitHub workflows
Essential elements
• Clear component names (e.g., DataManager, SoundManager)
• Annotations for extensibility points (plugin API, script loader)