JuanseCraft
Boot Manager for Minecraft Java.
Technology and Settings
What JuanseCraft looks like
Screenshots of version 1.3.1.3, exactly as it looks when you open it.
Patch Notes · v1.3.1.3
What changed, newest first. Everything comes inside the launcher: no need to download anything separately or install anything else.
- Your skin now shows in Minecraft 26.3. The mod that makes your skin show up (CustomSkinLoader) doesn't have an official version for 26.3 yet, and with the 26.2 one the game closed on startup. JuanseCraft now installs a fixed version of that mod on Fabric 26.3; once the official one is out, the official one is used. The mod is free software (GPL-3.0) and its source code, with what was changed, comes with the app.
- Installing for another version no longer picks the wrong mod. With the 26.3 mods in the folder, installing for 26.2 said Iris was “already installed” and left you without shaders. Now it downloads the right one, and if the right one was turned off, it turns it on.
- What you turn off stays off. A mod you turned off in My mods got turned back on when you hit Play.
- My mods tells you which mod isn't for your version. Next to it you see “Not for 26.2”. The app turns those off by itself when you play that version, but if you want to try one anyway, tick it and the app respects that.
- When updating, it tells you what's new. The “a new version is available” screen now lists the changes before you download anything.
- Open the mods folder, from My mods. It used to be in General.
- No internet? It opens anyway. If it can't reach the Juansekill server, the app goes straight in and shows a discreet “Offline” next to the name at the top. Everything that doesn't need internet keeps working.
- A clear warning if your copy isn't the official one. If the file doesn't match the one published here, a notice shows up in the middle of the screen with a button to get the official one. You can keep going, but it no longer goes unnoticed.
- Tidier Settings. The Account tab text no longer spills out of its card, and the garbage collector list opens downwards.
- Your skin shows from the very first game. Before, you had to go to Settings and hit Modify for it to show up; otherwise you were still Steve with no explanation. Now it works as soon as the version is created, and it keeps showing when switching from Fabric to NeoForge or back.
- No more false incompatible-mod warnings. A notice said pieces of Fabric API were missing with it installed and working. It was the app that couldn't find them.
- Mods get installed where they belong. They were being saved to a folder next to
.minecraft, so the game never saw them even though the app said “installed”. - If two mods don't get along, it sorts itself out. The latest Sodium and the latest Iris may not be compatible with each other. When that happens, the one that gives you FPS is kept, the other is turned off, and you're told. Before, the game simply wouldn't open.
- Installing for one version no longer breaks the other. If you installed for 26.3 and then for 26.2, you ended up with a mix and the game wouldn't start. Now the mods from the other version are turned off automatically.
- A single JuanseCraft window. Double-click it twice and, instead of opening another copy, the one you already had comes to the front.
- Iris no longer goes missing. If the download failed for a second, that mod was left uninstalled and you found out when opening the game. Now it retries.
- Several versions open, all created in one go. With vanilla, Fabric and a snapshot open at the same time, Create saved only one and the others were lost without a word.
- Each version has its own file. Before, the Fabric one overwrote the vanilla one because both had the same name. Now they're called Fabric 26.2, NeoForge 26.2, Minecraft 26.2.
- Every Minecraft version shows up, not just the downloaded ones. Before, only the ones the official launcher had already downloaded were offered, so you couldn't install Fabric on an old version.
- The profile shows up again in the official launcher. If you deleted it there and reinstalled it from the app, the app said all good and the launcher showed nothing.
- Your character in 3D in Settings → Account too. It spins on its own and you can drag it.
- About. Which version you have, a button to check for updates, and the file fingerprint to check your copy is the official one.
- Your session is no longer written in the file. The
.batfiles stored your Microsoft token in plain text: if you shared one, you gave away your session. For the ones you already had, hit Modify once to clean them. - The FPS drop when optimizing is fixed. In some versions two memory settings ended up fighting each other and the game wouldn't even open.
- If the game doesn't open, it now tells you why. Instead of nothing happening, a notice shows what failed and what to do.
- Enable and disable mods. One checkbox per mod, and the change applies
instantly — no save button. It's disabled by renaming the
.jar, the same convention used by Prism and CurseForge: a mod disabled from another launcher shows as disabled here too, and vice versa. - The launcher profile now has an understandable name. The Fabric installer
used to leave it as
fabric-loader-26.2; now it shows as Fabric 26.2 · JuanseCraft. And once it finishes installing, it lets you know you need to close and reopen the official launcher, which was the piece that was really missing. - Texture pack to gain FPS. Opaque leaves, invisible plants and flat water. It's generated on your PC, not downloaded from anywhere, and the same pack works for both old and new versions.
- Choose the garbage collector. G1, ZGC or Shenandoah. Only the ones actually supported by a Java you have installed show up, and if the version you're optimizing doesn't support it, G1 is used without you having to worry about it.
- Juansekill's server now comes pre-added. When you create a version it's added to your Multiplayer list. If you already had servers it's added at the end, and if you already had it added, nothing is touched.
- Warns about incompatible mods before you play. It detects duplicate mods, missing dependencies, versions that don't meet requirements, and conflicts declared by the mod authors themselves. Before, the game would just close after two seconds without saying anything. Extra mods are set aside, not deleted.
- World backups. One button in Settings → General. The zip is saved
outside
.minecraft, so nothing that happens in there can take it down with it. - Open the mods folder. The one for the active modset, which is the one you actually need when something goes wrong.
Quick Installation
- Download the file and unzip it to your desktop or preferred folder.
-
Run
JuanseCraft Java.exeto start. - Open Minecraft Java demo from the official launcher to get started.
- Wait for the demo to open and click on "Create Executable"
- An executable will be generated on your desktop, to launch the full game on that version!
📥 Download Launcher
Select your server. You will always get the latest version.
Your skin and cape on servers
You are the only one who sees your skin and cape. When you join a server, everyone else sees you as Steve — and you see them the same way. This is not a JuanseCraft bug: it is how Minecraft works.
Why it happens
In Minecraft your skin does not travel with you. When you join a server, every player's game asks Mojang's servers "which skin does this player have?". With a non-premium account nobody answers, so the default skin shows up.
What JuanseCraft does is install CustomSkinLoader and drop your PNG in your own folder. That is why you can see it. But the other player's game reads their folder, not yours.
How to fix it
If the server is yours
Install the SkinsRestorer plugin from your server panel (on Aternos
it is in the plugins section). From then on everyone sees your skin,
even players joining with the plain launcher and no mods. In game you use it with
/skin set <name>.
Heads up: this covers skins. Capes do not go through here.
If the server is not yours
Have the other person use JuanseCraft too. Sharing the same skin system means you see each other, capes included, without touching the server.
This is how non-premium launchers let their users see each other.
We are working on making this automatic: set your skin in JuanseCraft and everyone using the app sees it, with nothing to configure.
Frequently Asked Questions
I enabled a mod and it doesn't show up in the game
The change applies instantly, there's no save button. What the
manager does is rename the file: a disabled mod goes from something.jar
to something.jar.disabled. If you see it enabled in the list but not
in the game, it's almost always because Minecraft was open when you changed it:
close it and reopen it.
I installed Fabric and the profile doesn't show up in the launcher
You need to close the launcher completely and reopen it. It's not a bug: the official launcher only reads the profiles file once, on startup, and never checks it again. There's no way to force it to reload from outside. The profile is already created, you just won't see it until you reopen it.
Which garbage collector should I use?
If you're not sure, leave it on G1: it works everywhere. ZGC needs Java 15 or newer, 64-bit, and Shenandoah depends on who built that Java (Oracle doesn't include it; Adoptium and Red Hat do). The list only shows the ones supported by a Java you have installed, verified by actually running it, not guessed from the version number.
And if you pick one that the version you're optimizing doesn't support, G1 is used instead, no questions asked. That's on purpose: every Minecraft version ships its own Java, so picking ZGC just because 26.2 supports it would leave 1.16.5 unable to start.
Where do I download the texture pack from?
Nowhere: it's generated on your PC. It boosts FPS because normal leaves are drawn with transparency and the engine has to render everything behind every gap; with the opaque texture it just discards it. Tall grass alone is hundreds of transparent faces per chunk that don't cover anything.
Does it work for both old and new versions?
Yes, the same pack. Minecraft renamed the textures in 1.13, so both names are written, the old and the new one: the game uses whichever it recognizes and ignores the other. Tested on both ends, 1.16.5 and 26.2.
It warned me about incompatible mods. Does it delete them?
No. It sets them aside in a mods_desactivados folder,
and only if you choose "Set aside and play". You can also choose "Play anyway": the
diagnosis comes from what each mod declares, and it can be wrong.
Why does it generate a .bat file instead of opening the game?
Because that file is portable and you can inspect it: inside is the full command with the RAM, the Java, and the arguments that were chosen. You can move it, copy it to another PC, or open it with Notepad to see exactly what gets run. A launcher that launches the game internally doesn't let you see any of that.