Crash Assistant in All the Mons

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.

Good news: Crash Assistant needs no crafting. It is a client-only mod, so it does nothing on a server. It only wakes up after Minecraft crashes, and then it shows a window with all the affected logs, crash reports or hs_err files.^[1]

Unverified The sources here show no quests and no recipes for this mod, so there is no item to make first. If you want to know whether the pack's quest book mentions it, check the quest book itself.

What to do when the game crashes

1. Look at the window that pops up. It lists the logs from the crash and analyzes them for many known crash reasons. You can also drag and drop files straight out of it.^[1]
2. If a known problem is found, you get a dialog with a description and a suggested solution. In this pack the OK button on a reason you have not seen before is delayed by 10 seconds, so you actually read the advice. The analysis is switched on here.^[1][3]
3. Before your first upload you have to accept the privacy policy. This pack leaves that requirement enabled.^[3]
4. Use the Upload All button to upload the logs and build one message with the links. This pack uploads through gnomebot.dev, and the logs still go to mclo.gs first.^[3]
5. After pressing it, the pack shows a reminder to paste the logs in the correct Tech Support channel and to say what you were doing when it crashed.^[3]
6. If you still need help, the Request Help button opens the help link the pack has set in its config. Its wording is set to Discord.^[3]

The options behind all this are analysis.enabled, analysis.first_show_delay, general.enable_privacy_policy_acceptance, general.upload_to and general.help_link.^[3]

Good to know

• The window also appears when the game crashes while loading mods and the FML error screen shows, because general.show_on_fml_error_screen is on in this pack.^[3]
• The pack makes the mod write its own stderr log to logs/stderr_stream.log, since many launchers do not save that stream and it often holds the crash reason. See general.generate_own_launcher_log.^[3]
• The mod's crash command is disabled in this pack. If it were on, you would have to run it again within 10 seconds to confirm. See crash_command.enabled and crash_command.seconds.^[3]
• The analysis tools are enabled, with none blacklisted. See analysis_tools.enabled.^[3]

Crash Assistant isn't a machine mod, so there are no multiblocks, power networks or pipes to automate here. It's a client-only crash helper: when Minecraft crashes it opens a window that gathers your logs, analyzes them and helps you share them. On a server it does nothing.^[1]

What happens after a crash

After a crash the GUI shows the affected game and launcher logs, crash reports and hs_err files. From there you can upload them in one click, copy the link and do other reporting actions. You can also drag and drop files straight out of the window, or drag all logs at once from the "Available log files:" label.^[1]

• By default the app scans for terminated processes (they can show up with a delay) and only then enables the individual upload buttons. general.prevent_upload_buttons_delay is false in this pack, so that wait stays on.^[3]
• Logs always go to mclo.gs. general.upload_to is currently set to gnomebot.dev here, which wraps the link for nicer formatting.^[3]
• Before your first upload you must accept a privacy policy, because general.enable_privacy_policy_acceptance is currently on in this pack.^[3]
• With the pack's current settings, the window also appears when the game crashes during modloading and the FML error screen is displayed (general.show_on_fml_error_screen).^[3]
• With the pack's current settings, an old Crash Assistant window that is still open when you start a new Minecraft instance gets closed (general.kill_old_app), so you don't read a stale crash.^[3]
• general.generate_own_launcher_log is on, so a stderr log is written to logs/stderr_stream.log. Many launchers don't save that stream, and it can hold the crash reason.^[3]

Log analysis

The mod checks logs against many known crash reasons. When it recognizes one, it shows a dialog with a problem description and a detailed solution. The checks cover JVM crashes (hs_err), regular logs and crash reports, and the Windows Event Log. Examples include driver problems, running out of RAM, duplicated mods, Mixin conflicts and missing dependencies.^[1]

After an upload, every supported log is also run through the Codex logs analyzer from mclo.gs. For some Codex results, such as an erroring block or entity, the mod shows its own detailed how-to-fix message.^[1]

• analysis.enabled is currently on, and analysis.blacklisted_reasons is currently empty, so no crash reason is switched off in this pack.^[3]
• With the pack's current settings, the first time a crash reason is shown the OK button is delayed by 10 seconds so you actually read the recommendation (analysis.first_show_delay).^[3]
• analysis.trigger_on_original_modpack_mods is currently false. With that setting, when the end user runs the game, analysis does not blame mods that came with the original modpack. It only blames mods the user added or updated.^[3]

