Crash Assistant guide for All the Mods 10 2.30 to 5.1

Same as in the All the Mods 10 8.1 guide

Crash Assistant is a crash-helper mod. When Minecraft crashes, it pops up a window that immediately shows the affected game and launcher logs, crash reports and hs_err files. From there you can upload everything with one click and copy a link to paste into Discord or GitHub. The pack ships version 1.11.12.^[1][2]

It is client-only, so on a server it does nothing.^[1]

Who it is for

It is for anyone who crashes and wants to know why, and for people who help with support. You get a formatted, ready-to-paste report, and anyone helping you gets current logs without having to ask for more files. The mod's author says more than 75% of issues are common and easily solvable, and the analysis aims to cut that support load.^[1]

What it does for you

• Analyzes logs for many known crash causes. When it finds one, it shows a dialog with a description and a detailed fix. Examples include out-of-memory errors, duplicated mods, Mixin conflicts, and GPU driver problems.^[1]
• Warns you if Minecraft is running on an integrated GPU when a dedicated one is available, and offers a one-click Auto-Fix button on Windows.^[1]
• Warns you if your CPU is one of the Intel 13th/14th generation models known to have a critical stability bug.^[1]
• Includes analysis tools in the GUI menu, such as a Package/Class Finder that shows which mod contains a given Java class or package.^[1]
• Saves the modlist, and for modpack players it lists the mods you added, removed or updated compared with the official list. You can also save it manually with the /crash_assistant modlist save command.^[1]

It runs as a separate process that waits for the Minecraft JVM to stop. It also loads very early, so it can catch crashes during startup.^[1]

Where it fits in the pack

Crash Assistant is a utility rather than a gameplay mod, so it adds no progression of its own. You don't need to unlock or craft anything. It is there when something goes wrong.^[1]

Unverified The sources I was given show no quests or ATM Star path involvement for this mod, and no in-jar guidebook was found for it.

Same as in the All the Mods 10 8.1 guide

Good news: there's nothing to craft here. Crash Assistant is a safety net that only shows up when Minecraft crashes, so your first steps are really about knowing what it does and how to use it when something goes wrong.^[1]

The mod is client-only. It runs on your own game, and on a server it does nothing. If a dedicated server crashes, you won't get this window there.^[1]

What happens when the game crashes

1. After a crash, a GUI opens right away and shows all the affected game or launcher logs, crash reports and hs_err files.^[1]
2. If the mod recognizes a known crash reason, it shows a dialog with a description of the problem and a detailed solution. Read that first, since it may save you a lot of guessing.^[1]
3. If you need help, use the one-click option to upload the logs and copy the link. Sharing that link is much easier than sending files around.^[1]
4. You can also drag and drop. Drag a single file out of the GUI to wherever you want it, or drag the "Available log files:" label to move all the logs at once.^[1]

Handy extras to know about

• It warns you if Minecraft is running on an integrated GPU when a dedicated one is available. That's worth checking if the pack runs poorly.^[1]
• It includes auto-fixes for many common issues, plus several analysis tools.^[1]
• Its analysis covers many JVM crash (hs_err) causes, such as GPU driver problems and running out of RAM. It also covers many log and crash-report causes, including duplicated mods, missing dependencies, Mixin conflicts and running out of disk space.^[1]

Unverified No quests, crafting recipes or in-pack config values for Crash Assistant were found in the sources for this pack, so this section doesn't cover any pack-specific changes to the mod.

Crash Assistant has no machines, multiblocks, power, fluids or item automation. It's a client-only crash helper: when Minecraft crashes, it opens its own window that shows every affected log so you can report the problem quickly. It only runs on your client and does nothing on a server.^[1]

What happens when your game crashes

After a crash, a separate window lists all the affected game logs, launcher logs, crash reports and hs_err files. From there you can upload them with one click, copy the link and use other tools that make reporting and troubleshooting easier.^[1]

The window supports drag and drop. You can drag a single file anywhere you like, or drag every log at once by grabbing the "Available log files:" label.^[1]

