V6-3
Compatibility
Changes
Tek N Astra V6-3 (Sovereignty) Bug Fixes Fixed items not being enchantable Fixed items with abilities not showing the effects properly Fixed Cloaked One being put in death limbo if too much damage is dealt before the phase switch Fixed possible crash with Electrasteel Gauntlet stacking Fixed possible crash with Glitched shader effects.
Balancing Changes Cloaked One Speed stacking only goes up to 4 now. Cloaked One no longer gets Resistance in second phase. Nerfed Cloaked One's damage 96 > 88 Peppermint Slayer damage reduced 12 > 8.5 Antimatter Railgun damage increased 200 > 225 (base damage exluding buffs and projectile speed) Err.404 now only applies Slowness instead of the cobweb slowness
Misc Changes Gave Cloaked One phase 2 a new theme Optimized Cloaked One's code Fixed Texture inconsistencies with Cloaked One Updated Ascension Dusk's texture Removed AttributeFix as a dependency in favor of UniversalTweaks Gave TNT Charm a recipe Nerfed Nether Scarlet Ore spawnrates (Previously undocumented change.) Removed a bunch of unused audios to decrease file size Re-added Bone Spiders spawning in jungles as it was previously bugged Renamed ‘End Slime’ to ‘Ender Slime’ Added Titanium to the Starborn Cave Added more blocks relating to err.nullTextures Added Heavenly Potion Added brewing recipe for Luck Potions and Heavenly Potions Added Vitality (Potion) Added XP Candy Added an overlay to Frozen Added Sinister Minds discs to the creative menu Added some new achievements.
Weapons Nolarium Katana Genesis Blade Genesis Shortbow Equinox Greatblade Empyreus Spear Sovereign Spear
Armors Empyreus Armor Sovereign Crown
Baubles Hacker Shades
Music Discs Don't Come Back
Skins Voidbound
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:wGoSfqYr:v5DPqXnj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wGoSfqYr:v5DPqXnj"
}

