#✅ | I keep gettting crashes while playing with FancyMenu on.

1 messages · Page 1 of 1 (latest)

manic zenith
#

The crash fired the moment I opened your inventory (the stack trace goes through InventoryScreen → AbstractContainerScreen), and the actual error is a mixin violation inside FancyMenu 3.9.8 itself: its class ContainerWidgetPointerTracker lives in FancyMenu's declared mixin package, and some other part of FancyMenu referenced it directly — which the mixin framework flat-out forbids. That's not a config problem or anything you did; it's a packaging bug in that build of FancyMenu. Note the "Suspected Mods: NONE" line — the crash reporter couldn't attribute it because the referencing happened during class transformation, but the class name in the error makes it unambiguous.

severe pantherBOT
#

Hi! 👋 Please first click the button below to start this support ticket.

⚠️ It is not possible for anybody to send messages in this ticket before it has been started, so you need to click the button for others to be able to help/answer you.

severe pantherBOT
# manic zenith The crash fired the moment I opened your inventory (the stack trace goes through...

Do you prefer to continue in English, or in another first language? 🇬🇧

Your interpretation may be correct if the exact log contains the mixin-package violation involving ContainerWidgetPointerTracker, but I can’t confirm it from the description alone. Suspected Mods: NONE does not conclusively rule out FancyMenu.

Please try this order:

  1. Update FancyMenu 3.9.8, Konkrete, Melody, your mod loader, and Fabric API if applicable. Also update any FancyMenu addons you use.
  2. Test with only FancyMenu, Konkrete, Melody, and the required loader/API installed.
  3. Reproduce the inventory crash.
  4. Send /logs/latest.log as an attachment, captured immediately after the crash. The latest log is more useful than the crash report because it contains the relevant information at the end.

If the crash still occurs in the minimal setup, it is most likely a FancyMenu bug. At that point, please report it in the FancyMenu GitHub repository, including your Minecraft version, loader/version, mod versions, and latest.log.

manic zenith
severe pantherBOT
# manic zenith
Minecraft Crash Log Analysis

Log Overview
The game crashed due to an IllegalClassLoadError caused by FancyMenu attempting to reference a mixin class directly (ContainerWidgetPointerTracker). This usually occurs because a helper class within the mixin package was loaded directly or there is a mixin conflict with other mods modifying standard container screens (such as Applied Energistics 2 or IC2 Classic).

#

Potential Problem Solutions
Update FancyMenu to the latest version available for Minecraft 1.19.2 to see if this packaging issue has been resolved. Additionally, ensure Konkrete and MixinExtras are fully updated to prevent compatibility issues during mixin application.

#

Minecraft
Minecraft Version: 1.19.2
Mod Loader: Forge
Mod Loader Version: 43.5.0

Detected Optimization Mods
No optimization mods detected.

Compatibility-Relevant Mods
Essential: Not detected
Distant Horizons: Not detected
Sinytra Connector: Not detected

Important Mods
JustZoom Version: Not Detected
FancyMenu Version: 3.9.8
Spiffy Version: Not Detected
Drippy Version: Not Detected
Konkrete Version: 1.8.0
Melody Version: 1.0.1
MCEF Version: Not Detected
FER Version: Not Detected
WaterMedia Version: Not Detected
WaterMedia Binaries Version: Not Detected
Likely Caused by WaterMedia: No

⚠️ Crash logs are not as good/informative as full latest.log files. Please send the full log from <MC instance directory>/logs/latest.log for better debugging.

severe pantherBOT
# manic zenith

The attached crash log confirms the core diagnosis:

  • Minecraft: 1.19.2
  • Forge: 43.5.0
  • FancyMenu: 3.9.8
  • Konkrete: 1.8.0
  • Melody: 1.0.1
  • Error: IllegalClassLoadError involving ContainerWidgetPointerTracker
  • The crash occurs while creating AbstractContainerScreen, when opening an inventory.

This is not caused by a FancyMenu layout or configuration. However, the log also shows several other mods injecting into the same screen class, including AE2, Balm, SuperMartijn642CoreLib, and IC2 Classic, so a mod conflict cannot be ruled out yet.

