Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated 2 weeks ago
All versions
4.2.0
Release
Mythic Upgrades 4.2.0 / 1.21(.1)2 years ago 73.3K
Uploaded by
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platforms
Fabric
Quilt
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Ruby armor rework
- Removed Miners Shield effect
- Reason: very few cases of usage in PvP, and almost not usable in PvE.
- Added Spelunker effect, which will outline all ores within certain radius determined by amplifier. Note that every ore will have same outline, so you won't know which ore you are going to mine before you reach it. Modded ores are supported, including our own ones)
- Special thanks to FINGERFEED who allowed me to use some of his code for the effect.
- Ruby armor provides Spelunker VI by default, while ruby potion - Spelunker III.
Topaz items rework
- Removed 3x durability bonus on topaz armor
- Reason: Item Mastery effect is enough for "durability buff".
- Topaz tools now burn entities on hit and autosmelt mined loot (they work like Twilight Forest's Fiery Pickaxe).
- As result, Fire Aspect enchantment is banned on Topaz sword.
32x resolution resourcepack
- Now the mod bundles 32x resourcepack which can be activated in the corresponding menu. This couldn't be possible without skilledtissued and Patrizio's work, big thanks for them!
Smaller technical changes
- Added
#mythicupgrades:incorrect_for_<gem>_tooltag for each gem - Added
#mythicupgrades:spelunker_outlinedtag for blocks that Spelunker effect will outline, default value is#c:ores. - Fixed topaz upgrade duplication recipe, now requiring sandstone block instead of nether bricks
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:ERH7cFoy:taHiJ6AB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ERH7cFoy:taHiJ6AB"
}

