
Crash Assistant in FTB StoneBlock 4
FTB StoneBlock 4 1.23.0 ships version 1.11.12 · First seen in 1.3.0
Crash Assistant is a mod in FTB StoneBlock 4 1.23.0, where it is version 1.11.12. Shows a GUI after Minecraft crashes, immediately showing and analyzing all affected logs. (Summary from the mod's Modrinth page.)
Crash Assistant guide for FTB StoneBlock 4
Last verified for FTB StoneBlock 4 v1.23.0 on Oct 17, 2026 · text last changed Oct 16, 2026
Also applies to:All the Mods 10 2.30 to 8.3All the Mods 10: To the Sky 2.0.3 to 2.1.0All the Mods 11 0.1.0 to 0.12.0-betaAll the Mons 0.3.0-beta to 1.3.0FTB Skies 2 1.10.1 to 1.24.0FTB Skies 2: Aero 1.0.3 to 1.10.0
- Sections
- 5
4 sections are written for this pack; 1 is shared from another pack's guide.
Every recipe and number here was checked against FTB StoneBlock 4 1.23.0, read from the running game on Oct 13, 2026.
What is Crash Assistant?
3 parts
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.
How do you get started with Crash Assistant?
2 parts
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
- Read the crash window. If a known issue is detected, a dialog shows a problem description and a detailed solution.[1]
- 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]
- 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]
- 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]
How does Crash Assistant work?
5 parts
Crash Assistant is a different kind of mod from the machine and automation mods you may be used to. It is a client-only crash helper: on a server it does nothing. Its whole job is to show a window after Minecraft crashes, so this section walks through how that window behaves in this pack.[1]
What happens when the game crashes
After a crash, the GUI immediately shows all 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 in one click. The window also supports drag and drop, so you can pull files straight out of it, or drag all the logs at once by dragging from the "Available log files:" label.[1]
In this pack the window also appears when the game crashes while loading and the FML error screen is shown, controlled by general.show_on_fml_error_screen. If an old Crash Assistant window is still running when you start Minecraft again, it is closed so it can't confuse you with an old crash (general.kill_old_app).[3]
The pack also has general.generate_own_launcher_log turned on. It writes the stderr stream to logs/stderr_stream.log, because many launchers don't save it and it is very useful for debugging some crashes.[3]
Uploading and sharing logs
Logs are always uploaded to mclo.gs. The option general.wrap_link only decides which link gets copied afterwards. The pack uses the kostromdan.dev setting, which wraps the mclo.gs link through the author's paste viewer and copies a short link. After an upload the mod also sends metadata about the uploaded logs to the mod author's API, not the log contents, controlled by general.send_uploaded_logs_data_to_kostromdan_dev, which is on in the pack.[3]
The Upload All button builds one message for you to post. Its layout comes from generated_message.message_structure: a header with the upload link, optional custom text, the logs, the problematic frame from hs_err, the analysis result and the modlist changes. In this pack each log line gets a "### " prefix, logs are separated by a vertical bar, and ANSI colouring is off (generated_message.color_message).[3]
Logs that are too large for a single upload are split into a head part and a tail part. When you copy a link from an individual upload button, you normally get a dialog to pick head or tail. The pack keeps that dialog on, because copied_links.skip_split_dialog is false.[3]
Log analysis
The mod analyses logs for many known crash reasons. When it finds one, it shows a dialog with a problem description and a detailed solution. The checks cover hs_err files (JVM crashes, such as GPU driver and memory problems), logs and crash reports (for example Create6Addons, DuplicatedMods and OutOfMemoryError) and the Windows event log. After an upload, every supported log is also run through the Codex analyzer of mclo.gs.[1]
Analysis is enabled in the pack (analysis.enabled). The OK button on a crash reason shown for the first time is delayed by 10 seconds so you actually read the advice (analysis.first_show_delay). No analysis is blacklisted (analysis.blacklisted_reasons is empty).[3]
When Crash Assistant runs in modpack mode on a player's machine, it does not display an analysis that blames a mod from the original modpack. It only blames mods you added or updated. The pack keeps this default because analysis.trigger_on_original_modpack_mods is false.[3]
The GUI menu also has analysis tools, enabled in the pack through analysis_tools.enabled. Among them are the Create/Epic Fight Addons Compatibility scan, which finds addons that don't match your installed version of Create or Epic Fight, and the MCreator Mod Detector, which lists all mods made with the MCreator tool.[1][3]
Modlist tracking
The modlist feature is enabled (modpack_modlist.enabled). With modpack_modlist.auto_update on, modlist.json is overwritten on every launch when the game is started by a modpack creator, so it isn't forgotten before publishing. If you turn that off, you save it manually with the command /crash_assistant modlist save. Only the players in modpack_modlist.modpack_creators count as creators, and in this pack that list is FTB Team, Saereth and Artpoke_.[3]
The pack also adds resourcepacks to the modlist and the modloader jar name, and attaches a generated modlist.txt as a log. Datapacks are not added.[3]
Unverified The actual mod entries stored in config/crash_assistant/modlist.json are not shown in the sources here, because the file is too large to include. Check that file in the pack's config folder if you need the exact list.
Other pack settings
- Help wording: the GUI uses Discord wording (general.formulation_type), with the support name set to "FTB Discord" and the support place set to "#java-support" (text.support_name, text.support_place).[3]
- Simple mode is off by default (simple_mode.enabled). If it is turned on, modpack creators still see the Expert Mode with logs visible, because simple_mode.prevent_for_modpack_creators is true.[3]
- Crash command: the pack has crash_command.enabled on. You have to run the command again within 10 seconds to confirm you really want to crash the game (crash_command.seconds).[3]
- Piracy warning: disabled in the pack (piracy.enabled is false).[3]
- Too many changes warning: disabled in the pack, since too_many_changes_warning.count is -1. If it were enabled, the wording would be NOTIFY.[3]
- Scripts: the scripts feature and the Scripts IDE in the GUI are both enabled (scripts.enabled, scripts.ide_enabled).[3]
- Crash report fix: patches.MC307905 is on. It fixes a vanilla crash (MC-307905) that could break crash report generation itself in rare cases, and it does not change the report contents.[3]
Which Crash Assistant config options matter?
4 parts
Crash Assistant shows a window after Minecraft crashes, listing the affected logs and giving you a one-click upload. The mod is client-only. Here is how this pack version sets the options you are most likely to care about.[1]
Branding and where help goes
In this pack version, text.modpack_name is "StoneBlock 4", text.support_name is "FTB Discord" and text.support_place is "#java-support". These values replace the placeholders in the window's text, such as the one used in the request help wording.[3]
In this pack version, general.help_link points to the FTB modpack issues page, and general.formulation_type is set to DISCORD. The option's description lists DISCORD and GITHUB as the currently supported values, and DISCORD uses wording like 'join the Discord' and 'post in #channel'.[3]
Log analysis
- In this pack version, analysis.enabled and analysis_tools.enabled are both true, and analysis.blacklisted_reasons and analysis_tools.blacklisted_tools are empty, so none are disabled through those lists.[3]
- analysis.first_show_delay is set to 10. That is a delay in seconds for the OK button when a crash reason is shown for the first time, meant to make sure you read the recommendation.[3]
- analysis.trigger_on_original_modpack_mods is false. Per the option's description, when Crash Assistant runs in modpack mode for an end user, it won't blame mods that were part of the original modpack, only mods added or updated by the user.[3]
Uploading and the generated message
- Logs are always uploaded to mclo.gs. general.wrap_link is set to "kostromdan.dev" in this pack version, which only controls which link is copied after the upload. The option's description marks that value as recommended.[3]
- general.send_uploaded_logs_data_to_kostromdan_dev is true. According to its description, this sends metadata about uploaded logs, not the log contents, which still go to mclo.gs.[3]
- generated_message.color_message is false in this pack version, so the message from the Upload All button does not use ANSI colors. The description says disabling it can be needed when the message goes somewhere that does not support ANSI code blocks, like GitHub.[3]
Commands, warnings and modpack creator settings
- crash_command.enabled is true and crash_command.seconds is 10. Per the descriptions, you need to run the command again within 10 seconds to confirm you really want to crash the game.[3]
- piracy.enabled is false in this pack version, so the piracy warning is off. The option's description recommends enabling it for modpacks.[3]
- too_many_changes_warning.count is -1 in this pack version. The description says a positive integer enables the warning and a negative integer disables it, and that the value is how many changes an end user has to make before the warning is displayed.[3]
- simple_mode.enabled is false in this pack version. When it is enabled, the GUI starts in simple mode with logs hidden, so here that does not apply.[3]
- modpack_modlist.modpack_creators lists "FTB Team", "Saereth" and "Artpoke_". The description says only these players can overwrite modlist.json. With modpack_modlist.auto_update set to true, the file is overwritten on launch when the game is started by a modpack creator.[3]
What changed in Crash Assistant between versions?
2 parts
FTB StoneBlock 4 1.21.0 ships Crash Assistant 1.11.12, and the mod was already in the pack by 1.3.0 or earlier. I don't have pack changelog entries for it, so everything below comes from the mod's own changelogs. Some of those were cut short, so treat this as the highlights, not the full list.[5]
1.11.12 (the version in this pack)
- Persistent mod-list history. Each launch 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 one fixed baseline.[6]
- A filterable, sortable two-pane browser for comparing any two launch snapshots. Comparisons with 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 bug where a mod whose JAR was replaced without changing its file name or declared version was missed. If both snapshots have a comparable CurseForge or Modrinth hash and it differs, the mod now counts as updated.[6]
- The upload_to option under general was replaced by wrap_link, and the old value is not migrated. Copied log links now open in the new kostromdan.dev log viewer by default instead of gnomebot.dev.[6]
- The new log viewer is a fork of gnomebot.dev made for Crash Assistant. It adds a switcher between logs from the same launch, multi-line range links, quick links to the first error, last error and end of file, and a Download All button that saves every log from the launch as one ZIP.[6]
Earlier changes worth knowing
- 1.11.11: bumped JEXL to 3.7.0 and fixed JEXL scripts not being able to access allowed static fields of allowed classes.[7]
- 1.11.10: ported to 26.2 for NeoForge and Fabric, and fixed compatibility with the Radiance mod.[8]
- 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 could stop crash reports from generating. The patch is on by default and can be disabled in the config.[9]
- 1.11.8: a hotfix for a piracy warning redesign that was hiding the Join Discord button even for licensed players.[10]
- 1.11.6: two new GUI analysis tools, ConnectorModDetectorGUI (finds Fabric mods loaded by Connector) and ModsSearcherAnalysisGUI (searches mod files and the Minecraft folder for a string or regex). modlist.txt also gained a notes column.[11]
- 1.11.0: added theme support (the default theme is FlatLightLaf, and Swing gives the old look), JEXL scripting for custom log analysis and early startup scripts, and a built-in Scripts IDE. The problematic_mods_config.json feature was removed, and an existing file is automatically converted into startup scripts with identical behaviour.[12]
- 1.10.27: GZIP compression for McLogs API uploads, which cuts payload size and upload times by up to 100x.[13][14]
- 1.10.25: fixed OutOfMemory errors in the Crash Assistant process by hashing mod files with a streaming approach instead of reading whole files into memory.[15]
- 1.10.24: redesigned Mod List Difference into an interactive tool with Added, Updated and Removed sections, CurseForge and Modrinth integration, and Revert Update and Restore actions.[16]
Sources
- Crash Assistant project page (modrinth) · official mod data
- All the Mods 10 8.1 mod list · pack file
- FTB StoneBlock 4 1.21.0 config: config/crash_assistant/config.toml · pack file
- FTB StoneBlock 4 1.21.0 config: config/crash_assistant/modlist.json · pack file
- FTB StoneBlock 4 1.21.0 mod list · pack file
- Crash Assistant 1.11.12 changelog · changelog
- Crash Assistant 1.11.11 changelog · changelog
- Crash Assistant 1.11.10 changelog · changelog
- Crash Assistant 1.11.9 changelog · changelog
- Crash Assistant 1.11.8 changelog · changelog
- Crash Assistant 1.11.6 changelog · changelog
- Crash Assistant 1.11.0 changelog · changelog
- Crash Assistant 1.10.28 changelog · changelog
- Crash Assistant 1.10.27 changelog · changelog
- Crash Assistant 1.10.25 changelog · changelog
- Crash Assistant 1.10.24 changelog · changelog
Where this guide comes from
Written from what FTB StoneBlock 4 itself ships: its files and recipes, the in-game guidebooks and the mods' own pages. Every statement links to the source it came from, and the numbers are checked against the pack before publishing.
Guide last verified Oct 17, 2026.
Guides for other versions: 1.3.0 to 1.8.1
Report wrong info
Version in each release
39 releases, first in 1.3.0
| FTB StoneBlock 4 | Version | Jar | Where it came from |
|---|---|---|---|
| 1.23.0 Oct 12, 2026 | 1.11.12 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.12.jar | From the published release |
| 1.22.0 Sep 22, 2026 | 1.11.12 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.12.jar | From the published release |
| 1.21.0 Sep 9, 2026 | 1.11.12 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.12.jar | From the published release |
| 1.20.1 Sep 1, 2026 | 1.11.12 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.12.jar | From the published release |
| 1.20.0 Aug 26, 2026 | 1.11.12 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.12.jar | From the published release |
| 1.19.1 Aug 12, 2026 | 1.11.11 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.11.jar | From the published release |
| 1.19.0 Aug 11, 2026 | 1.11.11 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.11.jar | From the published release |
| 1.18.0 Aug 9, 2026 | 1.11.11 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.11.jar | From the published release |
| 1.17.2 Jul 29, 2026 | 1.11.11 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.11.jar | From the published release |
| 1.17.1 Jul 28, 2026 | 1.11.11 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.11.jar | From the published release |
| 1.17.0 Jul 24, 2026 | 1.11.11 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.11.jar | From the published release |
| 1.16.0 Jul 2, 2026 | 1.11.10 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.10.jar | From the published release |
| 1.15.3 Jun 17, 2026 | 1.11.9 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.9.jar | From the published release |
| 1.15.2 Jun 16, 2026 | 1.11.9 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.9.jar | From the published release |
| 1.15.0 Jun 13, 2026 | 1.11.9 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.9.jar | From the published release |
| 1.14.2 Jun 3, 2026 | 1.11.9 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.9.jar | From the published release |
| 1.14.1 May 31, 2026 | 1.11.9 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.9.jar | From the published release |
| 1.14.0 May 27, 2026 | 1.11.9 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.9.jar | From the published release |
| 1.13.1 May 12, 2026 | 1.11.9 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.9.jar | From the published release |
| 1.13.0 May 12, 2026 | 1.11.9 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.9.jar | From the published release |
| 1.12.0 May 7, 2026 | 1.11.8 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.8.jar | From the published release |
| 1.11.1 Apr 24, 2026 | 1.11.8 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.8.jar | From the published release |
| 1.11.0 Apr 16, 2026 | 1.11.8 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.8.jar | From the published release |
| 1.10.0 Apr 8, 2026 | 1.11.6 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.6.jar | From the published release |
| 1.9.6 Apr 3, 2026 | 1.11.6 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.6.jar | From the published release |
| 1.9.5 Apr 1, 2026 | 1.11.3 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.3.jar | From the published release |
| 1.9.4 Mar 25, 2026 | 1.11.3 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.3.jar | From the published release |
| 1.9.3 Mar 23, 2026 | 1.11.3 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.3.jar | From the published release |
| 1.9.1 Mar 19, 2026 | 1.11.0 | CrashAssistant-neoforge-1.20.6-1.21.4-1.11.0.jar | From the published release |
| 1.9.0 Mar 17, 2026 | 1.10.30 | CrashAssistant-neoforge-1.20.6-1.21.4-1.10.30.jar | From the published release |
| 1.8.1 Mar 11, 2026 | 1.10.28 | CrashAssistant-neoforge-1.20.6-1.21.4-1.10.28.jar | From the published release |
| 1.8.0 Feb 10, 2026 | 1.10.28 | CrashAssistant-neoforge-1.20.6-1.21.4-1.10.28.jar | From the published release |
| 1.7.3 Feb 3, 2026 | 1.10.28 | CrashAssistant-neoforge-1.20.6-1.21.4-1.10.28.jar | From the published release |
| 1.7.2 Feb 3, 2026 | 1.10.28 | CrashAssistant-neoforge-1.20.6-1.21.4-1.10.28.jar | From the published release |
| 1.7.0 Jan 30, 2026 | 1.10.28 | CrashAssistant-neoforge-1.20.6-1.21.4-1.10.28.jar | From the published release |
| 1.6.0 Jan 7, 2026 | 1.10.28 | CrashAssistant-neoforge-1.20.6-1.21.4-1.10.28.jar | From the published release |
| 1.5.0 Dec 16, 2025 | 1.10.27 | CrashAssistant-neoforge-1.20.6-1.21.4-1.10.27.jar | From the published release |
| 1.4.0 Dec 9, 2025 | 1.10.25 | CrashAssistant-neoforge-1.20.6-1.21.4-1.10.25.jar | From the published release |
| 1.3.0 Dec 4, 2025 | 1.10.24 | CrashAssistant-neoforge-1.20.6-1.21.4-1.10.24.jar | From the published release |
"From pack files" means the list came from the pack's own files; "from the published release" means ForgeBase read the jars of the release itself.
Items and blocks
We can't match this mod to the pack's item list: it registers as crash_assistant, and the pack's recipe dump has nothing under that name. That means we found nothing, not that the mod adds nothing. Search the item browser
Config options (how FTB StoneBlock 4 sets them)
400 settings this pack ships for the mod. We don't have the mod's own defaults to compare them against yet.
Show settings
| Setting | FTB StoneBlock 4 value |
|---|---|
analysis.blacklisted_reasons Here you can disable some Analysis by class names. List of them can be found here: dev.kostromdan.mods.crash_assistant.app.logs_analyser.crash_reasons For example "Create6Addons" config/crash_assistant/config.toml | [] |
analysis.enabled Enable feature. config/crash_assistant/config.toml | true |
analysis.first_show_delay Delay in seconds for the OK button when a crash reason is shown for the first time. Helps to ensure the user reads the recommendation. Set to 0 or -1 to disable the delay. config/crash_assistant/config.toml | 10 |
analysis_tools.blacklisted_tools Here you can disable some Analysis tools by class names. List of them can be found here: dev.kostromdan.mods.crash_assistant.app.gui.analysis For example "MCreatorModDetectorGUI" config/crash_assistant/config.toml | [] |
analysis_tools.enabled Enable feature. config/crash_assistant/config.toml | true |
analysis.trigger_on_original_modpack_mods By default if CA work in modpack mode and ran by the end user it won't display analysis if it blames mod which was part of original modpack. And will blame only mods which were added/updated by end users. By enabling this option you can bypass this and it will blame any mods. config/crash_assistant/config.toml | false |
Comments and tips
Loading comments...