Crash Assistant guide for All the Mons 0.3.0-beta to 1.0.0-rc.7

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 not something you build or craft. It is a safety net that opens a window after Minecraft crashes, shows the logs, crash reports or hs_err files affected, and lets you upload them with one click so you can ask for help. It is client-only, so on a server it does nothing.^[1]

What to do after a crash

1. Read the window that appears. It lists the available log files, and you can drag and drop files straight out of it, or drag all the logs at once from the "Available log files:" label.^[1]
2. Let the analysis run. It checks the logs for many known crash reasons and, when it finds one, shows a dialog with a description and a suggested solution. Analysis is switched on in this pack with analysis.enabled.^[1][3]
3. Wait for the OK button the first time a crash reason is shown. The pack sets analysis.first_show_delay to 10 seconds, so you have time to read the recommendation.^[3]
4. Accept the privacy policy before your first upload. The pack keeps general.enable_privacy_policy_acceptance on, so this prompt is required.^[3]
5. Use the Upload All button to upload your logs and build a message you can post. The pack leaves it visible (gui_customisation.disable_upload_all_button is false). Logs go to mclo.gs, and general.upload_to is set to wrap the link for better formatting.^[3]
6. If you still need help, the Request Help button opens the community link set in general.help_link.^[3]

Good to know

The window also appears if the game crashes while loading mods and the FML error screen is shown, because general.show_on_fml_error_screen is true in this pack.^[3]

In modpack mode, analysis will not blame a mod that was part of the original modpack, only mods that were added or updated afterwards. The pack leaves analysis.trigger_on_original_modpack_mods false, so if you add your own mods, those are the ones it points at.^[3]

The pack also has general.generate_own_launcher_log turned on. It writes the stderr stream to logs/stderr_stream.log, which many launchers do not save and which can help with some crashes.^[3]

There is a crash command in the mod, but crash_command.enabled is false in this pack. If it were enabled, you would have to run it again within the number of seconds set by crash_command.seconds (10 here) to confirm.^[3]

Unverified The sources here show no recipes, items to craft or quests involving Crash Assistant, so this guide gives no crafting order. Any such detail would live in the pack's recipes and quest book, which are not shown here. The mod's mod list data is in config/crash_assistant/modlist.json, which was not included in the sources, so its contents are unverified.

Crash Assistant is a different kind of mod from the machine and automation mods you may be used to. It shows a GUI after Minecraft crashes, lists the affected logs, analyzes them, and helps you share them. It is client-only, so on a server it does nothing. That means the mechanics here are about what the crash window does and which settings steer it.^[1]

What the crash window shows

After a crash, the GUI immediately displays 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 steps. It also supports drag and drop: you can drag files out of the GUI, or drag every log at once by grabbing the "Available log files:" label.^[1]

In this pack's config, general.show_on_fml_error_screen is on, so the window is shown when the game crashes during mod loading and the FML error screen appears. general.kill_old_app is also on in the pack, so if an old Crash Assistant window is still running when you start a new game, it gets closed to avoid confusing you with a window from an earlier crash.^[3]

The pack also keeps general.generate_own_launcher_log on. It writes the stderr stream to logs/stderr_stream.log, because many launchers do not save that stream and it can hold the crash reason. The original stream is left untouched.^[3]

Uploading logs

In this pack's config, general.enable_privacy_policy_acceptance is on, so you have to accept a privacy policy before the first upload. The config comment says logs are uploaded to mclo.gs regardless, and the pack sets general.upload_to to gnomebot.dev, which wraps the link for better formatting.^[3]

By default the mod scans for terminated processes, which can appear with a delay, and only after that scan finishes does it enable the individual upload buttons. The pack leaves this as it is (general.prevent_upload_buttons_delay is false). The config comment says turning the option on would enable those buttons immediately after the crash, which can make people click them instead of the Upload All button.^[3]

According to the config comments, a log that is too large for a single upload is split into a head part and a tail part, each with its own link. When you copy from an individual upload button, a dialog lets you choose one part or both, unless copied_links.skip_split_dialog is enabled. In this pack's config it is false, so the dialog is shown.^[3]

The generated message

The Upload All button builds a message to paste into a support channel. Per the config, its layout comes from generated_message.message_structure: a header with the upload link, custom text, the log links, the problematic frame, the analysis result and the modlist changes. In this pack's config, the names of the crash reasons are put into the message (generated_message.put_analysis_result_to_message) and the hs_err problematic frame is included (generated_message.put_problematic_frame_to_message).^[3]

In this pack's config, the prefix is "### " (generated_message.prefix), which the config comment says helps avoid links that are too small to hit on mobile. ANSI colouring is off (generated_message.color_message is false), and the message language is en_us (generated_message.generated_msg_lang).^[3]

Log analysis

