Crash Assistant in All the Mods 11

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.

Crash Assistant is a crash helper rather than a content mod, so this section is about what it does for you when the game goes down, not about something you build. After Minecraft crashes, it opens a window that shows the affected game and launcher logs, crash reports and hs_err files, with a one-click way to upload them and copy the link.^[1]

What to do after a crash

1. Let the window open and look at the list of available log files. You can drag files straight out of the window to wherever you want, or drag all the logs at once by dragging from the "Available log files:" label.^[1]
2. Before your first upload you have to accept the privacy policy, because general.enable_privacy_policy_acceptance is on in this pack.^[3]
3. If the mod recognises a known crash reason, it shows a dialog with a description and a suggested fix. In this pack the analysis is switched on (analysis.enabled), and the OK button is delayed by 10 seconds the first time a reason is shown (analysis.first_show_delay), so read the advice while you wait.^[1][3]
4. Use the Upload All button to send the logs and get a ready-made message. The pack leaves this button visible (gui_customisation.disable_upload_all_button is false), and its logs go to mclo.gs, wrapped as a gnomebot.dev link (general.upload_to).^[3]
5. If you still need a hand, press the Request Help button. It opens the help link set in general.help_link, and the pack's wording is set to the Discord style by general.formulation_type.^[3]

What it can recognise

The analysis covers a long list of known problems, including JVM crashes tied to GPU drivers, running out of memory or disk space, duplicated mods, Mixin conflicts, and mismatches between Create and its addons. It also warns you if Minecraft is running on an integrated GPU when a dedicated one is available, and it offers auto-fixes for many common issues.^[1]

Other pack settings worth knowing

• The window also appears when the game crashes while loading mods and the FML error screen is shown (general.show_on_fml_error_screen is true).^[3]
• The pack generates its own stderr log at logs/stderr_stream.log, because many launchers do not keep that stream (general.generate_own_launcher_log).^[3]
• The crash command is turned off in this pack (crash_command.enabled is false). If it were enabled, you would have to run it a second time within the number of seconds set by crash_command.seconds, which is 10 in this pack, to confirm.^[3]
• Analysis does not blame mods that came with the original pack when it runs for an end user, unless analysis.trigger_on_original_modpack_mods is changed. In this pack it is false.^[3]

Crash Assistant has no machines, multiblocks, power or fluid handling, so there is nothing to automate here. It is a client-only crash helper: after Minecraft crashes it opens a window that shows the affected logs and helps you report the problem. On a server it does nothing. This section walks through how that window works and how this pack has it set up.^[1]

What the crash window does

When the game crashes, the window lists the affected game and launcher logs, crash reports and hs_err files. From there you can upload them, copy the link and do other reporting actions. It also supports drag and drop: you can drag single files out of the window, or drag all logs at once by dragging the "Available log files:" label.^[1]

It also warns if Minecraft is running on an integrated GPU when a dedicated one is available, and it includes auto-fixes for several common issues.^[1]

When the window appears

• As the pack is currently configured, general.show_on_fml_error_screen is on, so the window also shows when the game crashes while loading mods and the FML error screen appears.^[3]
• general.win_event_is_crash is off, so a Windows event log entry alone does not make the window pop up. The config notes this can be a false positive from unrelated Windows error spam.^[3]
• In this pack's current settings, general.kill_old_app is on, so an old window that is still running gets closed when a new Minecraft instance starts. That way you are not confused by a window from an old crash.^[3]
• general.generate_own_launcher_log is on, so the mod writes the stderr stream to logs/stderr_stream.log. Many launchers do not save it, and it can be very helpful for debugging.^[3]
• In the pack's current settings, the manual crash command is switched off through crash_command.enabled. If it were enabled, you would have to run it a second time within crash_command.seconds seconds (10 in this pack) to confirm.^[3]

Log analysis

The mod checks the logs against many known crash reasons. When it finds one, it shows a dialog with a description of the problem and a detailed fix. The analysis covers JVM crashes (hs_err) such as GPU driver problems and out of memory situations. It also covers log and crash report problems such as duplicated mods, missing dependencies, Mixin conflicts, OutOfMemoryError and a full disk. Windows event logs are covered too.^[1]

As currently set in this pack, analysis.enabled is on and analysis.blacklisted_reasons is empty, so no analysis is turned off. The first time a reason is shown, the OK button is delayed by analysis.first_show_delay seconds (10 here) so you actually read the advice.^[3]

