World Dimension Loader 1.1.3

WDL 1.1.3 includes the fixes and improvements introduced throughout the 1.1.x update series.

1.1.3 - Documentation & Release Polish

Improved Documentation

• Added updated English and Japanese beginner-friendly guides directly inside the JAR.

• The full README files can be found inside the JAR under the docs/ folder:

  • docs/WDL_README_JA.txt - Japanese guide
  • docs/WDL_README_EN.txt - English guide

• Reworked the first-time setup tutorial to make WDL easier to configure.

• Added clearer explanations for:

  • External world installation
  • Dimension registration
  • Gate creation
  • /wdl scan
  • Return Gates
  • Return Scrolls
  • Return History
  • Bed Respawn
  • Lazy Loading
  • keep_loaded
  • Creative Dimension Igniter
  • Rarity / Weight
  • Auto-Unload

Config Guidance Improvements

• keep_loaded does not need to be written for normal dimensions.
• allow_bed_respawn does not need to be written for normal dimensions.
• Both settings default to false when omitted.

Only add these settings when you want to enable the feature:

[dimensions.runtime]
keep_loaded = true

[dimensions.bed]
allow_bed_respawn = true

Existing Config Compatibility

Existing WDL configs remain compatible.

You do not need to delete your current config when updating.

However, newly generated configs include newer options and explanatory comments.

If you want a clean copy of the latest config format:

1. Back up config/worlddimensionloader/
2. Temporarily move the existing config folder
3. Start WDL once to generate the latest config files
4. Close the game/server
5. Copy your existing Dimension and Gate definitions into the newly generated files

Do not overwrite the newly generated files with old config files if you want to keep the new comments and examples.

JAR Packaging

The JAR now includes:

• docs/WDL_README_JA.txt - Japanese README
• docs/WDL_README_EN.txt - English README
• Config examples/templates
• Changelog
• License
• Credits

To read the full setup and configuration guide, open the WDL JAR and check the docs/ folder.

No major runtime behavior was changed from the tested 1.1.2 implementation.

1.1.2 - Advanced Runtime & Creative Tools

Per-Dimension keep_loaded

Added an optional advanced runtime setting:

[dimensions.runtime]
keep_loaded = true

When enabled:

• The WDL Dimension is automatically mounted when available.
• It remains loaded even with zero players.
• It is protected from Auto-Unload.
• It is protected from normal capacity eviction.
• It still consumes one max_loaded_dimensions slot.

This is intended for a small number of:

• Hub dimensions
• Base dimensions
• Frequently used worlds
• Worlds that need to remain active

When omitted, keep_loaded defaults to false and normal Lazy Loading behavior is used.

/wdl scan also reevaluates the current keep_loaded configuration.

Creative Dimension Igniter Upgrade

worlddimensionloader:creative_dimension_igniter is now treated as an administration/testing Master Igniter.

It can:

• Activate Gates even when it is not listed in allowed_igniters
• Bypass configured Gate costs
• Be used without item consumption or durability loss

Creative Igniter does not bypass structural or safety validation.

It still requires:

• A valid Gate frame
• A valid Gate definition
• A usable destination
• Normal current-dimension exclusion
• Safe resolution of multiple Gate definitions

If multiple Gate definitions physically match the same frame, WDL will not silently choose one based on config order.

Shutdown Hardening

Added additional protection for server/game shutdown.

When shutdown begins, WDL stops starting new:

• Dimension staging operations
• Mount operations
• Unload operations
• Auto-Unload operations
• keep_loaded mount requests

Pending lifecycle work is safely prevented from being dispatched during world shutdown.

This was added after investigating a rare save/shutdown freeze seen during testing.

The issue could not be consistently reproduced, but additional safeguards were added to reduce shutdown race conditions.

New diagnostic log markers include:

WDL SHUTDOWN BEGIN
WDL SHUTDOWN COMPLETE

1.1.1 - Lazy Dimension Login Resume Fix

Fixed: Player Returned to the Overworld After Restart

Previously, if a player logged out while inside a Lazy-Mounted WDL Dimension and then restarted the game/server, Minecraft could fail to find that Dimension during the initial login process.

This could cause the player to appear in the Overworld using coordinates from the WDL Dimension, sometimes placing the player underground.

WDL now stores the player's previous WDL Dimension and position when they log out.

On the next login:

1. WDL detects the saved Dimension
2. The player is temporarily moved to a safe Overworld holding position if necessary
3. The previous WDL Dimension is Lazy Mounted
4. The player is restored to the original Dimension
5. The original position and orientation are restored

Session Resume

The resume system stores:

• Player UUID
• WDL Dimension ID
• X / Y / Z
• Yaw
• Pitch

Session Resume is player-specific and works with multiplayer.

It does not modify Return History.

If the previous Dimension is:

• Disabled
• Removed from config
• Missing
• Invalid
• Unable to mount

WDL safely falls back to the Overworld instead of repeatedly attempting an invalid restore.

This fix allows WDL to keep the advantages of Lazy Dimension Loading without ejecting players from imported dimensions after restarting the game/server.

Compatibility Notes

• Minecraft: 1.20.1
• Forge: 47.4.22
• Java: 17
• Existing WDL configs remain compatible.
• Config deletion is not required.
• Missing new optional settings use safe default values.
• Lazy Dimension Loading remains the default behavior.
• Existing Gate LIST / ALL selection remains supported.
• Rarity / Weight selection remains supported.
• Return History remains supported.
• Return Scroll remains supported.
• Per-Dimension Bed Respawn remains supported.
• Dimensional Anchor remains supported.
• Auto-Unload remains supported.
• Valkyrien Skies 2.4.11 unload/remount compatibility is preserved.

For the complete setup and configuration documentation, open the WDL JAR and see:

• docs/WDL_README_JA.txt
• docs/WDL_README_EN.txt

Thank you to everyone who reported issues and tested WDL.