The ‘crash description’ already says exactly that: only the actual error message you’re disconnected for. None of the other crash boilerplate. Evidently it’s not a crash. Do you really think users would understand a whole book written about ‘why did it crash’?
On FiveM, this looks a bit as follows (on RedM it probably lacks the ‘because game unloading failed’):
A normal crash looks more like this:
… and DropPlayer usually looks like this:
The only thing I can imagine changing about the disconnection-case crash dialog at least until the crash dialog rewrite is the following:
- Collapse the details and make ‘save information’ into a small button, not a command link.
- Remove the ‘this is a fatal error because’ part, I don’t think this has been actioned upon ever at all.
- Change the UAC error task dialog type to a more plain warning/error icon.
- Audit early-disconnection flow and see if there’s any easy wins here.
By the way, with this supposed ‘repro’ the client doesn’t even crash when unmodified: It just gets stuck at ‘Connecting to server…’ because what you’re doing is complete nonsense.