Home Limits

SmartHomes uses permission nodes to control how many homes a player can set. This gives per-rank control without editing config files.

How It Works

Grant smarthomes.limit.<n> to a group to give them n home slots. The highest node granted to the player wins.

smarthomes.limit.3   → 3 homes
smarthomes.limit.10  → 10 homes
smarthomes.limit.50  → 50 homes

If the player has no limit node, config.yml limits.default is used (default: 3).

The shipped plugin.yml pre-declares smarthomes.limit.3 (default true), smarthomes.limit.5 and smarthomes.limit.10 (default false). Any other positive integer node is accepted at runtime — declare it in your permissions plugin and SmartHomes will pick it up.

Setting Up Per-Rank Limits (LuckPerms)

# Default rank — 3 homes (smarthomes.limit.3 is true by default)

# Member rank (5 homes)
/lp group member permission set smarthomes.limit.5 true

# VIP rank (10 homes)
/lp group vip permission set smarthomes.limit.10 true

# Premium rank (20 homes)
/lp group premium permission set smarthomes.limit.20 true

# Elite rank (50 homes)
/lp group elite permission set smarthomes.limit.50 true

# Staff (effectively unlimited)
/lp group staff permission set smarthomes.limit.999 true

Which Node Wins?

The highest smarthomes.limit.<n> node granted wins. If a player is in both VIP (limit.10) and Premium (limit.20), they get 20 homes.

Note: If you want to restrict a player below the default, set limits.default low and use permission nodes to increase it.

Checking a Player's Limit

Players can see their own limit via PlaceholderAPI:

%smarthomes_limit%

Staff can check via /home admin <player> which lists their homes and the slot count.

Home | Configuration | Commands & Permissions