How legend-of-dragoon-modding/severed-chains works
Relationships and Interactions
• A high-level flow from Initialization to Runtime Loop:
– Input events (from platform/input) flowing into the Game Engine.
– Calls to the Graphics (RenderEngine, Gpu, ShaderManager) and Audio subsystems for output.
• Integration point of the Modding API:
– This component intercepts or augments game events using its own event bus (modding events, configuration updates).
• Dependency on external tools:
– Note Gradle (build.gradle and gradlew) orchestrates builds and dependency management.
Architectural Patterns & Principles
• Layered/Modular Structure – The system splits between low-level subsystems (graphics, audio, input) and high-level game logic.
• Event-Driven Design – The game and modding API use events extensively (as seen by the presence of many “Event” classes in modding and debugger packages).
Relevant Technologies & Frameworks
• Java (Java 21 is required) is the basic language.
• Gradle for build automation.
• Modding API and reflection/event dispatching mechanisms enabling dynamic behavior.
• Supporting libraries such as LWJGL for low-level system and possibly log4j2 for logging (log4j2.xml is present).
Final Steps
• Gradually decompose the system into its layers (initialization, engine core, subsystems, modding API).
• Be as detailed as possible; include even the modules you think are “auxiliary” (debugger, UI screens, etc.) since capturing them can help mod developers and maintainers understand integration points.