Tags
Creators
Details
mc1.21.8-am1.3.0-b
Compatibility
Required content
Changes

An Abyssium major & beta update. A work in progress. Expect mild & moderate bugs and unfinished features.
πͺ² Known Issues
Noneπ‘ Updating Abyssium?
Although there were no changes with the Abyssium world generation, major changes with the balancing of the mod were introduced. It is recommended that you start a new world!1.3.0-a β 1.3.0-b
Updated Features
Abyssium Upgrade Template
[UPDATED!] Abyssium Upgrade Template now spawns in End City chests with a 6.25% chance.
Abyssium Upgrade Template now has a texture.
1.2.3 β 1.3.0-a
New Features
Abyssium Upgrade Template
[NEW!] This template is similar to the Netherite Upgrade Template, requiring the player to use the Smithing Table and Netherite Equipment to upgrade them to Abyssium Equipment. You can obtain them from End City chests. It has a 6.25% chance of spawning per chest.
Advancements
[NEW!] We added brand-new advancements for Abyssium. Get grinding.
Balancing Changes
Abyssium Equipment (All) π‘-π’
All Abyssium Equipment have been significantly buffed after the introduction of the Abyssium Upgrade template. Although you will now need to obtain an Abyssium Upgrade template, all equipment will now only use one Abyssium ingot to craft.
Abyssium Ingot π’
Changed Abyssium Ingot crafting recipe to only require 4 diamonds and a singular obsidian block.
Abyssium Ore π’
Reduced hardness of the Abyssium Ore. (40 -> 35)
What do the circles mean?
π΄ = Nerf π‘ = Balanced π’ = BuffBug Fixes
Abyssium Ore
Abyssium Ore can now be silk touched and obtained in survival.
It can also now be smelted via the Blast Furnace. You cannot smelt it via the regular Furnace.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| mc1.21.8-am1.3.0-b-sources.jar | Unknown | 235.6 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:nDxAwnzY:vKeGRoNz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nDxAwnzY:vKeGRoNz"
}