By default, when the mod runs in modpack mode on an end user's machine, it will not blame mods that were part of the original modpack. It only blames mods you added or updated. This pack currently leaves analysis.trigger_on_original_modpack_mods off, so that default applies.^[3]

After an upload, every supported log is also run through the Codex logs analyzer from mclo.gs. When Codex's message would be unclear, the mod shows a detailed how-to-fix message instead, for example for an erroring block or entity.^[1]

Analysis tools

In this pack's current settings, the GUI menu has a set of analysis tools, enabled via analysis_tools.enabled with nothing blacklisted. They include the Create/Epic Fight Addons Compatibility scan, which finds addons that do not match your installed Create or Epic Fight version, and the MCreator Mod Detector, which lists all mods made with MCreator.^[1][3]

Uploading and the generated message

Logs are always uploaded to mclo.gs. This pack currently sets general.upload_to to gnomebot.dev, which wraps the link for better formatting. Before your first upload you have to accept a privacy policy, because general.enable_privacy_policy_acceptance is on.^[3]

The mod scans for terminated processes before it enables the individual upload buttons, which stops you from clicking them instead of Upload All. This pack currently keeps that scan, since general.prevent_upload_buttons_delay is off.^[3]

With the pack's current settings, the Upload All button builds one message for you to post. Its layout comes from generated_message.message_structure, which is the header, the text under the crash title, the prefix, the logs, the problematic frame, the analysis result and the modlist diff. The pack currently uses "### " as the line prefix so links are bigger and easier to hit on mobile. ANSI colouring is off through generated_message.color_message. The message includes the names of the crash reasons and the problematic frame from hs_err, per generated_message.put_analysis_result_to_message and generated_message.put_problematic_frame_to_message.^[3]

If a log is too big for one upload, it is split into a head and a tail. With copied_links.skip_split_dialog currently off in this pack, you get a dialog to copy one part or both.^[3]

Support-related features in this pack

• In this pack's current settings, the help button opens the community link from general.help_link, and the wording of the window follows general.formulation_type, which is currently DISCORD here.^[3]
• As currently configured, the piracy check is enabled through piracy.enabled. It notifies you if piracy is not supported in the pack's community, and its OK button is delayed by piracy.delay seconds (10 in this pack).^[3]
• In the pack's current settings, the Intel corruption notice is enabled through intel_corrupted.enabled.^[3]
• As currently set in this pack, the "too many changes" warning triggers at 5 changes (too_many_changes_warning.count). The pack currently uses the DROP_SUPPORT wording, which says support is not given for that many changes and suggests reinstalling the pack.^[3]
• In this pack's current settings, simple mode is enabled, so the window starts with logs hidden and a single "Show Logs (Expert Mode)" button. Modpack creators still see the expert view, because simple_mode.prevent_for_modpack_creators is on.^[3]
• The modlist feature is enabled and set to auto-update. The file is rewritten at launch when a listed modpack creator starts the game, and it also records datapacks and resource packs. This is how the mod can tell which mods you changed from the original pack.^[3]
• As the pack is currently configured, scripting is off (scripts.enabled is false), and so is the Scripts IDE.^[3]

Unverified The actual list of mods the pack ships is stored in config/crash_assistant/modlist.json. That file was too large to include, so the sources here do not show its contents.

Crash Assistant is client-only, so these options only matter on your own game, not on a server. Everything lives in one file, and most of it is cosmetic or message formatting. These are the settings you're most likely to care about, and how this pack version sets them in that file.^[1][3]

Simple mode

simple_mode.enabled is on in this pack. The mod describes this option as disabled by default, so this is a pack change. With it on, the crash window starts in simple mode: logs are hidden and you get a single "Show Logs (Expert Mode)" button.^[3]

simple_mode.prevent_for_modpack_creators is also on, so modpack creators always see the logs. simple_mode.hide_modlist_section is off, so the mod list changes section is not hidden while simple mode is active.^[3]

Getting help and uploading logs

