I just released Godot Project Doctor v0.2.0, a lightweight editor plugin for checking common problems inside Godot projects.
It currently checks for:
Broken resource paths
Missing resources
Missing scripts
Invalid or unresolved UIDs
Empty script files
Supported project configuration problems
After scanning, it generates a clear report with the number of files scanned, references checked, errors, warnings, and detected issues. The complete report can also be copied to the clipboard with one click.
The workflow is simple: install it in addons, enable the plugin, open Project Doctor, and click Scan Project.
Godot Project Doctor v0.2.0 has been tested with Godot 4.7.2, including a clean ZIP installation in a fresh project.
This looks quite interesting, but I have a few questions, if you don’t mind!
You mentioned it checks for “Broken resource paths, Missing resources and missing scripts”
I could be wrong but I’m quite sure Godot already does this and will not even let you open certain scenes / resources if there are problems with it. Does the addon do anything different other than try and open these resources / scenes to see if anything is broken?
What exactly does “Supported project configuration problems” mean?
Given that the project has the AI Assisted tag on itch, how much of the addon was written by AI vs. yourself?
You’re right that Godot already catches some broken or missing resource/script references during normal editor usage. Project Doctor isn’t intended to replace those built-in checks.
The main difference in the current version is that it performs a project-wide scan and collects the supported issues into one report, without requiring you to manually discover them while opening individual scenes/resources. It also checks unresolved uid:// references and currently warns about empty script files.
By “supported project configuration problems,” the current v0.2.0 includes a check for a missing main scene. I agree that the wording is a bit broad, and I plan to make that description more specific as more configuration checks are added.
Regarding AI: yes, AI was used substantially during development, including assistance with the GDScript implementation. I defined the tool’s purpose and features, tested it in Godot, created broken-project test cases, verified the results, tested the clipboard/report functionality, and performed clean installation tests before release. I marked it as AI-assisted on itch.io specifically to be transparent about that.
Thanks for asking — this kind of feedback is useful, especially for deciding which checks would make future versions genuinely useful beyond what Godot already catches
I’d especially appreciate feedback from people working on larger Godot projects: what other project-level problems would you want a tool like this to detect?
@mrseghiour Please don’t create new topics about the same project. I moved your new post here. If you have any updates about this project in the future - use this thread. Thank you.