Links
Tags
Creators
Details
0.5.0-alpha.2-fabric+26.2
Compatibility
Required content
Changes
- 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
- I'm still feeling out what the most popular versions are (across all my mods), so this may go away in the future if it doesn't get utilized
- 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
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
1.20.1 still cant open the config in game, long story short I forgot I needed to make a screen as Forge Config Port API doesn't ship one on that version. I'm working on one, and it will hopefully be included in alpha.3
I will add 26.3 during this update cycle if enough features have the required mods updated
Optional dependencies
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| vcc-0.5.0-alpha.2-fabric+26.2-sources.jar | Unknown | 90.57 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:CGxcDHHQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TwGzXNhG:CGxcDHHQ"
}

