2.0.5a
Compatibility
Required content
Changes
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.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| experiencedworlds-2.0.5a+1.21.4+fabric-sources.jar | Unknown | 134.29 KiB |
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:OlqO2jmh:69i46Dsz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OlqO2jmh:69i46Dsz"
}