Analysis tools

The GUI menu has a set of analysis tools. They include the Create/Epic Fight addons compatibility scan, which finds addons incompatible with your installed Create or Epic Fight, and the MCreator mod detector, which lists mods made with MCreator. In this pack's current config the tools are enabled (analysis_tools.enabled) and none is blacklisted (analysis_tools.blacklisted_tools).^[1][3]

The Upload All message

The Upload All button builds one message for you to paste into the support channel. In this pack's current config, generated_message.message_structure lays it out: a header with the upload link, optional text under the crashed line, the logs, the problematic hs_err frame, the analysis result and the modlist changes.^[3]

• Currently each log line gets a "### " prefix, which keeps links big enough to hit on mobile (generated_message.prefix).^[3]
• Currently the message includes the names of the crash reasons, not just a count (generated_message.put_analysis_result_to_message), and the problematic frame (generated_message.put_problematic_frame_to_message).^[3]
• ANSI coloring is currently off in this pack (generated_message.color_message).^[3]
• With the pack's current settings, after you press Upload All a reminder tells you to add some context about what you were doing at the time of the crash (generated_message.warning_after_upload_all_button_press).^[3]
• Logs too large for one upload are split into a head and a tail link. If you copy a single log from its own button, a dialog lets you pick which part. copied_links.skip_split_dialog is currently false, so that dialog stays.^[3]

Simple mode and the mod list

With the pack's current settings the GUI starts in simple mode, with the logs hidden behind a single "Show Logs (Expert Mode)" button (simple_mode.enabled). Modpack creators always see the expert view with logs visible (simple_mode.prevent_for_modpack_creators).^[3]

Crash Assistant also keeps a mod list file for the pack, currently enabled by modpack_modlist.enabled. Datapacks and resource packs are added to that list too. Auto-update is currently off, so the list is only saved manually with the /crash_assistant modlist save command, and only by players named in modpack_modlist.modpack_creators.^[3]

With the pack's current settings, once you make 5 changes a warning appears (too_many_changes_warning.count). It uses the DROP_SUPPORT wording, which says support isn't provided for that many changes and suggests reinstalling the pack (too_many_changes_warning.formulation_type).^[3]

Other safety nets

• patches.MC307905 is currently on. It fixes a rare vanilla bug where generating the crash report itself crashes, which would stop the original report from being created. It doesn't change the report contents.^[3]
• The piracy check is currently enabled with a 10 second OK button delay (piracy.enabled, piracy.delay). The mod ignores it if the help link is left at its default.^[3]
• The crash command is currently disabled in this pack (crash_command.enabled). The scripts feature is currently disabled too (scripts.enabled).^[3]

Unverified The exact contents of the pack's saved mod list (config/crash_assistant/modlist.json) and of its custom GUI theme (config/crash_assistant/ATMons.theme.json) are not shown in the sources here. Check those files in the pack's config folder.

Crash Assistant is the window that pops up after Minecraft crashes and shows your logs. It only runs on the client, so these options do nothing on a server. Everything below lives in the main config file, and these are the values this pack currently ships with.^[1][3]

Crash analysis

• analysis.enabled is currently true, so the mod checks your logs against known crash reasons. analysis_tools.enabled is also currently true, so the extra analysis tools are available.^[3]
• analysis.first_show_delay is currently 10. When a crash reason is shown for the first time, the OK button waits 10 seconds so you actually read the recommendation. Setting it to 0 or -1 removes the delay.^[3]
• analysis.trigger_on_original_modpack_mods is currently false. When you run the pack as an end user, the analysis will not blame mods that came with the original modpack. It only blames mods that were added or updated afterwards.^[3]
• analysis.blacklisted_reasons and analysis_tools.blacklisted_tools are both currently empty, so no analysis or tool is switched off.^[3]

Uploading and getting help

• general.upload_to is currently set to gnomebot.dev. Logs are always uploaded to mclo.gs, and this option wraps the link in gnomebot.dev for nicer formatting.^[3]
• general.help_link currently points to the AllTheMods Discord, and general.formulation_type is currently DISCORD. The config lists DISCORD and GITHUB as the supported wordings, and DISCORD uses terms like 'join the Discord' and 'post in #channel'.^[3]
• general.enable_privacy_policy_acceptance is currently true, so you have to accept the privacy policy before your first log upload.^[3]
• generated_message.color_message is currently false, so the message built by the 'Upload all' button has no ANSI colors. The language for that message is generated_message.generated_msg_lang, currently set to en_us.^[3]

