Frequently asked questions.

Flarial is designed as a quality-of-life utility client, but you should verify any downloaded executable. Start from the official download page, compare the published SHA-256 value, and do not run a file from a mirror or with a mismatched hash. Server rules are separate from file safety, so check the rules wherever you play.

The full feature set is: ad-free launches on Android and Windows, Beta access to Windows builds, a Flarial+ role in the Discord, and in-game perks, like a special nametag color and icon

Yes. Flarial's core client, launcher, modules, and cosmetics are free. The Android launcher may show a launch ad, and this website may also run ads to help cover hosting and CDN costs. The core client and module library are not locked behind a paywall.

No client or module can be guaranteed to be allowed everywhere. Each server controls its own rules and can change them over time. Check the current rules for the server you join and disable any module the server does not permit.

No. Flarial is not a hack client and does not provide Storage ESP, X-ray, or unfair-play cheat features. Flarial support only covers Flarial’s official QoL, HUD, visual, scripting, and utility modules.

Yes. Flarial is a client for Minecraft Bedrock and expects a legitimate Bedrock installation from Microsoft, Xbox, or Google Play depending on platform. It is not a free Minecraft download, cracked launcher, mobile app patcher, or replacement for owning the game.

Yes — the changelog has been rolling weekly since 2023. The development team is volunteer-run, so update speed tracks Minecraft Bedrock releases, compatibility changes, and developer availability.

Bedrock 1.20 and newer is the broad target, but Flarial support is version-specific. The launcher tracks supported versions and warns you if you are on something untested. For the most reliable answer, check the launcher, Discord announcements, or support channels for the current supported build.

Flarial has to be updated for specific Minecraft Bedrock builds. New or beta builds can be unsupported or unstable even if they launch. Check the launcher, Discord announcements, or support channels for the current supported version. If you are on a newer broken build, use the Flarial version switcher to install the supported version, restart the launcher, and avoid auto-updating until support is announced.

Use the Flarial version switcher to select a build currently marked as supported. If Windows repeatedly replaces it, record when the update happens and ask support for guidance for the current launcher. Do not disable Windows services as a routine fix.

DLL injection requires elevated rights to attach to the Minecraft process. This is standard for Bedrock clients that inject into the game process. Only run the official Flarial launcher from the official website/CDN.

Usually yes. If injection fails or nothing appears, open Minecraft Bedrock first, wait for it to reach the menu or a world, then use the Flarial launcher. If Minecraft or Flarial was already stuck, close both completely and retry from a clean launch.

The DLL is not an app or installer. It is a library that must be loaded by the Flarial launcher/injector. Do not double-click the DLL or try to register it with Windows. Download the official Windows Installer from the Flarial website, use it to set up the launcher, launch Minecraft Bedrock if needed, then use the launcher to inject Flarial.

The error alone does not identify the cause. Restart the launcher, check the official download page in your browser, then test another trusted network such as a mobile hotspot. Check firewall, antivirus, school/work filtering, or DNS filtering only after that comparison. Save the exact error and launcher logs if it still fails.

The Flarial Windows Installer can trigger SmartScreen or antivirus reputation warnings because it is unsigned or newly updated. Do not bypass a warning based only on the filename: download through the official site and compare the SHA-256 value on the Security page before deciding whether to continue. Report any mismatched checksum to Flarial.

Close Minecraft and the launcher completely, then reopen the official launcher so it can check for updates. If the launcher still cannot update, download the latest Windows Installer from the official Flarial website or official CDN link. Do not use reposted installer files. If downloads fail too, troubleshoot network/CDN blocking first.

Close Minecraft and the Flarial launcher first. Rename the Flarial folders in %localappdata% and %appdata% so they remain recoverable, then download the latest Windows Installer from the official website and reinstall. Test the clean installation before restoring any old config.

Install Flarial only from the official Google Play listing linked from Flarial’s download page. Do not install patched packages or reposts. iOS is not supported because Apple's sandbox blocks the same client/modding approach, and we do not recommend jailbreak or sideload workarounds.

Flarial's Android build requires Android 9.0 or newer. If Google Play cannot install it, clear enough device storage, restart the device, and retry from the official Google Play listing. Devices that cannot update past Android 8 cannot install the current mobile build.

Migration copies Minecraft worlds, resource, behavior, and skin packs, Minecraft options, Flarial settings, module configuration, launcher preferences, Xbox/XAL files, and logs. It does not copy Discord or Flarial+ login, Android permissions, notification settings, caches, embedded-browser data, device-protected data, app-specific external storage, or package-bound runtime files. The destination app recreates excluded runtime data, and Xbox or Minecraft may ask you to sign in again.

