OutputDebugging

ONLY AVAILABLE IN VERSION 1 OR HIGHER

Output debugging if enabled will only give more infomation towards issues that would have been suppressed otherwise. System breaking errors and visible unexpected behavior will still be logged to the output.

The OutputDebugging setting will print out intentional prints and warnings into the developer console as a main and great way to spot errors that either you have caused or issues with this package. To access this infomation, while in game press the f9 key on your keyboard or if in studio open the output window.

Additional Information

Output Type	Meaning
Print (White)	Executions that are running as expected
Warning (Yellow)	Player data infomation or script has changed to another option to avoid an error which would have stopped the script
Error (Red)	There is an unintentional error with the script or a Roblox outage

Full errors, warnings and prints:

Full errors list

Use case:

The useage case for this feature is to be able to understand how the system is inferring your data sets to allow you the developer to debug and resolve problems.

You will recieve print's for if a player has got something added to their backpack or equipped or maybe even the process behind CanSaveBackpack finding tools to save.

You will recieve warning's for EITHER conditionally working/not working segments such as the saving process which will show you the JSON table of what was saved for a player OR it will be used for hard-coded errors that are NOT designed to break the script because they are more controllable or confined such as a spesific player's data save request failing.

You will recieve errors for EITHER Roblox API outages that prevents parts of the system from working OR an issue or bug has gone under the radar. If you don't know why an error is showing then send a message via Discord or DevForums and it will be looked into and fixes can quickly be rolled out.