Roxy legacy

Support reports and bug reporting

Run /roxy report after reproducing a problem, before closing the game. Attach .minecraft/roxy/support-report.txt; each run replaces the file and nothing uploads automatically.

The report includes GPU/OpenGL, OS/Java, heap/CPU counts, selected mod versions, renderer state/counters and up to 16 recent failure traces. Exception messages and source filenames are omitted. Forge now displays the correct release version.

Filing an issue

• Include the exact GTNH version and pack changes, OR another modpack's name/version and full mod list with versions.
• Attach reviewed same-session logs/fml-client-latest.log and logs/latest.log if present. Include matching crash reports or JVM crash logs when applicable.
• Describe expected/actual behavior, reproduction steps if known, frequency and tests already tried.
• For visual bugs, attach screenshots/video, shader/resource-pack versions and settings, and normal/Roxy render distances.
• If startup fails or the command is unavailable, submit available logs and explain why the report is missing.

Review all attachments before posting. Full logs and recordings are not anonymized; redact private paths, usernames, server addresses, chat and credentials.

Reporting guide | Issue form