In All the Mods 10, general.show_on_fml_error_screen is on, so the window also appears when the game fails during mod loading and shows the FML error screen. general.kill_old_app is on as well, so any window left over from an old crash closes when you start Minecraft again.^[3]

The pack hides the "CrashAssistant: latest.log" file from the log list with general.blacklisted_logs.^[3]

Automatic log analysis

Crash Assistant checks your logs for many known crash causes. When it recognises one, it opens a dialog that describes the problem and gives a detailed fix. For some issues it also offers one-click auto-fixes, or a button that finds the mods responsible.^[1]

It reads several kinds of files: hs_err JVM crash files, normal logs and crash reports, and the Windows Event Log. Once you upload, each supported log is also run through the mclo.gs Codex analyzer. When a Codex message is hard to understand, Crash Assistant adds its own how-to-fix guide, for example for an erroring block or entity.^[1]

• OutOfMemoryError: Minecraft ran out of the RAM it was given.^[1]
• DuplicatedMods: more than one version of the same mod is installed.^[1]
• MixinApply: covers a wide range of crashes caused by Mixin conflicts or errors, including missing classes.^[1]
• DiskSpaceEnded: your system has run out of disk space.^[1]
• UsedByAnotherProcess: a file is locked by another program.^[1]
• WasClosedByWindows: the game froze and the OS terminated it, often because of input during loading.^[1]

It also warns you if Minecraft is running on an integrated GPU while a dedicated one is available. The mod's author says more than 75% of issues are common and easy to solve, which is why this analysis takes so much load off modpack support.^[1]

The menu includes extra analysis tools. One scans your mods for addons that don't match your installed Create or Epic Fight version. Another, the MCreator Mod Detector, lists every mod made with MCreator.^[1]

Uploading logs and getting help

Uploaded logs always go to mclo.gs. All the Mods 10 sets general.upload_to to gnomebot.dev, which wraps the link for nicer formatting.^[3]

The "Upload all..." button creates a ready-to-post message for you. In this pack, generated_message.generated_msg_lang is en_us, and generated_message.h3_prefix is on, so every filename gets a heading prefix that makes the links easier to tap on mobile. generated_message.text_under_crashed and generated_message.warning_after_upload_all_button_press are both empty, so the pack adds no extra form or warning to that message.^[3]

The help button opens the All the Mods Discord invite set in general.help_link. The pack sets text.support_name to "ATM10 Support Channel" and text.support_place to "#atm10-techsupport channel", so the window tells you exactly where to ask. text.modpack_name fills in the pack's name and version automatically through Better Compatibility Checker placeholders.^[3]

The crash command

The mod includes a command that crashes the game on purpose, but All the Mods 10 turns it off with crash_command.enabled. If it were enabled, crash_command.seconds is set to 10, meaning you would have to run the command a second time within 10 seconds to confirm.^[3]

The pack's mod list

Crash Assistant keeps a modlist.json file that records the jar file name, mod id and version of every mod in the pack. Resource packs are included with a "(resourcepack)" suffix because modpack_modlist.add_resourcepacks is on.^[3][4]

modpack_modlist.enabled is on, but modpack_modlist.auto_update is off. That means the list is not rewritten on launch; the creators save it manually with the /crash_assistant modlist save command. Only the players listed in modpack_modlist.modpack_creators, whatthedrunk and Uncandango, can overwrite the file.^[3]

Unverified The sources don't explain how Crash Assistant uses modlist.json during a crash, for example whether it compares your installed mods against the pack's list and flags added or removed mods.

Crash Assistant is client-only, so everything here lives on your side of the game. On a server it does nothing. The pack's settings are in the Crash Assistant config file, and most of them control where your crash logs go and what the crash window shows you.^[1][3]

Where your crash reports go

• general.help_link is set to the pack's own Discord invite, so the request help button takes you straight to the pack's community. If this option were left as CHANGE_ME, it would open the Forge, NeoForge, Fabric or Quilt Discord instead.^[3]
• general.upload_to is set to gnomebot.dev. Your logs are always uploaded to mclo.gs, and this setting wraps the link in gnomebot.dev for nicer formatting.^[3]
• text.support_name and text.support_place point you to the pack's tech support channel. That tells you where to post when the crash window asks you to request help.^[3]
• text.modpack_name pulls the pack's name and version from the Better Compatibility Checker config. That way the "crashed!" message always shows the exact version you're running.^[3]

