Links
Creators
Details
Licensed GPL-3.0-only
Published last year
Updated last month
All versions
1.4.1
Release
wakes-1.21.1-NeoForge-1.4.1.jarlast month 29.8K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Shader support improvements:
- Fixed wakes clipping through the water surface when using shaders that animate water. Wakes are now lifted by the exact wave height of the loaded shader pack, read from the pack itself along with your in-game shader settings, instead of a one-size-fits-all guess
- Supported out of the box: Complementary (Reimagined, Unbound, Spooklementary, Voxlementary), Rethinking Voxels, BSL and BSL Classic, AstraLex, Insanity, Pastel, Photon, Hysteria, Sildur's Vibrant Shaders and Kappa. Packs that do not animate water are detected too and get no offset at all
- Added "Extra shader water offset" for the rare pack whose water animation cannot be detected automatically
- Fixed wake lighting under shaders. Wakes were being dimmed by a flat 50% that had nothing to do with actual light levels, which fought against the lighting the shader pack was already applying. Wakes are now lit entirely by the shader pack, so they respond properly to time of day, shadows and nearby light sources
Fixes:
- Fixed dedicated servers failing to start when Wakes was left in the server's mods folder.
- Fixed wake trails breaking up into hard square blocks when a lot of wakes were made at once. Ripples now spread smoothly across block borders instead of stopping at them, and wakes fade out gradually instead of whole blocks popping out of existence
- Wakes no longer flicker between neighbouring blocks of different brightness as they fade
Additions:
- Paddling with a shovel while standing on a floating structure now makes a wake (needs Sable, 1.21.1 only)
Optional dependencies
Any compatible version
Any compatible version
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:E0SdeAoH:Z3Ic8n5N"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:E0SdeAoH:Z3Ic8n5N"
}

