Crash Assistant in All the Mods 10: To the Sky

All the Mods 10: To the Sky 2.1.0 ships version 1.11.12 · First seen in 1.0

Checked Sep 17, 2026All the Mods 10: To the Sky 2.1.0Sources: All the Mods 10: To the Sky 2.1.0 modlist.json · Modrinth

Report a mistake on this page

Also in 6 other packs →

Crash Assistant is a mod in All the Mods 10: To the Sky 2.1.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 All the Mods 10: To the Sky

Written for All the Mods 10: To the Sky 2.0.4 · also fits 2.0.3 to 2.1.0 · updated Oct 15, 2026

Last verified for All the Mods 10: To the Sky v2.1.0 on Oct 17, 2026 · text last changed Oct 15, 2026

Also applies to:All the Mods 10 2.30 to 8.3All 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.0FTB StoneBlock 4 1.9.0 to 1.23.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 All the Mods 10: To the Sky 2.1.0, read from the running game on Oct 15, 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 not something you craft or unlock. It sits in the background, and when Minecraft crashes it opens a window that shows the affected game and launcher logs, crash reports or hs_err files. From there you can upload them in one click and copy the link to share.[1]

It is client-only, so on a server it does nothing.[1]

Unverified The sources here show no quests and no recipes for this mod, so there is no first item to make and no quest chapter to follow. A list of the mods in the pack's modlist lives in config/crash_assistant/modlist.json, which the sources here do not show.

What to know before your first crash

The window analyzes logs for many known crash reasons. If it spots a known issue, it shows a dialog with a description of the problem and a solution. It can also warn you if Minecraft is running on an integrated GPU when a dedicated one is available. You can drag and drop log files straight out of the window, or drag every log at once by dragging the "Available log files:" label.[1]

In this pack, log analysis is switched on through analysis.enabled, and the analysis tools through analysis_tools.enabled. The first time a crash reason is shown, the OK button is delayed by the number of seconds in analysis.first_show_delay, which is 10 here, so you have time to read the recommendation.[3]

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

Sharing your logs

Logs are always uploaded to mclo.gs. This pack sets general.wrap_link to kostromdan.dev, which means the link you copy afterwards is a short wrapped link rather than the original mclo.gs one. The help button opens whatever is set in general.help_link, and the window's wording follows general.formulation_type, which is DISCORD in this pack.[3]

Uploading also sends metadata about the uploaded logs (not their contents) to api.kostromdan.dev, since general.send_uploaded_logs_data_to_kostromdan_dev is true here. Turn it off in that config file if you would rather not.[3]

The mod also writes its own copy of the stderr stream to logs/stderr_stream.log, because general.generate_own_launcher_log is enabled. Many launchers do not save that stream, and it can help with debugging.[3]

Tip: The crash command is turned off in this pack: crash_command.enabled is false. If you enable it, you have to run the command again within the number of seconds in crash_command.seconds (10 here) to confirm you want to crash the game.[3]

How does Crash Assistant work?

6 parts

Crash Assistant is not a machine mod, so there is no power, fluid or item handling to learn here. It is a crash helper: when Minecraft crashes, it opens a window that collects the relevant logs, analyzes them and helps you report the problem. It is client-only, so on a server it does nothing.[1]

What happens after a crash

The window immediately shows all 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. It also supports drag and drop: you can move files out of the window, or drag every log at once from the "Available log files:" label.[1]

In the pack's config as it currently stands, the window also shows up when the game crashes during mod loading and the FML error screen appears, because general.show_on_fml_error_screen is on.[3]

The window 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. In the pack's current config, the Intel corruption notice is switched on through intel_corrupted.enabled.[1][3]

Uploading logs

Logs are always uploaded to mclo.gs. The general.wrap_link option only decides which link gets copied afterwards. The pack currently uses the option the config recommends, which copies a short link that is easier to open on mobile.[3]

With the pack's current settings, the individual upload buttons are not enabled immediately after a crash. The app first scans for terminated processes, which can appear with a delay, and then enables them. This is controlled by general.prevent_upload_buttons_delay, which is currently false here. Turning the delay off could confuse users into clicking single uploads instead of the Upload All button.[3]

If a log is too big for a single upload, it is split into a head and a tail. When you copy from an individual button, a dialog asks which part you want, unless copied_links.skip_split_dialog is enabled. In the pack's current config it is disabled.[3]

