All versions
1.5.0
Release
WE Selection Overlay 1.5.05 months ago 14
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Changes
1.5.0
Added
- Added client-side block isolation mode in the block inspection screen.
- Added checkbox controls for selecting one or more block types to keep visible.
- Added a reset button above the block list to clear the isolation selection.
- Added selected block groups pinned above all other groups, regardless of sorting mode.
- Added fluid-aware hiding so water, lava, and similar rendered fluids disappear when they are not selected.
- Added bucket icons for fluid entries in the block list and filter menu without changing the stored block ids.
- Added Sodium support for block and fluid isolation rendering.
Changed
- In isolation mode, non-selected blocks inside the WorldEdit selection are hidden visually on the client only.
- In isolation mode, selected blocks remain visible with their normal textures.
- In isolation mode, the internal selection grid is hidden while the outer selection boundary and ruler can remain visible.
- Isolation rendering now works even when normal overlay visibility is disabled.
- Selected blocks are brightened enough to keep their textures readable.
Fixed
- Fixed selection overlay visibility by using the current Fabric world render event path and automatic selection source handling.
- Fixed overlay line flickering caused by an incorrectly short Gizmo lifespan.
- Fixed visual holes on the boundary between hidden blocks and neighboring blocks outside the selection.
- Fixed hidden block entities so block entity renderers disappear with their hidden blocks.
- Fixed fluid rendering paths so liquids do not remain visible after surrounding blocks are hidden.
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:OnBeSnYD:ZoqerjA0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OnBeSnYD:ZoqerjA0"
}

