WDL 1.4.0

Important Upgrade Notes

Back up your Minecraft world, WDL config files, and WDL_custom_dimensions folder before updating.

WDL 1.4.0 changes how physical Dimension IDs and runtime world storage are handled.

Because of these changes, world data created with older WDL versions may not always be usable in exactly the same way after updating, especially if runtime folders were manually moved, renamed, partially deleted, or copied between saves.

Do not manually rename or move WDL runtime folders unless you fully understand the new storage layout.

It is also recommended to:

1. Back up your existing WDL config files.
2. Allow WDL 1.4.0 to regenerate fresh config files.
3. Reapply your custom settings to the newly generated files.

The Config format remains largely compatible, but regenerating the files ensures that the latest comments, examples, and documentation are available.

Fixed Dimension IDs for Non-Reset Worlds

Dimensions using:

reset_on_empty = false

now use a fixed physical Dimension ID for new/pristine runtimes.

Example:

wdl:dragons

Storage:

dimensions/wdl/dragons/

The physical ID remains stable across game restarts.

This improves compatibility with mods that need to reference a specific Dimension ID directly, such as Dimension Separator.

Reset Worlds Continue to Use Timestamp Generations

Dimensions using:

reset_on_empty = true

continue to use timestamp-based physical generations.

Example:

wdl:dragons/20260828013951

Storage:

dimensions/wdl/dragons/20260828013951/

A new timestamp generation is created when an actual Reset/Rotation occurs.

Unified WDL Runtime Storage

Runtime world storage is now unified under:

dimensions/wdl/

New Reset-OFF worlds:

dimensions/wdl/<id>/

Reset-enabled worlds:

dimensions/wdl/<id>/<timestamp>/

This replaces the mixed runtime storage layouts used during earlier implementations.

Existing 1.3.0 Worlds

Existing 1.3.0 timestamp-based runtimes are not automatically converted back to fixed IDs.

For example:

wdl:dragons/20260827123456

may continue to use that existing physical authority even if Reset is later disabled.

WDL 1.4.0 intentionally does not perform an automatic timestamp-to-fixed reverse migration because other mods, player data, SavedData, Dimension references, and caches may still reference the existing physical Dimension.

This means upgrading does not guarantee that every older runtime will be physically reorganized into the new layout.

Always keep a backup before upgrading.

Safer Runtime Authority Detection

WDL now performs stricter checks before deciding which physical world belongs to a configured Dimension.

If multiple possible runtime worlds exist and WDL cannot safely determine the correct one, it now fails closed instead of guessing.

In ambiguous situations WDL will avoid:

• creating another generation;
• deleting existing runtime data;
• moving world folders;
• performing unsafe garbage collection;
• silently selecting the wrong physical Dimension.

This significantly reduces the risk of world-data loss during unusual upgrade or recovery situations.

Reset and Recovery Safety Improvements

The Reset transaction system has received additional safety checks.

Improvements include:

• safer destructive-operation authority handling;
• improved Journal and Rotation Receipt validation;
• protection against conflicting or malformed recovery data;
• safer handling when SavedData is missing;
• improved restart recovery;
• protection against cancelling an already-authorized destructive Reset transaction through a later Config change;
• safer handling of stale completed operations.

WDL now prefers stopping safely over guessing when recovery authority is unclear.

Live Reset Configuration Changes

Changing an existing Dimension from:

reset_on_empty = false

to:

reset_on_empty = true

while the game is running is now handled more safely.

The existing fixed world is not immediately renamed or destroyed.

Instead, it remains usable until an actual Reset occurs.

At the first real Reset, WDL can safely transition from:

wdl:<id>

to:

wdl:<id>/<timestamp>

Improved Restart Recovery

Reset operations can now recover more reliably across a full Minecraft restart.

This includes situations where the game is closed while a Dimension is:

• waiting for its Reset countdown;
• in GRACE;
• waiting for active timed sessions;
• waiting for restart-safe Resident Reset handling.

WDL restores the saved Reset state after startup and continues the transaction only when it is safe to do so.

Startup Cleanup Safety

Startup garbage collection has been hardened for the new fixed/timestamp storage layout.

WDL avoids deleting a fixed world root as if it were an old timestamp generation.

Only generations that can be safely identified as retired are eligible for cleanup.

Reset Log Improvements

Reset waiting logs have been redesigned to prevent excessive log spam.

Normal non-terminal waiting now uses:

WDL RESET DEFERRED

at INFO level.

Examples include:

timed_session_present
resident_restart_required
resident_restart_required_same_process_nonlive

Repeated identical reasons are deduplicated by Dimension, Reset operation, and Reset phase.

Terminal fail-closed situations continue to use:

WDL RESET BLOCKED

at ERROR level.

This keeps important failure diagnostics visible while preventing thousands of repetitive waiting messages.

Bug Fixes and Stability Improvements

Fixed or improved several Reset/runtime edge cases, including:

• excessive WDL RESET BLOCKED INFO log spam;
• repeated alternating Reset wait reasons;
• Reset recovery after a complete game restart;
• re-entry after Reset/Rotation;
• stale Rotation Receipt cleanup;
• Resident Reset restart handling;
• fixed-world to timestamp-generation transitions;
• unsafe ambiguity handling when multiple physical runtimes exist;
• incorrect cleanup risks around the new fixed storage root;
• Reset state handling when Config changes during gameplay;
• timed-session interaction with pending Reset operations;
• post-restart generation Rotation and re-entry stability.

Compatibility

WDL continues to treat Valkyrien Skies and Distant Horizons as optional integrations.

They are not required to use WDL.

Additional compatibility and safety work has been retained for environments where these mods are installed.

Notes

There are no new required Config options in WDL 1.4.0.

However, because this release contains major runtime-storage and Reset-system changes, backing up your worlds and regenerating the WDL config files before updating is strongly recommended.