{"id":33547,"date":"2026-06-01T18:41:57","date_gmt":"2026-06-01T15:41:57","guid":{"rendered":"https:\/\/vpesports.com\/minecraft\/mods\/bonfire\/"},"modified":"2026-06-01T18:41:57","modified_gmt":"2026-06-01T15:41:57","slug":"bonfire","status":"publish","type":"mod","link":"https:\/\/vpesports.com\/minecraft\/mods\/bonfire\/","title":{"rendered":"Bonfire – Chunk Claim"},"content":{"rendered":"

![Bonfire Banner](https:\/\/cdn.modrinth.com\/data\/cached_images\/db28a0b6a87970ec70de6059bf798ea096bd9fc7.webp)<\/p>\n

—<\/p>\n

### Claims
\nA **claim** is a group of connected claimed chunks by one player. Unless there is none, a claimed chunk is added to the nearest existing **claim**. Otherwise, a new one is created.<\/p>\n

Players can use **claim rules** to manage how others can interact with chunks in their claim. Scroll down to see a list of all rules, their options, and how to change them. Additionally, specific **players that bypass all claim rules can be added** to a claim, either permanently or only while the claim owner is online.<\/p>\n

\"Command<\/p>\n

—<\/p>\n

### Limits
\nTo prevent players from claiming the whole world, the number of chunks and claims per player is limited based on the playtime statistic. Players get **one chunk for every hour** of playtime they have, and **one claim for every day** of playtime they have, with a maximum of 5 claims. This can be customised in the config.<\/p>\n

—<\/p>\n

### Commands
\nPlayers use the `\/chunk` command to manage their claims. The subcommmands, e.g. to claim chunks, change claim rules and manage players, become visible as soon as the player can use them.<\/p>\n

Using Bonfire’s commands is pretty easy and self-explanatory, even for unexperienced players. Every commands execution tells the player exactly what they just changed and what that means.<\/p>\n

\"Command<\/p>\n

Operators can manage claims of other players using the `\/bonfire` command, which allows them to unclaim chunks, remove claims or change their owner, and more.<\/p>\n

—<\/p>\n

### Claim Rules
\nThey are enforced on the server-side and client-side. Players visually see that they can’t break blocks or interact with entites. For example, the block mining outline vanishes when breaking blocks isn’t possible.
\n| Rule | Options | Description |
\n|:-:|:-:|:-:|
\n| `allowBlockBreak` | `truefalse` | Whether blocks can be destroyed or placed by players, explosions, pistons, water, growing strucutures, etc. |
\n| `allowBlockInteract` | `truefalse` | Whether players can interact with blocks by clicking them or trough physical actions, vibrations, etc. |
\n| `allowEntityInteract` | `truefalseonlyMounts` | Whether players can damage entities, collide with them, get targeted by them, or only mount them. |<\/p>\n

_Players can always interact with mobs they have tamed or own, regardless of allowEntityInteract._<\/p>\n

—<\/p>\n

### BlueMap
\nIf BlueMap is installed on the server, claims are automatically visible on the map. To see Bonfire claim markers live on BlueMap, click the image below to open the demo map.<\/p>\n

<\/p>\n

—<\/p>\n

### Config
\nBonfire’s default configs should work perfectly for most servers and SMPs. However, if you want to adjust some settings, you can do that in the `config.yml` in `plugins\/Bonfire`. There you can change claim limits, the default rules for newly created claims, the design and functionality of BlueMap markers, and much more.<\/p>\n

\nDefault config.yml<\/summary>\n

“`
\n# Default rules for newly created claims
\ndefault-rules:
\n allowBlockBreak: false
\n allowBlockInteract: false
\n allowEntityInteract: false<\/p>\n

# Claiming Limits Configuration
\nlimits:
\n # If set to false, claiming isn’t limited at all
\n enabled: true
\n # Base values every player starts with
\n starting-values:
\n chunks: 0
\n claims: 1
\n # Earning additional chunks and claims based on playtime
\n playtime-earning:
\n enabled: true
\n minutes-per-chunk: 60
\n minutes-per-claim: 1440 # 24 hours
\n # Absolute hard caps (use -1 for no limit)
\n maximum:
\n chunks: -1
\n claims: 5<\/p>\n

# Configs for BlueMap claim markers, if BlueMap is installed
\nbluemap:
\n # If set to false, markers don’t show at all
\n enable-markers: true
\n # Whether claim markers should be listed in BlueMap’s marker menu
\n # This allows players to easily find all claims that exist in a world
\n list-markers: false
\n # $name gets replaced with the name of the claim owner
\n label: Claimed by $name
\n # The accent RGB color of markers
\n accent-color: 255, 221, 161
\n # If the camera is further to this marker than this distance, it will be hidden
\n view-distance: 1000
\n“`<\/p>\n<\/details>\n

—<\/p>\n

!