Tags
Creators
Details
All versions
6.10.0
Release
tetra 6.10.0last year 1,524
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Changes:
- reworked and re-added destabilization effects
- added advancements for enchanting and destabilization
- buffed efficiency gain from quality improvement
- changed visuals for the bleeding effect
- made thrown modular items glow after not being picked up (and chunk loaded) for an hour
- increased magic capacity use for enchantments (from minCost + maxCost / 2 to minCost + maxCost)
- tweaked tool icons to make prying more apparent
Fixes:
- fixed holosphere animation issues
- fixed some incorrect localization entries
- prevented players from placing holospheres with faulty nbt (and fixed crash caused by looking at holospheres with faulty nbt)
- fixed text color issues in some tooltips
Technical changes:
- holosphere entries are now datadriven (or resource-driven rather)
- added "tetra:on_use" item effect trigger
- added random and count fields to find blocks item effect outcome
- fixed position vector provider origin field not being optional
- Added spawn entity item effect outcome
- added crafting effect outcome for spawning blocks
- added spawn entity crafting effect outcome
- added lightning strike crafting effect outcome
- added lingering potion cloud crafting effect outcome
- added explosion crafting effect outcome
- added spawn_sculk crafting effect outcome
- added active field to crafting effects, can be set to false to stop the effect from triggering directly
- added 'references' field to apply_list crafting effect outcomes
- added isRiding field to item effect entity condition
- added "bookEnchantmentSchematic" feature flag, can be disabled in the config to prevent tetra table book enchanting
- added clamp stat getter
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:YP9DjOvN:kqKKpFGP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YP9DjOvN:kqKKpFGP"
}