Behavior around a crash

• general.show_on_fml_error_screen is currently true, so the GUI also shows when the game crashes while loading mods and the FML error screen appears.^[3]
• general.generate_own_launcher_log is true. It writes logs/stderr_stream.log, because many launchers don't save that stream and it often holds the crash reason.^[3]
• general.kill_old_app is currently true, so an old Crash Assistant window is closed when you start a new Minecraft instance.^[3]
• general.win_event_is_crash is false. A Windows event log entry alone won't trigger the window, because it can be a false positive.^[3]
• crash_command.enabled is currently false, so the manual crash command is off. If you turn it on, crash_command.seconds (currently 10 here) is how long you have to run the command again to confirm.^[3]

The theme file only holds colors for the Crash Assistant window and has dark set to true. You don't need to touch it.^[4]

All the Mons 1.3.0 ships Crash Assistant 1.11.12, and the mod has been in the pack since 0.3.0-beta or earlier. There are no pack changelog entries for this mod, so everything below comes from the mod's own changelogs.^[5]

1.11.12 (the version in this pack)

• Mod-list history is now saved between launches. Each snapshot records whether the game only started, reached the title screen, joined a world, crashed during gameplay, or closed without a crash. The main comparison now picks a suitable earlier launch instead of one fixed baseline.^[6]
• There is a new two-pane mod-list history browser that you can filter and sort, to compare any two launch snapshots. Comparisons that involve Current keep the Remove, Enable/Disable, Revert, Restore and Show Folder actions, while snapshot-to-snapshot comparisons are read-only.^[6]
• You can import modlist.txt data from a file or the clipboard and compare it with Current.^[6]
• Fixed: a mod whose JAR was replaced without changing its file name or declared version was missed by comparisons. If both snapshots have a comparable CurseForge or Modrinth hash and it differs, the mod now counts as updated.^[6]
• The config option general.upload_to was replaced by general.wrap_link. The old value is not migrated. By default, copied log links now open in the new kostromdan.dev log viewer instead of gnomebot.dev.^[6]
• The new log viewer is a fork of gnomebot.dev made for Crash Assistant. Among other things it can switch between logs from the same launch, select a range of lines and copy a link to it, and use a Download All button that saves every log from that launch in one ZIP archive.^[6]

Recent earlier releases

• 1.11.11: JEXL was bumped to 3.7.0, and JEXL scripts can now access allowed static fields of allowed classes.^[7]
• 1.11.10: the mod was ported to 26.2 for NeoForge and Fabric, and compatibility with the Radiance mod was fixed.^[8]
• 1.11.9: fixed a race condition when the Crash Assistant GUI starts. On 1.19+ it also patches vanilla issue MC-307905, which could stop crash reports from generating. The patch is enabled by default and you can turn it off in the config.^[9]
• 1.11.6: added the ConnectorModDetectorGUI tool, which detects Fabric mods loaded by a connector mod, and the ModsSearcherAnalysisGUI tool, which searches mod files and the Minecraft folder for text or regex names. The modlist.txt file also gained a notes column, which can say "via Connector" or "MCreator mod".^[10]
• 1.11.0: added theme support (the default theme is FlatLightLaf, and Swing gives the old look) and JEXL scripting for custom log analysis and early startup scripts. It also added a built-in Scripts IDE. The old problematic_mods_config.json functionality was removed, and an existing config is automatically turned into startup scripts with identical behaviour.^[11]

Older releases

• 1.10.24: the Mod List Difference feature was redesigned into an interactive tool with Added, Updated and Removed sections, CurseForge and Modrinth support, and actions like Revert Update and Restore.^[12]
• 1.10.25: fixed out-of-memory errors in the Crash Assistant process by hashing mod files with a streaming approach.^[12]
• 1.10.27: McLogs API uploads now use GZIP compression, which cuts payload size and upload times by up to 100x.^[12]
• 1.10.28: added new trusted domains and fixed links sometimes failing to open on Linux. The next release, 1.10.30, fixed a message generator formatting bug introduced in 1.10.29.^[12][13]