Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated last month
All versions
2.1
Release
B'things 2.1last month 28
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Changes
- Compatibility with Enchantment Descriptions
- Added the new Ghostly Armor set.
- Added custom translucent armor rendering, giving the set a ghost-like appearance.
- Added a passive ability to Ghostly Armor:
- Each armor piece gives a chance to completely ignore incoming damage.
- The full set grants a total 50% chance to negate damage.
- This passive works on any living entity wearing the armor, not only players.
- Added the Ghost Flight ability.
- When wearing the full Ghostly Armor set, players can press the Ghost Flight keybind to toggle flight on or off.
- Ghost Flight has no duration limit while the full set remains equipped.
- Removing any piece of the set automatically disables Ghost Flight.
- Fall damage is negated while Ghost Flight is active and after it is disabled.
- Added a new Ghost Flight keybind.
- Updated the Thingsopedia Gear section with pagination.
- Added a new Thingsopedia entry for Ghostly Armor.
- Added Eye of Avarice.
- Added Curios support for Eye of Avarice.
- Added Avarice Sight keybind.
- Eye of Avarice can reveal selected blocks nearby through walls.
- Baron of Bones now drops Eye of Avarice.
Fixes
- Fixed Emperor Penguin failing to spawn in some large modpacks.
- Fixed EMF warnings related to custom armor model rendering.
- Optimized Jaguar, Black Jaguar, Albino Jaguar, and White Album armor models by caching them properly.
- Improved compatibility with heavily modded environments.
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:RPiWan5z:1MGYRzq6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RPiWan5z:1MGYRzq6"
}



