Skip to content

Upgrading to v1.1.0

Innectic edited this page Nov 9, 2026 · 1 revision

Upgrading to v1.1.0

Stop the server, back up worlds and plugin data, replace DimensifySpigot.jar, and restart. Use Spigot 26.3 and Java 25. The API is bundled in the plugin JAR. The Sponge module remains a placeholder.

See Backups and Recovery for the files needed for a complete restore. Minecraft's world-format upgrade is separate from Dimensify's settings migration.

World settings

Existing registry entries are migrated into worlds.yml when they do not already have world settings. Available legacy type and generation metadata are reused. Migration cannot recover generation settings that were never saved by the old version.

The older preload_worlds and world_preload settings seed autoload during that migration. Subsequently, use:

/dimensify modify survival autoload true

Existing world files remain in their folders. Worlds missing their folders are reported rather than silently recreated. The old customized and default_1_1 generation types are no longer supported.

Access changes

  • Explicit world-deny nodes now take priority over default entry and allow nodes.
  • Operator fallback permission values are not treated as an explicit world denial.
  • Restrictions apply when administrators send other players, and to cross-world teleports from other plugins.
  • Main/default worlds are protected from unload, unregister, delete and regeneration.
  • Deletion and regeneration require confirmation and retain the original world folder.

Review World Access and Command Permissions when updating existing permission groups.

Inventory groups

Separation remains disabled by default; installing v1.1.0 does not automatically split player inventories. Enable it and configure groups with no affected players online. Pairing Overworld/Nether/End worlds does not automatically share their inventories.

See Inventory Groups before separating survival and creative worlds.

Storage and builds

SQLite remains the default. Spigot downloads the declared JDBC libraries on first startup. For MySQL, create the configured database first. Backend/connection changes require a restart and do not migrate data between backends.

Maven was replaced by Gradle. Use ./gradlew clean build or gradlew.bat clean build with Java 25.

Install DimensifySpigot/build/libs/DimensifySpigot.jar. The standalone API is API/build/libs/DimensifyAPI.jar. Integrations should rebuild against the current API and review changed world-management behavior.

See Getting Started for installation and Configuration for the complete configuration reference.

Clone this wiki locally