Description
What FrontierZZ Does
- Registers separate territory providers for player and clan ownership inside ZZCore.
- Supports territory modes for clans only, players only, or both.
- Supports claim sizing by owner kind, with personal and clan settings handled separately.
- Provides a standalone map UI with claim, unclaim, recenter, and personal-permissions flows.
- Enforces protections for break, place, damage, interact, PvP, and entry on personal and clan claims.
- Stores claim ownership, territorial metadata, access policies, and upkeep data in JSON.
Commands And Workflow
/frontieris the module entry point.- The main experience is UI-first through the Frontier hub entry and standalone map.
- The module does not expose style commands.
- ZZClan consumes the clan territory provider for clan claims, unclaims, visitor rules, and conquest flows.
Runtime Files And Data
config.jsonstores territory mode, owner-kind claim sizes, personal-claim settings, protections, costs, allowed worlds, and upkeep.- The module stores its runtime data under
ZonaZeroMc/ZZFrontier. - The JSON repository stores both player and clan ownership in the same data base.
- Personal-policy data stores allowed-player lists and related territory metadata.
Visible Config Example
This is the kind of config.json file you will see when the module generates its settings:
{
"version": 1,
"territoryMode": "both",
"parcelSizeX": 2,
"parcelSizeZ": 2,
"clanParcelSizeX": 0,
"clanParcelSizeZ": 0,
"playerParcelSizeX": 1,
"playerParcelSizeZ": 1,
"requireAdjacency": false,
"protectBlockBreaking": true,
"protectBlockPlacing": true,
"protectBlockInteraction": true,
"protectPvp": true,
"notifyDeniedActions": true,
"enableClaimCosts": true,
"claimCostBase": 0.0,
"claimCostPerExistingClaim": 0.0,
"personalMaxClaims": 8,
"enableClaimUpkeep": false,
"claimUpkeepPerParcel": 0.0,
"claimUpkeepIntervalMinutes": 1440,
"adminBypassPermission": "frontier.admin",
"adminBypassPlayers": [],
"allowedWorlds": []
}
The section below explains what each line changes in normal language.
Configuration Reference
Territory Mode And Parcel Size
version(number): internal config schema version.territoryMode(text): active territory mode. The current code normalizesboth,clans, orplayers.parcelSizeX(number): base parcel width.parcelSizeZ(number): base parcel depth.clanParcelSizeX(number): clan parcel width override.clanParcelSizeZ(number): clan parcel depth override.playerParcelSizeX(number): player parcel width override.playerParcelSizeZ(number): player parcel depth override.requireAdjacency(true/false): requires adjacency for new claims when enabled.
Protection Rules
protectBlockBreaking(true/false): blocks unauthorized block breaking when enabled.protectBlockPlacing(true/false): blocks unauthorized block placing when enabled.protectBlockInteraction(true/false): blocks unauthorized interaction when enabled.protectPvp(true/false): applies PvP protection on claims when enabled.notifyDeniedActions(true/false): sends denial feedback when blocked actions happen.
Costs And Limits
enableClaimCosts(true/false): enables claim costs.claimCostBase(number): base cost for claiming.claimCostPerExistingClaim(number): extra cost per already owned claim.personalMaxClaims(number): max personal claims allowed.enableClaimUpkeep(true/false): enables upkeep costs.claimUpkeepPerParcel(number): upkeep charged per parcel.claimUpkeepIntervalMinutes(number): minutes between upkeep checks.
Admin And World Scope
adminBypassPermission(text): permission used as territorial admin bypass.adminBypassPlayers(list): player names that bypass protections.allowedWorlds(list): worlds where the module is allowed to operate.
Permissions
frontier.usefrontier.admin
Installation
- Copy
ZZCore.jarinto the servermodsfolder first. - Copy
ZZFrontier.jarinto the same servermodsfolder after that. - If you want clan territory, conquest, and war integrations, also install
ZZClan.jar. - Start Hytale.
- Configure territory mode, claim sizes, protections, and world rules.
License
All Rights Reserved.
Redistribution, reposting, resale edits, or reuploading forks is not allowed without written permission from the author.