What you see after a crash

• general.show_on_fml_error_screen is on. The crash window also appears when the game fails during mod loading and shows the FML error screen.^[3]
• general.kill_old_app is on. When you start Minecraft again, any Crash Assistant window left over from an old crash is closed, so it can't confuse you.^[3]
• general.blacklisted_logs hides the CrashAssistant latest.log entry from the log list in the window.^[3]
• general.default_lang is en_us. It is only used if your options.txt doesn't exist yet.^[3]

The crash command

The crash command feature is turned off in this pack through crash_command.enabled. If you enable it yourself, crash_command.seconds is set to 10. That means you have to run the command a second time within 10 seconds to confirm you really want to crash the game. Setting it to 0 or lower removes the confirmation.^[3]

The generated "Upload all" message

generated_message.generated_msg_lang is en_us, so the message built by the Upload all button is in English, which support channels can read. generated_message.h3_prefix is on. It adds a heading prefix before each filename, which keeps the links from being too small to tap on mobile. The pack leaves generated_message.text_under_crashed and generated_message.warning_after_upload_all_button_press empty, so there is no extra form to fill in and no warning pops up after you press the button.^[3]

The modlist (for pack makers)

modpack_modlist.enabled is on, and the pack ships a modlist.json that records each mod's jar name, mod id and version. modpack_modlist.auto_update is off, and only the players listed in modpack_modlist.modpack_creators can overwrite the modlist. As a player, you don't need to touch any of this. The same goes for greeting.shown_greeting.^[3][4]

Unverified The sources don't show Crash Assistant's default config values. That means this guide can't confirm which of these settings the pack changed from the defaults, apart from the help link and support text clearly being set to the pack's own community. It also can't confirm exactly how the modlist is used when analysing crashes.

Crash Assistant was added to All the Mods 10 in 2.30 at version 1.3.0, and All the Mods 10 5.1 ships version 1.10.20. The pack team has updated it often, so you'll see lots of version bumps below.^[5][6]

Updates by pack release

• All the Mods 10 2.30: Crash Assistant added at version 1.3.0.^[5]
• All the Mods 10 2.31: updated from 1.3.0 to 1.3.2.^[7]
• All the Mods 10 2.32: updated from 1.3.2 to 1.3.3.^[8]
• All the Mods 10 2.33: updated from 1.3.3 to 1.3.4.^[9]
• All the Mods 10 2.36: updated from 1.3.4 to 1.3.7.^[10]
• All the Mods 10 2.37: updated from 1.3.7 to 1.4.3.^[11]
• All the Mods 10 2.42: updated from 1.4.3 to 1.5.1.^[12]
• All the Mods 10 2.43: updated from 1.5.1 to 1.7.2.^[13]
• All the Mods 10 2.44: updated from 1.7.2 to 1.7.4.^[14]
• All the Mods 10 2.47: updated from 1.7.4 to 1.8.0.^[15]
• All the Mods 10 3.2: updated from 1.8.0 to 1.9.1.^[16]
• All the Mods 10 4.0: updated from 1.9.1 to 1.9.4.^[17]
• All the Mods 10 4.1: updated from 1.9.4 to 1.9.6.^[18]
• All the Mods 10 4.3: updated from 1.9.6 to 1.9.9.^[19]
• All the Mods 10 4.5: updated from 1.9.9 to 1.9.15.^[20]
• All the Mods 10 4.12: updated from 1.9.15 to 1.10.4.^[21]
• All the Mods 10 4.13: updated from 1.10.4 to 1.10.12.^[22]
• All the Mods 10 4.15: updated from 1.10.12 to 1.10.19.^[23]
• All the Mods 10 5.1: updated from 1.10.19 to 1.10.20.^[24]

Unverified The pack changelogs only list version numbers, and the mod's own changelogs for these versions weren't available. What each update actually changed (new features, fixes or behaviour changes) is unverified.