The Upload All button builds one message for you to post. Its layout comes from generated_message.message_structure: a header with the title and upload link, optional custom text, the logs, the problematic frame from an hs_err file, the analysis result and the modlist changes. As the pack's config currently stands, it keeps the "### " prefix before each filename, which stops the links from being too small to hit on mobile. It also puts the names of the crash reasons and the problematic frame into the message.[3]

Metadata about uploaded logs is also sent to the mod author's API. It does not include log contents. In the pack's current config, general.send_uploaded_logs_data_to_kostromdan_dev is true.[3]

Log analysis

When a known crash reason is detected, the mod shows a dialog with a description of the problem and a detailed solution. In the pack's current config, analysis is on through analysis.enabled, and no individual analyses are blacklisted in analysis.blacklisted_reasons.[1][3]

The built-in checks are grouped by log type. For JVM crashes (hs_err files) they cover things like driver DLLs, running out of memory and a Java version that is too new. For regular logs and crash reports they include duplicated mods, Mixin errors, missing dependencies, Create and Epic Fight addon mismatches, out of memory errors and a locked file. For Windows event logs there is a check for a game that froze and was terminated by the OS.[1]

After an upload, supported logs are also run through the Codex logs analyzer on mclo.gs. When its message might be unclear, the mod shows a detailed how-to-fix message for things like an erroring block or entity.[1]

The first time a crash reason is shown, the OK button is delayed by analysis.first_show_delay, which is currently 10 seconds in this pack, so you actually read the recommendation.[3]

Tip: By default, when the mod runs in modpack mode on a player's machine, analysis will not blame a mod that was part of the original modpack. It only blames mods that were added or updated afterwards. That is analysis.trigger_on_original_modpack_mods, and it is currently false in this pack.[3]

Analysis tools

The GUI menu has a suite of analysis tools, enabled by analysis_tools.enabled. Examples are the Create and Epic Fight addons compatibility scan, which finds addons that do not match your installed version, and the MCreator mod detector, which lists every mod made with MCreator. Individual tools can be turned off with analysis_tools.blacklisted_tools, which is empty here.[1][3]

Modlist tracking

In the pack's current config the modlist feature is on. It keeps a modlist.json that the config describes as part of the modlist feature, and it adds a generated modlist.txt to the logs. It also records the modloader jar name so a loader version change is easy to spot.[3]

The file is overwritten when the game is launched by one of the listed modpack creators. With modpack_modlist.auto_update currently on, that happens on every launch at the first tick of the title screen. If you turn it off, you save manually with the /crash_assistant modlist save command. As currently configured, resource packs are added to the list and datapacks are not.[3]

Unverified The full list of mods recorded for this pack is stored in config/crash_assistant/modlist.json, and the sources here do not show its contents.

Other behavior in this pack

  • general.generate_own_launcher_log is on, so the mod writes the stderr stream to logs/stderr_stream.log. Many launchers do not save that stream, even though it can contain the crash reason.[3]
  • patches.MC307905 is currently on in this pack. It fixes a rare vanilla bug where generating the crash report itself crashes, which would stop the original report from being created.[3]
  • In the pack's current config the crash command is turned off (crash_command.enabled is false). If it were enabled, you would have to run it a second time within crash_command.seconds (10 seconds) to confirm.[3]
  • Simple mode is currently off in this pack (simple_mode.enabled is false), so the logs are visible straight away.[3]
  • In the pack's current config the piracy warning is off (piracy.enabled is false).[3]
  • The too many changes warning is currently disabled in this pack: too_many_changes_warning.count is -1, and a negative value turns the feature off.[3]
  • As currently configured, the interface language comes from the operating system (general.language_source is SYSTEM), with en_us as the fallback.[3]
  • In the pack's current config, scripts and the Scripts IDE are enabled in the GUI through scripts.enabled and scripts.ide_enabled.[3]

Which Crash Assistant config options matter?

4 parts

Crash Assistant pops up a window after a crash and helps you upload your logs. It is client-only, so it does nothing on a server. Here are the options you are most likely to care about and how this pack sets them.[1]

