







Description
Bug Radar
Documentation file - here
WHAT IS BUG RADAR? Bug Radar is a bug-reporting and error-detection system that lives entirely inside your Roblox experience. Players report a problem with one tap. The server quietly records its own recent errors. A built-in engine links each report to the error that most likely caused it, groups similar reports together and ranks them from P0 (most urgent) to P3. Your Owner and Dev staff see the result in clean, mobile-friendly in-game screens.
No web server. No outside service. No web requests. Everything is plain, readable Luau saved in your own game's DataStore.
HOW IT WORKS
A player taps Report a bug and answers one question: "Did you just see something go wrong?"
They pick the problem (Lag, Freeze/Crash, Stuck, Can't buy / item issue, Visual/UI, Cheater, Other), when it happened, and can add a few words.
The server checks everything, attaches its recent errors and a rounded location, and runs the engine.
Your staff open the dev screens and see grouped, prioritized bugs with the likely cause.
FOR PLAYERS
One small report button (a "!" icon on small screens). Works on phone, tablet, PC and console-sized screens.
Report menu: problem type, when it happened, optional short text.
Built-in limits: 30 seconds between reports and 10 per hour per player (configurable).
Players only send reports. They never see any dev screen.
FOR YOUR STAFF
Dev screens: Home, Bug reports, Groups, Group detail, Unsorted and Analytics.
Priority P0 to P3, based on how many different players are affected, the trend, servers affected, how recent and the kind of bug. One player spamming cannot make a bug look huge.
Merge groups, move a report, add notes and set a status.
Owner and Dev roles: by UserId lists, the game creator, or a staff group rank.
Open with the Dev button or F9 on PC.
Documentation file - here
WHAT IS BUG RADAR? Bug Radar is a bug-reporting and error-detection system that lives entirely inside your Roblox experience. Players report a problem with one tap. The server quietly records its own recent errors. A built-in engine links each report to the error that most likely caused it, groups similar reports together and ranks them from P0 (most urgent) to P3. Your Owner and Dev staff see the result in clean, mobile-friendly in-game screens.
No web server. No outside service. No web requests. Everything is plain, readable Luau saved in your own game's DataStore.
HOW IT WORKS
A player taps Report a bug and answers one question: "Did you just see something go wrong?"
They pick the problem (Lag, Freeze/Crash, Stuck, Can't buy / item issue, Visual/UI, Cheater, Other), when it happened, and can add a few words.
The server checks everything, attaches its recent errors and a rounded location, and runs the engine.
Your staff open the dev screens and see grouped, prioritized bugs with the likely cause.
FOR PLAYERS
One small report button (a "!" icon on small screens). Works on phone, tablet, PC and console-sized screens.
Report menu: problem type, when it happened, optional short text.
Built-in limits: 30 seconds between reports and 10 per hour per player (configurable).
Players only send reports. They never see any dev screen.
FOR YOUR STAFF
Dev screens: Home, Bug reports, Groups, Group detail, Unsorted and Analytics.
Priority P0 to P3, based on how many different players are affected, the trend, servers affected, how recent and the kind of bug. One player spamming cannot make a bug look huge.
Merge groups, move a report, add notes and set a status.
Owner and Dev roles: by UserId lists, the game creator, or a staff group rank.
Open with the Dev button or F9 on PC.


ReAwoken Studios


Urban Studios
