Tags
Creators
Details
All versions
v1.5.1
Release
[YM] VILC v1.5.1 - public release3 days ago 87
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Required content
Unavailable version
Unavailable version
Unavailable version
Changes
Version 1.5.1
Changed
- Updated to Veil 4.5.2 (minimum required version)
- Shaderpack detection now uses the official Iris API
- License metadata set to the YesMenn Custom License 1.0
- Built against Sodium 0.8.13 (minimum stays 0.8.12-beta.1); Iris 1.8.14-beta.1 is still the latest for 1.21.1
- Addons can register a combined config screen (ConfigScreenBridge.registerCombinedScreen); the mod list entry and config key then open it
- Removed the now unused resolved-light texture (one less full-screen RGBA16F texture)
- Removed the unused bundled glsl-transformer library
- Corrected mod descriptions: VILC renders Veil point and area lights and no longer runs Veil shader programs through Iris
Fixed
- Fixed a thin dark ring around the player at 48 blocks: surface-normal derivatives were evaluated in non-uniform control flow at the detailed-normals range boundary
- Saturated light colors are much stronger with shaderpacks: the shaderpack pass now composites from a scene copy like the vanilla pass instead of GL blending into the 8-bit target, which clamped the light term and capped colored light at 2x the scene color
- Fixed the full-screen magenta checkerboard and magenta first-person hand with Iris installed: Veil's own deferred light pass is skipped while Veil keeps its albedo buffer disabled under Iris; VILC renders the lights instead
- Guarded voxel-occlusion light checks against Veil light handles without light data
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:MJEsr0LL:dyvORApT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MJEsr0LL:dyvORApT"
}![[YM!] Veil Iris Lights Compat (VILC)](https://cdn.modrinth.com/data/MJEsr0LL/3eb9b59ab6cdee0233e70f062cc9f3bc44b40d35_96.webp)

