Crash Assistant guide for FTB StoneBlock 4 1.3.0 to 1.8.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 FTB StoneBlock 4 1.21.0 guide

Crash Assistant is a little different from most mods you'll meet in this pack. It only matters after Minecraft crashes, so the first steps are about knowing what it does and what to click, not what to build.^[1]

When the game crashes, the mod shows a window with all the affected logs, crash reports or hs_err files. From there you can upload them in one click, copy the link and share it for troubleshooting. It also analyzes the logs for many known crash reasons and warns you if Minecraft is running on an integrated GPU when a dedicated one is available.^[1]

What to do after a crash

1. Read the crash window. If a known issue is detected, a dialog shows a problem description and a detailed solution.^[1]
2. If an analysis dialog appears for the first time, the OK button is delayed by 10 seconds in this pack so you actually read the recommendation. That delay is set by analysis.first_show_delay.^[3]
3. Use the Upload All button to send your logs. Logs are always uploaded to mclo.gs, and this pack is set to copy a wrapped short link, controlled by general.wrap_link.^[3]
4. Paste the copied message where you ask for help. The Request Help button opens the help link from general.help_link.^[3]

Good to know in this pack

• Analysis is on, controlled by analysis.enabled. The analysis tools are on too, via analysis_tools.enabled.^[3]
• analysis.trigger_on_original_modpack_mods is false in this pack. When the mod runs in modpack mode on a player's machine, analysis won't blame mods that were part of the original modpack, only mods that were added or updated afterwards.^[3]
• crash_command.enabled is true. The command to crash the game on purpose must be run again within 10 seconds to confirm, set by crash_command.seconds.^[3]
• The GUI is shown even when the game crashes while loading mods and the FML error screen appears, because general.show_on_fml_error_screen is true.^[3]
• The interface language follows your operating system by default, via general.language_source, with general.default_lang as the fallback.^[3]

Crash Assistant is a crash-reporting helper, not a tech mod, so there are no machines, multiblocks, power or automation to set up. Its "mechanics" are what happens after the game crashes and how the pack configures that. It is client-only, so on a server it does nothing.^[1]

What happens after a crash

When Minecraft crashes, the mod shows a window that immediately lists 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 steps. The window supports drag and drop, so you can pull files out of it, or drag every log at once from the "Available log files:" label.^[1]

The window also appears if the game dies during mod loading and the FML error screen is shown (general.show_on_fml_error_screen is on in this pack). If an old window from a previous crash is still open when you start Minecraft again, it gets closed so it can't confuse you (general.kill_old_app).^[4]

The pack also has the mod write the stderr stream to a log file, because many launchers don't save it and it can hold the crash reason (general.generate_own_launcher_log). The original stream is left untouched.^[4]

Log analysis

The mod checks your logs against many known crash reasons. When it recognises one, it shows a dialog with a description of the problem and a detailed solution. Analysis is switched on in this pack (analysis.enabled), and the list of disabled analyses (analysis.blacklisted_reasons) is empty. If you ever want to turn one off, you list its class name there, for example "Create6Addons".^[1][4]

The known reasons are grouped by the kind of log they come from. Some examples:^[1]

• JVM crash files (hs_err): driver problems such as nvoglv64.dll and atio6axx.dll, InsufficientMemory, and JavaTooHigh.^[1]
• Logs and crash reports: OutOfMemoryError, DuplicatedMods, MixinApply, MissingUnsupportedDependencies, DiskSpaceEnded and UsedByAnotherProcess.^[1]
• Windows event log: WasClosedByWindows, where the game froze and the OS terminated it.^[1]

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

There is also a set of analysis tools in the GUI menu, enabled in this pack (analysis_tools.enabled). One scans your mods for addons that are incompatible with your installed Create or Epic Fight. Another, the MCreator Mod Detector, lists every mod made with MCreator. Individual tools can be disabled by class name in analysis_tools.blacklisted_tools, which is empty here.^[1][4]

Uploading and the generated message

Logs are always uploaded to mclo.gs. This pack wraps the link for gnomebot.dev for nicer formatting (general.upload_to). Before your first upload you have to accept a privacy policy (general.enable_privacy_policy_acceptance).^[4]