Do not uninstall or clear data for the source Flarial app; open it first to check your worlds. If they do not appear in the destination app, open Settings, then General, then Manage Files. Flarial can offer to move valid content from the inactive Minecraft storage location. Migration Snapshots preserve the data that was previously in the destination app. If worlds are missing from both apps, stop using or reinstalling them and contact support with both Flarial versions and screenshots of Manage Files.

Fully close Flarial and Minecraft, turn off Wi-Fi and mobile data, reopen Flarial, and press Launch. If Minecraft opens, restore internet after reaching the menu or a world. If it still hangs, confirm your Minecraft version is supported, back up worlds, packs, and add-ons, then reinstall from the official Google Play listing. Include your Android, Minecraft, and Flarial versions when reporting a persistent failure.

Open Flarial, go to Settings → Manage Files, and use Import for the downloaded .mcpack, .mcaddon, or shader file. Do not rely on Android's Open with menu, which can target a different Minecraft app. If the importer is unavailable, use a file manager with app-data access to copy resource packs into resource_packs and behavior packs into behavior_packs, then restart Flarial.

Open the browser settings on the Discord authorization page, turn Desktop site off, then restart the linking flow from Flarial. If it still fails, retry without a VPN and confirm the browser is signed into the Discord account you intend to link.

On Android, Zoom can sometimes return to a lower FOV instead of the original value after unzooming. The reported workaround is to tap the quick perspective button after unzooming; if that snaps the view back, use it until a newer build fixes the state. If it still happens after updating and relaunching, report your Android version, Flarial version, and a short clip.

Open Flarial's in-game settings and enable Use Game button; the wording may vary slightly by build. If the button is present but hard to see, increase its opacity with the background-color picker. Rejoin or restart if it does not appear immediately.

Open Minecraft's accessibility settings and turn off Text to Speech for UI, then reopen Minecraft and Flarial. That accessibility mode changes controls to a double-tap interaction and is not normally a Flarial input bug.

If a module keybind works from touch input but not from an attached keyboard or mouse, open that module's keybind settings and enable both options shown for the bind, then test again with the keyboard/mouse attached through OTG. If it still does not trigger, send support a screenshot of the keybind configuration.

If the current Android client requires an older supported Minecraft build, follow the support tutorial here: https://youtu.be/Lbu2rQDIPzU. Only use trusted sources and avoid patched or reposted packages.

If tester applications are open, use the official tester form or pinned tester instructions. If applications are closed, wait for a public release or the next tester opening. Do not use unofficial Android app links or third-party mirrors. If the form asks whether you have a PC, answer honestly.

Yes. The Scripts tab in the ClickGUI supports Lua-based community modules. Use the official docs and launcher/client repositories for the current API surface.

Close Minecraft completely, reopen it through the Flarial launcher, join a world or server, then press K. If K still does not open ClickGUI, run .bind clickgui K in chat and try again. Make sure your HUD modules are enabled and on-screen. If the UI is still invisible, reset or delete your Flarial config and relaunch; this resets your settings.

Join a world or server with Flarial injected, open the menu with K, then press L while the menu is open or click the pen/edit icon to enter HUD edit mode. Drag the HUD modules where you want them, then close edit mode. If K does not open the menu, fix ClickGUI first.

Close Minecraft, press Win + R, paste %localappdata%\Flarial\Client\Config, and press Enter. Copy the trusted JSON profile into that folder, then reopen Flarial and select it. Files ending in .flarial use a legacy format; do not rename them to .json or import them by hand without current migration guidance.

First, change one small setting, close Minecraft and the launcher normally, then reopen and check whether it saved. If nothing saves, check whether Windows controlled-folder access or security software is blocking the config folder. Back up and rename the Config folder for a temporary reset instead of deleting it.

Some keybind editing is safest after joining a world/server with Flarial injected because the ClickGUI and module state are fully loaded there. Join a world, press K, open the module, then set the keybind. If keybind editing crashes, clear config and report the module/key.

Open Flarial with K, open the ClickGUI module settings, then adjust the available color/theme settings there. This changes Flarial’s in-game menu, not Minecraft resource packs or Discord name colors.

A beta or newly supported Minecraft build may not include every module immediately. Check the changelog for that build, use another currently supported version if you need the missing module, or wait for a Flarial update.

No. Armor HUD durability can display wrong values on some Minecraft builds. The inventory durability is the safer source of truth. Disable Armor HUD or switch to another currently supported version if you need accurate HUD durability.

Update Flarial, confirm your Minecraft version is supported, and test the module again after reconnecting. If it still fails, report the module settings, Minecraft and Flarial versions, and the Hive mode you tested. Do not enter an API key unless current official setup instructions explicitly require one.

If a promotion/client message option is available in settings, disable it there. The website may still show ads to help pay hosting/CDN costs, but the client and launcher do not have a paid tier or cosmetics paywall.

That is usually the Low Health Indicator module. Disable Low Health Indicator or adjust its settings if you do not want the warning border. It is a visual warning, not a crash or Minecraft damage bug.

