Crash Assistant guide for All the Mods 10: To the Sky 1.6 to 2.0.0

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 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]

Crash Assistant is not a machine mod. There is no power, fluid or item handling to automate here. It is a client-only tool: after Minecraft crashes it shows a window with every affected log, analyzes them, and helps you report the problem. On a server it does nothing. So "core mechanics" here means what that window does and how the pack has configured it.^[1]

What the crash window does

After a crash, the window lists the game and launcher logs, crash reports and hs_err files. From there you can upload them in one click, copy the link, and take other reporting actions. It also supports drag and drop: you can drag a file out of the window to wherever you want, or drag all logs at once by grabbing the "Available log files:" label.^[1]

The window also appears when the game crashes while loading mods and the FML error screen is shown, because general.show_on_fml_error_screen is on in the pack. If an older crash window is still running when you start Minecraft again, general.kill_old_app closes it so you are not confused by a stale window.^[4]

Log analysis

Analysis is enabled in the pack (analysis.enabled). The mod checks logs for many known crash reasons. When it recognises one, it shows a dialog with a problem description and a detailed fix. The checks cover JVM crashes (hs_err files such as GPU driver problems or running out of RAM), regular logs and crash reports (such as duplicated mods, Mixin conflicts, missing dependencies or OutOfMemoryError), and the Windows event log.^[1][4]

After an upload, the mclo.gs Codex logs analyzer also checks each supported log. When its message would be unclear, the mod shows its own detailed how-to-fix message instead, for example for an erroring block or entity.^[1]

You can switch off individual checks by class name with analysis.blacklisted_reasons. The pack leaves that list empty, so every check is active.^[1][4]

The window's menu also has analysis tools. One scans your mods for addons that are incompatible with your installed Create or Epic Fight version. Another lists every mod made with the MCreator tool.^[1]

Uploading and getting help

Logs are always uploaded to mclo.gs. general.upload_to is set to "mclo.gs" in the pack, and the other supported value would wrap the link for different formatting. Before your first upload, the window asks you to accept a privacy policy, because general.enable_privacy_policy_acceptance is enabled.^[4]

The Request Help button opens the link set in general.help_link, which the pack points at its Discord community. The wording around it comes from these text settings: text.modpack_name is "$BCC.modpackName$ - $BCC.modpackVersion$" (filled in from Better Compatibility Checker), text.support_name is "ATM10 To the Sky Support Channel", and text.support_place is "#10sky-techsupport channel".^[4]

The generated message

The Upload all button builds one message you can paste when asking for help. In the pack it is set up like this:^[4]

• generated_message.put_analysis_result_to_message is on, so the message names the crash reasons instead of only counting them.^[4]
• generated_message.put_problematic_frame_to_message is on, so the problematic frame from an hs_err file is included.^[4]
• generated_message.one_line_logs is on, so logs are separated by a short divider instead of new lines, keeping the message vertically small.^[4]
• generated_message.h3_prefix is on, which adds a ### prefix before each filename so the links are not tiny and hard to tap on mobile.^[4]
• generated_message.color_message is on, which colors the modified mods count and analysis with ANSI. It can need turning off if you report somewhere that does not support ANSI code blocks, like GitHub.^[4]
• generated_message.text_under_crashed and generated_message.warning_after_upload_all_button_press are both empty in the pack, so no extra text or warning is added.^[4]

Window appearance

The pack keeps the default look. The Upload All button uses font size 16 and the color "0_178_0" (dark green), and the Request Help button uses font size 16 and "0_0_178" (dark blue). Colors are written as R_G_B. The window's border is animated to grab your attention, and a notice reminds you that a screenshot of the window tells the pack's creators nothing.^[4]

• gui_customisation.upload_all_button_font_size and gui_customisation.request_help_button_font_size control the button sizes.^[4]
• gui_customisation.screenshot_of_gui_notice_animated_border and gui_customisation.show_dont_send_screenshot_of_gui_notice control the animated border and the screenshot notice.^[4]

The crash command and the modlist

The pack ships with the crash command disabled (crash_command.enabled is false). If it were enabled, crash_command.seconds (10 here) is how long you would have to run the command a second time to confirm.^[4]

The modlist feature is enabled (modpack_modlist.enabled). It records the pack's mods in a modlist.json file, and the pack also adds a generated modlist.txt to the logs, includes the modloader jar name and lists resource packs. Auto-update is off, so the file is not overwritten on every launch. Only the players listed in modpack_modlist.modpack_creators can overwrite it, and the manual save command is /crash_assistant modlist save.^[4]

