Update Notes: v1.7.2 → v1.7.3

Nether/End portals no longer send you into the wrong world

Bukkit doesn't pair custom-named worlds through portals just because they follow a challenge_world / challenge_world_nether naming convention - by default it links a portal to any world with a matching Environment, which in practice is usually the server's actual default nether/end (the one tied to level-name in server.properties), not the challenge world's own nether/end.

Left unhandled, this meant: walking through a nether portal in challenge_world silently sent you into the wrong dimension, and walking back brought you into a completely different world - indistinguishable from "the seed changed" even though no reset had happened.

A new PortalLinkListener now explicitly resolves the correct target world for every nether/end portal use, based on the same challenge-world config key the reset logic already uses:

• Nether portals: standard 1:8 coordinate scaling, same as vanilla.
• End portals: entry always lands on the fixed obsidian platform, exit always returns to the challenge world's spawn (vanilla behavior, not coordinate-scaled).

If a portal doesn't yet exist on the other side, one is created automatically (event.setCanCreatePortal(true)), same as vanilla.

Challenge world creation now uses one shared seed

ensureChallengeWorldsExist() (which creates challenge_world + _nether + _the_end on first server start) called WorldCreator without an explicit seed for each of the three worlds, so each dimension rolled its own independent random seed instead of sharing one - same class of bug the /tr reset path already avoided by threading a single seed through. Fixed to draw exactly one seed and reuse it for all three dimensions, matching vanilla (where overworld/nether/end always share the same seed) and matching what /tr reset already did correctly.

Only affects fresh installs / servers where the challenge worlds didn't exist yet - if yours were already created under an older version, this doesn't retroactively fix their seeds; run /tr reset confirm once to regenerate them consistently.