Last updated
Submitting Logs
How to find latest.log and crash reports, plus the checklist for submitting a Discord support ticket.
Good logs and screenshots save everyone time. Before you Submit a Ticket in Discord, gather the details below.
Standard support checklist
Include these with every Discord support ticket
- What you were doing when the problem happened
- Screenshot of the error if one is on screen
- Launcher being used (Modrinth App recommended)
- Modpack / instance version from Discord announcements if known
latest.log- Crash report file if one exists
- Any manually installed mods or shaders
How to get help
- Collect the checklist items above.
- Open Discord and Submit a Ticket(opens in a new tab) through the Submit Ticket channel.
- Attach your logs and screenshots to the ticket — do not rely on a vague chat message alone.
New to StoneHaven? Join through the Welcome channel first: discord.gg/ZXAbSR9mGG(opens in a new tab).
Locating latest.log
In a typical Modrinth instance, logs live under the instance folder:
.../<instance>/logs/latest.log
Exact click-paths vary by Modrinth App version. If you cannot find the folder, open instance settings / folder shortcuts in the launcher, or mention that in your ticket and ask for a screenshot guide.
Locating crash reports
Crash reports are usually under:
.../<instance>/crash-reports/
Attach the newest file that matches the time of your crash.
Privacy tips
- You can redact emails if they appear, but do not trim the stack traces staff need.
- Do not post passwords, tokens, or session files.
- Prefer attaching files directly in your Discord ticket or using a paste service staff trust.
After you submit
Stay available for follow-ups in the ticket. “It still broken” without a new log after changes is hard to diagnose — send an updated latest.log and any new screenshots after each major attempt.