Economy

Economy System

SCS2 integrates with Vault to provide a full economy system for claims. When enabled, players pay to claim chunks and can sell their claims to other players.

Enable economy in config.yml:

claims:
  economy:
    enabled: true
    max-price: 1_000_000_000
    formatted-number: true
    currency-format: "%amount%$"   # 2.8

• enabled — activates the economy system
• max-price — maximum price a player can set when selling a claim
• formatted-number — displays prices with formatting (e.g., 1,000,000 instead of 1000000)
• currency-format — how money is displayed everywhere (messages, menus, holograms, web maps, dashboard): %amount% stands for the formatted number. Examples: "%amount%$" (default), "$%amount%", "%amount% coins", "%amount% €". (2.8)

Chunk Costs & Multipliers

Each time a player claims a chunk, they pay a configurable cost. How that cost grows as a claim gets bigger is controlled by the cost mode and the cost multiplier.

Cost modes

The global claims.economy.cost-mode option chooses how the per-chunk price is computed (N = the number of chunks the player already owns):

claims:
  economy:
    cost-mode: EXPONENTIAL   # EXPONENTIAL | LINEAR | FIXED

How chunk cost works (EXPONENTIAL)

The formula for the Nth chunk is:

cost = chunk_cost * (cost_multiplier ^ (N - 1))

Where N is the number of chunks the player already owns + 1.

Example

With chunk-cost: 100 and cost-multiplier: 1.5:

Example — LINEAR

With chunk-cost: 100, cost-multiplier: 50 and cost-mode: LINEAR, every chunk costs 50 more than the previous one: 100, 150, 200, 250, 300, …

In EXPONENTIAL mode, set cost-multiplier: 1.0 for a flat rate per chunk, or higher values to make large claims progressively more expensive.

Both chunk cost and cost multiplier can be set per player via permissions (scs.limit.cost.<amount>, scs.limit.cost-multiplier.<amount>) or admin commands.

Paying past your chunk limit (Added in 2.6.6)

By default a player is hard-stopped the moment they reach their max-chunks limit. With pay-over-limit you let them keep claiming beyond that limit as long as they can pay a per-chunk fee. Chunks up to the limit are unaffected (free, or at the normal chunk cost); only the chunks past the limit are charged this extra fee.

claims:
  economy:
    pay-over-limit:
      enabled: false
      price: 1000.0      # price of the 1st chunk past the limit
      mode: FIXED        # FIXED | LINEAR | EXPONENTIAL
      multiplier: 1.0
      max-price: 0.0     # per-chunk cap, 0 = no cap

When enabled: true — with the economy on and price > 0 — the fee for each over-limit chunk is derived from how many chunks the player is already past the limit (over, starting at 0 for the first one):

max-price caps the fee of a single over-limit chunk (0 = no cap). This applies only to the chunk limit (max-chunks); the claim-count limit (max-claims) stays a hard limit and is never sold past. If the player can't afford the fee they are blocked as usual with the "not enough money" message.

Claim creation cost (2.8)

Independently from the chunk price, a server can charge a price for every new claim. It is added to the chunk cost of the first chunk(s) on /claim, /claim <radius>, /claim create and auto-claim, and never charged for /claim addchunk, merges or purchases. Nothing is refunded on unclaim.

claims:
  economy:
    claim-creation:
      enabled: false
      mode: FIXED          # FIXED | LINEAR (base + multiplier × claims owned) | EXPONENTIAL (base × multiplier ^ claims owned)
      multiplier: 1.0
      max-price: 0.0       # cap per claim, 0 = no cap

players:
  default:
    claim-cost: 0.0        # base price of a new claim

• claim-cost is the per-player base price: players.default.claim-cost, overridable per rank with scs.limit.claim-cost.<amount> (lowest wins) or per player with /scs player <player> set-claim-cost <amount>. Players with scs.limit.bypass create claims for free.
• mode, multiplier and max-price follow the same formulas as the chunk cost, with the number of claims the player already owns as the tier.
• The confirmation message shows the total; when a creation price is part of it, a second line details it (claim-confirmation-money-details, placeholders %creation-price% and %chunks-price%).
• Placeholders: %claim-cost% and %next-claim-cost% in the player and claim menus, %scs_claim-cost% and %scs_next_claim_cost% in PlaceholderAPI.

Selling & Buying Claims

Players can put their claims up for sale and other players can buy them:

Selling

/claim sell [claim] <price>

Puts the specified claim up for sale at the given price. The claim appears in the sale list and on map integrations with a "for sale" style. A sale announcement can be broadcast to the server (configurable).

Cancelling a sale

/claim cancel-sale [claim]

Removes the claim from the sale listing.

Buying

/claim buy

Buys the claim you are standing in (if it is for sale). The price is deducted from the buyer's balance and added to the seller's balance. Full ownership — including all chunks, members, permissions, flags, and settings — transfers to the buyer.

Claim Tax / Rent

Claims can optionally incur a recurring tax that the owner must pay to keep them. Disabled by default — opt in via config:

claims:
  tax:
    enabled: false
    taxation-period: 1d
    amount-per-chunk: 1.0
    grace-periods: 3
    notify: true
    default-multiplier: 1.0

• taxation-period — how often the tax is charged. Any duration: 30s, 15m, 1h, 2h, 1d, 1w… The owner is billed once per elapsed period.
• amount-per-chunk — amount charged per owned chunk, per taxation-period, summed across all of the owner's claims.
• grace-periods — how many consecutive unpaid periods the owner can accumulate before all their claims are auto-unclaimed.
• notify — when true (default), the console logs a line each time the tax is charged, partially charged or could not be charged. The owner always receives the in-game message when online. (2.6.7, console-only since 2.8)
• default-multiplier — multiplies every bill. Per-rank override with scs.limit.tax-multiplier.<value>, lowest value wins: give scs.limit.tax-multiplier.0.5 to a VIP rank for half price, or .0 to exempt it. Read live for online owners, from their last saved value for offline ones. (2.7.1)

How it works

• Billing is timestamp-based, not tick-based: the plugin stores each owner's last-tax-paid time and charges for every whole taxation-period elapsed since. It survives restarts — if the server is offline across several periods, the next run bills for them all at once.
• Total charged = amount-per-chunk × number of chunks × periods elapsed × multiplier. Chunk counts come straight from the database, so every owner is billed — not only those whose claims happen to be loaded.
• On success the balance is debited and the meter advances by exactly the periods charged; any sub-period remainder carries over to the next run.
• If the balance doesn't cover the whole bill, the plugin still collects every whole period the balance covers and advances the meter by those; the remaining periods stay due and the owner is told (when online) how much is missing. Once the unpaid periods exceed grace-periods, every claim the owner has is unclaimed automatically. (2.8: partial collection; before, nothing was collected until the full bill could be paid)

Checking and paying by hand

Because the collector only passes every taxation-period ÷ 10, an owner who just topped up their balance could wait a long time for the next attempt. Two commands remove the guesswork. (2.8.1)

• Both need scs.claim.tax (granted by default) and only show up in tab-completion while the tax is enabled.
• A manual payment never removes claims: only the automatic collector enforces grace-periods.
• An owner who logs in with periods already due is charged again a few seconds after joining, so a player who comes back with enough money does not wait for the next pass.
• The collector and a manual payment can never charge the same periods twice, including across servers sharing a database.
• The total shown by /claim tax counts the payments made since 2.8.1.
• ClaimTaxEvent fires for manual payments too.