Create a Towny starter town and test outsider permissions

Towny combines land claims, town membership and optional economy costs. Set up a small town before inviting residents, then test what an outsider can do. A mayor test alone cannot show whether a public visitor can open doors or change blocks.

Review costs and the intended world

Use a Towny release that lists support for your Minecraft and server platform. Keep the release's command help nearby, because rank permissions and configuration defaults can change. Check whether the target world permits towns, how much creating and claiming costs, and which upkeep rules apply. Town creation can affect an in-game balance; use a private test environment with agreed test funds before experimenting.

Record the town's intended home area and existing protection plugins. Back up Towny's data and configuration with its economy storage before changing an established setup. Avoid creating a trial town over player builds, spawn, another town or a resource world scheduled for resets.

Create the smallest useful claim

Join as an ordinary account with the intended town-creation permission. Stand in the chosen world and use /towny map to inspect nearby townblocks.
After checking the displayed creation cost, create an unused town with /town new ExampleTown. Replace the name and use your server's documented naming rules.
Inspect /town and its information output. Confirm the homeblock, membership and balance rather than assuming the message proves all settings are correct.
Use /town claim only for an adjacent test townblock whose cost and position you have checked. Keep expansion to the planned area.

Test each outsider action

Towny distinguishes build, destroy, switch and item-use permissions. In the test town, inspect the current town permission display and record its values. For a town where visitors should not place or break blocks, use the installed release's town permission controls, such as /town set perm outsider build off and /town set perm outsider destroy off.

Bring a second non-operator account that belongs to no town, nation or alliance involved in the test. Attempt a harmless block placement and removal inside the claim, then check doors and buttons separately. Do not assume blocking destruction also blocks switching. Keep disposable test blocks away from valuable containers.

Repeat at a plot with its own permissions, if one exists. Plot-level rules and resident-owned land need their own checks. Record which account owns the plot, because testing with the owner can hide an outsider mistake. Review PvP, explosions, fire and mobs as separate town policy choices before opening the area.

Correct rules without deleting land

Adjust the specific town or plot rule responsible for a failed test, then repeat the same visitor action. Grant a resident only the role they need instead of adding administrative bypass permissions. If the result still differs, check Towny ranks, overlapping protection plugins and the world configuration.

Restore the recorded permission values to undo a test. Avoid deleting a live town or unclaiming occupied land as a troubleshooting shortcut. Plan upkeep and staff coverage before inviting players so a test balance or unexpected daily cost does not put their claims at risk.

back up the server files · review LuckPerms groups and inheritance · check the Vault economy connection

Official references