Tags
Creators
Details
Licensed ARR
Published 4 years ago
Updated 3 months ago
All versions
1.1.9.4
Beta
CreRaces - 1.20.1 - 1.1.9.4last year 378
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Beta 1.1.9.4: (Note: Due to the results of the latest poll, versions of CreRaces Classic for 1.19.2/4 and 1.20.4/6 will be marked for Legacy with a warning in-game to swap project)
- Light Fairy Orb placement logic fixed
- Pixie Toxic Surprise now won't activate on raceteam members
- Optimized and rewrote the Pixie Toxic Surprise to is now be placed at the feet of the user upon activation.
- Rewrote the Dark Fairies & Autumn Fairies A1 logic
- Fix a bug where the Pixie couldn't dry their wins on Paper (yikes)
- You now actually get the new guide book when using the Handbook menu button
- Adjusted the Fairy/Pixie bonuses from Sugar ("Speed" and "Jump Boost" instead of just "Jump Boost")
- The Sun Protection potion can now be brewed using a sunflower
- Adjusted the Dark Fairies passive (helmets no longer block Weakness)
- The Light Fairies passive now also checks for light level (More than 7 light value blocks Weakness)
- The RaceGUI now directs directly to the Pixie instead of a sub-menu
- The Undead is now immune to the Hunger, Regeneration, Instant Health and Poison effects
- The (Legacy) Spikes now have a crafting recipe
- A general metric-ton of optimization and QoL code fixes
- Gave the Pixie another ability to replace Snatch if Experimental Mode is disabled called Disarm
- The Pixie's A3 now also properly goes on cooldown when used
- The Pixie's A1 dart now also has 0.1 piercing
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:ekeYhQOi:7dntVV2M"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ekeYhQOi:7dntVV2M"
}

