1.5.0
Compatibility
Changes
BondCraft Fabric v1.5.0
This update introduces BondCraft's first Fusion Evolution, 2 new monsters, new combat mechanics, expanded language support, and various gameplay improvements.
✨ Added
2 New Monsters
- Nightgrizz
- Arcane Knight: Noel
Fusion Evolution
Added BondCraft's first Fusion Evolution.
Combine:
- Lost Boy: Noel
- Arcane Armament: Aegis
- Arcane Armament: Gladius
to evolve into:
Arcane Knight: Noel
Fusion Evolution is a new evolution method that requires specific bonded monsters to meet the required conditions.
New Combat Mechanics
Arcane Knight: Noel introduces:
- Sword attacks
- Shield Bash
- Guard behavior
- Defensive support abilities
Nightgrizz
Added Nightgrizz, a large nocturnal beast that appears in the desert at night.
When bonded, Nightgrizz can support exploration by granting its owner Night Vision in dark areas.
🌐 Localization
BondCraft now supports 5 languages:
- Japanese
- English
- Simplified Chinese
- Russian
- Brazilian Portuguese
🛠 Improvements
- Added Party HUD visibility toggle
- Added configurable Party HUD key binding
- Improved Party HUD controls
- Improved combat AI
- Improved passive ability handling
- Improved status effect handling
- Improved localization consistency
- Improved Party and Bench data handling
- Improved Fusion Evolution handling
- Various bug fixes and internal cleanup
⚠ Notes
- Balance and systems may continue to change.
- Fusion Evolution may receive further improvements in future updates.
- World backup is recommended before updating.
❤️ Thank You!
Thank you for playing and supporting BondCraft!
More monsters, evolutions, and new possibilities are coming in future updates.
Claim the allies you have yet to meet.
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:vcq7lFVC:J6PSWOyz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vcq7lFVC:J6PSWOyz"
}

