Find the bugs in your game before your players do.
dk-doctor reads your RPG Maker project and reports real bugs and risks — broken transfers, dead switches, dangling references, plugin conflicts — each with its exact location and the fix. Never a wall of statistics.
Every line is a bug and its exact place.
dk-doctor states cause and symptom — and, where it can, the treatment. No event counts, no graphs to interpret. Just findings you can act on.
Transfer Player → Map099, which does not exist — the game crashes when the event fires.
Skill #44 is learned by Hero at level 12 but is absent from Skills.json — crash on level-up.
Switch #14 is read by 3 page conditions but never set by any event — those pages are unreachable.
Both alias Game_Battler.prototype.gainHp; load order clobbers ABMZ_Core's logic.
Imported but referenced by no event or database row — safe to remove.
Never called by command 117 and not autorun or parallel — dead code.
Not a wall of errors — a map of your project.
The same deterministic findings, placed where they happen. Open straight into a severity heatmap of every map, then walk into one and read each event in context.
Overview heatmap
Every map lit by its worst finding — see what's on fire before you open a single one.
Walk the map
Events are drawn where they live, over real tiles. Click one to read its findings in place.
What changed
Events with findings new since the last run get a marker — triage a fresh scan at a glance.
Jump from any finding
“Show on map” from the list lands you on the exact event and centres it.
Regions & minimap
Toggle a region overlay; a minimap and “go to worst” keep huge maps navigable.
Export the map
Save an annotated PNG of any map to share a bug report or a to-do list.
Point it at your project. Read the diagnosis.
No config and no changes to your game. dk-doctor reads, runs every rule in parallel, and hands back a triaged report.
Point dk-doctor at any RPG Maker MV/MZ folder — dk-doctor ./MyGame. It reads the files, never writes them.
Maps, events, the database, assets and plugins are parsed into one engine-agnostic model — then every deterministic rule runs at once.
Triaged errors → warnings → info, grouped by category and map, each with its exact location, confidence, and the fix.
Categories of problem, one severity language.
Color always means severity — never decoration. Every finding is tagged certain or likely, so you always know how much to trust it.
DB referential integrity — skills, items, traits, troops, encounters that point at nothing.
Event and database cross-references that resolve to a missing target.
Broken and orphaned images, audio and tilesets across the project.
Orphan common events, unreachable pages and dead conditional branches.
Load-order hazards between plugins that alias the same method.
Plugins that silently clobber each other's logic at runtime.
Run it on your project. Read the diagnosis.
dk-doctor is free and offline — a deterministic engine with honest confidence that reads your project and never touches your files.