Please do the following:

  1. Update FancyMenu, Konkrete, Melody, Forge, and all other mods to the latest builds available for Minecraft 1.19.2.
  2. Test with only FancyMenu, Konkrete, and Melody installed.
  3. Reproduce the inventory crash.
  4. Send the full /logs/latest.log file captured immediately afterward. The attached crash report confirms the exception, but latest.log provides more context.

If it still crashes in that minimal setup, this is most likely a FancyMenu bug in that build. Please then report it in the FancyMenu GitHub repository with the latest.log, Minecraft/Forge versions, and the listed mod versions.

manic zenith
severe pantherBOT
# manic zenith
Minecraft Log Analysis

Log Overview
The game crashed due to a division by zero error (ArithmeticException: / by zero) when FancyMenu tried to render a nine-sliced or repeating widget background. This typically occurs because a customized button or UI element in a FancyMenu layout has a width or height configuration of 0, which causes the layout math inside GuiGraphics.slices to fail recursively.

#

Potential Problem Solutions
Ensure all customized buttons, textures, and elements in your FancyMenu layouts have a width and height greater than 0. If you cannot access the menu to fix this, locate your instance's configuration files for FancyMenu (usually in .minecraft/config/fancymenu/ or .minecraft/fancymenu/) and look for any layout configuration containing a zero-sized element. Alternatively, temporarily disabling customized layouts or updating FancyMenu to its latest version for 1.19.2 may resolve this issue.

#

Minecraft
Minecraft Version: 1.19.2
Mod Loader: Forge
Mod Loader Version: 43.5.0

Detected Optimization Mods
No optimization mods detected.

Compatibility-Relevant Mods
Essential: Not detected
Distant Horizons: Not detected
Sinytra Connector: Not detected

Important Mods
JustZoom Version: Not Detected
FancyMenu Version: 3.9.6
Spiffy Version: Not Detected
Drippy Version: Not Detected
Konkrete Version: Unknown
Melody Version: Unknown
MCEF Version: Not Detected
FER Version: Not Detected
WaterMedia Version: Not Detected
WaterMedia Binaries Version: Not Detected
Likely Caused by WaterMedia: No

severe pantherBOT
# manic zenith

The new log shows a different crash from the previous one:

  • Error: ArithmeticException: / by zero
  • Location: FancyMenu’s blitNineSliced / blitRepeating rendering code
  • Screen: An Applied Energistics 2 inventory screen
  • FancyMenu actually loaded: 3.9.6, not 3.9.8

The most likely cause is a FancyMenu custom button/widget texture using nine-slicing with an invalid zero-sized value, possibly through a global button texture or button template. The AE2 screen is where it becomes visible, but AE2 may not be the root cause.

Please do this first:

  1. Remove old FancyMenu JARs from the mods folder and ensure only the latest FancyMenu build for Forge 1.19.2 is installed.
  2. Update Konkrete, Melody, Forge, and the other mods.
  3. If the crash remains, temporarily disable FancyMenu’s custom button textures/nine-slicing or button templates, especially global customizations.
  4. Test again and send /logs/latest.log captured immediately after the crash.

Also, this log confirms that the instance is still loading fancymenu_forge_3.9.6_MC_1.19.2.jar. If you intended to test 3.9.8, the old JAR is still being loaded or the update was made in a different instance.

If the crash persists with only FancyMenu, Konkrete, and Melody installed and with current builds, it is most likely a FancyMenu bug. Please report it in the FancyMenu GitHub repository with the new latest.log.

severe pantherBOT
# manic zenith
Message Edit Ignored

Editing messages does not change the AI conversation history. Alice will continue to see and use the original message text that was stored before the edit.

severe pantherBOT
# manic zenith
Message Edit Ignored

Editing messages does not change the AI conversation history. Alice will continue to see and use the original message text that was stored before the edit.

severe pantherBOT
#
Thread Marked as Solved

This support thread has been automatically marked as solved because there were no new messages for at least 24 hours.

The AI helper is now disabled. If you still need help, please create a new support thread.

Marked automatically after 24h of inactivity