The mod checks logs against many known crash reasons. When it finds one, it shows a dialog with a problem description and a detailed solution. The checks cover JVM crashes (hs_err), logs and crash reports, and the Windows event log. After upload, supported logs are also run through the Codex analyzer from mclo.gs. The project page says that more than 75% of support issues are common and easily solvable problems.^[1]

In this pack's config, analysis is on (analysis.enabled) and no crash reasons are blacklisted (analysis.blacklisted_reasons is empty). The config says that when a crash reason is shown for the first time, the OK button is delayed by 10 seconds (analysis.first_show_delay) to help make sure you read the recommendation.^[3]

The config describes a modpack mode: by default, when the mod runs in that mode for an end user, it does not display analysis that blames a mod which was part of the original modpack, and blames only mods added or updated by the end user. In this pack's config, analysis.trigger_on_original_modpack_mods is false, so that default is kept.^[3]

In this pack's config, analysis tools are enabled (analysis_tools.enabled) and none are blacklisted (analysis_tools.blacklisted_tools). The project page lists these tools in the GUI menu, among them a Create/Epic Fight addons compatibility scan, which looks for addons that are incompatible with your installed version of Create or Epic Fight, and an MCreator Mod Detector, which lists all mods made with the MCreator tool.^[1][3]

Simple mode

In this pack's config, simple_mode.enabled is on. The config describes this as the GUI starting in simple mode, with logs hidden and a single "Show Logs (Expert Mode)" button. With simple_mode.prevent_for_modpack_creators on in the pack, modpack creators always see Expert Mode with logs visible. simple_mode.hide_modlist_section is false, so the mod list changes section is not hidden while simple mode is active.^[3]

Modlist tracking and change warnings

The modlist feature (modpack_modlist.enabled) keeps a modlist.json so the mod can tell which mods you added or updated after installing the pack. The pack also records datapacks, resource packs and the modloader jar name in it, and adds a generated modlist.txt to the logs.^[3]

Only the players listed in modpack_modlist.modpack_creators can overwrite modlist.json. Automatic saving is off in this pack (modpack_modlist.auto_update is false). The config says to save manually with the /crash_assistant modlist save command.^[3]

In this pack's config, too_many_changes_warning.count is 5, which is how many changes an end user can make before the warning is displayed. The config comment names the supported wordings, NOTIFY and DROP_SUPPORT, and the pack uses DROP_SUPPORT (too_many_changes_warning.formulation_type). That wording says no support is provided for that many changes and suggests re-installing the modpack.^[3]

Unverified The exact mod entries the pack records are stored in config/crash_assistant/modlist.json, which the sources here do not show.

Other switches in this pack

• Piracy check: in this pack's config, piracy.enabled is on with a 10 second OK button delay (piracy.delay). Per the config comment, it notifies if piracy is not supported in your community.^[3]
• Crash command: crash_command.enabled is off in this pack's config. The config says that if it were enabled, the command would have to be run again within 10 seconds (crash_command.seconds) to confirm.^[3]
• Scripts and the Scripts IDE are both off in this pack's config (scripts.enabled, scripts.ide_enabled).^[3]
• Support text: the pack names its support channel in text.support_name and text.support_place, and the help button opens the link in general.help_link. The config comment lists DISCORD and GITHUB as the currently supported wording styles (general.formulation_type), and the pack uses DISCORD.^[3]
• Look: in this pack's config, the GUI theme is FlatDarkLaf (gui_customisation.theme_file_name) and the logo path is set in gui_customisation.modpack_logo_path to display the pack logo at the top of the GUI.^[3]

The mod page describes Crash Assistant as client-only, so it does nothing on a server. It shows a window after Minecraft crashes, listing your logs and offering upload options. Here is how this pack sets the options you're most likely to touch, all in config/crash_assistant/config.toml.^[1][3]

Simple mode

The option's comment says simple mode is disabled by default, but this pack turns it on. With simple_mode.enabled set to true, the window starts with the logs hidden and a single "Show Logs (Expert Mode)" button. simple_mode.prevent_for_modpack_creators is true, so modpack creators always see Expert Mode with the logs visible. simple_mode.hide_modlist_section is false, so the mod list changes section is not hidden while simple mode is active.^[3]

Crash analysis and warnings

• analysis.enabled is true. The OK button is delayed when a crash reason is shown for the first time, by the number of seconds in analysis.first_show_delay, which is 10 in this pack.^[3]
• analysis.trigger_on_original_modpack_mods is false. In modpack mode, when the mod is run by an end user, the analysis is not displayed if it blames a mod that was part of the original modpack. It only blames mods added or updated by the end user.^[3]
• piracy.enabled is true, with a delay of 10 seconds on the OK button from piracy.delay. The option's comment says it is ignored if general.help_link is left at its default value (CHANGE_ME).^[3]
• too_many_changes_warning.count is 5 and too_many_changes_warning.formulation_type is DROP_SUPPORT. That wording says support is not provided for that amount of changes, and suggests re-installing the modpack or being on your own.^[3]

