Description
Create your island from the same menu (or /is create). /visit <player> and /is hub also exist.
- Roles: Owner, Co-Owner, Member, Visitor. Invite people with
/is invite <player>(they accept with/is accept); promote, demote, remove, ban and transfer the island from the members menu or by command. - Rules (
/is settings): who can build, break, open containers, use doors, use buckets, touch animals, set the spawn, invite, remove and ban (each is the lowest role allowed, the owner cycles them with a click), plus switches for visitors, PvP, monster / animal spawning, fire spread and explosions. - Protection: build, break, containers, doors, plates, buckets, animals, item frames, PvP, spawning,
explosions, fire and liquids are checked per island. Banned players and closed islands cannot be entered
(walking, ender pearls and teleports). Falling into the void sends you home (or to the hub). Water and lava
never cross to another island. Operators are protected like everyone else until they switch the opt-in
/is admin bypasson. - Reset and delete clear the island in the background, a few milliseconds per tick, so they never lag the server. The status is saved first, so a crash in the middle is finished at the next start.
| Command | Permission | |
|---|---|---|
/is, /is menu |
skyrpg.island.use |
Island menu |
/is create, home, sethome, hub |
skyrpg.island.create / home / sethome / hub |
|
/is visit [player], /visit [player] |
skyrpg.island.visit |
Visit menu or a player's island |
/is invite <player>, accept, deny, leave |
skyrpg.island.invite / use / leave |
Co-op |
/is kick, ban, unban, bans |
skyrpg.island.kick / ban |
Plus the island's own role rules |
/is promote, demote |
skyrpg.island.manage |
Owner only |
/is transfer <player> |
skyrpg.island.transfer |
Owner only, asks to confirm |
/is settings, lock, unlock, name <name> |
skyrpg.island.settings / rename |
|
/is members, info [player] |
skyrpg.island.use / info |
|
/is reset, /is delete |
skyrpg.island.reset / delete |
Owner only, asks to confirm |
/is admin info\|tp\|delete\|reset\|setowner\|save\|backup\|bypass\|stats |
skyrpg.island.admin (+ .admin.bypass) |
Admins can enter every island |
All player permissions default to everyone, the admin ones to operators; skyrpg.island.* gives all of them.
skyrpg.island.members.<n> raises the member limit of that owner (see islands.max-members in config.yml).
Database and data safety
- SQLite by default (
islands.db, nothing to set up) or MySQL; both JDBC drivers ship with Spigot. Tables are created on first start (table-prefixis configurable). - Every island lives in memory; the database is read once at startup and only written afterwards. All database work runs on one dedicated thread, so the server thread never waits for disk or network.
- Changed islands are saved in batches every few seconds (
flush-seconds); creating, deleting, members and ownership are written at once. Writes are transactions, a failed write is retried on a new connection and kept for the next flush, and shutdown waits for the database thread. Resets and deletes are crash safe. - SQLite is copied to
backups/every few hours and the newest copies are kept (database.backup). The island blocks themselves are saved by the server together with the island world. - Paper servers get asynchronous teleports automatically.
Files
config.yml (settings, abilities, islands), messages.yml (all text), items.yml, reforges.yml, enchants.yml.
The plugin also writes anvils.yml, mana.yml, islands.db and backups/. /skyrpg reload re-reads
everything except the island database and world settings, which need a restart.
Languages
Each top-level key of messages.yml is a language. Set language: in config.yml; with
per-player-language: true chat, menus and the action bar follow each player's client language.
Item lore is stored on the item, so it uses the server language, but items made in any language are
understood. To add one, copy the en: block, rename it, translate it.
Performance
- A player's stats are cached and recomputed only when gear can change (slot change, inventory click,
drop, equip), plus a slow safety refresh (
stats-refresh-seconds). - One timer per second does the work for everyone; the action bar is only re-sent when it changes.
- Damage numbers: at most 60 armor stands, recycled, swept by a single timer.
- Disk is touched on start, on quit (asynchronously) and on shutdown. Island data goes through the database thread.
- Island lookups are hash lookups; protection and liquid / move events return at once outside the island world.
- Reflection for sounds, particles and the action bar is resolved once and cached.
