Installation
On this page(4)
- Download the latest
snplayerwarps-v*release from Sn-Releases. - Place the
.jarfile into your server'splugins/folder, next toSnLib.jar. - Start the server once. SnPlayerWarps creates the shared license file
plugins/.Sn-License/license.yml. - Paste your Sn license key into that file, replacing the placeholder line.
- Restart the server. SnPlayerWarps validates the key at startup and then enables.
Requires SnLib installed (depend: [SnLib]), version 1.37.0 or later.
SnPlayerWarps is part of the licensed Sn bundle. The key lives in plugins/.Sn-License/license.yml, shared by every bundled Sn plugin on the server, so one key unlocks them all. Without a valid key the plugin refuses to enable, and the console shows [Sn] License: FAIL.
Dependencies
| Plugin | Required |
|---|---|
| SnLib | Yes |
| PlaceholderAPI | No, but the placeholders and every command-backed currency need it |
| Vault (with an economy plugin) | No, but every vault: true currency needs it |
| SnSuperiorSkyblock | No, enables the island rules |
| SuperiorSkyblock2 | No, enables the island rules (either island plugin is enough) |
Requirements: Java 21+, Paper 1.20.x (1.20.4 or newer) or 1.21.x.
First boot
SnPlayerWarps writes every file it needs on first boot:
plugins/
.Sn-License/
license.yml your bundle key, shared by every Sn bundle plugin
SnPlayerWarps/
config.yml warps, visits, browser, sponsors, limits, currencies, islands
lang/
messages_en.yml every line the plugin sends
guis/
browse.yml the warp browser
warp-picker.yml one owner's warps, when a visit names several
sponsor-select.yml picks the warp to feature in a sponsor slot
confirm-sponsor.yml confirms a sponsor slot purchase
my-warps.yml your warps (and staff view of another owner's)
warp-manage.yml manages one warp
confirm-delete.yml confirms a warp deletion
bans.yml the players banned from your warpsWith database.type: sqlite (the default) the database file lives in the same folder. Nothing is written to data files: warps, sponsor slots and queued refunds all live in the database.
Switching between SQLite and MySQL starts with empty tables. Nothing is migrated, so your warps, sponsor slots and queued refunds stay in the old database. Give each server its own database: the plugin loads it once at start and does not see another server's changes.
Before players use it
- Point the sponsor currency at a currency you actually have. The shipped
sponsor.currencyisokicoins, a command-backed example that reads%sncredits_balance%and runs SnCredits commands. On a server without SnCredits, set it tomoney(Vault) or declare your own currency. See Configuration. - Check the costs.
limits.costs.create,moveandrenameship at0(free), paid inmoneywhen you raise them. - Set the warp limit.
limits.default-warpsis1. Grantsnplayerwarps.limit.<n>to ranks that may own more. See Permissions.
Island setup
The island rules work with SnSuperiorSkyblock or SuperiorSkyblock2 (the islands: block of config.yml). With islands.require-island: true, warps can only be created on an island you belong to.
With islands.privilege-check: true (the default), you also need the PLAYER_WARPS privilege of your island role to create or move a warp there. SnPlayerWarps registers the privilege itself. Two steps are yours, in the island plugin's own files:
- Add
PLAYER_WARPStoisland-roles.ladder.member.permissionsin itsconfig.yml, so every member has it by default. Higher roles inherit it. - Add a
player_warpsentry underpermissions:in itsmenus/permissions.yml. Copy an existing entry such asbuildand change its item and texts. Without it, island owners cannot toggle the privilege in/is permissions.
The console reminds you of both steps at every start while the privilege check is on. To rely on island membership alone, set islands.privilege-check: false.
With islands.enabled: true and neither island plugin installed, the console warns once at start that the island rules are off. Warps can then be placed anywhere the world rules allow.