Please add more features
I have a lot of feature ideas.
- Mutiple auth services eg. https://ely.by/ and https://littleskin.cn/
- More security features
- A enhanced ui like lunar but with a nice red gradient background and a nice icon sidebar
- More animations
- Modrinth, curseforge and more mod support
- More optimized
- Have a mod menu in game
- Custom UI in game I really hope you can add some of these features if you need feel free to tell me!
EDIT: You also can't join multiplayer servers either.
EDIT: Add instance creating and deleting
- This is not planned, we're only supporting official Minecraft authentication. You can implement them into your fork, but we won't give support in that case.
- Define "security features"?
- Feel free to fork and edit the UI to suit your needs
- Not sure what are @dscalzi thoughts about this, but you may always open a PR for this
- Curseforge is supported, and there's a PR for Modrinth support
- Define "optimized"
- I'm gonna assume you want custom menu? There's a mod for that
- Thesaid mod can do that too!
Edit: You can remove instances by simply removing the folder from Nebula, and multiplayer works, unless you broke something (try to logout and login from the launcher)
Thanks for the reply and clarifications! Let me elaborate on what I meant for each suggestion:
Instance Creation and Removal: I was referring to being able to create and delete instances directly from inside the launcher UI, similar to how other launchers like ATLauncher or Prism Launcher do it-where you can add a new instance with a button and remove them from a context menu, rather than manually handling folders. This would make managing different modpacks and setups much more user-friendly.
Security Features: By security, I meant things like having authentication data (tokens, passwords) encrypted more robustly, and ideally encrypting other sensitive user data stored by the launcher. I’m aware that Minecraft’s default password storage isn’t very secure, so stronger encryption or even integration with OS-level credential storage (like Windows Credential Manager, macOS Keychain, etc.) would be great for user safety.
Custom In-Game Menu (Mod Menu): For the custom menu, I meant an in-game mod/configuration menu similar to what Lunar Client offers. This would include toggles and settings for client-side features like CPS (clicks per second), FPS counters, coordinates, armor HUD, and more-all accessible and configurable in-game, not just in the launcher. Mods like MiniHUD, Inventory HUD+, and others replicate some of this on Fabric, but a built-in, unified menu like Lunar’s would be awesome.
Let's talk about instance creation and removal, and in game menu:
-
Helios is made for servers that needs (or wants) a custom launcher for their services. This is not made for the average John Doe to use as a replacement of a "normal" launcher, like Prism for example. For the same reason, if you want a Lunar-like approach, feel free to make a mod yourself. It's up to the server owner to decide which mods should be added or not
-
Regarding the "security features", I'd yet have to see a launcher that encrypts the tokens and everything, besides the official one.
- Mutiple auth services eg. https://ely.by/ and https://littleskin.cn/
The authentication service is managed by Helios-Core and the processbuilder via Authlib-Injector, you can take a look at my forks to use them as reference, altought you might want multiple auth services without the need of making a core build to get just a single one working, i studied that possibility and it should be possible by passing the authserver endpoint to the processbuild and the auth flow (by specifying the Authlib-Injector url at login, just how Polly and Fjord do) but i wasn't searching for that, seeing it working would be cool so give it a try and let us see your results!
the skin renderer part would be a bit difficult as it should support every authserver and for some reason the Minecraft usernames aren't syncing automatically when the user changes it so this would be another barrier, as i can't know if it's fault from the custom authserver or it was a flaw even when official Yggdrasil protocol was working