Repository navigation
Installation and Migration
Use Minecraft 26.1.2, NeoForge 26.1.2.122 or later for that Minecraft version, and Java 25. Place the GSTweaks jar in the instance’s mods folder. Use the same version on the client and dedicated server, and keep one GSTweaks jar per instance. See mod compatibility for the integrations available with other mods.
GSTweaks can start on its own. To use GSPack’s progression recipes, use GSPack’s KubeJS setup or copy the relevant recipe scripts into a compatible KubeJS instance with the required ingredients and mods.
- Stop the server or close Minecraft. Back up the instance and world.
- Install GSTweaks in a copy of the instance. Restart it so the converter can run before KubeJS loads.
- Check existing inventories and placed blocks, then test the recipes and integrations you use. Apply the same change to the original instance after the copy works.
The converter backs up recognized legacy KubeJS files and installs updated scripts where applicable. It stops if a file has been customized and needs a manual merge. Automatic backups are written under gstweaks-backup/kubejs-*/kubejs. To preview the migration from a checkout of the source repository, run the following in PowerShell.
.\migration\Install-GSTweaks.ps1 -Instance 'D:\path\to\GSPack-copy'Existing IDs such as gspack:tech_core, gspack:infinity_trophy, and stellaris:mars carry over. If an older customized pack used other IDs, define aliases in config/gstweaks-id-aliases.json on the client and server. An alias should use an old ID that is now free.
{
"items": {
"kubejs:tech_core": "gspack:tech_core",
"kubejs:infinity_trophy": "gspack:infinity_trophy"
},
"blocks": {
"kubejs:infinity_trophy": "gspack:infinity_trophy"
}
}Close Minecraft or stop the server, remove the GSTweaks jar, restore the archived KubeJS files, and remove files listed in the backup’s created-files.json. Restore the pre-upgrade world backup as well, since GSTweaks can convert blocks as chunks load.