• general.help_link is set to the pack's Discord invite and is opened in the browser when you press the request help button. general.formulation_type is DISCORD. The mod currently supports DISCORD and GITHUB wording, and DISCORD uses terms like "join the Discord" and "post in #channel".^[3]
• text.support_name and text.support_place are filled in with the pack's support channel, and text.modpack_name builds the pack name and version from the Better Compatibility Checker values.^[3]
• general.upload_to is set to gnomebot.dev. Logs are uploaded to mclo.gs anyway, and this option only wraps the link for better formatting.^[3]
• general.enable_privacy_policy_acceptance is on, so the privacy policy has to be accepted before the first log upload.^[3]
• generated_message.color_message is off, so the message built by the Upload All button does not color the modified mods count or analysis with ANSI.^[3]

Analysis and warnings

• analysis.enabled is on, and analysis.first_show_delay is 10, so the OK button is delayed by 10 seconds the first time a crash reason is shown. The mod says this helps ensure the user reads the recommendation.^[3]
• analysis.trigger_on_original_modpack_mods is off. By the mod's description, when it runs in modpack mode for an end user, analysis does not blame mods that were part of the original modpack, only mods added or updated by the end user.^[3]
• piracy.enabled is on with piracy.delay at 10 seconds. The mod says this option is ignored if the help link is left at its default.^[3]
• too_many_changes_warning.count is 5, and too_many_changes_warning.formulation_type is DROP_SUPPORT. The mod currently supports NOTIFY and DROP_SUPPORT for this warning, and DROP_SUPPORT says support is not provided for that amount of changes and suggests reinstalling the modpack.^[3]

Features that are switched off

crash_command.enabled is off in this pack's config. The scripts feature is off too: scripts.enabled, scripts.ide_enabled and scripts.generate_scripts_folder_with_example are all false.^[3]

All the Mods 11 0.8.0-beta ships Crash Assistant 1.11.12, and the mod has been in the pack since 0.0.6 or earlier. The pack changelogs have no entries for this mod, so everything below comes from the mod's own changelogs for its recent releases.^[4]

1.11.12 (the version in this pack)

This update is mostly about comparing your mod list between launches, plus a new log viewer.^[5]

• Crash Assistant now keeps a persistent mod-list history. 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 previous launch instead of relying on a single static baseline.^[5]
• There is a new filterable, sortable two-pane history browser for comparing any two launch snapshots. Comparisons involving Current keep the Remove, Enable/Disable, Revert, Restore and Show Folder actions, while snapshot-to-snapshot comparisons are read-only.^[5]
• You can import modlist.txt data from a file or the clipboard and compare it with Current. When migrating, your previous modlist.json snapshot is kept in history.^[5]
• Fixed: a mod updated by replacing its JAR without changing the file name or declared version was missed. If both snapshots have a comparable CurseForge or Modrinth hash and the hashes differ, the mod now counts as updated.^[5]
• Upload All messages now include non-empty mod list differences and unavailable-reference notices. Unchanged comparisons are not uploaded.^[5]

The kostromdan.dev viewer is a fork of the gnomebot.dev one, tuned for Crash Assistant. Highlights:^[5]

• A switcher between logs from the same Crash Assistant launch, plus a Download All button that saves every log from that launch in a single ZIP archive.^[5]
• Drag across line numbers to select a range and copy a link to the whole range. Selecting a line or range copies its link automatically, and you can turn that off in the settings.^[5]
• Quick links to the first error, last error and end of the file, plus a jump-to-top button.^[5]
• Separate Raw and Download buttons, options to show full stack-trace locations and to wrap long lines, and individually hideable navigation and download buttons.^[5]
• Fixed parsing and rendering of modern Minecraft stack-trace locations.^[5]

Earlier releases

• 1.11.11: bumped JEXL to 3.7.0 and fixed JEXL scripts not being able to access allowed static fields of allowed classes. Also fixed the 1.12.2 Cleanroom processor getter after an OSHI update, and fixed the CurseForge API requiring an API key from July 15 to download mods from its CDN.^[6]
• 1.11.10: ported the mod to 26.2 for NeoForge and Fabric. Fixed the better compatibility checker (BCC) config format and fixed compatibility with the Radiance mod, which should also help with other mods that replace the OpenGL API with Vulkan.^[7]
• 1.11.9: fixed a race condition when the Crash Assistant GUI starts. On 1.19+ it also patches the vanilla issue MC-307905, which had started to block crash reports from being generated. The patch is enabled by default and can be disabled in the config.^[8]
• 1.11.8: a hotfix for the piracy warning redesign, which had been hiding the Join Discord button even for licensed players.^[9]