[PLUGIN] Game Doctor - Easy Studio Analyzer

Hey everyone!
I built a plugin that scans your game, and points out common mistakes, performance drains, and little oversights that are easy to miss,. so instead of hunting them down one by one, I made a tool that does the boring checkup for me.

Each issue comes with a simple and easy to understand explanation of why it matters, and many can be fixed instantly with one click, with a full undo stack if you change your mind. Think of it as a QA buddy that helps you ship smoother, cleaner games without having to hunt for bugs.

The current UI is barebones visually, but i plan to update it overtime if people like the plugin!


Features

  • Catches common mistakes like:
    • LocalScripts in server services (won’t run)
    • Server Scripts in StarterGui/StarterPlayer (won’t run)
    • Unanchored parts clogging physics
    • Transparent parts still casting shadows
    • Looping sounds blasting at full volume
    • Accessories not set to Massless
    • Busy loops without yields
    • Remotes in ReplicatedStorage with no server handler
    • more! :>
  • easy to understand explanations for every finding
  • One click autofixes for many issues (with full undo support)
  • Undo stack so you can safely roll back changes

UI & Workflow

  • Click Analyze to see a list of issues.
  • Each issue shows what’s wrong, why it matters, and where it is.
  • Click Fix to resolve it instantly, or AutoFix all to batch apply safe fixes.
  • Dont like the change? Hit undo!!!

Why use it???

  • Save time: no more digging through Explorer for silent probems.
  • Learn best practices: every finding explains why its a problem
  • Stay safe: autofixes are undoable
  • Ship smoother games: fewer bugs, better performance, happier players! :>

Roadmap

Here’s what I’m planning next:

  • More rules for subtle issues (asset references, constraints, UI quirks).
  • A cleaner, more polished UI.
  • Community suggested checks and fixes.

Drop your thoughts below, I’ll be updating Game Doctor regularly based on community feedback!

you can get the plugin here

GameDocshowcase-ezgif.com-video-to-gif-converter

13 Likes

I’d brand it as an analyser; it’d be good to go inline with the plugin!

I don’t consider it much of a debugger (because that’s more about runtime issues, as in, you catch them AT runtime), but rather a static analysis tool.

Great work

4 Likes

Thanks so much! And great idea! If you have any feedback or suggestions lmk :slight_smile:

2 Likes

VERSION 1.1 CHANGELOG (Quality of Life)

  • Refined CanQuery rule: no longer flags non collidable parts. Added Humanoid checks (toggle in Settings, off by default)
  • Added Ignore button: hide findings for the current scan.
  • Added Perm Ignore button: persistently ignore specific findings across scans.
  • Added Clear Ignores option in Settings.
  • General polish and stability improvements.

Update here

2 Likes

I appreciate this plugin idea, but I don’t like how it was executed. You analyze, and the plugin lists a bunch of issues and can implement a quick fix. These fixes are quite subjective and don’t apply to all types of experiences. It’s also hard to grasp where the issue actually is! Instead, I believe that the UX could be improved if it instead focuses on helping the developer track down unoptimized portions of the experience with intuitive visualizations in the viewport.

Here’s some suggestions to improve it! They’re all based on merging each type of issue into one section, allowing the developer to manage them all at once.

1: LocalScripts in server services

Current Behavior: Highlights the script and provides one quick fix.
Suggested Behavior: Allow the developer to sift through these scripts one by one and allow them to move it to any other service.

2: Server Scripts in StarterGui/StarterPlayer

Server scripts do infact run in StarterGui. Why? No idea.

Current Behavior: Highlights the script and provides one quick fix.
Suggested Behavior: Same as above!

3: Unanchored parts clogging physics

Current Behavior: Allows setting the part to anchored.
Suggested Behavior: Enable a controller that highlights unanchored parts and will have their anchored state toggled on click or when lasso selected. This provides a visual way to implement optimizations where needed.

4: Transparent parts, shadow casters

Current Behavior: Allows fixing an individual part.
Suggested Behavior: Same as above! Provide a controller to click or select parts to visually fix.

You get the idea, I won’t clog up the post too much. Simply provide better UX and analytics, and more people might use the plugin! Having to manage each issue individually is time consuming. But managing them all at once with intuitive controllers could really speed up a workflow!

1 Like

these are all incredible ideas!

I will try my best to test out these methods and implement them in the coming updates along with my current plans to add more detectable stuff. I think what you’re suggesting could bring a lot to the plugin.

Thanks for the feedback! :slight_smile:

2 Likes

Also, just incase its helpful to others, the location of the affected issue is listed here on the warning card, and below the warning text:

i do totally agree a visualizer would be much better, though!

This is easily a 9/10 plugin for me as of its current state, but I have some suggestions to make this more versatile.

  • View Button — This will be for objects in the workspace, highlighting it until any buttons are clicked
  • Tabs — These tabs will just help organize the detections. (EX: All, scripts, parts, etc)
  • Search Bar — This will be for searching for certain things like object names, MaterialVariants (MV: search), Tags (Tag: search), and Attributes (Attri: search)
  • Tutorial — Just a little tutorial to show off how it works and how to use it effectively. Saves time for the developers so they don’t have to manually learn the plugin.
  • Performance Colors — Have the UI have colored borders depending on how it effects performance. Green = low, Yellow = medium, Red = high.
  • Batch Actions — Allow us to select multiple detections (ctrl + click) and choose an action that effects all selected actions.
2 Likes

my scan never finishes, shows 100% then does nothing, i try and do anything and it says that the scan is currently running…

is there any setting i need to enable?

Thats really weird, ill look into that and get it fixed as soon as i can.

i dont see why anyone would use this if they fully understand how their game works and their code and know what they’re doing but okay plugin i guess

Some people do forget about it and need some reminders. You really can’t remember the whole codebase without looking at them.

Plus, not everyone is that well-versed in Roblox game development yet, and so stuff like this is incredibly useful.

i mean they could make a todo list like i and some people do but yeah
anyways i looked at ops activity and it seems like they were selling a 20 dollar volu. lighting but it was a scam and it used free models and they had “quit” developing entirely?

Do you really think we foss devs waste precious time that we could use to invent a linux distro, and make a todo list?

No not quit, took a break. Only from that project. Poor OP

doesn’t excuse the fact that the resources they were selling for 20 dollars could easily be made in 10 minutes max

I wasn’t giving an excuse for that because there really isn’t any.
It should have been 4.99$ max considering some similar plugins.

hi, ALARE was completely and indefinitely cancelled, due to accusations regarding stuff like this, which I have already responded to countless times prior. Either way, I am trying my best to move on, and learn from the terrible experience and idea ALARE was. Thank you :slight_smile: