promotional bannermobile promotional banner

Crash Link

Crash reports made easy for both clients and dedicated servers, with mclo.gs uploads and support packets.

File Details

Crash Link V3.0.0 (Minecraft 1.20.1)

  • R
  • May 5, 2026
  • 72.97 KB
  • 11
  • 1.20.1
  • Forge

File Name

Crash Link V3.0.0 (Minecraft 1.20.1).jar

Supported Versions

  • 1.20.1

Curse Maven Snippet

Forge

implementation fg.deobf("curse.maven:crash-link-1531809:8044742")
Curse Maven does not yet support mods that have disabled 3rd party sharing

Learn more about Curse Maven

CrashLink — Support Packet Update V.3.0.0

This update expands CrashLink from a crash/log uploader into a fuller support handoff tool for players, modpack developers, server staff, and support teams.

CrashLink now helps players send a useful support-ready report instead of only copying a mclo.gs link.

New: Crash Context / Flight Recorder

CrashLink now saves useful context from the previous client session before Minecraft stopped.

The saved context can include:

  • Last known state
  • Last screen
  • World type
  • Last dimension
  • Time since launch
  • Recent session timeline

This helps support understand what the player was doing before the crash, such as joining multiplayer, opening a world, sitting on the main menu, or being in-game.

Crash Context is not a diagnosis and does not claim what caused the crash.

New: Copy Support Packet

The old basic copy-link flow has been expanded into a full Copy Support Packet action.

The copied Support Packet can include:

  • mclo.gs crash/log link
  • Crash Context
  • Selected file name
  • File type
  • Repeated-crash status
  • Trimmed upload status
  • Trim reason, if applicable
  • Recent timeline
  • Player support answers, if provided
  • Clear non-diagnosis note

The Support Packet is formatted to be easier to read in Discord and GitHub Issues, with section headings, bold labels, code formatting for file names, and cleaner player-answer formatting.

New: Quick Support Questions

Added a Quick Support Questions screen after upload.

Players can answer simple support questions before sending their report, such as:

  • What were you doing?
  • Has this happened before?
  • Did you add extra mods, shaders, or resource packs?

Saved answers are included in the copied Support Packet.

Saving answers now automatically copies the updated Support Packet to the clipboard, so players do not need to remember to click Copy Support Packet again.

New: Other... custom answer field

Each support question now includes an Other... text field.

Players can type their own short answer if the preset buttons do not fit.

Custom typed answers are included in the Support Packet.

The Other field is limited to 80 characters to keep reports short and readable.

New: Support Link Intake Prompt

If a configured support link is available, CrashLink now gently prompts players before opening Discord or GitHub Issues if they have not answered quick questions yet.

Players can choose to:

  • Answer Questions
  • Open Anyway
  • Go Back

If the player answers questions first, CrashLink copies the updated Support Packet and then automatically opens the selected support link.

This helps players arrive in Discord or GitHub with a useful report already copied and ready to paste.

New: Modpack custom support questions

Modpack developers can now define their own support questions in:

config/crashlink/settings.json

This allows each modpack or server team to ask the questions that matter most for their own support process.

Custom questions support preset answer buttons and the player’s Other... typed answer.

Safe limits are used to keep the UI simple and readable:

  • Maximum 5 questions
  • Maximum 5 answers per question
  • Blank or broken questions are ignored
  • If no valid custom questions are configured, CrashLink uses default fallback questions

Improved: Support Packet formatting

The copied Support Packet has been reformatted to be clearer in Discord.

It now uses a cleaner layout like:

 
## Crash Report:
https://mclo.gs/xxxxxx

## Crash Context:
**Last state**: Joining multiplayer server
**Last screen**: Connecting to Server
**World type**: Multiplayer
**Time since launch**: 38 seconds
**Selected file**: `crash-report.txt`
**File type**: Crash report
**Repeated error**: Looks similar to a previous crash
**Trimmed upload**: No

## Recent timeline:
- Main menu opened
- Multiplayer screen opened
- Started joining server
- Session ended unexpectedly

## Player answers:
> What were you doing?
Joining server

***Note***: This is not a diagnosis. It only combines crash context and the uploaded log.
 

The generated timestamp/footer line was removed to keep the packet cleaner.

Improved: Upload prompt UI

The upload prompt now shows a calmer quick-context summary instead of overwhelming players with too much text.

Overlapping and hard-to-read helper text was removed so the buttons are easier to read.

The full detailed context stays in the copied Support Packet instead of being shown as a large wall of text on-screen.

Improved: Trimmed upload reporting

The Support Packet now reports whether the uploaded file was trimmed.

If trimming happened, the packet includes the trim reason.

Existing oversized log behavior is preserved:

  • Normal-sized logs/crash reports upload fully
  • Oversized logs keep the beginning and end
  • Only the middle is trimmed
  • The original local crash/log file is never modified

Improved: Repeated crash reporting

The Support Packet now includes whether the selected crash/log looked similar to a previous handled crash.

This helps support know whether the issue may be recurring.

Privacy and safety

  • No silent uploads
  • Uploads still only happen when the player chooses to upload
  • Support answers are only added when the player saves them
  • Original local crash/log files are not modified
  • Crash Context and Support Packet wording avoids diagnosis or blame
  • The packet clearly states that it is not a confirmed cause

Planned for a future update

Known Issue Notices are still planned for a future update.

That future system would allow modpack developers to provide pack-specific known issue notices, but it is not included in this release.