Tags
Creators
Details
2.1.1
Compatibility
Required content
Changes
WorldEditDisplay v2.1.1 Release Notes
Summary
Release adding per-shape see-through settings, a rendering rebase task, and fixing a rendering issue with polyhedron selections.
Note: This release is not fully backward-compatible for configuration.
renderer.global.see_throughhas been removed. Please update yourconfig.ymlbefore upgrading.
Changelog
-
fix(renderer): Polyhedron vertex visibility
- Fixed a bug where polyhedron vertex markers were not displayed when only vertex (
p) events had been received and faces (poly) had not yet been reported by WorldEdit. Vertex markers are now rendered immediately as vertex events arrive.
- Fixed a bug where polyhedron vertex markers were not displayed when only vertex (
-
change(renderer): Per-shape
see_throughconfiguration- Removed the global
renderer.global.see_throughsetting. - Added individual
see_throughsettings for each shape type (cuboid, cylinder, ellipsoid, polygon, polyhedron). - Existing configurations using
renderer.global.see_throughmust be updated to the new per-shape format.
- Removed the global
-
feat(renderer): Rendering rebase task
- Added a periodic rebase task to keep TextDisplay entities within view range as players move.
-
perf(renderer): Reduce ellipsoid grid line count
- Changed
calculateGridStepformula fromradius / Ntoceil(2 * radius / N). radius_grid_divisionnow controls the approximate number of grid lines per axis plane rather than being a divisor of the radius.- For mid-sized ellipsoids (e.g. radius 10), grid lines per plane drop from ~20 to ~5, reducing total line entity count by up to 75%.
- Changed
-
chore(deps): Bumped TextDisplayShape dependency to 1.3.0.
Notes
- No public API changes.
- Configuration is not fully backward-compatible:
renderer.global.see_throughhas been replaced with per-shape settings.
Full Changelog: https://github.com/TWME-TW/WorldEditDisplay/compare/2.1.0...2.1.1
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:eVvfozdY:OSnubcfu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eVvfozdY:OSnubcfu"
}

