Launch checklist
Check Java, game files, and mod compatibility before launching.
Read launch checklist →WISC / TROUBLESHOOTING
Get back to your world.
Work through the common causes of launch, download, mod, and skin problems.
Java or game startup errors
Confirm the selected executable is Java, and that its version meets your exact Minecraft and loader requirements. Reduce overly large RAM allocations and remove experimental JVM arguments while testing. Read the game output for the first meaningful error.
Downloads stop or fail
Check your connection, available storage, and write access to the instance folder. Retry the failed installation. For provider errors, check the provider’s availability; CurseForge needs its API key and some projects require manual file downloads.
Mods conflict
Match the game version and loader, install required dependencies, and remove duplicate JAR versions. Disable recent additions one at a time. For a pack, keep pack-managed versions pinned and follow the pack author’s instructions.
Skin sync problems
Check the selected Ely.by account, reconnect, and refresh the skin. Confirm the PNG format and Classic / Slim model. Offline usernames use default Steve or Alex skins, and servers or other clients may display skins differently.
Updates or portable launch problems
Extract the entire ZIP into a writable directory; running only the executable without companion files can fail. Close the launcher before replacing a portable build and keep your worlds and instance data backed up.
Report an issue
Include launcher version, OS, Minecraft version, loader, and redacted relevant logs. Never include passwords or session tokens.
GitHub issues ↗