Experienced Worlds V-2.0.5
Added support for 1.21.4! (this is a separate jar unfortunately)
Reworked the Fairness Checker system.
For some lore, this system went relatively unchanged from the V-1 in the initial V-2 release, so it had some design flaws.
- Fairness checker now can be disabled. If this is disabled the world border center will be set to the world spawn.
- Added 2 different block travelling algorithms, selectable in the config.
- The new default settings work as follows: the initial block is checked, if it is unfair, the checking range is extended and 8 more blocks are checked in a random order until a valid spawn is found.
- Also, the start position of the spawn checker is set to the world spawn-point.
The fairness checker is now much faster and much more reliable as a result of these changes (most worlds have fair spawns by default).
Other
Updated to Persist 1.1.6
Added /experiencedworlds recalculate - Recalculates the border expansions (not the multiplier). This may update the border size. /experiencedworlds forceloadstats now also runs recalculate after wards (there's currently an unknown bug causing this to not work as intended, recalc works fine though).
As a note of why recalculate was added, my server exceeded the storage space which corrupted the experienced worlds data files, re-running forceloadstats should have fixed the problem, but it seems it was broken by the world corruption (and I don't know how). Recalculate is 100% accurate. If you're wondering about how expansions are calculated, they are only calculated when a stat changes and only for that stat. Recalculate calculates the total expansions for all stats which is much more computationally expensive especially as stats grow.
V-2.0.5a:
Removes a fairness checker debug message left in.
Experienced Worlds V-2.0.5
Added support for 1.21.4! (this is a separate jar unfortunately)
Reworked the Fairness Checker system.
For some lore, this system went relatively unchanged from the V-1 in the initial V-2 release, so it had some design flaws.
- Fairness checker now can be disabled. If this is disabled the world border center will be set to the world spawn.
- Added 2 different block travelling algorithms, selectable in the config.
- The new default settings work as follows: the initial block is checked, if it is unfair, the checking range is extended and 8 more blocks are checked in a random order until a valid spawn is found.
- Also, the start position of the spawn checker is set to the world spawn-point.
The fairness checker is now much faster and much more reliable as a result of these changes (most worlds have fair spawns by default).
Other
Updated to Persist 1.1.6
Added /experiencedworlds recalculate - Recalculates the border expansions (not the multiplier). This may update the border size. /experiencedworlds forceloadstats now also runs recalculate after wards (there's currently an unknown bug causing this to not work as intended, recalc works fine though).
As a note of why recalculate was added, my server exceeded the storage space which corrupted the experienced worlds data files, re-running forceloadstats should have fixed the problem, but it seems it was broken by the world corruption (and I don't know how). Recalculate is 100% accurate. If you're wondering about how expansions are calculated, they are only calculated when a stat changes and only for that stat. Recalculate calculates the total expansions for all stats which is much more computationally expensive especially as stats grow.
Experienced Worlds V-2.0.4
Adds commands:
/experiencedworlds forceloadstats - (admin) automatically loads offline player stats files if they have not been accounted for. /experiencedworlds leaderboard - shows the players ranked by expansion power
Patches a 1.21 & 1.21.1 specific crash with the DimensionDataStorage Mixin
Experienced Worlds V-2.0.3
Patches a critical problem with high amounts of statistic data causing the server stats data to become too large to store using an NBT tag. This is encountered mostly when too many blocks have been mined individually. This fix will not impact worlds that have not encountered the issue but may cause some weird issues on worlds that have encountered it. It won't be game breaking or world corrupting though. If this is a significant problem, contact @drathon on discord for information on how to fix.
Patches issues with C2ME Compatibility due to multithreading by forcing thread synchronization in many places.