Tags
Creators
Details
2.1.1
Compatibility
Changes
2.1.1 - 2026-09-27
Added
-
shape: "depth"— a mask leaf driven by the scene distance. Coverage is 0.5 exactly at the leaf'sdistanceand falls to 0 atdistance + softness/2(the leaf's ownsoftnessis the falloff width, so there is one knob, not two), and 1 nearer than that. Bind a post effect to it and you get depth-of-field masking: sharp up close, blurred past the focus distance, with the sky on the uncovered side unless you compose it away.invertflips it, and adifferenceof two depth leaves is a band around one distance. It has no geometry of its own and needs no per-frame driver, so it is the camera-relative alternative to a sphere leaf bound to the player. See masks. -
"occlusion": falseon an aura leaf — a fill that ignores the depth buffer. Translucent surfaces (stained glass, ice, water) write depth, so a wall of aura behind a glass window was correctly-but-unhelpfully treated as occluded and the fill disappeared. The flag turns the occlusion term off, so the volume shows through glass. It is an aura-only leaf field, defaults to the current behaviour, and costs no extra sampling; being all-or-nothing it also draws the volume over nearer terrain and over anything else in front of it. See masks. -
"occlusion_softness"on an aura leaf — the occlusion width as its own knob. The occlusion ramp used to be denominated in the leaf's ownsoftness, so a deliberately soft silhouette also decided how softly the fill was hidden by terrain, and a blocky hillside (a 1-block staircase) turned into a stack of ~45 bands along the silhouette. The new field is that width in world blocks: 0.5 where the volume's entry sits on the surface, falling to 0 or 1 over the given distance. Absent, the ramp keeps followingsoftnessexactly as before, animation included, so no existing mask changes. A sub-block value gives a crisp silhouette that follows the terrain instead of a 45-band fade. See masks. -
order- the compositing order of screen effects inside a layer. Screen effects accept anorderparam next toscreen_layer: a float, lower runs earlier, default0, and effects that leave it alone keep the order they were started in, so no existing pack changes.screen_layerstays the outer, semantic axis (which part of the frame the pass belongs to) andorderonly sequences the effects that layer already selected; being fractional,10.5slots an effect between two at10and11. It is an ordinary param, so the datapack, the command param-map,setParamand keyframes all reach it, and the wire format, UBO andPROTOCOL_VERSIONare untouched. See screen effects. -
A plugin can declare its field's gradient bound.
VFXAPI.registerMaskShapeGlsl(id, plugin, lipschitz)is a new overload: the plugin field must be a conservative distance (|grad d| <= 1), and a field that is perturbed (noise, a biased blend) can no longer stay silent about it — either scale the value down or declare a true upper bound, which the aura march and the envelope then respect. A variant of several plugins compiles against the largest declared bound. The mask guide now states the rule next to the plugin contract. Additive: an existing registration compiles exactly as before. See masks and the API.
Fixed
-
volume: "aura"on a GLSL-plugin mask leaf: a smooth soft edge instead of a banded ramp with a hard cliff. A wide, soft plugin volume rendered its silhouette in visible steps and dropped from ~50% coverage straight to zero within a fraction of a degree. The plugin aura estimated the ray's deep point as the sampled minimum of its march, so the edge resolved into sample-sized steps, and any entered ray scored at least 0.5 while a miss scored exactly zero — a built-in ~0.5 jump at the silhouette. Both are gone by construction: the deep point is now a Lipschitz cone-envelope of the samples already taken (continuous in screen space, exact for creasedmax/minfields, never thinner than the truth), a ray that misses the volume fades over the leaf's ownsoftnessinstead of vanishing, and the entry distance is bracketed by false-position, which also dequantises the occlusion ramp. The edge lands in the same place, the interior still saturates to full coverage, and the cost is unchanged - no extra SDF evaluations. Standing inside the volume keeps filling the view, growing towards full coverage with depth. See masks. -
The aura march grades a ray by its deepest penetration, not its first exit. Entry and exit were two marches and the second stopped at the first
d > 0, so on a wall with a bump the solid mass behind the bump was never sampled and the silhouette reported the bump's shallow depth - the coverage dipped across it (the reported arch at the bottom of a wall). One pooled loop over the same 40 + 16 steps now runs to a real termination: the cone bound stays global over the whole ray (so the mass behind a bump is what gets measured), the first entry still drives the occlusion ramp and the last exit brackets the horizon fade. Saturation stays a sample certificate and budget exhaustion deliberately does not saturate - a long shallow corridor would light up. An additive anti-crawl step keeps a grazing approach or the gap behind a bump from eating the budget; it is bounded, which is why a ray that never enters can now reach at most 0.6 rather than 0.5 of coverage. Measured: the bump profile goes from1.00 ×9, 0.58 0.70 0.80 0.85 0.80 0.70 0.58, 1.00 ×9to a flat1.00, the fixture's flat wings drop from 22.0 to 8.9 SDF calls per ray, and a receding ray terminates in 5 instead of burning all 40. See masks. -
The occlusion ramp is kept at least 48 pixels wide on screen. A depth-driven edge inherits the depth buffer's granularity: blocky terrain steps by a block at every block edge, and at a grazing view of the ground those steps land less than a pixel apart, so the mask's silhouette aliased into a comb. The ramp is widened with the per-pixel depth slope wherever the depth moves fast, capped at 4x the authored width so a depth discontinuity (a cliff edge) cannot smear the edge; the authored
occlusion_softnessstays the floor, so a near face-on occluder is unchanged. Measured at 2.8 blocks per pixel: the ramp runs 44.8 → 134.4 blocks and the coverage step per terrain block edge falls from 0.0223 to 0.0074 - below what an 8-bit target can show. No uniform, no UBO/wire change, no new knob. See masks.
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:HBhB8m4j:zmv271zx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HBhB8m4j:zmv271zx"
}

