This article is a stub.
A base is the main territory of a faction and constitutes all of their tangible assets (i.e., spawners, custom blocks, and loot). Bases are often protected by multiple layers of watered walls to lengthen or even prevent certain forms of raiding.
Claiming land
A claim is a 16×256×16 piece of land aligned to chunk coordinates. The terms chunk, claim, and land are often used interchangeably. A faction member can claim land for their faction by running /f claim, and using /f map to analyze nearby claims. Power determines the amount of chunks a faction can claim (run /f info to view power of your faction). It is possible for a faction to be in a state where they have more land than power. In this state, the faction remains vulnerable to overclaiming—a scenario where any outsider can seize land from the faction.
Claim types
/f map, showing the core claim (yellow), base claims (light green), and raid claims (dark green) of a faction.Land claims are of four types—core, base, raid, and premium. A core claim is the first piece of land claimed by the faction, and determines location of the base. A core claim cannot be unclaimed without unclaiming all claims (i.e., by running /f unclaimall). Base claims are land that is connected to the core claim or other base claims. Raid claims are land disconnected from the base claim, and appear dark-green in /f map to distinguish them from base claims (which appear light-green). A raid claim is automatically unclaimed after 8 hours. This is unlike core and base claims which are persistent.
Premium claims are land claimed within a distance of ≤ 3 chunks from the warzones in overworld or the nether. Unlike other kinds of claims, premium claims are a weekly rental and are priced relative to their distance from the warzone. Failure to pay timely rent will automatically unclaim the land, immediately leaving the claim unprotected and up for grab by any outside faction. Run /f showpremiumclaims to view due rent.
| Distance | Price |
|---|---|
| 1 chunk (i.e., connected to warzone) | $1,500,000 + ($500,000 weekly increment) |
| 2 chunks | $1,125,000 + ($375,000 weekly increment) |
| 3 chunks | $750,000 + ($250,000 weekly increment) |
Claim transformation
The type of a claim is largely determined by its connectivity (except for a core claim). When a base claim disconnects from its core claim, it is immediately transformed into a raid claim. This can happen from unclaiming land (i.e., by running /f unclaim). Likewise, a raid claim turns into a base claim upon being connected to another base claim. This makes raid and base claims volatile. On the contrary, core and premium claims remain non-transformable.
Permission labels
A label is a collection of terrain permissions for players, member roles, and other friendly factions. Labels can be assigned to specific claims. Labels can be configured using the /f label command.
Labels consist of 6 properties—a name (unique), a priority value (default: 0), an auto-set toggle (default: false), a collection of player permissions, a collection of role permissions, and a collection of faction permissions. Multiple labels can be assigned to one claim, in which case the label with the highest priority is evaluated first. Labels with auto-set toggle enabled are automatically applied to any new claims.
Permission collections are also known as permission groups. The 3 permission groups are: player · role · faction. When a player is applicable to multiple permission groups within a label, the player permission group takes priority, followed by role permissions, and lastly faction permissions.
/f label test to evaluate permissions of a player for a given chunk.Running /f label create mylabel creates a label named mylabel. This label is ineffective by default. The label can be assigned to a specific chunk, to all chunks touching a chunk, or to all claimed chunks through /f label edit mylabel and heading to the Manage Claims section. The same panel also offers ways to rename, change priority, and set permissions for different players, roles, and factions. Permissions in a given chunk for a given player (whether online or offline) can be tested by standing in the chunk and running /f label test <player>.
A permission can be given one of 3 values—allow, deny, and default. If a permission is set to default, the label is effectively ignored and the next label is evaluated. If a label with a non-default value (i.e., allow or deny) is not found, then default (i.e., hardcoded) role permission are used as fallback, and apply only to members of the faction.
| Permission | Description | Default Roles |
|---|---|---|
| Permission | Description | Default Roles |
| Break and Place Dispensers | Ability to break and place dispensers |
|
| Break Blocks | Ability to break blocks |
|
| Break Spawners | Ability to break Spawners |
|
| Break String | Ability to break String |
|
| Place Blocks | Ability to place blocks |
|
| Place Spawners | Ability to place Spawners |
|
| Place String | Ability to place String |
|
| Set Home | Ability to /sethome |
|
| Use Buttons | Ability to use buttons |
|
| Use Containers | Ability to open containers |
|
| Use Creeper Eggs | Ability to use Creeper Eggs |
|
| Use Doors | Ability to use Doors |
|
| Use Levers | Ability to use levers |
|
| Use Obsidian | Ability to use Obsidian |
|
| Use Sponges & Chunk Busters | Ability to break/place Chunk Busters |
|
| Use TNT | Ability to use TNT |
|
Base
Derps
Tips & Tricks
Timeline
| 2025-01-23 |
|
| 2025-01-19 |
|
| 2024-12-12 |
|
| 2024-10-24 |
|
| 2021-10-04 |
|
| 2021-07-24 |
|
| 2020-07-31 |
|