File Details
crashdetector-0.4.0-SNAPSHOT.jar
- B
- Feb 8, 2026
- 6.68 MB
- 693
- 1.21.11+46
- Forge + 2
File Name
crashdetector-0.4.0-SNAPSHOT.jar
Supported Versions
- 26.1-snapshot
- 1.19-Snapshot
- 1.17-Snapshot
- 1.20-Snapshot
- 1.21-Snapshot
- 1.18-Snapshot
- 1.21.2-Snapshot
- 1.21.6-snapshot
- 1.21.1-Snapshot
- 1.21.5-Snapshot
- 1.21.4-Snapshot
- 1.21.9-snapshot
- 1.21.11-snapshot
- 1.21.11
- 1.21.10
- 1.21.9
- 1.21.8
- 1.21.7
- 1.21.6
- 1.21.5
- 1.21.4
- 1.21.3
- 1.21.2
- 1.21.1
- 1.21
- 1.20.2-Snapshot
- 1.20.5-Snapshot
- 1.20.3-Snapshot
- 1.20.6
- 1.20.5
- 1.20.4
- 1.20.3
- 1.20.2
- 1.20.1
- 1.20
- 1.19.4-Snapshot
- 1.19.3-Snapshot
- 1.19.4
- 1.19.3
- 1.19.2
- 1.19.1
- 1.19
- 1.18.2
- 1.18.1
- 1.18
- 1.17.1
- 1.17
Curse Maven Snippet
Added Simple Clouds +Shaders+DH check
Added CDLauncher, our relauncher (similar to the CleanroomRelauncher or NotEnoughCrashes back to title screen), this is supposed to be a relauncher which will allow you to relaunch the game directly from CrashDetector with debug tools. It is important to note that this is only a relauncher, not a standalone launcher, it still requires a traditional launcher to start the game. By default CrashDetector for security does NOT copy your access token to its process, so you will not be able to play on online mode servers unless you go to the CrashDetector privacy settings and allow for the CD Process to have access to your access token, however this is generally not recommeneded, playing the game in general from CDLauncher is generally not recommeneded as by default we have the deepest logging enabled plus other debug tools which generally really harms peerformance, CDLauncher is mostly for debugging (especially for early or restricted areas) and allowing for patches to be enabled on fabricmc (by default fabricmc doesnot hae traditional transformers limiting the patching capabilities)
Right now the WIP debu tools are
CDTracer - Log Every method call, good for knowing what happened before a crash
CDProfiler - Scan what classes are taking the most resources, good for finding why your game takes up so much cpu or ram
CDSampler - Scan the time each method takes, good for finding lag causes or things being slow
It is important to note that these tools are more limited versions of these tools. For more serious debugging we would suggest using VisualVM.
All these are very new and WorkInProgress, especially the Tracer,Sampler, and Profiler.

