Integrations

Advanced

Integrations

PlaceholderAPI

SCS2 provides a PlaceholderAPI expansion with 42+ placeholders for use in scoreboards, chat plugins, holograms, and more. The expansion registers automatically when PlaceholderAPI is detected.

Player placeholders

PlaceholderDescription
%scs_chunks_count%Total claimed chunks
%scs_claims_count%Total claims
%scs_max-chunks%Maximum claimable chunks
%scs_max-claims%Maximum claims allowed
%scs_max-members%Maximum members per claim
%scs_remaining_chunks%Remaining claimable chunks
%scs_remaining_claims%Remaining claims allowed
%scs_chunk-cost%Cost per chunk
%scs_cost-multiplier%Cost multiplier
%scs_next_chunk_cost%Next chunk cost (with multiplier applied)
%scs_fly%Remaining fly time in seconds (raw number); for staff / claim.fly.infinite
%scs_fly_formatted%Remaining fly time as a human-readable duration — same format as the action-bar timer (e.g. 1:23:45, or 2j, 03:00:00 past a day); when unlimited
%scs_delay%Teleportation delay
%scs_distance%Minimum claim distance
%scs_max-radius%Maximum claim radius
%scs_max-roles%Maximum custom roles per claim
%scs_max-claim-price%Maximum chunk cost cap (shows infinity if 0)

Toggle status placeholders

PlaceholderDescription
%scs_auto-claim%Auto-claim status
%scs_auto-unclaim%Auto-unclaim status
%scs_auto-addchunk%Auto-addchunk status
%scs_auto-delchunk%Auto-delchunk status
%scs_auto-merge%Auto-merge status
%scs_auto-fly%Auto-fly status
%scs_auto-map%Auto-map status
%scs_auto-purge-bypass%Auto-purge bypass status

Current claim placeholders

These return data about the claim at the player's current location:

PlaceholderDescription
%scs_claim_owner%Owner of the claim
%scs_claim_name%Name of the claim
%scs_claim_description%Description of the claim
%scs_claim_player_role%Player's role in the claim (supports custom roles)
%scs_claim_is_in_sale%Whether the claim is for sale
%scs_claim_sale_price%Sale price
%scs_claim_members_count%Number of members
%scs_claim_members_online%Number of online members
%scs_claim_spawn%Spawn location coordinates
%scs_claim_chunks_count%Number of chunks in the claim
%scs_claim_setting_<permission>_<role>%Value of a specific permission for a role

Dynamic chunk placeholders

Query claim data for specific chunks by absolute coordinates or relative offset from the player:

PlaceholderDescription
%scs_claim_chunk_<world>_<x>_<z>_name%Claim name at specific chunk coordinates
%scs_claim_chunk_<world>_<x>_<z>_owner%Claim owner at specific chunk coordinates
%scs_claim_chunk_<world>_<x>_<z>_player%Player's role at specific chunk coordinates
%scs_claim_chunk_relative_<world>_<dx>_<dz>_name%Claim name at relative chunk offset from player
%scs_claim_chunk_relative_<world>_<dx>_<dz>_owner%Claim owner at relative chunk offset
%scs_claim_chunk_relative_<world>_<dx>_<dz>_player%Player's role at relative chunk offset

Relative placeholders are useful for creating custom map displays. For example, %scs_claim_chunk_relative_world_-1_0_owner% returns the owner of the chunk one west of the player.

WorldGuard

When WorldGuard is installed, SCS2 automatically registers a custom scs-claim region flag. This prevents players from claiming chunks that overlap with WorldGuard regions where the flag is set.

This integration is automatic — no configuration needed. WorldGuard regions take priority over SCS claims.

Map Plugins

SCS2 integrates with four web map plugins to display claims on your server's online map:

  • Dynmap — fully supported with customizable polygon styles
  • BlueMap — fully supported with customizable marker styles
  • Pl3xMap — fully supported
  • squaremap — fully supported

Each map plugin has its own configuration section in config.yml with style options for line weight, opacity, colors, labels, and popups. Normal claims and for-sale claims can have different visual styles.

# Example Dynmap configuration
dynmap:
  enabled: true
  show-labels: true
  styles:
    normal:
      line-weight: 2
      line-opacity: 0.8
      line-color: "00FF00"
      fill-opacity: 0.3
      fill-color: "00FF00"
      label-format: "%claim_name%"
    for-sale:
      line-color: "FFCC00"
      fill-color: "FFCC00"

Discord Webhooks

SCS2 can send notifications to a Discord channel via webhooks. Events that trigger notifications include:

  • Claim creation and deletion
  • Claim sales and purchases
  • Player bans and kicks from claims
  • Ownership transfers

Configuration:

discord-webhook:
  enabled: true
  url: "https://discord.com/api/webhooks/your-webhook-url"

Create a webhook in your Discord server settings (Server Settings > Integrations > Webhooks) and paste the URL into the config.

Web Dashboard

The admin web dashboard provides remote management capabilities through a browser interface:

web-dashboard:
  enabled: true
  port: 8095
  url: "http://localhost:8095"

Run /scs dashboard in-game to get a one-click [Click here] auto-login link in chat. The link points to web-dashboard.url with the admin token baked in as a query parameter (?token=...), so the player lands signed in without pasting anything. Token hashes are persisted in web-tokens.json across restarts.

Dashboard features include:

  • View all claims on an interactive map
  • Manage player limits and settings
  • View claim details, members, and audit logs
  • Perform administrative actions remotely

Geyser / Floodgate (Bedrock)

Bedrock Edition players connecting through Geyser or Floodgate are fully supported. The plugin automatically detects Bedrock players and displays dedicated Bedrock-compatible GUIs that work with the Bedrock inventory system.

No additional configuration is needed — install Geyser/Floodgate and SCS2 handles the rest.

QuickShop-Hikari

SCS2 integrates with QuickShop-Hikari for shop management within claims. This allows shop-related permissions to be controlled through the claim's role system — for example, allowing only members to create shops in the claim.

Vault & VaultUnlocked (Economy)

Install Vault (or its modern fork VaultUnlocked) and an economy provider (e.g., EssentialsX, CMI, PlayerPoints) to enable all economy features:

  • Chunk claiming costs
  • Cost multipliers per additional chunk
  • Selling and buying claims between players
  • Daily tax / rent
  • Public-warp visit fees (paid to the owner)
  • Formatted number display (e.g., 1,000,000)

Enable the economy system in config.yml:

claims:
  economy:
    enabled: true

Both Vault (net.milkbowl.vault.economy) and VaultUnlocked (net.milkbowl.vault2.economy) are supported transparently. SCS2 probes the modern vault2 service first and falls back to legacy Vault if only the older API is registered — the startup log shows which provider was bound. Both plugins are listed as softdepend, so SCS2 picks up either one regardless of which is installed. (2.5.0 fix: the previous version only checked for the legacy "Vault" plugin name and missed VaultUnlocked-only setups on Paper.)

If neither plugin is installed, all economy features are silently disabled. Players can still claim and manage territory without spending money.

Still need help?

Ask our team on Discord or browse the source.