well bro not to get to personal, but not only does a bundled cef hog resources which constrained setups may lack, it also forces chromium onto your machine (people have loads of opinions about which browser to use) but most significantly of all:
It makes LiquidBounce genuinely, literally unusable on my system. My game crashes on a good launch every 20 30 minutes with SIGILL / SIGSEGV and it comes directly from libcef.so
The 50MB of extra disk space needed by the ScriptAPI sure may be an itch to some users but it's NOT where priorities should lie.
"Legacy" LiquidBounce had 3 flavors of it's NATIVE ui.
No browser, no nothing, NATIVE UI with 3 different bundled flavors.
We're now at Java SDK 26, in the great 2026 and you're telling me a Svelte-Websocket-bundled-chromium is the only possible rendering backend?
Please take the time and make it happen, it's not that hard. Or set an AI to do it, it doesn't even cost you anything. It's literally free and it would improve the client by 200% for certain parts of it's audience that still haven't ditched it because it's just so good in other ways..
We're not asking for you to overhaul your client, just hide a toggle deep in the settings where it says: "Use minecraft-style / native GUI" -- which then uses an alternate backend for users who simply: prefer it simple.
Or, keep it all as is but native-i-fy it? How about that? Don't ditch your UI, just ditch how it's implemented.
Keep the visual, change the engine. (Think Flutter for example)
I've been using AI so much i literally sound like it by now XD
Yeah anyways. I don't like to hate but i literally can't ignore it - I'm reminded every half an hour that libcef.so has caused a crash again, i'm sorry.
EDIT: I just thought about it a bit but flutter would fix all current cef issues while making it possible to keep the UI pixel-for-pixel
This would be how: (Feed into AI and voi la)
implement the LiquidBounce design language (Flutter just decoupled, material / cupertino design is no longer required or default, dozens of design languages are live on https://pub.dev + flutter desktop support is mature enough by now)
implement as high level ui with normal socket communication (or none at all but idk if technically possible, perhaps dart's ffi (foreign function interface) works)
ship the respective flutter engines, see https://dart.dev/overview#platform - there's literally a native engine for every target, so it even fixes the SIGILL / SIGSEV problems, which as i understand come from certain cpu instruction mismatches generated by chromiums JIT compilation sometimes.