The "Upload All" button builds one message for you to paste when asking for help. In this pack that message puts the names of the detected crash reasons in, not just a count (generated_message.put_analysis_result_to_message). It also includes the problematic frame from an hs_err file (generated_message.put_problematic_frame_to_message), and the logs are separated on one line to keep it short (generated_message.one_line_logs).^[4]

The individual upload buttons stay disabled for a short moment after a crash while the mod scans for terminated processes, which can appear with a delay. The pack keeps that delay (general.prevent_upload_buttons_delay is false), so you are nudged towards Upload All. If a log is too big for one link, it is split into a head and a tail part, and the copied text can contain both links. The pack still shows the head/tail choice dialog (copied_links.skip_split_dialog is false).^[4]

The Request Help button opens the link set in general.help_link, which in this pack points to an FTB modpack issues page. The support name shown to you is "FTB Discord" (text.support_name).^[4]

Crash command

The mod includes a command that deliberately crashes the game, and it is enabled in this pack (crash_command.enabled). To make sure you really mean it, you have to run the command again within 10 seconds (crash_command.seconds). Setting that value to 0 or below removes the confirmation.^[4]

Modlist tracking

The modlist feature is enabled (modpack_modlist.enabled). It keeps a modlist.json so the GUI can compare the mods you have against the published pack. In this pack the file is rewritten automatically on every launch by a modpack creator (modpack_modlist.auto_update). The creators are listed as "FTB Team" and "Saereth" (modpack_modlist.modpack_creators), and only they can overwrite the file. If auto update is off, the file is saved by hand with '/crash_assistant modlist save'.^[4]

A generated modlist.txt is added to the logs, listing mod names, mod ids, mixin configs and jarjar mods (modpack_modlist.add_modlist_txt_as_log). The modloader jar name is added too, so a changed loader version is easy to spot (modpack_modlist.add_modloader_jar_name). Resource packs are included in modlist.json with a " (resourcepack)" suffix (modpack_modlist.add_resourcepacks).^[4]

Unverified The actual contents of the pack's modlist.json are not shown in the sources here. That file lives at config/crash_assistant/modlist.json.

Simple mode and change warnings

Simple mode, which hides the logs behind a single "Show Logs (Expert Mode)" button, is off in this pack (simple_mode.enabled). Even if it were on, modpack creators would still see the expert view (simple_mode.prevent_for_modpack_creators). The "too many changes" warning is disabled because its count is -1 (too_many_changes_warning.count). Its wording is set to NOTIFY, one of the wordings the config currently supports (too_many_changes_warning.formulation_type). If the warning were switched on, that wording would tell you that adding random mods or clicking the "Update All" button without proper testing is not a good idea and is expected to crash.^[4]

Problematic mods config

A second file, config/crash_assistant/problematic_mods_config.json, lets a pack author attach a custom message to a specific mod id. The message can use a $JAR_NAME$ placeholder and HTML, and a flag controls whether the game should crash on startup. In this pack the file only shows the template entry, example_modid (example_modid.msg and example_modid.should_crash_on_startup).^[5]

Crash Assistant is a client-only mod, so these settings only matter on your own game and do nothing on a server. It shows a window with your logs after a crash. Here are the options you're most likely to care about and how this pack sets them.^[1]

Who gets your crash reports

In this pack's config file, the text that appears in the crash window is filled in like this: text.modpack_name is set to the pack's own name, text.support_name is "FTB Discord", and text.support_place points you to the pack's channel there. The Request Help button opens whatever general.help_link is set to, and in this pack's config that is the FTB modpack issues tracker on GitHub.^[4]

The option descriptions say logs are uploaded to mclo.gs either way. In this pack's config, general.upload_to is set to "gnomebot.dev", which only wraps the link for better formatting.^[4]

The crash window

