PollyMC VS org.polymc.PolyMC

Use https://github.com/fn2006/PollyMC

u need a premium account to be logged in, after that u can make offline accounts, you'll have to install pollymc , it's a fork of prism launcher that lets u make an offline account without premium

Its called Polly MC

Pollymc is a fork of prism launcher (and according to them not affiliated in any way with prism) and it has support for ely.by accounts and offline accounts. Used it for awhile, 0 issues and it's FOSS so idk what you mean by hacked. Alternatively you can also use UltimMC. https://github.com/AfoninZ/UltimMC https://github.com/fn2006/PollyMC

PollyMC. Get the best Java JRE at adoptium.net.

I think there is no "hungarian client" that isnt a trojan, even if it bypasses AVs. If you want full Minecraft with mod support, try PollyMC (the second L is important). It is a Prism Launcher fork, which is one of the most popular FOSS launchers, but allows signing in with offline or ely.by accounts.

https://github.com/fn2006/PollyMC is what i found not tested it since I'm a using the one it fork of. It can download mods from modrinth,curseforge and more "mod hubs"

You can try PollyMC

It could be modified to be malicious after approval, but then the admins can mark it as EOL which shows a warning at install time (happened during the polymc drama for example)

I'm sure it's planned, but not only does onboarding to flat hub take time, but there's an on-going discussion on the fate of the current PolyMC flatpak. For those itching to get the launcher.

The Flatpak is in control of someone on the PlaceholderMC team and will likely be switched over to PlaceholderMC. You're free to mask updates out of an abundance of caution, of course, but it's fairly unnecessary and may cause harm if you forget to undo it later on. Relevant issue

For those who use PolyMC, the most pressing question at the moment would be "what should I do right now"; one of the discussions had a link to the following gist https://gist.github.com/Earthcomputer/dc65391f84a2c19ebac6c3... which says that the two most important steps (before opening PolyMC, otherwise it could auto-update) would be to disable automatic updates, and change the metadata server to the one from the MultiMC project (from which PolyMC had forked).

That gist also links to an issue on the flatpak package (https://github.com/flathub/org.polymc.PolyMC/issues/35); if I understood the situation correctly, if you're using the flatpak package, they will do the metadata server change for you (and it probably never had automatic updates enabled, since updates should be through flatpak itself).