Uploading and support links

• general.formulation_type is DISCORD. The config currently supports DISCORD and GITHUB wording, and DISCORD uses terminology like "join the Discord" and "post in #channel". general.help_link is set to a Discord invite rather than CHANGE_ME, and text.support_name and text.support_place point at the pack's own support channel.^[3]
• Logs are uploaded to mclo.gs either way. general.upload_to is gnomebot.dev, which only wraps the link for better formatting.^[3]
• general.enable_privacy_policy_acceptance is true, so you must accept the privacy policy before the first log is uploaded.^[3]
• generated_message.color_message is false, so the message from the Upload All button has no ANSI coloring. generated_message.prefix is "### ", which the comment says can prevent links that are too small and hard to hit on mobile.^[3]
• text.modpack_name uses the Better Compatibility Checker placeholders for the pack name and version.^[3]

Other settings

• crash_command.enabled is false in this pack.^[3]
• The mod list feature is on via modpack_modlist.enabled, but modpack_modlist.auto_update is false. Per the option's comment, saving manually is done with the /crash_assistant modlist save command. Only the players listed in modpack_modlist.modpack_creators can overwrite modlist.json.^[3]
• The window theme is FlatDarkLaf, set through gui_customisation.theme_file_name. The option's comment lists it among the supported core themes.^[3]
• The scripts feature is off: scripts.enabled is false.^[3]

All the Mons 1.0.0-rc.7 ships Crash Assistant 1.11.9, and the mod has been in the pack since 0.3.0-beta or earlier. The pack changelogs have no entries for this mod, so everything below comes from the mod's own changelogs, newest first.^[4]

1.11.9 (the version in this pack)

• Fixed a race condition during the start of the Crash Assistant GUI.^[5]
• On 1.19+, it patches the vanilla issue MC-307905, which had recently started to stop crash reports from generating. The patch is enabled by default and you can turn it off in the config.^[5]

1.11.6

• New GUI analysis tools: ConnectorModDetectorGUI detects Fabric mods loaded by a connector mod, and ModsSearcherAnalysisGUI searches mod files and the Minecraft folder for text or regex names you enter. The second one helps when you can't tell where a problem or resource comes from.^[6]
• The modlist.txt file now has a notes column (renamed from isMCreator) that says "via Connector" or "MCreator mod" where applicable, plus a separator row for readability.^[6]
• startup_scripts.log is only added to the logs list if it has errors. Otherwise its contents go into the Crash Assistant log.^[6]
• Fixes: blacklisting the CodexMessage crash reason now works, missing or corrupted mixins config analysis works more reliably (with a button to find which mod provided it), and duplicated analysis results in generated message filenames are fixed.^[6]
• CorruptedConfigFinder now analyses json5 correctly and also supports jsonc and properties formats.^[6]

1.11.0

• Theme support, set with the gui_customisation.theme_file_name config option. The default theme is FlatLightLaf, and you can use Swing if you want the old look.^[7]
• JEXL scripting support for custom log analysis scripts (run after a crash, before the usual analysis) and startup scripts (run very early in the Minecraft process, before the Crash Assistant process starts).^[7]
• problematic_mods_config.json functionality was removed. An existing file is automatically transformed into startup scripts with identical functionality.^[7]
• A built-in Scripts IDE under the file menu, with syntax highlighting, undo/redo and an integrated console for testing log analysis scripts.^[7]
• LogDeletionDialog lets you select logs, select all, and delete the selected ones. You can also customise the animated border and button blinking colors.^[7]
• Several warnings now include guides: JVM arguments for Jemalloc, LibGLFWDotSo, LibOpenALDotSo, ResourceLocationException and GroovyModLoaderIPv6, memory allocation instructions for OutOfMemoryError and InsufficientMemory, and a Java version guide for MacJDK.^[7]

1.10.x highlights

• 1.10.30 fixed a formatting bug in the message generator introduced in 1.10.29.^[8]
• 1.10.28 added new trusted domains and fixed links sometimes not opening on Linux.^[9]
• 1.10.27 added GZIP compression for McLogs API uploads, reducing payload size and upload times by up to 100x.^[9]
• 1.10.26 marked 1.21.11 as compatible and added a Malay translation.^[9]
• 1.10.24 redesigned Mod List Difference into an interactive tool with Added, Updated and Removed tables, CurseForge and Modrinth support, and Revert Update, Restore and Manage actions. It also gained a manual download fallback with drag and drop, and fixed the mods folder location on Lunar Client.^[9]
• 1.10.23 added an option to skip the split dialog for large logs and automatically copy both links, and a Simple Mode that hides logs behind a button (disabled by default).^[9]
• 1.10.22 made the Crash Assistant log show the full analysis message formatted with Markdown, so support channels can copy and paste it. It also fixed logs missing from the list on Lunar Client.^[9]