Unverified The contents of config/crash_assistant/modlist.json (the saved list of the pack's mods) are not shown in the sources here, so what it records for this pack is unverified.

Crash Assistant is the window that pops up after a crash and lets you upload your logs in one click. It's client-only, so on a server it does nothing. Everything below is how this pack sets it up in its config file.^[1][4]

Getting help and uploading logs

• general.help_link points the Request Help button at the pack's own Discord invite. The config comment says that if this were left at CHANGE_ME, the button would open the modloader's Discord instead.^[4]
• text.support_name and text.support_place are set to the pack's tech-support channel. They fill in the wording of the "Request help" text in the window.^[4]
• general.upload_to is "mclo.gs". Logs always go to mclo.gs. The alternative value, gnomebot.dev, only wraps the link for nicer formatting.^[4]
• general.enable_privacy_policy_acceptance is true, so you have to accept the privacy policy before your first log upload.^[4]

When the window shows up

• general.show_on_fml_error_screen is true, so you also get the window when the game crashes during mod loading and the FML error screen appears.^[4]
• general.kill_old_app is true. If an old Crash Assistant window is still open when you start Minecraft again, it gets closed so you don't mix up an old crash with a new one.^[4]
• analysis.enabled is true, and analysis.blacklisted_reasons is empty. No crash analyses are switched off.^[4]
• crash_command.enabled is false, so the manual crash command is turned off. If you enable it, crash_command.seconds (10 here) is how many seconds you have to run the command a second time to confirm.^[4]

The message you paste into support

The "Upload all" button builds a message for you to post. In this pack, generated_message.one_line_logs, generated_message.h3_prefix and generated_message.color_message are all true. That keeps the message compact, makes the links bigger and easier to tap on mobile, and colours the analysis with ANSI. The comment on the colour option says to turn it off if you're posting somewhere that doesn't support ANSI code blocks, like GitHub.^[4]

generated_message.put_analysis_result_to_message and generated_message.put_problematic_frame_to_message are true too. So the message lists the names of the detected crash reasons instead of just a count, and includes the problematic frame from any hs_err file. The message language is "en_us", and the extra text and warning options (generated_message.text_under_crashed, generated_message.warning_after_upload_all_button_press) are empty.^[4]

The header line of that message comes from text.modpack_name. It's set to use Better Compatibility Checker placeholders for the pack name and version, so the message shows the exact version you're running.^[4]

Modlist tracking (for the pack team)

modpack_modlist.enabled is true, and the pack ships a saved modlist.json snapshot of its mods with jar names, mod ids, versions and hashes. modpack_modlist.auto_update is false, so that file is not overwritten on every launch. The config comment says the team saves it manually with the '/crash_assistant modlist save' command. modpack_modlist.modpack_creators lists three nicknames, and only those players can overwrite the file. As a normal player, you can ignore this.^[4][5]

Button looks

The Upload All button uses font size 16 and the color "0_178_0" (dark green). The Request Help button uses font size 16 and "0_0_178" (dark blue). Per the config comments, these are the standard looks for those buttons, so the pack hasn't restyled them. The notice about screenshots and the animated border are both on.^[4]

All the Mods 10: To the Sky 2.0.0 ships Crash Assistant 1.10.30, and the mod has been in the pack since 1.0 or earlier. The notes below come from the mod's own changelogs, newest first, so everything up to 1.10.30 is in your pack.^[6][7]

Recent releases

• 1.10.30: fixed a formatting bug in the message generator that was introduced in 1.10.29.^[7]
• 1.10.28: added new trusted domains and fixed links sometimes not opening on Linux.^[8]
• 1.10.27: added GZIP compression for McLogs API uploads, which cuts payload size and upload times by up to 100x.^[8]
• 1.10.25: fixed OutOfMemory errors in the Crash Assistant process. Hashing mod files now streams them instead of reading whole files into memory.^[8]
• 1.10.24: redesigned the Mod List Difference feature into an interactive tool with Added, Updated and Removed sections. It supports CurseForge and Modrinth, and has Revert Update, Restore and Manage actions, with drag and drop as a fallback when a mod blocks third-party downloads.^[8]
• 1.10.23: added an option to skip the split dialog for large logs and copy both links automatically. Also added a Simple Mode that hides logs behind a button, disabled by default.^[8][9]
• 1.10.22: the Crash Assistant log now shows the full analysis message formatted with Markdown, instead of just the first line.^[8][9]

Analysis and log changes

• 1.10.21: added new log analyses including JnaPermissionIssue, AzureLibAddons, MedievalOriginsVsForgeOrigins and McdaMcdwVsClumps. The stderr_stream.log is now shown to you only if it includes stack traces.^[9]
• 1.10.20: Crash Assistant started generating stderr_stream.log with the stderr output of the Minecraft process.^[9]
• 1.10.11: added config options to customize the log order in available logs and to include the modpack logo in the GUI.^[10]
• 1.10.8 and 1.10.9: introduced optional Auto-Fix buttons inside log analysis warnings. 1.10.9 added a one-click Auto-Fix for GroovyModLoaderIPv6.^[10]

Major update and compatibility

• 1.10.0 (major update): on Fabric, the mod's process now launches from a LanguageAdapter so it starts from the earliest possible point. It also added an Auto-Fix option for the Integrated GPU warning, so it can be fixed with one click.^[11]
• 1.9.15: Crash Assistant became available for all modloaders on every version in the 1.16.5 to 1.21.8 range without gaps.^[12]
• 1.9.13 was the initial release for 1.7.10, and 1.9.10 was the initial release for 1.12.2.^[12]