Getting help and sharing logs

  • general.help_link is where the Request Help button sends you. The mod's own default value is CHANGE_ME, which opens the modloader's Discord. This pack currently changes it to point at its own community Discord.[3]
  • general.formulation_type is currently set to DISCORD in this pack, so the window talks about joining the Discord and posting in a channel. The support name and channel shown in the window come from text.support_name and text.support_place, and the pack currently sets both to its own support channel.[3]
  • text.modpack_name is currently built from the Better Compatibility Checker modpack name and version in this pack, so the crash window shows the exact pack version you are running.[3]
  • general.wrap_link is currently set to kostromdan.dev in this pack. Logs are always uploaded to mclo.gs, and this option only changes which link gets copied: a wrapped link that is easier to read, especially on mobile.[3]
  • general.send_uploaded_logs_data_to_kostromdan_dev is currently true in this pack. After an upload, the mod sends metadata about the uploaded logs to the mod author's API. The log contents themselves are not sent there; they still go to mclo.gs.[3]

Crash analysis

  • analysis.enabled is currently true in this pack, so known crash reasons get a description and a suggested fix.[1][3]
  • analysis.first_show_delay is currently 10 in this pack. The first time a crash reason is shown, the OK button is delayed by 10 seconds so you read the recommendation.[3]
  • analysis.trigger_on_original_modpack_mods is currently false in this pack. When the end user runs the pack, analysis will not blame mods that shipped with the original pack, only mods you added or updated.[3]

Features the pack leaves off

Mod list tracking

modpack_modlist.enabled and modpack_modlist.auto_update are both true. That means modlist.json is rewritten on launch when a listed modpack creator starts the game, so the mod can later show which mods you added or changed. The creators listed in modpack_modlist.modpack_creators are oly2o7, billbertking1 and Satherov. You normally don't need to touch this.[3]

Tip: If you add or update mods yourself, a crash caused by them can be blamed on you. Crash analysis only skips mods that were part of the original pack, so keep that in mind when you read its results.[3]

What changed in Crash Assistant between versions?

3 parts

All the Mods 10: To the Sky 2.0.4 ships Crash Assistant 1.11.12, and the mod has been in the pack since version 1.0 or earlier. The notes below come from the mod's own changelogs, newest first.[4]

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 dynamically instead of a single fixed baseline.[5]
  • A filterable, sortable two-pane history 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.[5]
  • You can import modlist.txt data from a file or the clipboard and compare it with Current.[5]
  • Fixed: an updated mod was missed when its JAR was replaced without changing the file name or declared version. If both snapshots have a comparable CurseForge or Modrinth hash and it differs, the mod now counts as updated.[5]
  • The option general.upload_to was replaced by general.wrap_link. The old value is not migrated and is removed during the update. Copied log links now open in a new log viewer by default, a fork of the previous one made for Crash Assistant.[5]
  • The new log viewer can switch between logs from the same launch, download every log from a launch as one ZIP, wrap long lines, and show or hide each navigation and download button individually.[5]

Earlier releases

  • 1.10.0 was a major update. It added a one-click Auto-Fix for the Integrated GPU warning and moved the Fabric launch of the crash process earlier, using a LanguageAdapter.[6]
  • 1.10.8 and 1.10.9 added optional Auto-Fix buttons inside log analysis warnings, including Create6Addons, EpicFightAddons and GroovyModLoaderIPv6.[7]
  • 1.10.11 added config options to customize log order in the available logs and to include the modpack logo in the GUI.[7]
  • 1.10.23 added a Simple Mode that hides logs behind a button (disabled by default) and an option to skip the split dialog for large logs and copy both links automatically.[8]
  • 1.10.24 redesigned Mod List Difference into an interactive tool with Added, Updated and Removed sections, CurseForge and Modrinth integration, and Revert Update, Restore and Manage actions.[9]
  • 1.10.27 added GZIP compression for McLogs API uploads, which cuts payload size and upload times by up to 100x.[9]

Older highlights

With 1.9.15, Crash Assistant became available for all modloaders on every version from 1.16.5 to 1.21.8 without gaps. Version 1.9.9 added the MissingIndium, ModuleFind and UnsupportedClassVersion analyses.[10]

Sources

  1. Crash Assistant project page (modrinth) · official mod data
  2. All the Mods 10 8.1 mod list · pack file
  3. All the Mods 10: To the Sky 2.0.4 config: config/crash_assistant/config.toml · pack file
  4. All the Mods 10: To the Sky 2.0.4 mod list · pack file
  5. Crash Assistant 1.11.12 changelog · changelog
  6. Crash Assistant 1.10.4 changelog · changelog
  7. Crash Assistant 1.10.11 changelog · changelog
  8. Crash Assistant 1.10.23 changelog · changelog
  9. Crash Assistant 1.10.28 changelog · changelog
  10. Crash Assistant 1.9.15 changelog · changelog
