Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published last year
Updated 4 days ago
All versions
0.5.0-alpha.4-neoforge+26.3
Alpha
Vesper's Compatibility Compendium 0.5.0-alpha.4 Neoforge 26.34 days ago 14
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Client-side
Server-side
Client and server
Required content
Any compatible version
Any compatible version
Changes
- Add support for 26.3
- Add a tweak to Wakes' Splash Clouds effect to make them "glow" just like the wakes
- The "glow" is really just a color shift to better match the wakes, improvements coming (I hope)
- Better Effectual glowing player droplet effect
- This is now considered a tweak, is on all versions, and is on by default again
- Switch config to Forge Config API Port
- The way I eventually want to set up the config wouldn't have been possible using YACL, the Forge API port was the best option I could find for an existing config API
- Re-add support for 26.1.2
- Enabled applicable fixes on NeoForge >=26.1.2
- Properly version some fixes and remove unneeded ones
- List of fixes and versions will be updated at the end of the update cycle
- Glowing Wakes is now considered a tweak of Wakes on all versions
- Use MixinConstraints to fully prevent the running of non-applicable mixins
- Update for Effectual 1.4.2
- Remove info about needing to enable Effectual's breath effect as it is now on by default
Alpha Version Changes:
- Note that Wakes Reforged settings are in the same menu as Fabric Wakes
- Improve config
- Including tooltip descriptions (#8)
- Feel free to open pull requests with translations
- Add a screen for 1.20.1 config using Forge Config Screens (#9)
- This isn't a perfect solution, but it sure is the easiest. Given that I expect 1.20.1 to be the first or second dropped version I don't feel its worth the effort to write a custom screen system for this.
- This is a switch from alpha.3 which used Configured, I couldn't get it to work on Fabric and FCS worked with zero work on my part, please let me know if you encounter issues with it as it has been archived and may be out of date
We return to feature additions in the next update
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| vcc-0.5.0-alpha.4-neoforge+26.3-sources.jar | Unknown | 90.51 KiB |
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:TwGzXNhG:3NtwPxqD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TwGzXNhG:3NtwPxqD"
}

