Understand diasurgical/devilutionx's source layout and find a starting point for your task using the saved repository evidence.
Measured from the parsed import graph, retained from the earlier analysis. Coupling, not a reading order.
Files at b0a3b7babbdd · descriptions are AI-written.
The descriptions and the file list come from different revisions. Check responsibilities against source.
Suggested by the saved analysis. Verify the proposed change against these source files.
Suggested by the saved analysis. Verify the proposed change against these source files.
Suggested by the saved analysis. Some step paths were not captured or refer to generated or vendor files; only observed source files are linked.
Start with possible startup or request handlers, then follow the calls for your scenario. These suggestions use file names, not verified execution paths.
Use a nearby test as a pattern. Read the root manifest or contribution guide for the correct test command. These suggestions use file names, not verified execution paths.
Inspect the relevant configuration and the commands it runs before changing the workflow. These suggestions use file names, not verified execution paths.
File paths come from a snapshot of up to 500 captured paths; an omitted file may still exist.
Main entry point and game loop orchestration; every contributor must understand the primary game state machine
Build system configuration; required to set up compilation for multiple OS targets
UI framework backbone; handles menu rendering and navigation flow for all interface components
Input mapping layer; centralizes keyboard, controller, and touch input handling across platforms
Game HUD and in-game UI management; coordinates spell, inventory, and player status display
File I/O abstraction; handles loading game assets and cross-platform file access
CMake
Enables portable cross-platform builds targeting Windows, macOS, Linux, Switch, PS4, Xbox, and web platforms from single configuration
SDL2
Abstracts platform-specific video, audio, and input APIs behind unified interface for deployment to multiple operating systems
C++
Provides performance-critical implementation while maintaining compatibility with original Diablo binary assets and reverse-engineered game logic
Modular Input Layer (Controller/Keyboard/Touch)
Allows independent handling of diverse input devices and platform-specific constraints without coupling game logic to hardware
Build-time
Runtime
Separate UI framework layer rather than inline UI code
Enables consistent menu experience across all platforms and simplifies porting to new OSes with different windowing systems
Additional abstraction layer adds code complexity but provides platform independence
Modular control system with multiple device layers (gamepad, keyboard, touch)
Supports diverse input methods on mobile and console ports without redesigning core game input handling
Input dispatch overhead and maintenance burden across multiple device abstractions
Asset loading through cross-platform file abstraction rather than direct OS calls
Enables consistent behavior across console SDKs, web environments, and desktop platforms with different file system APIs
Custom file I/O layer must be maintained rather than relying on standard library
This repo is in good health with CI, tests, and active maintenance.
How maintainable the code looks — from complexity, code issues, test presence, file size, and hotspot load. It grades the shape of the code, not defect risk, and doesn't replace review.
Provider: GitHub Actions
186 test files detected
Where: test · test/fixtures/diablo
186 test files / 655 source files. This is a file-count ratio, not real line coverage — set up Codecov for authoritative numbers.
No Dependabot / Renovate / Snyk / Trivy / CodeQL config found. Enable Dependabot or Renovate.
Real-time data from Codecov, GitHub Actions, GitHub Issues, deps.dev — not estimates.
last 50 runs · median 6m
of 7 recent open issues are 30d+ old with no replies
median first-reply across 13 recent issues · fast
last 6mo: 97 commits · prior 6mo: 3
Files edited often AND hard to reason about. Churn = recent commit frequency, Complexity = branches and nesting, Risk = both combined. These are the highest-leverage targets for refactoring or testing.
Files that change often and are complex tend to accumulate more bugs
Pattern-matches from the file structure and dependencies — useful as hypotheses, but not grounded in actual source. For real findings see Code Scanning above.
SDL2 calls and platform checks intermixed with game logic; suggests incomplete abstraction between platform layer and core systems
Multiple files in Source/controls/devices and Source/DiabloUI
Input handling may rely on mutable static state or global references, making concurrent input handling brittle and testing difficult
Source/controls/game_controls.cpp, Source/controls/controller.cpp
Menu transitions and dialog state changes appear to use implicit state through function calls rather than explicit state objects, risking navigation bugs
Source/DiabloUI/diabloui.cpp, Source/DiabloUI/mainmenu.cpp
Speculation from file structure, not profiling data. Validate against real metrics before acting on these.
Asset loading and codec decompression likely blocks game loop during level transitions; no evident streaming or async loading
Source/data/file.cpp
Centralized input dispatch for all input types (keyboard, gamepad, touch) may serialize event handling and limit responsiveness on high-frequency input
Source/controls/game_controls.cpp
UI rendering and event handling in single pass may cause frame rate drops if menu rendering is complex
Source/DiabloUI/diabloui.cpp
Static analysis on sampled source files (up to 15 files).