Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated last month
All versions
3.1.0+26.1.2
Release
bonded-forge-3.1.0+26.1.26 months ago 64
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Bonded Changelog
All notable changes to Bonded will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
3.1.0
Added
- Repair benches can now over-repair gear. Extra repair becomes temporary durability, shown as a pink bar on the item.
- Added Scrap, a general repair material for the repair bench. Scrap can appear in chest loot, drop rarely from armored enemies, drop from broken bonded gear, and appear as a byproduct of upgrading gear.
- Tool benches and repair benches can now use matching items from adjacent chests and barrels.
- Gear found in chest loot or carried by monsters can now start with an innate bond level.
- Added config options for innate loot bond.
- Added public addon APIs for registering Bonded gear behavior and reading or changing Bonded item stack state.
- Added advancements for bonding, upgrading, over-repairing, and finding or using Scrap.
Changed
- The old
APIaddon entry point is deprecated. Addons should useBondedApi.
Removed
- Item level-ups no longer automatically repair gear. Use over-repairing instead.
Fixed
- Repair and upgrade addon events now fire from the benches.
Types of changes
Addedfor new features.Changedfor changes in existing functionality.Deprecatedfor soon-to-be removed features.Removedfor now removed features.Fixedfor any bug fixes.Securityin case of vulnerabilities.
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:rTXmXcev:nTAYahzi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rTXmXcev:nTAYahzi"
}

