Crash Assistant guide for All the Mods 10: To the Sky 1.1.1 to 1.2.1

Report a mistake on this page

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

Same as in the All the Mods 10: To the Sky 2.0.4 guide

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?

8 parts

Crash Assistant is a different kind of mod from the machine mods you'll find elsewhere in the pack. It has no machines, multiblocks, power, fluids or item handling to automate. Its whole job is to help you and the pack's support team when Minecraft crashes, so this section walks through how that works and which settings the pack uses.[1]

It's client-only. On a server it does nothing.[1]

What happens when the game crashes

After a crash, the mod shows a window that immediately lists all the affected game or launcher logs, crash reports and hs_err files. From there you can upload them in one click, copy the link, and do other things that make reporting a problem easier.[1]

The window supports drag and drop. You can drag a single file out of it, or drag all the logs at once by dragging from the "Available log files:" label.[1]

  • 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 on in the pack.[1][4]
  • If an old crash window is still open when you start Minecraft again, the mod closes it so you don't get confused by a stale crash: general.kill_old_app is on.[4]
  • Log files whose names start with an entry in general.blacklisted_logs are hidden from the log list. The pack leaves that list empty.[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 fix. The mod's page says a large share of issues (more than 75%) are common and easy to solve, which takes load off modpack support.[1]

The checks cover JVM crashes (hs_err files), normal logs and crash reports, and the Windows event log. Examples are GPU driver problems, running out of memory, duplicated mods, Mixin conflicts and a mod compiled for a newer Java than the one you're running.[1]

In this pack the feature is switched on with analysis.enabled. analysis.blacklisted_reasons is empty, so no analysis is turned off. If a pack maker wanted to disable one, they would list its class name there, for example Create6Addons.[4]

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

Analysis tools

The GUI menu has a set of analysis tools. Two are described: one scans your mods for addons that don't match your installed version of Create or Epic Fight, and the MCreator Mod Detector lists every mod made with the MCreator tool.[1]

Uploading and the generated message

Logs are uploaded to mclo.gs. general.upload_to is set to mclo.gs in the pack, and the other supported value, gnomebot.dev, would only wrap the link for better formatting. Before your first upload the mod asks you to accept a privacy policy, because general.enable_privacy_policy_acceptance is on.[4]

The "Upload all" button builds a message you can paste into a support channel. The pack configures it like this:[4]

Getting help from the window

The window has a Request Help button that opens the link in general.help_link, which the pack points at its community Discord. The support channel wording in the window comes from text.support_name and text.support_place. The crash title uses text.modpack_name, which reads the pack name and version from Better Compatibility Checker placeholders.[4]

Both big buttons are enlarged to get your attention. The Upload All button has font size 16 and a dark green colour (0_178_0), and the Request Help button has font size 16 and dark blue (0_0_178). For comparison, the default Swing font size is 12. The colour format is R_G_B with values from 0 to 255.[4]

The pack also keeps the window's animated border on and shows a notice that a screenshot of the window tells the pack makers nothing.[4]

The crash command

The mod has a command for deliberately crashing the game, but in the pack crash_command.enabled is off. If it were enabled, you would have to run it a second time within the number of seconds in crash_command.seconds (10 here) to confirm. A value of 0 or less disables the confirmation.[4]

Modlist tracking

modpack_modlist.enabled is on in the pack. This feature keeps a modlist.json for the pack. With modpack_modlist.add_modlist_txt_as_log on, a generated modlist.txt is added to the logs, listing mod names, mod ids, mixin configs and jarjar mod info. modpack_modlist.add_modloader_jar_name and modpack_modlist.add_resourcepacks are also on, so the modloader jar name and your resource packs are included too.[4]

Only the players named in modpack_modlist.modpack_creators can overwrite modlist.json. modpack_modlist.auto_update is off, so it isn't rewritten on every launch. A pack maker saves it manually with the /crash_assistant modlist save command.[4]

Unverified The actual contents of the pack's modlist are in config/crash_assistant/modlist.json, which the sources here do not show.

Intel processor warning

The pack has the Intel corrupted warning on, along with its funny gif (intel_corrupted.enabled and intel_corrupted.show_gif). The generated message also gets a line saying the Intel processor can be corrupted, through generated_message.intel_corrupted_notification.[4]

Which Crash Assistant config options matter?

5 parts

Crash Assistant is the window that pops up after Minecraft crashes, and it only runs on the client. This pack ships version 1.9.15. Most of its settings are fine as they are, so here are the ones you're most likely to touch or wonder about, with the values this pack uses.[1][5]

Support and branding

Uploading logs

Analysis and the generated message

Tip: generated_message.color_message is true, which colors the generated message with ANSI. If you paste it somewhere that doesn't support ANSI code blocks, like GitHub, set it to false.[4]

Crash command and GUI look

Modlist tracking

modpack_modlist.enabled is true, so the pack keeps a modlist file that is added to your logs. modpack_modlist.auto_update is false, so the modlist is not rewritten on every launch. The pack's creators save it manually with the /crash_assistant modlist save command. modpack_modlist.modpack_creators lists the people allowed to overwrite it, and it's a technical setting that isn't shown anywhere in-game.[4]

What changed in Crash Assistant between versions?

2 parts

All the Mods 10: To the Sky 1.2.1 ships Crash Assistant 1.9.15, and the mod has been in the pack since version 1.0 or earlier. Here are the notable changes from the mod's own changelog, newest first.[6][7]

Recent releases

  • 1.9.15: backported to a long list of older Minecraft versions and loaders (Forge, Fabric and NeoForge). Crash Assistant is now available for all modloaders on every version from 1.16.5 to 1.21.8 without gaps, plus small fixes and improvements.[6]
  • 1.9.14: marked 1.21.8 as compatible. The rest of this release is fixes for the 1.7.10 and 1.12.2 versions, such as client-side-only initialization and a fix for the mod rarely starting twice.[6]
  • 1.9.13: initial release for 1.7.10. The 1.12.2 version got compatibility work, with most coremods removed in favor of Forge events.[6]
  • 1.9.12: finally fixed the root cause of the gpu-detect-jni.dll issue. Before this, the check for running on an integrated GPU could extremely rarely fail to work.[6]
  • 1.9.11: fixed a rare issue where Crash Assistant did not start, caused by the switch to gpu-detect-jni.dll in 1.9.7. GPU detection now runs in a separate process, so a detection failure can't stop the app from starting. The ModuleFind analysis text was also made clearer.[6]
  • 1.9.10: backport to 1.12.2, which was its initial release for that version, plus a small fix in 1.16.5.[6]

Log analysis additions

Version 1.9.9 was the big one for crash diagnosis. It added a MissingIndium analysis for when the Indium mod is missing and the game is crashing. It also added a ModuleFind analysis for "Module A not found, required by B", and an UnsupportedClassVersion analysis for a mod compiled with a more recent version of Java.[6]

The same release improved the MixinApply analysis, which now detects a mixin config declared with a more recent version of Java. It also improved the error message for multiple Create mods in the CreateDependencies analysis, and fixed Crash Assistant not starting in some rare cases because it thought Minecraft had finished normally.[6]

Version 1.9.8 fixed the Create6Addons analysis, which had been slightly broken by the 1.9.7 update and wasn't triggered in some cases.[6]

Unverified Changes before 1.9.8 and any pack changelog notes about this mod could not be confirmed from the available sources.

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 1.2.1 config: config/crash_assistant/config.toml · pack file
  5. All the Mods 10: To the Sky 1.2.1 config: config/crash_assistant/modlist.json · pack file
  6. Crash Assistant 1.9.15 changelog · changelog
  7. All the Mods 10: To the Sky 1.2.1 mod list · pack file
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.3 to 2.1.0 · 2.0.1 to 2.0.2 · 1.6 to 2.0.0 · 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.