Graph View

AGE of Joy Documentation

Global debug mode

2 min read

Diagnostic & Bug Reporting Instructions

How to use the built-in diagnostic utility to report technical issues.

  1. Activating Debug Mode To capture detailed technical information, you must enable active logging before reproducing a bug:
  • Locate the Configuration Cabinet in your current room.
  • Switch to Global Configuration Mode.
  • Navigate to the “Debug & Bug Report” in the Global menu.
  • Toggle Debug Logging to ON.

Once active, the system will record all internal engine events, script executions, and stack traces to a local diagnostic file.

  1. Generating a Bug Report After the issue has occurred (or if you have just experienced a hard crash), follow these steps:
  • Return to the Debug & Bug Report menu.
  • Select “Generate Bug Report ZIP”.
  • Wait for the status message: “ZIP created in AgeOfJoy dir!”
  1. Handling System Crashes (GPFs) If the game crashes entirely to the Quest Home:
  • IMPORTANT: Re-launch the game but DO NOT toggle Debug Logging back on immediately. Toggling it ON creates a new blank log, which will overwrite the log containing the crash data.
  • Go directly to the Debug menu and click “Generate Bug Report ZIP”.
  • The system uses “Auto-Flush” technology, meaning the details of the crash are preserved on your storage even if the application terminates abruptly.
  1. Submitting Your Report The utility will generate a file named AgeOfJoy_BugReport_YYYYMMDD_HHMMSS.zip located in your root AgeOfJoy data folder. This package is comprehensive and contains:
  • The detailed debug log: Internal engine and script execution events.
  • System Specifications: Hardware details and version numbers.
  • Installation Map: A directory list to verify file integrity and ROM placement.
  • Configurations & Scripts: A full copy of your .yaml configuration files, your AGEBasic .bas scripts, and any .debug crash reports generated by the interpreter.

A Note on AGEBasic Errors

If you see a “runtime error” or “compilation error” message printed on an in-game cabinet screen, the game automatically generates a .debug file containing a snapshot of the code and variables at the moment of failure. These files are automatically harvested and included in the ZIP report described above.

Please upload this ZIP file to the bug-report channel along with a brief description of the actions leading up to the issue.

You can delete the ZIP file from your storage after uploading it.

Backlinks