Troubleshooting
The problems people actually run into, and how to fix them.
Studio
There’s no Massif button and G does nothing
Massif Studio isn’t loaded. Check that you launched the Massif Studio instance (not your usual
one), that it runs Minecraft 26.2 with Fabric, and, if you installed the mod by hand, that
Fabric API is in the mods folder too.
“No login is waiting with that code”
The code is mistyped or has expired: codes last ten minutes. Press G again in Minecraft for a fresh one.
Studio asks me to update
Your Studio is older than the version Massif Cloud needs. Download the latest from Downloads and replace the old one.
Export says signing isn’t available
Massif can’t sign worlds right now, usually during maintenance. Your project is safe; try again later.
Server
Paper: my world is vanilla terrain
Massif didn’t load your world. Look for Massif’s line in the console: it says why. The usual causes:
- the file isn’t at
plugins/Massif/world.massif, or isn’t named exactly that; - the plugin doesn’t match your server version (26.3 and 1.21.11 are different files);
- the server runs Java 21 instead of 25;
bukkit.ymlnames a different world thanlevel-nameinserver.properties.
After fixing it, delete the world before exploring: chunks that were already generated stay vanilla.
Paper: “not signed by Massif”
The file was changed after export, or wasn’t exported by Massif. Download it again from your account.
My changes don’t show up on the server
Existing chunks never change. Export again, replace the file, restart, and explore new areas, or start a fresh world.
Account
I lost my password
Password reset by email isn’t available during the beta yet. Contact us and we’ll sort it out.
Remove an old computer
Every computer you log in from appears under Linked Studios on your account. Remove the ones you don’t use any more: they’re signed out immediately.