Tags
Creators
Details
1.6
Compatibility
Changes
After 9 months of conceptualization, gathering feedback, development, and testing, the first full release of Bonfire is being published today. It comes with many fundamental yet definitive changes that have been in the works for a long time.
- Claim Escaping is now possible using the
/chunk escapecommand, which solves the problem of players getting stuck in claims where blocks can't be destroyed. To prevent abuse, it has a configurable cooldown. - Nether Claims are now split into separate ground and roof chunks, allowing players on the ground to travel beneath a claimed gold farm on the roof.
- Origin tagging has been refined, allowing mobs on claims to attack each other without malicious players being able to exploit it. It is now possible, for example, to zombify your villagers on your own claim.
- Dialogs are now implemented across all commands, taking the user experience to a whole new level. Inexperienced players can use intuitive menu flows, while experts can continue to use commands exclusively.
- Squaremap markers are now supported and display claims. Shoutout to PawelWielga for implementing it and creating a pull request on GitHub.
- Claim rules have been reworked into
blockActionsandentityActions, with the optionsalways,interactOnly, andnever. The dream of a perfectly protected claim that never impacts the owner is now reality. - Limit overrides are now possible using the
/bonfire overrideLimitscommand, and allow you to grant additional chunks and claims to players. A dynamic playtime multiplier permission has been implemented as well.
In addition to that, many smaller issues and bugs have been resolved.
- Blocks can no longer be destroyed by interacting with their supporting blocks, for example when opening a trapdoor attached to a lantern.
- Players can now throw wind charges to interact with blocks on their claim.
- Bonfire no longer takes exclusive control of game modes and attributes, and now restores a player's previous values instead of resetting them.
- The
config.ymlis now updated automatically whenever new options are added. Options for map plugins only appear if the matching plugin is installed. - Claim lookups and player refreshes are now significantly faster.
- Creative players no longer need OP to bypass claim restrictions.
- It is no longer possible to bring mobs onto a claim using leashes or vehicles.
- Item frames, paintings, and cushions are now handled as blocks rule-wise.
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:iTQ6HFG3:ynHCj0Ou"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iTQ6HFG3:ynHCj0Ou"
}

