Tags
Creators
Details
Licensed ARR
Published last year
Updated 3 days ago
All versions
2.3.0
Beta
Gilded Doom 2.3.0 - Empowerment5 months ago 12
Compatibility
Minecraft: Java Edition
1.19.2
Platforms
Fabric
Quilt
Supported environments
Client and server
Required content
Changes
- Book of Documentation added
- There is now lore for Gilded Banishment
- Pending Death gamerule added - dorealbans (disabled by default)
- This will use an actual permaban system along with purgatory
- if the target has a soul, they will be sent to purgatory
- if the target does not have a soul, they will be perma banned.
- Pending Death Requirement’s Nerfed
- Target must be at 3.5 Hearts minimum (7hp) (old was 5 Hearts)
- Removed Pending Purgatory
- Removed Purgatory Amalgam’s sending feature
- Cleansing Tome revamped
- Banishment Removal Enchant Removed
- Purgatory Removal Enchant Removed
- Evading Pending Death adds to your current deathcurse (overflowing gives 7 day bans)
- Rarity Enchant added.
- Short Fuse Enchant added. (Does nothing)
- Removed Ducks from spawning.
- Removed Chipped Amalgam “glitch”
- Purgatory Escape Requirements modified
- 20 Piglin Brutes -> 200 Piglins (Any Type)
- 200 Wither Skeletons -> 200 Skeletons (Any type.)
- 500 Ducks -> 200 Blazes
- Redstone Infused Purgatory Stone Removed
- Demenanite Ore Added
- Purgatory Dust refactored into Demonic Dust
- Crushing purgatory stone with an Iron hammer creates coal
- Book of Gilded Banishment Reworked/Buffed
- Host is now granted Gilded Empowerment
- Gilded Stasis is granted on crit (ignores the cooldown because of how its codded)
- Credits to H3artless_YT for helping me out with that one :3
- The Book is now a pickaxe (because items can’t do on hit bullcrap)
- This caused the Book of Gilded Banishment to do NOTHING on hit >:C
Optional dependencies
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:RUNvX1dD:bl6Xwzka"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RUNvX1dD:bl6Xwzka"
}