• In this pack's config, simple_mode.enabled is false, so the window opens in the full view with the logs visible instead of the single "Show Logs (Expert Mode)" button. The option's own description says it is disabled by default.^[4]
• simple_mode.prevent_for_modpack_creators is true in this pack's config. If simple mode is ever turned on, modpack creators still see the Expert Mode view.^[4]
• In this pack's config, the Upload All button uses font size 16 and the dark green color "0_178_0" (gui_customisation.upload_all_button_font_size and gui_customisation.upload_all_button_foreground_color). The option descriptions give the same values as the defaults.^[4]
• gui_customisation.disable_upload_all_button is false in this pack's config, so the Upload All button is shown.^[4]
• general.show_on_fml_error_screen is true in this pack's config, so the window also appears when the game crashes during mod loading and the FML error screen is shown.^[4]

Privacy and uploads

general.enable_privacy_policy_acceptance is true in this pack's config, so you have to accept the privacy policy before your first log upload. The option's description warns that turning it off may be illegal in some countries for modpack creators.^[4]

Crash command and modlist tracking

• In this pack's config, crash_command.enabled is true and crash_command.seconds is 10, so you must run the command a second time within 10 seconds to confirm you really want to crash the game.^[4]
• modpack_modlist.enabled and modpack_modlist.auto_update are both true in this pack's config. Per the option description, the mod list file is overwritten on launch when the game is started by a modpack creator, and modpack_modlist.modpack_creators lists "FTB Team" and "Saereth" here.^[4]
• In this pack's config, too_many_changes_warning.count is -1, which the description says disables the warning about making many changes to the pack. The config's description names NOTIFY and DROP_SUPPORT as the currently supported types for too_many_changes_warning.formulation_type, and this pack sets NOTIFY, which only tells the user that big changes are expected to crash.^[4]

FTB StoneBlock 4 1.8.1 ships Crash Assistant 1.10.28. The mod was already in the pack in 1.3.0 or earlier. Below are the notable changes from the mod's own changelogs, from 1.10.22 up to the version in your pack.^[6][7]

Unverified No pack changelog entries for this mod were available, so what the pack itself changed about Crash Assistant between its releases is unverified. The mod changelog entries before 1.10.22 were also not available here.

1.10.28 to 1.10.25

• 1.10.28 (the version in your pack): new domains were added to the trusted list, and a bug where opening links on Linux sometimes didn't work was fixed.^[6][7]
• 1.10.27: log uploads to the McLogs API now use GZIP compression, which cuts payload size and upload times by up to 100x.^[6]
• 1.10.26: 1.21.11 was marked as compatible, and a Malay translation was added.^[6]
• 1.10.25: fixed OutOfMemory errors in the crash assistant process. They came from the new hashing reading entire mod files into memory. It now streams the files, so memory use stays constant whatever the file size.^[6]

1.10.24: Mod List Difference redesign

This was the big one. The Mod List Difference feature went from a simple text list to an interactive tool. Changes show up in organized Added, Updated and Removed sections, and CurseForge and Modrinth support was added. Local files are identified by hashing, and clickable icons link to the mod project pages.^[8]

• Revert Update downloads and restores the version defined in the modpack or from the latest successful launch.^[8]
• Restore downloads and restores missing mods.^[8]
• Manage buttons let you disable, enable, remove, or show mods in Explorer.^[8]
• Downloads work automatically via API. If a mod prevents third-party downloads, a dialog appears where you download the file in your browser and drag it into the tool to install it.^[8]
• Hashing and network requests are asynchronous, to prevent the GUI from freezing. The new interface also got translations (en, de, es, it, pt, ru, zh).^[8]

The same release also fixed the mods folder location on Lunar Client and calculated the width of the upload button automatically.^[8]

1.10.23 and 1.10.22

• 1.10.23: added an option to skip the split dialog (for large logs split into two parts) and automatically copy both links.^[6]
• 1.10.23: added a "Simple Mode" that hides logs behind a button. The changelog says it is disabled by default.^[6]
• 1.10.22: the Crash Assistant log now shows the full analysis message, formatted with Markdown, instead of just the first line. That makes it easy to copy into Discord for support.^[6]
• 1.10.22: fixed logs missing from the log list on Lunar Client, a truncated upload button text in Brazilian Portuguese, and the MedievalOriginsVsForgeOrigins analysis sometimes not triggering.^[9]