Where this guide comes from

Written from what All the Mods 10: To the Sky 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: 2.0.1 to 2.0.2 · 1.6 to 2.0.0 · 1.1.1 to 1.2.1 · 1.0 to 1.0.2

Was this helpful?

Report wrong info

A few words are enough, up to 500 characters. Please do not include personal details.

Version in each release

25 releases, first in 1.0
All the Mods 10: To the SkyVersionJarWhere it came from
2.1.0
Oct 15, 2026
1.11.12CrashAssistant-neoforge-1.20.6-1.21.4-1.11.12.jarFrom the published release
2.0.7
Oct 5, 2026
1.11.12CrashAssistant-neoforge-1.20.6-1.21.4-1.11.12.jarFrom the published release
2.0.6
Sep 21, 2026
1.11.12CrashAssistant-neoforge-1.20.6-1.21.4-1.11.12.jarFrom the published release
2.0.5
Sep 21, 2026
1.11.12CrashAssistant-neoforge-1.20.6-1.21.4-1.11.12.jarFrom the published release
2.0.4
Sep 11, 2026
1.11.12CrashAssistant-neoforge-1.20.6-1.21.4-1.11.12.jarFrom the published release
2.0.3
Sep 9, 2026
1.11.12CrashAssistant-neoforge-1.20.6-1.21.4-1.11.12.jarFrom the published release
2.0.2
Apr 1, 2026
1.11.3CrashAssistant-neoforge-1.20.6-1.21.4-1.11.3.jarFrom the published release
2.0.1
Mar 27, 2026
1.11.3CrashAssistant-neoforge-1.20.6-1.21.4-1.11.3.jarFrom the published release
2.0.0
Feb 24, 2026
1.10.30CrashAssistant-neoforge-1.20.6-1.21.4-1.10.30.jarFrom the published release
1.9.1
Feb 5, 2026
1.10.28CrashAssistant-neoforge-1.20.6-1.21.4-1.10.28.jarFrom the published release
1.9
Feb 4, 2026
1.10.28CrashAssistant-neoforge-1.20.6-1.21.4-1.10.28.jarFrom the published release
1.8
Dec 20, 2025
1.10.23CrashAssistant-neoforge-1.20.6-1.21.4-1.10.23.jarFrom the published release
1.7
Nov 28, 2025
1.10.23CrashAssistant-neoforge-1.20.6-1.21.4-1.10.23.jarFrom the published release
1.6.1
Oct 23, 2025
1.10.11CrashAssistant-neoforge-1.20.6-1.21.4-1.10.11.jarFrom the published release
1.6
Oct 17, 2025
1.10.11CrashAssistant-neoforge-1.20.6-1.21.4-1.10.11.jarFrom the published release
1.5.1b
Oct 2, 2025
1.10.4CrashAssistant-neoforge-1.20.6-1.21.4-1.10.4.jarFrom the published release
1.5
Sep 26, 2025
1.9.15CrashAssistant-neoforge-1.20.6-1.21.4-1.9.15.jarFrom the published release
1.4
Sep 11, 2025
1.9.15CrashAssistant-neoforge-1.20.6-1.21.4-1.9.15.jarFrom the published release
1.3.1
Sep 3, 2025
1.9.15CrashAssistant-neoforge-1.20.6-1.21.4-1.9.15.jarFrom the published release
1.2.1
Aug 28, 2025
1.9.15CrashAssistant-neoforge-1.20.6-1.21.4-1.9.15.jarFrom the published release
1.2
Aug 28, 2025
1.9.15CrashAssistant-neoforge-1.20.6-1.21.4-1.9.15.jarFrom the published release
1.1.2
Aug 22, 2025
1.9.15CrashAssistant-neoforge-1.20.6-1.21.4-1.9.15.jarFrom the published release
1.1.1
Aug 21, 2025
1.9.15CrashAssistant-neoforge-1.20.6-1.21.4-1.9.15.jarFrom the published release
1.0.2
Aug 15, 2025
1.9.15CrashAssistant-neoforge-1.20.6-1.21.4-1.9.15.jarFrom the published release
1.0
Aug 14, 2025
1.9.15CrashAssistant-neoforge-1.20.6-1.21.4-1.9.15.jarFrom 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 All the Mods 10: To the Sky sets them)

400 settings this pack ships for the mod. We don't have the mod's own defaults to compare them against yet.

See all 400 settings →

Show settings
SettingAll the Mods 10: To the Sky 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...