uSkyBlock 3.4.1 replaces 3.4.0, which had a startup logger regression and should not be used. If you installed 3.4.0, upgrade directly to 3.4.1. uSkyBlock 3.4.x makes setup and upgrades safer with explicit config migrations, clearer schematic configuration, and more predictable validation and fallback behavior. Please check your startup logs after upgrading: some legacy config problems that were prev iously silently ignored now produce warnings, and while known cases are migrated automatically, not every invalid configuration can be repaired safely. If you have issues, you are welcome to reach out via issues ( https://github.com/uskyblock/uSkyBlock/issues) for support.

3.4.1

• Fixed a startup failure in 3.4.0 caused by Guice logger injection conflicting with Guice's built-in Logger binding.
• No config or data migration changes were introduced in 3.4.1 beyond the 3.4.0 release line.

Upgrade and config reliability

• Added explicit, versioned config.yml migrations to make upgrades safer and more predictable.
• Time-based config values now use duration syntax like 30s, 2m, and 1h to make units explicit. Existing configs are migrated automatically.
• Please verify options.party.invite-timeout after upgrading. Older defaults, docs, and runtime behavior were not aligned between s and ms. The new default is 2m.
• Legacy-only keys are cleaned up automatically during upgrade.
• config.yml is now the only supported main config filename. If you use config_.yml, rename it to config.yml before upgrading.

Schematics and island setup

• Island schemes now use explicit schematic file paths, with automatic migration from older config layouts.
• Startup validation is stricter: invalid or unusable default schemes now produce clear warnings and safer fallback behavior.
• Fixed spawn placement on first world generation (hotfix already shipped in 3.3.2).

Config validation and defaults

• Invalid config values now log clear warnings and fall back deterministically instead of being silently ignored.
• Bundled config.yml defaults are now applied more consistently.
• Invalid or unsupported language values now warn and always fall back to English.
• options.island.teleportCancelDistance and signs.enabled are now explicitly supported config keys. They were previously read, but were missing in the default config and documentation.

Spawning

• Added dedicated guardian habitat spawn controls for deep-ocean prismarine habitats on islands.
• Fixed guardian habitat spawning when island mob limits are disabled.
• Existing configs are migrated automatically to add the new guardian settings.

Other admin notes

• levelConfig.yml is no longer created on fresh installs. Existing on-disk overrides still work if you already have one.

Full Changelog: v3.3.2...v3.4.1