Bonfire - Chunk Claim
An intuitive chunk claim plugin that focuses on the user experience, including claim limits adapting to your playtime and BlueMap markers.
Описание
Claims
A 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.
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.
Commands
Players 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.
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. Most commands also have dialogs to guide inexperienced players trough the process.
Operators can manage claims of other players using the experimental /bonfire command, which allows them to unclaim chunks, remove claims, change their owner, and more.
Claim Rules
They are enforced on both the server and the client. Players are given visual feedback when their actions are restricted on a claim, for example, when block outlines or attack indicator vanish for them.
| Rules | always | interactOnly | never |
|---|---|---|---|
blockActions | Blocks can be broken, placed, and fully interacted with. | Blocks can be interacted with, but can't be placed or broken. | Blocks can't be placed, broken, or interacted with. |
entityActions | Entities can be interacted with and collided with, as well as damaged. | Entities can be interacted with, but can't be damaged, leashed, or collided with. | Entities belonging to the claim can't be interacted with. |
Mobs that players own, or that don't belong to the claim, are unaffected by the entity actions rule.
Maps
If BlueMap or squaremap are installed on the server, claims are automatically visible on the map and their config options dynamically appear in Bonfire's config.yml. Clicking the images below opens the demo map.
Limits
To 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.
Limits can be adjusted per player with the /bonfire overrideLimits command, which opens a dialog for granting additional chunks and claims. You can also use the dynamic permission bonfire.playtime_multiplier.<percent>. For example, bonfire.playtime_multiplier.200 doubles a player's playtime earnings.
Config
Bonfire'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 map markers, and much more.
Default config.yml
# Default rules for newly created claims
default-rules:
blockActions: never
entityActions: interactOnly
# Claiming Limits Configs
limits:
# If set to false, claiming isn't limited at all
enabled: true
# Base values every player starts with
starting-values:
chunks: 0
claims: 1
# Earning additional chunks and claims based on playtime
playtime-earning:
enabled: true
minutes-per-chunk: 60
minutes-per-claim: 1440 # 24 hours
# Absolute hard caps (use -1 for no limit)
maximum:
chunks: -1
claims: 5
# Configs for the /chunk escape command
escaping:
# Whether the command is visible and can be used
enabled: true
# How many seconds a player has to wait between uses
cooldown: 1800
# Configs for BlueMap claim markers, if BlueMap is installed
bluemap:
# If set to false, markers don't show at all
enable-markers: true
# Whether claim markers should be listed in BlueMap's marker menu
# This allows players to easily find all claims that exist in a world
list-markers: false
# $name gets replaced with the name of the claim owner
label: Claimed by $name
# The accent RGB color of markers
accent-color: 255, 221, 161
# If the camera is further to this marker than this distance, it will be hidden
view-distance: 1000
# Configs for squaremap claim markers, if squaremap is installed
squaremap:
# If set to false, the Bonfire Claims layer won't be shown
enable-markers: true
# Layer name displayed in squaremap's layer control
layer-label: Bonfire Claims
# $name gets replaced with the name of the claim owner
label: Claimed by $name
# Whether the layer should be hidden when the map is first opened
default-hidden: false
# RGB colors and opacity for claim borders and fill
stroke-color: 255, 221, 161
stroke-opacity: 0.8
stroke-weight: 2
fill-color: 255, 221, 161
fill-opacity: 0.15
# Ordering relative to other squaremap layers
layer-priority: 50
z-index: 50
# Use /bonfire reloadConfig to apply your changes without restarting
Галерея
