diagnose

Diagnoses a reported Roblox symptom down to its cause before anything is changed. Use whenever the user says something in their game is broken, wrong, missing, duplicated, intermittent, or works in Studio but not live - leaderstats resetting, players falling through the map, a shop granting free items, a server dying after a while, an event firing twice - and no file has been named yet, even when Roblox is never mentioned. Classifies the symptom, asks which side owns the state and whether a client could have caused it, narrows the surface, reproduces, and confirms the cause before handing the fix over. Hand-offs: judging code that was handed over goes to the code-review skill, writing the fix to the best-practices skill, sync toolchains and driving Studio tools to the studio-ops skill.

Version

1.11.4

License

MIT