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 (excludes players in Spectator mode and players hidden from the viewer)
%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 draws your claims on four web-map plugins: Dynmap, BlueMap, Pl3xMap and squaremap. Install the plugin, keep its hooks.<plugin> toggle on, and SCS2 detects it and starts rendering automatically.

Normal and for-sale claims can use different styles — line weight, opacity, colour, label and a clickable HTML popup. The full key reference and examples live in Configuration → Map Integration.

Discord Webhooks

SCS2 posts claim events to Discord through webhooks. Define several named webhooks and route each event to the one(s) you want.

Routable events

Names usable under routing:

claim-created, claim-deleted, claim-sold, claim-for-sale, claim-sale-cancelled, member-added, member-removed, member-promoted, member-demoted, member-role-changed, owner-transfer, claim-ban, claim-unban, claim-renamed, claim-description-changed, claim-spawn-changed, chunk-added, chunk-removed, claims-merged, unclaim-request.

Beyond routing, each event can be switched off completely with discord-webhook.events.<event>: false — a disabled event is never sent to any webhook, whatever routing says (omitted events default to true). For instance, set chunk-added: false and chunk-removed: false to drop the per-chunk spam while keeping member and role events. Configure it under Configuration → Discord Webhook. (Added in 2.6.6)

Each event's title, description and colour come from the language file (discord-webhook-<event>-title / -description / -color), so embeds can be translated or restyled.

Webhook URLs, named webhooks and routing rules are configured in Configuration → Discord Webhook.

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
  • Claim 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.

PvPManager

When PvPManager is installed, SCS2 stops combat-tagged players from reaching any claim whose pvp flag is disabled — so a player can't escape a fight by ducking into a no-PvP safe zone.

While PvPManager reports a player in combat, both ways into such a claim are denied:

  • Walking across the border — the player is bounced back to the chunk they came from.
  • Teleporting in/claim tp, /claim back, /claim visit, public & player warps, the claim GUIs, and the respawn-in-claim redirect are all refused.

The lock applies to everyone, including the claim's owner and members. Grant scs.bypass.combat (part of scs.bypass.*) to let staff or trusted accounts ignore it. Claims that allow PvP are never affected.

Automatic once PvPManager is installed — just keep the pvpmanager hook enabled under Configuration → Plugin Hooks. The denial messages are the not-enter-combat and not-teleport-combat language keys.

Still need help?

Ask our team on Discord or browse the source.