Check Towny outpost costs before claiming a distant base

Applies to: Towny; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

A distant outpost can have separate eligibility and costs from an ordinary adjacent claim. Confirm those requirements before charging a player or extending the town’s upkeep commitments.

Before you start

Towny combines town membership, plots, permissions and economy rules. Test with a mayor, resident and outsider where relevant; an administrator can bypass the restriction you intend to check. Record the town and world so similarly named places do not confuse results.

Work through the check

Record the intended outpost location, town balance and current claim usage, then confirm that the world permits the relevant Towny activity.
Read the installed release’s outpost requirements and configured costs, including any nation, distance or ownership limitations in your server policy.
Try the documented outpost flow on an isolated copy or a deliberately chosen empty test area, recording the exact refusal or quoted cost before confirming.
Inspect the resulting town claims, bank debit and upkeep estimate, and test who can travel to or use the outpost under the existing permissions.

Confirm the result

The outpost should be attached to the correct town with the expected cost and access rules. A rejected claim should leave the bank and surrounding ownership unchanged.

If the result differs

A failed adjacency check is not proof that outposts are disabled. Compare the specific requirements and available town capacity before changing global claim limits or bypass permissions.

Recover safely

If the trial is abandoned, undo only the temporary empty claim through supported Towny controls after confirming its boundaries. Preserve existing bases and do not remove real player structures to repeat a cost test.

Documentation and related help

Check the Towny maintainer documentation and Towny maintainer reference against your installed release before applying changes.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report