Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated 23 hours ago
All versions
26.1.3+neoforge
Release
[NeoForge 26.1.X] 26.1.3yesterday 31
Compatibility
Minecraft: Java Edition
26.1.x
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
26.1.3
- fix: face culling of snowy vertical slabs
26.1.2
- fix: snow destroy overlay missing or misplaced
- fix: destroy overlay mixin on 26.1
- fix: z-fighting on the sides of snowy fence gates
- feat: wind charges blow snow off leaves
- fix: render destroy overlay on snow-covered blocks
26.1.0
- feat: higher step height on snow(close #450)
- fix: incorrect occlusion shapes (close #491)
- feat: convert blocks below non-rain-blocking blocks to snowy forms
- fix: world gen not generating snow covered blocks
- feat: snowy leaves (close #355)
- fix: DUMMY block entity log spam (close #482)
- build: bump NeoForge to 26.1.2.112 and Forgified Fabric API to 0.155.3
- feat: now you can define snowy model variants in the
srm_variantsfolder rather than .mcmeta files
26.0.4
- build: add missing dependencies jarjar 2
- build: add missing dependencies jarjar
26.0.3
- fix: 8-layer snow block shade brightness
- fix(neoforge): wrap diagonal snow models
- fix
- Merge pull request #484 from Snownee/feature/26.1-neoforge
- build(neoforge): embed required Forgified Fabric modules
- build: fix CF mod id
- fix(neoforge): update platform and Kiwi registration
- fix(neoforge): resolve compile api drift
- build(neoforge): remove stale fabric resource expansion
- fix(neoforge): initialize client model hooks
- fix(neoforge): restore harvest mixin
- build(neoforge): migrate common events
- build(neoforge): update pack format
- build(neoforge): migrate access transformers
- build(neoforge): migrate mod metadata
- build(neoforge): migrate Gradle to NeoForge 26.1
- Update build.gradle for 26.1-fabric
- chore: update dependencies
26.0.2
- fix: snowy fence/wall connection
- fix: unlimited max snow layers is not working properly
Optional dependencies
Any compatible version
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:iJNje1E8:43V2J2ab"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iJNje1E8:43V2J2ab"
}

