Troubleshooter

The Troubleshooter collects a diagnostics snapshot of your Foundry environment and your installed 3DS modules. You use it when filing a bug report so the maintainer sees your setup without a back-and-forth. The report is Markdown, so you paste it straight into an issue.

Opening the troubleshooter

Open the module settings and find the 3DS:ATLAS entry. Click the “Open Troubleshooter” button to launch the window.

At the top of the window is a report scope selector. “Full Troubleshooter” covers every registered 3DS module. Each registered module also appears as its own option, so you can narrow the report to the one module a bug involves. Changing the scope rebuilds the report in place.

What the report contains

The report opens with a System section listing your Foundry version, your game system and version, your language, your world id, and a count of active and total modules. When the data is available it also lists performance mode, screen and viewport, operating system, client, GPU, and maximum texture size.

If you have viewed a scene, a Scene section reports the scene dimensions, grid, padding, and the counts of walls, lights, sounds, tiles, and tokens. A Counts section lists your actors, items, journal entries, tables, playlists, chat messages, packs, and world scripts.

Each 3DS module in scope gets its own section with the module version, its selected theme (and any forced theme), and every registered setting for that module with its current value. A module may also add its own debug lines. On the dnd5e system this includes the enabled CompendiumBrowser sources.

When world and compendium sizes are available, the report adds a World Data section and a Compendium Data section listing document counts and file sizes. The report closes with an All Modules section listing every installed module with its version, title, manifest, and an inactive marker where it applies.

Exporting for a bug report

Two buttons sit in the window footer. “Copy Report” copies the current report to your clipboard. “Export” downloads it as a timestamped Markdown file named for the scope. Use either one to attach the report to your bug report.

Logging level

The “Logging Level” setting controls how much 3DS modules write to the browser console. It is a per-client setting with four choices: Off, Errors, Warnings, and Verbose. Raising it to Verbose captures the most detail, which helps when you are reproducing a bug and want the console output alongside the exported report.