Shader Loader is for loading supported custom RenderDragon shader files. It is optional and more advanced than normal Flarial settings. If you do not know what shader file you are loading, leave it alone.

Restart Minecraft and the Flarial launcher to pull the latest client update, then test again. If it still happens on the newest build with a fresh config, report your Minecraft version, Flarial version, and whether Zoom is set to toggle or hold.

Close Minecraft and the Flarial launcher completely, reopen the launcher so it can pull the latest client update, then retest. If the issue started after enabling Better Frames or VSync Disabler, leave those disabled. If Minecraft cannot stay open, back up and rename the Config folder, then relaunch and send the matching logs if the crash continues.

First check whether the vanilla Minecraft HUD is hidden. Press F1 or check Minecraft video/HUD settings. If only Flarial overlays are missing, use the ClickGUI/HUD troubleshooting steps instead. If both Minecraft and Flarial UI are gone after injection, restart Minecraft and send logs if it keeps happening.

Yes. Custom DLLs, other injectors, overlays, or third-party native mods can conflict with Flarial and stop it from opening or make Minecraft crash. Test with only the official Flarial launcher/client first. If that works, add custom DLLs back one at a time so you can identify the conflict.

Reset your Flarial config or remove the custom font setting from the config, then relaunch. Some fonts can crash or fail to render correctly. After recovering, use a normal/common font and avoid re-selecting the font that caused the crash.

Clear or reset your Flarial config, then set your keybinds again. Broken or old keybind entries can crash newer builds. If the crash happens after binding one specific module, report the module name, the key, your Minecraft version, and logs.

Disable Insta Hurt Animation first. If it still crashes, also disable Hurt Color and retest combat. If you cannot open settings, reset your Flarial config, then report your Minecraft version and enabled combat/visual modules.

Check Minecraft VSync, Windows display refresh rate, GPU control panel limits, and any Flarial FPS/VSync-related modules. NVIDIA users should also check the NVIDIA Control Panel for max frame rate or VSync overrides. Some current builds may not bypass the FPS cap reliably without unstable modules, so use the stable recommended build if needed.

This can be raw mouse throttling or very high polling-rate mouse issues. After Flarial injects, close the launcher and leave Minecraft open. If your mouse supports 4K/8K polling, test at 1K or lower. Advanced registry fixes should only be used if staff/support recommends them.

Update GPU drivers, reboot, disable Better Frames/VSync Disabler and third-party overlays, then test again. If logs still mention D3D11On12/DX12 device failures, send the full Flarial logs to support because it is likely a graphics/UI hook issue.

Move Minecraft to the monitor you want, set that display as your main monitor in Windows, then relaunch Minecraft and Flarial. If Minecraft keeps choosing the wrong screen, check Windows display settings and any GPU control-panel display overrides.

Clear the affected Hive/resource-pack cache, restart Minecraft, and rejoin Hive so the pack can redownload. If it only happens with Flarial injected, test without other packs or custom DLLs and report your Minecraft version plus screenshots.

Some texture packs or UI packs replace controls in ways that can conflict with Java Hotkeys. Test with the pack disabled first. If the hotkeys work without the pack, the pack is the conflict; use a different pack or report the pack name and exact hotkey that fails.

Disable Waila, relaunch, and test the same world again. If the crash stops, keep Waila disabled until a fix ships and report the Minecraft version, world/server, and what you were looking at when it crashed.

Disable Compact Chat and relaunch. If Minecraft cannot stay open long enough to disable it, clear your Flarial config. Include your Minecraft version and any chat messages/server where the crash happens when reporting it.

Disable Skin Stealer and update to the latest Flarial build. If it still crashes, report the player/skin type if relevant, your Minecraft version, and logs. Do not keep retrying the same crash loop with the module enabled.

Some bugs only happen on specific servers, resource packs, UI packs, or Minecraft versions. Test in a normal world with default packs first. If it only breaks on one server, report the server, pack, module, and steps.

Include your Minecraft Bedrock version, Flarial launcher/client version, whether you are on Windows or Android, what you clicked right before it broke, enabled modules that might be related, screenshots or screen recordings, and any crash logs or launcher logs. For crashes, explain whether it happens on launch, injection, joining a world/server, leaving a server, or pressing a keybind.

Include your Bedrock version, launcher/client version, platform, screenshots or logs, and exact steps another person can follow. Discord support is useful for quick help; the contact page lists the current support routes.

Try restarting Minecraft and the launcher, confirm your Minecraft version is supported, test with default packs and no custom DLLs, disable the module that seems related, and collect screenshots or logs. Then ask with exact steps instead of just saying help.

Name colors/icons are tied to Flarial roles such as default user, booster, supporter, media, staff, or developer. For supporter perks, link the required account/payment source if instructed and run the claim command exactly as shown in Discord. Role names, capitalization, and spaces matter.