Flarial
Download
Troubleshooting

Troubleshooting: Crashes

Fixes for common Flarial crashes and freezes — fonts, keybinds, skins, worlds, and conflicting DLLs.

Crash after selecting a custom font

Symptoms

  • Minecraft runs fine without Flarial injected.
  • After changing a module font, joining a world or server with Flarial injected crashes the game.
  • Reinjecting, launching normally first, or switching launchers does not help.

Cause

The selected custom font is likely broken or incompatible with Flarial's font rendering.

Fix

  1. Launch Flarial in private mode so the problematic font setting is not applied.
  2. Open the module/font settings you changed.
  3. Switch the module font back to a known working font.
  4. Restart Minecraft and inject Flarial again.
Still crashing?

Collect the crash_*.txt file from your Flarial logs folder (not latest_*.log) and share it in the Flarial Discord so support can inspect it.

Crash when entering a world with Walia enabled

Symptoms

  • Minecraft crashes when you enter a world.
  • The crash happens after Flarial has already launched.
  • You have Walia enabled or saved in your Flarial config.

Cause

The Walia module/config can trigger a world-entry crash on affected builds.

Fix

  1. Close Minecraft and the Flarial launcher.
  2. Open the Flarial config folder.
  3. Disable the Walia module in the config file.
  4. If you don't need to keep your settings, delete the whole Flarial config and relaunch instead.
  5. Launch Minecraft/Flarial again and test entering the world.
Note

Deleting the whole config resets all of your Flarial settings. If the crash continues after disabling Walia or resetting the config, share your crash_*.txt report in the Flarial Discord.

Crash with Insta Hurt Animation during combat

Symptoms

  • Minecraft/Flarial crashes during combat on Minecraft 26.13.
  • The crash happens when you hit another player or get hit.
  • You have Hurt Color or Insta Hurt Animation enabled.

Cause

The Insta Hurt Animation module was bugged on the affected build.

Fix

  1. Open Flarial settings if the client can still launch.
  2. Disable Insta Hurt Animation.
  3. If the crash continues, also disable Hurt Color and test combat again.
  4. Update and relaunch Flarial once a newer client build is available — the broken module was disabled in a follow-up build.
Note

If you can't reach settings, reset your Flarial config before testing again.

Crash when pressing a Flarial keybind

Symptoms

  • Minecraft/Flarial crashes only when you press a specific key.
  • The culprit is often a bind such as K.
  • A command prompt or console window may flash up just before the crash.
  • Logs don't clearly match the exact key press.

Cause

A broken or stale keybind/module config can make pressing that bind trigger a crash.

Fix

  1. Close Minecraft and Flarial.
  2. Open the Flarial config folder: %localappdata%\Flarial\Client\Config.
  3. Delete the files in that folder to reset your module/keybind settings.
  4. Relaunch Minecraft/Flarial and test the key again before restoring old settings.
Note

Deleting these files resets your Flarial settings and keybinds. If it still crashes after the reset, zip all of your Flarial logs and crash files and send the zip in the Flarial Discord.

Skin Stealer crashes on newer builds

Symptoms

  • Minecraft crashes when you use the Skin Stealer module.
  • The crash started after a recent Minecraft/Flarial update.
  • Other modules may also be broken on the same new build.

Cause

A recent update broke Skin Stealer and some other modules. There is no user-side repair for the module itself.

Fix

  1. Disable Skin Stealer for now.
  2. Update Flarial when a newer build is available.
  3. If you need a stable setup immediately, use the last stable Minecraft/Flarial version recommended by staff.
  4. If Minecraft keeps crashing with Skin Stealer disabled, that's likely a separate issue — grab your crash logs.
Note

Repeatedly reinstalling is not a known fix for Skin Stealer. If crashes persist with it disabled, share your crash logs in the Flarial Discord.

Flarial won't open alongside a custom DLL

Symptoms

  • Minecraft launches, but the Flarial UI won't open when you press the keybind.
  • You see another injected DLL/mod menu instead of Flarial.
  • You're trying to run BetterRenderDragon or another custom DLL at the same time as Flarial.

Cause

Flarial cannot reliably run alongside another custom injected DLL at the same time.

Fix

  1. Disable the custom DLL/injector before launching Flarial.
  2. Launch Minecraft with only Flarial injected and confirm the Flarial UI opens.
  3. For BetterRenderDragon-style visual changes, try Flarial's Shader Loader module instead of injecting a second DLL.
  4. If Shader Loader isn't present, it may not be available on your Minecraft/Flarial version yet.
Note

Running two injected clients at once is not a supported setup. Always reproduce issues with only Flarial injected first.

Better Frames or VSync Disabler freezes/crashes Minecraft

Symptoms

  • Minecraft freezes on the loading screen or menu after enabling Better Frames.
  • Minecraft crashes after launching Flarial, especially right after updating.
  • You have Better Frames or VSync Disabler saved in your config.
  • Some logs mention a DirectX/DX12 error; AMD/RX-series systems report this more often.

Cause

Better Frames and VSync Disabler are unstable on some current setups, especially AMD/DirectX configurations.

Fix

  1. Leave Better Frames and VSync Disabler disabled for now.
  2. If Minecraft won't stay open long enough to change settings, run .clearconfig if that command is available.
  3. Otherwise open %localappdata%\Flarial\Config and delete the saved config files, then relaunch Minecraft/Flarial.
  4. For GDK builds, clear %localappdata%\Flarial\Client\Config instead.
  5. To avoid a full config reset, open the PRIVATE config file in %localappdata%\Flarial\Config, set killdx to false, save, and relaunch.
  6. If clearing the config or setting killdx=false isn't enough, reinstall Flarial.
  7. Do not re-enable Better Frames or VSync Disabler unless a newer Flarial build explicitly fixes the issue.
Note
  • Clearing the config resets your Flarial settings.
  • You may lose motion blur or FPS gains while Better Frames is disabled.
  • On newer builds, VSync Disabler may not bypass the FPS cap without Better Frames. If you need that FPS behavior, stay on stable 26.13 until the newer build is fixed.
  • If the game still freezes or crashes with both modules disabled, share your launcher/client logs in the Flarial Discord.