Items and economy

Money, shops, loadouts, custom items, rarity, recipes, the store, the marketplace, auctions, the coin exchange, gatcha and the stock market.

Loadouts and shop #

Loadouts and shop (/manage/loadouts, permission loadouts.manage). Per server group: turn loadouts on, choose in-game money or global coins, allow player-built loadouts and how many each. Staff build the shop (material, amount, data value, custom name, enchantments, unbreakable, armour slot, price) and preset loadouts with an optional fixed price; otherwise the price is the predicted price (the shop prices added up, shown live while building). Players build loadouts on the portal (/account/loadouts) or in-game with /loadout save <name>, which saves what they're wearing and carrying (items are matched to the shop by material, data value and enchantments; anything not sold there is left out and listed). They use them with /loadout <name> or the Use button (sent to their server). Never while in combat; money is only taken once the items are handed over.

Item Shop (/shop) #

Item Shop (/shop). Each item in a group's shop says where it's sold: the Item Shop (bought and sold in-game), loadouts, or both. /shop shows the group's Item Shop items in a chest menu with their prices (in Japanese for players using /jp), with pages when there are more than 54.

  • In the menu: left click buys one lot, shift + left buys a stack, right click sells one lot, shift + right sells all you have. A lot is the item's Amount.
  • Selling: give an item a Sell price and the shop buys it back; empty means it doesn't. Selling always pays in-game money, even where prices are in global coins. Only plain items can be sold (no custom name, not temporary), unless the row is a custom item, which the shop knows by its ID. A sell price above the buy price is refused, so it can't print money. Untick Players can buy this for an item the shop only buys.
  • Limits: Buy limit and Sell limit cap how many lots one player can trade of that item, separately, over Every (hours), which defaults to 24. Empty means unlimited, which is the default. It's a rolling window, so a lot counts until that many hours after it was traded. A stack or sell all counts each lot, and is cut down to what's left.

Unless an item is set to Keep on death, everything bought from the Item Shop or a loadout is temporary: it is removed on death instead of dropping, and the respawn gives back the default gear (giveKit: iron sword, bow, 32 arrows and armour). Payment uses the group's currency setting; in-game money also runs money_take_command from config.sk (default money take {player} {amount}, as the old shop did). Add the classic Item Shop items recreates the five items the old hard-coded shop sold. Recent trades are listed on the shop page.

/pay and bounties #

/pay and bounties. /pay <player> <amount> sends global coins to anyone on the network, in one transaction. Bounties (/account/bounties, under Pit; in-game /bounty) hold global coins on a player's head until someone kills them on any server on the network where PvP is on (the PvP world rule of the server or its category). Every server sees the same bounties. The panel marks each bounty claimed with a single conditional update, so two servers reporting kills at the same moment can't both pay it. You can't claim bounties you placed, and unclaimed bounties are refunded after 7 days (the expire-bounties task).

Store recent purchases #

Store recent purchases. /store lists the last 8 completed purchases: who and what, never the price. Refunds and packages staff gave by hand are left out. Players can hide theirs with Show my store purchases in their settings (on by default).

Price format #

Price format. How in-game money looks. Staff set the network default in Settings → Prices, using <price> where the number goes: $<price> (the default), €<price> or <price> gold. A category (Servers → Manage groups) or a single server (Servers → edit) can override it, and the server wins, then the category, then the network. Empty means "use the next one up". The format can't contain & colour codes, because prices sit inside sentences that set their own colour. It only changes the look: amounts aren't converted, and global coins keep their own wording. It covers the Item Shop, loadouts, Marketplace, jobs, crew rewards, Tag, the Pit scoreboard and kill message, and fishing and envoy money, plus replies from the panel about these. Servers pick up a change with the group settings, within 15 seconds. In your own scripts, use Net_Price(amount) for numbers (Net_PriceText("1,500") for text) and don't write a $ in the sentence. Pet ability descriptions ("Costs 5 money each use") and survival's quest reward text still use their own wording.

Custom items #

Custom items (Items → Custom items, /manage/custom-items, permission customitems.manage; network/Items/CustomItems.sk). Staff register an item with a name, material, lore, enchantments, glow and unbreakable. Each gets a random 8-character ID when it is created, like 3fa9c0d1, which never changes. Items reach every server with the group settings, within about 15 seconds. They are network-wide, not per category.

Pet treats. Set Pet XP when used on a custom item to make it a pet treat. In-game, right-clicking it uses one and gives the player's active pet that much XP; sneak + right-click uses the whole stack. The panel decides the XP: with no pet out, or a pet already at its top level, nothing is used, and only as many treats as reach the cap are taken. Whatever isn't used goes back to the player (or, if they left before the panel answered, the next time they join that server). Creative mode uses none. Say what it does in the item's lore, because the item doesn't add a line by itself. Hand treats out like any custom item: shops, rewards, loot, crates or citem give <id> {player}.

Item scripts. Under Scripts on an item's page, staff attach Skript code to its events (right or left click, hitting, being hit while holding or wearing it, killing, mining, consuming, holding, equipping, unequipping, dropping), each with its own cooldown. It runs only for that item, is checked by the linter when saved, and is published to every category's servers with their Projects. See Custom item scripts under Script hooks reference in skript.md.

Use 1.8 material names (IRON_SWORD, WOOL:14, SKULL_ITEM:3). The panel only accepts materials that work on both 1.8 and modern servers (app/Support/ItemMaterials.php, renames in core/Support/Compat.sk), so modern-only items like netherite are refused. A given item carries its ID in the item's own data under neutine:custom_item, so it is still recognised after a pickup, a death, a restart or an anvil rename: persistent data on modern servers, NBT on 1.8, both written from Java in core/Support/Compat.sk. Copies handed out before NBT have the ID as hidden colour codes at the end of the lore; these are still read, and 1.8 falls back to that if NBT can't be written. Editing an item changes new copies only; copies players already have keep their old look and their ID. Deleting one leaves existing copies alone, but servers can no longer give it, and an item a shop still sells can't be deleted.

Where staff pick one: Custom item on a shop item (Pit → Loadouts and shop), which then works in /shop, presets, player-built loadouts on the portal and /loadout save, and with a sell price the shop buys back only that item; a Custom item reward on quests, achievements, events, jobs, level rewards and crew quests; and a "Custom item" drop in fishing or envoy loot. A custom item keeps its own name, lore and enchantments everywhere. As with all /shop and loadout gear, a copy bought there is temporary and lost on death unless the shop item is set to keep on death; one from a reward is not.

Items are copies inside functions (fixed 2026-11-11). Skript hands every function a copy of an ItemStack, so a function that changes an item and returns nothing changes only the copy. That was why a custom item given on Paper had no ID tag (/citem held said it wasn't a custom item), no rarity line and no enchantments: Net_Enchant, Net_Glow, Net_TagSet and Rarity_Apply changed copies and CItem_Build handed out the untouched stack. Every network function that changes an item now returns it, and callers keep what comes back: set {_stack} to Net_TagSet({_stack}, "3fa9c0d1"). That covers Net_TagSet, Net_NbtSet, Net_Enchant, Net_Glow (core/Support/Compat.sk), Rarity_Set and the new Rarity_Applied (returns the changed stack, or nothing when nothing changed; Rarity_Apply now only says whether it would change), Net_RaritySet (Script editor), and Combat_TagSet, Combat_Write, Combat_Imbue, Combat_Enchant (nothing when it can't go on) and Combat_Lore. The script linter (App\Services\SkriptLinter::ITEM_CHANGERS) refuses a call to one of them on a line of its own, and CustomItemsTest checks every script for it. On modern servers enchantments are now looked up through the enchantment registry first (Net_EnchantOf), in case Paper drops Enchantment.getByName. CItem_Give adds the rarity line straight away instead of at the next sweep.

Other ways to give one: /citem give <id> [player] [amount]; /citem menu, a chest menu of every item where a click gives you one; a console command in store packages (citem give <id> {player}); or Script editor projects, with Net_Item, Net_ItemGive, Net_ItemIs and Net_ItemId (listed in the editor). The player must be on the server that runs the command, which for rewards is the server they are on or last played on.

Resource pack #

Resource pack (Items → Resource pack, /manage/resource-pack, staff with islands.manage or customitems.manage; App\Support\ResourcePack). One Minecraft resource pack for the whole website. Upload the whole pack (.zip, or the game's .jar): its block textures (assets/minecraft/textures/block/, or textures/blocks/ before 1.13) and item textures (textures/item/, or textures/items/) are kept, replacing the ones there were; everything else in the pack is ignored. Single PNGs named after a texture (oak_planks.png, diamond_sword.png) are added on top, as blocks or items. A zip of loose PNGs counts as block textures.

  • Where it shows. The island 3D views (staff and portal) draw blocks with the block textures (App\Support\BlockTextures). Every item picture on the site comes from ItemIcon::urlFor(): a picture staff set on Item icons first, else the pack's item texture (modern or 1.8 name: GOLD_SWORD finds golden_sword), else the side of the block. A custom item without its own picture uses its material's. That covers recipes (list, form and preview), the web inventory, the Pit kit layout, homes and the settings menu preview. Items with no picture show their name.
  • Files. Block textures are kept under block-textures/ and item textures under item-textures/ on the local disk, listed in the island.textures setting (named from when only islands used it). They're served to anyone at /island-textures/{version}/{name}.png and /item-textures/{version}/{name}.png, cached for a year (a new upload changes the version).
  • The pack uploaded before (2026-11-15). Only its block textures were kept then, so it keeps working for blocks and the island views, and the page says it has no item textures yet: upload the whole pack again to give items their pictures.
  • Not for players. Game clients never download it. Uploads, single textures and removing it are in the audit log (resourcepack.upload, resourcepack.clear).

Rarity #

Rarity (Items → Rarity, /manage/rarity, permission rarity.manage; app/Support/Rarity.php, network/Items/Rarity.sk). An item with a rarity gets one lore line showing it. Which items have one is up to staff (see Which items have a rarity below; by default only the items on the list). Staff manage the tiers: it starts with Common, Rare, Epic, Legendary, Mythical and Unique, and Add a rarity adds another (a name, a key such as ancient that scripts and /rarity set use and that can't change later, a colour, an optional lore line and its place in the list; lowest first, and the place is the rank scripts compare). Edit next to a tier changes its name, colour, lore line or place, and deletes it. Staff put vanilla materials on the list by their modern name (NETHERITE_SWORD, several at once, each with a tier or Random; Take off the list removes one), give custom items their own rarity, which lists them (a tier or Random; empty: the same as their material's, and listed only if the material is; also on the custom item form), and set each tier's colour and lore line ({colour}, {name}, {NAME}; default {colour}&l{NAME}, so &5&lEPIC).

Deleting a tier never breaks an item: everything rated with it moves to the default (Common) in one go (Rarity::remove()). Listed materials with it stay on the list as Common, and custom items, artifacts, recipes, class skills, weapon skills and elite mob drops that had it get Common; the edit page says how many of each before you delete. Servers stop getting the tier with the next group settings, and an item a script gave the deleted tier (Rarity_Set) reads as Common in-game and its lore line changes at the next sweep. Anything else still holding the old key reads as the default on the panel too (Rarity::normalise()). Common can be renamed and recoloured but not deleted. Adding, editing and deleting tiers are in the audit log (rarity.create, rarity.update, rarity.delete), and need rarity.manage. Tiers are stored in item_rarities (the old rarity.tiers setting was folded in by the 2026-11-13 migration). The line shows per category: every category is on until staff untick it. Only modern servers show it; 1.8 (Pit) never does.

Which items have a rarity (added 2026-11-17). A rarity line and its persistent data change the item, so the same item with and without a rarity didn't stack, and anything comparing items exactly (vanilla stacking, isSimilar, Skript's remove 4 of {_item}, villager trades, trial vaults) treated them as different. So rarity is opt-in. The mode at the top of the page (Rarity::mode(), setting rarity.mode, audit rarity.mode) is one of:

  • Off: no item has a rarity.
  • Only the items on the list (the default, and the list starts empty): listed materials, and custom items with their own rarity or a listed material (Rarity::listedFor()).
  • Every item: as before, anything not listed is Common.

Servers strip every item that has no rarity back to a plain item: the rarity lore line goes (other lore stays) and both neutine:rarity_line and neutine:rarity are removed, so it is identical to one that never had them and stacks and matches again. A listed item is never stripped. Stripping happens wherever the line is added, never every tick: drops as they spawn, the player's inventory on join, pickup, craft and inventory close, a chest-like container when opened, and the 20-second sweep. A Rarity_Set from a script (elite drops, recipe results, rewards) on an unlisted item is undone the same way, so nothing puts a rarity on unlisted items. Items marked none (lobby menu items) keep that mark. /rarity held says when the held item isn't on the list.

Before and after, for an unlisted diamond sword that got the old Common line: lore [... its own lines ..., "§f§lCOMMON"] and persistent data neutine:rarity_line = "§f§lCOMMON" (plus neutine:rarity = "<tier>" if a script set one) becomes lore [... its own lines ...] (no lore at all if that was its only line) and no rarity persistent data.

Random on the list rolls a tier for each item the first time a server sees it (Rarity_Roll): each tier is half as likely as the one below it, so with the six starting tiers Common is 32 in 63 and Unique 1 in 63. The item keeps what it rolled (stored as neutine:rarity, like a script's). Random items of the same material only stack when they rolled the same tier. On the panel a Random entry reads as the default tier wherever one tier is needed (Rarity::forCustomItem()); Rarity::RANDOM is reserved, so no tier can be called random.

Custom matching already ignores rarity: shops (Shop_Matches), recipes (Recipes_Token), quests (QuestStory_ItemKey) and dungeons compare the material or custom item ID, and vanilla crafting compares the material, so a listed item with a rarity still counts there.

Ratings reach servers with the group settings (rarity in the group wire, kept as {-net::group::rarity}: mode, enabled for the category, default, tiers, materials as MATERIAL => tier or "random", and skip; each custom item says rarity and rarity_listed itself). The script adds the line to items with a rarity as they spawn (mined blocks, mob and player deaths, dropped items), and sweeps a player's inventory when they join, pick up, craft, open a chest-like container or close an inventory, and every 20 seconds, which also picks up rating changes. It is always the last lore line, and the item remembers the line it was given (persistent data neutine:rarity_line), so it is replaced rather than added twice and other lore is left alone; turning a category off removes it again. Script menus (inventories with no holder) are not touched. Scripts can give an item its own rarity with Rarity_Set(stack, "epic") (persistent data neutine:rarity), which beats its custom item's and material's. Rarity_Set(stack, "none") means never a rarity line: the lobby's hotbar items (Play, Pets, Profile) have it. /rarity held shows what you're holding and /rarity set <tier|none|clear> sets it (network.items). The group wire's default is the default tier's key; the script uses the panel's tiers only once it has them (until then the six starting ones), so a deleted tier is gone in-game too. Script editor projects use Net_Rarity, Net_RaritySet and Net_RarityRank.

Trial keys never get a rarity line (fixed 2026-11-14). A vault only opens for a key exactly like its own, components included, so the rarity line and its persistent data (added to every item, also to keys dropped by trial spawners) made every trial key and ominous trial key useless. Materials in Rarity::SKIP (TRIAL_KEY, OMINOUS_TRIAL_KEY) go to servers as skip in the group wire and never get a line or rarity data; the script always skips the two keys itself too, before the panel's list arrives. A skipped item that already has the line gets it and the neutine:rarity_line / neutine:rarity data taken off at the next sweep (Rarity_Stripped), so keys players already hold work again. The list is built in, not staff-editable; add a material to Rarity::SKIP if something else turns out to need exact items. Rarity_Skipped(stack) tells scripts whether an item is skipped.

Trial vaults on Survival (survival/game/Server/Game/TrialVaults.sk). Any trial key opens a vault: when a player uses a trial key or ominous trial key on one, the key in their hand is made a plain key first (lore, anvil names and data taken off), so it matches what the vault wants. A normal key still doesn't open an ominous vault, and custom items made from a trial key (they have a custom item ID) are left alone. A vault breaks once anyone opens it: after it has thrown out its loot (BlockDispenseLootEvent, then waiting while it is unlocking or ejecting, at most a minute) the block is removed, so nobody else can open it. Not on the panel; it applies to every vault on Survival.

Artifacts #

Artifacts (Items → Artifacts, /manage/artifacts, permission artifacts.manage; app/Models/Artifact.php, network/Items/Artifacts.sk). An artifact is a custom item that does something while a player carries it anywhere in their inventory. Staff pick the custom item (one artifact per item; the custom item page links to it, or offers "Make it an artifact"), an optional rarity that overrides the item's (the item's rarity line then shows the artifact's tier), the categories it works in (none ticked: every category; elsewhere it's a plain custom item), on/off, and up to 4 effects:

  • Repels mobs: a list of entity types (ZOMBIE, SKELETON), HOSTILE (every hostile mob) or ALL (every mob, never players or NPCs), a radius (1-16 blocks) and a push strength. Those mobs are pushed away 4 times a second, drop the carrier as their target, and can't pick them as a target.
  • Potion effect: any combat-script potion at level 1-5, kept on while carried.
  • Pulls in dropped items within a radius.
  • Particle effect: one of the Particle effects on the carrier, played again every N seconds (0 = once, for an effect set to "Repeat until stopped"), stopped when they stop carrying it.
  • More mana (MP): extra max MP and/or MP per second (0.1 steps), only where the Mana rule is on (see Gameplay → Mana). This artifact's limit is the artifact's own cap: its bonus never takes the carrier's max MP past that number, counting their base, class and script bonuses (0 = no limit of its own). All carried artifacts together then stop at the category's "Most max MP / MP per second artifacts can add" rules.

Two copies count once. The artifact goes to servers inside its custom item's definition (CustomItem::toWire()['artifact'], with key, name, rarity, lore, summary and effects), so changes arrive with the group settings within about 15 seconds and copies players already have get the new effects at once. CustomItems.sk adds the artifact's lore lines (a gap, "✧ Artifact (works while carried)" and one line per effect) under the item's own lore when the item is made, so copies made before the change keep their old lore. Inventories are checked every 2 seconds. A custom item can't be deleted while it is an artifact; deleting the artifact leaves the item. Players see what they carry with /artifacts (alias /myartifacts). Other scripts can ask Art_Carries(player, key). Works on 1.8 and modern servers.

Custom recipes #

Staff make crafting and furnace recipes on the panel (Network gameplay → Recipes, permission recipes.manage) and choose where each one is on. Modern servers only; 1.8 (Pit) ignores them.

  • Making one. Give it a name (what players see), an ID (lucky_charm, used by quests) and optionally a category (Weapons, Food: the tab it's under in-game; blank is Other, and the field suggests the ones in use). Pick the kind: shaped (a pattern in the 3×3 grid; it can sit anywhere in the grid and be flipped, and a pattern 2×2 or smaller also works in the player's own grid), shapeless (items anywhere), or furnace (one item smelted into another, with cooking time and experience). Each box takes a material name (DIAMOND, NETHERITE_INGOT) or a custom item (CITEM-1a2b3c4d, from the list) and an amount; more than 1 means the box needs a stack. The result is a material or custom item with an amount, and optionally its own rarity tier. Above the boxes the form draws the recipe as the game shows it (grid or furnace, an arrow, the result, amounts on stacks), redrawn as you type (resources/js/recipe-preview.js). The list of recipes shows each one the same way, small, sorted by category. Pictures come from the resource pack and Item icons; an item without one shows its name.
  • Where it's on. Tick categories (every server in them) and/or single servers. New recipes start with Survival categories ticked. "On" off removes it everywhere.
  • In-game (network/Items/Recipes.sk). The list for each server comes with the group settings (recipes), so changes land within 15 seconds. The server registers each recipe under neutine:recipe_<id> and removes every neutine:recipe_* recipe that isn't on its list: after a change, a reload (on load checks everything again) or a move to another category. Taking the script off removes them all.
  • Custom items as ingredients are checked by their hidden tag when the grid changes: a box that wants a custom item only takes that custom item, and a plain material box doesn't take custom items. Recipes with stacks in a box, or that the server matched as a different recipe, are crafted by the script (click, shift-click, number keys and drop all work).
  • Rarity. The result shows its rarity line in the result slot: the recipe's tier if chosen, else the item's own.
  • Players get the recipes unlocked in their recipe book when they join (and when new ones arrive). /recipes (alias /customrecipes, and /recipe, below) opens the recipes menu:
    • The list. Tabs along the top: All, each category (its icon is the first recipe's result), and Other when some recipes have none. With more than 8 tabs, the 8th is More categories. The top-right switch shows only what they can make now. 36 recipes a page, each saying "✔ You have everything for this" or "✘ Missing: 2 × Diamond, ..." (counted from their inventory when the menu opens), with previous and next page and a count of how many they can make.
    • A recipe. The crafting grid as it is placed (or a furnace: the item on top, fuel below), how to make it (crafting table, or the cooking time), and the result with what's missing. Each ingredient says how many they have against what its box needs, and one that has its own custom recipe opens that recipe when clicked; Back goes to the recipe before, then the list. Previous recipe and Next recipe walk the tab they came from.
    • The game draws items with the player's own textures: the website's resource pack isn't sent to players.
  • /recipe replaces EssentialsX's. On a server with at least one custom recipe on, /recipe opens the same menu and /recipe <ID or name> opens that recipe (colours, case, spaces and _ don't matter; else the first recipe whose name contains it). Every form is caught in PlayerCommandPreprocessEvent before Essentials sees it: /recipe, /formula, /method, the e-prefixed ones (/erecipe...), /recipes and any plugin: prefix (/essentials:recipe), the same way Spawn and Teleports replace Essentials' commands. A name that isn't one of ours goes on to Essentials' /recipe (vanilla recipes). On servers with no custom recipes on (and 1.8/Pit) Essentials keeps its /recipe. The script also registers /recipe (aliases /formula, /method) so it tab-completes everywhere; that command does the same and hands over to Essentials where there are no recipes. Nothing to change in the Essentials config: don't add recipe to disabled-commands, or the hand-over for vanilla recipes stops working. The name after /recipe doesn't tab-complete (Skript commands don't suggest text arguments).
  • Quests. Every craft counts the craft_recipe objective (param = the recipe ID, blank = any).

Store (Tebex) #

Store (Tebex) (Economy and store → Store (Tebex), permission store.manage):

  • Connecting: paste the store's public token (Tebex: Integrations → API Keys) and add the panel's webhook address (shown on the page, /api/v1/tebex/webhook) under Tebex: Developers → Webhooks → Endpoints, with "Payment Completed", "Payment Refunded", "Payment Dispute Opened" and "Recurring Payment Ended". Paste its webhook secret, save, then press Validate on Tebex. Every webhook's signature is checked; you can also limit them to Tebex's IP addresses.
  • Packages are fetched from Tebex every 15 minutes (task tebex-packages) or with Fetch packages now.
  • When a package is bought, its actions run for the buyer (or the gift's receiver): set their in-game rank, give a Discord role (needs the Discord bot), a badge, global coins (times the quantity), a pet, set a global value, run a console command (their server, every server or a category's), or send them a message. Each can wait some minutes first, and end after some days (a 30-day rank goes back to what it was, unless it was changed since; roles, badges, coins and pets are taken back; commands run their "when it ends" command). Due actions run every minute (task tebex-actions).
  • Refunds, chargebacks and ended subscriptions cancel what hasn't run and take back the rest (can be turned off). Each payment's page shows every action and its result, with Try again, Cancel and Take everything back.
  • Notifications (each can be turned off): a thank-you to the buyer in-game (when they're next online, within a week), an announcement to everyone online, and Discord webhooks with "Store purchases (Tebex)" ticked.
  • Give it to a player on a package's page runs its actions without a payment, to test them.
  • Making packages here: Tebex doesn't let other sites create packages, so make one on the panel (Make a package here: name, price, for a player or a crew), make a package with the same name on Tebex, fetch packages, then link the two on the panel package's page. From then on, saving it sends its name, price and on/off to Tebex (needs the server secret key from Tebex: Game Servers), and fetching keeps the panel's name and price.
  • Crew packages ("For: the buyer's crew") can give Crew: Premium, unlock a crew perk (cosmetics), give crew XP or message the crew. They go to the crew the buyer is in when they buy, are bound to it (leaving the crew doesn't take them along) and are taken back from that crew on a refund. Bought without a crew, the payment shows it as failed.
  • Discord: each purchase can be announced to Discord webhooks with "Store purchases (Tebex)" ticked, with your own message ({player}, {package}, Discord formatting). Can be turned off.
  • Tell staff when it's bought (on each package, for things staff set up by hand like custom ranks):
    • Discord: posts to webhooks with "Store: staff alerts" ticked, for example a private staff channel.
    • Email: emails staff in the roles you tick (none ticked: everyone with store.manage), with a link to the payment. Needs email set up in Settings and the queue worker running.
    • Message: your own text, with {player}, {uuid}, {package}, {crew}, {amount} and {transaction} filled in.
    • Not sent when staff give the package from the panel.
  • Store page (/store, public): players buy packages on the panel. Signed-in players buy for their linked Minecraft account; anyone else types their username first (they must have joined the network once). Each package shows Buy, or why not:
    • One-time (the default): it can't be bought again while an earlier purchase still applies (not refunded, not ended); crew packages count only purchases for the crew they're in now. Tick Unlimited purchases on a package for things bought again and again (coins, crew XP).
    • Not if they already have it (on by default): also blocked when they already have everything it gives, however they got it: the rank, the badge, the pet, or Crew: Premium / the crew perk for their current crew. Coins, XP, roles and commands don't count.
    • Buy sends them to Tebex checkout for that username (if Tebex asks them to sign in with Minecraft first, they come back and go on to checkout; signing in as someone else is checked again).
    • Nothing is sold while something's wrong: no public token or webhook secret, fetching packages failed or hasn't worked for 3 hours, or the store page is closed (Store page open in settings). A package isn't shown if it isn't linked to Tebex, is off the Tebex store, has no price, is not on sale or has Show on the store page unticked. The Store page lists what's wrong for staff, and if Tebex fails during checkout the player is told nothing was charged.
    • The limits only apply on the panel's store page; set the matching purchase limits on Tebex too if players can also buy directly on your Tebex webstore.
    • Descriptions on the store page are Tebex's (its formatting kept as Markdown), or your own: Description on the store page on a package, in Markdown. - Players not seen on the network yet (offline-mode names) get their actions when they first join. No emails, IP addresses or postal details from Tebex are kept.

Marketplace #

Marketplace (/marketplace, alias /market, /ah): players sell items to each other for the category's in-game money. Each category has its own marketplace, so items never reach another game mode. Turn it on with the "Marketplace" rule (off by default; a server can override it) and set the sales fee, listing fee, listings per player, price range and how long listings last on the group's settings. /marketplace sell <price> (e.g. 1.5k) takes the item in your hand and stores it on the panel; bought items, unsold items and sale money wait in your collection box until /marketplace collect (bought items are collected straight away). Staff see and take down listings under Economy and store → Marketplace (needs the marketplace.manage permission). When the category's "Auctions" rule is on too, the marketplace menu has an Auctions button that opens /auction, and the auction menu has a Marketplace button back. With either rule off, its button is hidden and the command stays closed.

Auctions #

Auctions (/auction, alias /auctions; network/Economy/Auction.sk): players auction items to each other for global coins, and the price goes up with each bid. Each category has its own auctions, so items never reach another game mode. Turn them on with the category's "Auctions" rule (off by default; a server can override it). Players can also reach them from the Auctions button in /marketplace while both rules are on.

  • /auction sell <starting bid> [hours] takes the item in your hand. It runs for 1 hour unless the seller says otherwise, up to 72 hours. /auction browses (ending soonest first); clicking an item bids the lowest amount allowed, and /auction bid <number> <amount> bids more. /auction mine lists your auctions (one with no bids can be cancelled) and /auction bids the ones you've bid on.
  • Minimum step. Each bid has to beat the last by the minimum step or a percentage of the last bid, whichever is more (10 coins or 5% by default). The first bid can be the starting bid.
  • Held coins. The panel takes a bid from the bidder straight away and holds it. Whoever is outbid gets their coins back at once and a chat message. Raising your own top bid only takes the difference.
  • Ending. The finish-auctions task (every minute) settles auctions whose time is up. The seller gets the top bid less the sales fee (5% by default). The item goes to the winner as an /inbox reward that can only be claimed in that category. If the winner is online in that category, their server claims it for them straight away; otherwise it waits in /inbox. Items nobody bid on, cancelled auctions and auctions staff take down go back to the seller the same way. Taking one down also gives the top bid back.
  • Lost replies. Selling uses the marketplace's request IDs: the item is kept on the server as pending until the panel answers, and checked after 90 seconds if no answer came, so it's never lost or copied.

Economy and store → Auctions (/manage/auctions, permission auctions.manage) lists each category's auctions by status, with an auction's bid history, and Take down. Its Settings set the usual and longest length (72 hours at most), the starting bid range, the minimum step and percentage, the sales fee, and how many auctions one player can run at once.

Discord webhooks with Auctions ticked (Settings → Discord webhooks) get a message for each new auction, each bid and each sale.

Coin exchange #

Coin exchange (/exchange; network/Economy/Exchange.sk): players swap global coins for the category's in-game money and back, at rates staff set. It's off everywhere until staff turn it on.

  • Settings. Economy and store → Coin exchange (/manage/coin-exchange, permission coinexchange.manage). Pick a category and set: on or off; Money for 1 coin (global coins to money) and Money it costs to get 1 coin (money to global coins), each of which can be turned off on its own; the least and most global coins per exchange; and an optional daily limit per player for each way. A server can have its own settings, which replace its category's completely; Use the category's settings goes back. Every change is in the audit log (coin_exchange.category, coin_exchange.server, coin_exchange.server_reset).
  • Rates. Up to 4 decimals. Players always type an amount of global coins. Money paid out is rounded down and money charged is rounded up, so rounding never favours the player. Every server in a category shares its money, so a rate that pays out more money per coin than any rate in that category charges to buy a coin back is refused (players could exchange back and forth for free money).
  • In game. /exchange opens a menu with the rates, what's left today and up to four quick amounts each way; /exchange money <coins> and /exchange coins <coins> do any amount. The menu shows "closed" where it's off.
  • Safe exchanges. The panel holds global coins and the game server holds money, so global coins to money takes the coins on the panel and the server pays the money on the panel's "ok"; money to global coins takes the money on the server first and gives it back if the panel refuses (including when the rate changed since the menu was opened). Each exchange carries the marketplace's request IDs: it's stored on the server until the panel answers, a resent request never happens twice, requests over a minute old are refused, and a lost reply is checked after 90 seconds, so money is only given (or given back) once the panel says for sure. Global coin changes show in the player's coin history as "Exchanged ..." with the server.
  • The latest 50 exchanges in the category are listed under the settings. The website can't exchange, because in-game money is only safe to change on the server the player is on.

Gatcha #

Gatcha (once called Wishes; /gatcha in game, and /wish and /gacha still work; network/Economy/Wish.sk; WishService, which keeps its old name inside the code, like its tables and the wishes.manage permission): players spend global coins on wishes, 1, 3 or 10 at a time. Each wish wins one prize, and the prizes wait in the player's gatcha storage until they collect them. It's off until staff turn it on, and it was not tried on a live server yet.

  • Settings. Economy and store → Gatcha (/manage/wishes, permission wishes.manage): on or off, global coins per wish (3 wishes cost 3 times that, 10 wishes 10 times), and the pity. It can be turned on once there's at least one prize that's on; turning every prize off pauses it (the menu says closed) and the page warns. Every change is in the audit log (wishes.settings, wishes.item_created, wishes.item_updated, wishes.item_deleted).
  • Prizes. Each has a name (colour codes work in game), a menu icon (1.8 material name, like DIAMOND or WOOL:14), a tier (one of the item rarity tiers, Items → Rarity; a prize whose tier is deleted counts as the default, Common), its own chance in percent with up to 4 decimals (any number of prizes, several can share a chance, and they don't have to add up to 100%), an order, and what it gives: global coins, a global value, a badge (its ID), a console command ({player}), a custom item (ID and amount), or days of a subscription: Premium, Crew: Premium or Island access (an island subscription). Subscription days are added to what the player has left. Crew: Premium goes to the winner's crew; a winner who isn't in a crew gets a Crew: Premium code with those days on their account to redeem later (see Crews). Subscription prizes can be collected on the portal as well as in game, and show in Premium and island subscription history as "A reward". Prizes can be turned off without deleting them. What a player won is copied when they win it, so changing or deleting a prize later doesn't change their storage.
  • Rolls. Always on the panel. A wish tries the prizes rarest first, each with its own chance; prizes with the same chance are tried in a random order. The first that hits is won. If none hits, it falls back to the most common prize (one at random when several share the highest chance). So with three 1% prizes, a 10% prize and a 60% prize, each 1% prize gets its 1% roll, then the 10%, then the 60%, and anything left goes to the 60% one. The staff list shows each prize's Really chance, what that order makes it (before pity, adding up to 100%); the in-game Odds and the portal show the same numbers (odds in the API; chance is the prize's own). Pity is counted per player across the game and the portal:
    • Rare or better every N: after N-1 wishes in a row without a rare or legendary prize, the next one is rolled over the rare and legendary prizes only (same order, falling back to the most common of them).
    • Legendary every N: after N-1 wishes in a row without a legendary, the next one is rolled over the legendary prizes only.
    • Soft pity from wish N, step S%: from the Nth wish without a legendary, each legendary prize's own chance goes up by S percent points each wish (they keep their place in the order).
    • "Rare or better" is and "Legendary" is pick which rarity tiers pity counts as those: that tier and every tier above it (Rare and Legendary to start with).
    • 0 turns any of them off. A legendary resets both counts, a rare resets the rare count. Prizes pity decided are marked "Pity".
  • Announcing wins (on): when someone wins a prize from From this tier up (Rare) it's told to everyone on that server ("Alice won Sky gem (Epic)!"). Players turn it off for their own wins with Announce my gatcha wins (Privacy, in /settings and on the portal; on by default).
  • Coins. The coins are taken and the prizes written in one transaction with the player's row locked, so two batches at once can't spend the same coins. Each batch has a request ID: sent twice (a double click, a resent request) it happens once. Coins show in the player's coin history as "Wish: 10 wishes".
  • In game. /gatcha opens the menu: the balance, wish once, 3 times or 10 times (with what it costs, or how many coins are missing), Your pity, Odds (every prize and its real chance, in chat) and Gatcha storage. After wishing, a short roll animation plays (prizes spin past in the result slots with a click each frame, slowing down, then stop one by one with a chime for each win: louder for rarer ones), then a results menu shows what was won (legendary ones glow) and it's listed in chat. Previous rolls in the menu lists the last 45, collected or not (the portal shows the last 20 under Your last rolls). In the storage, click a prize to collect it on that server, or Collect everything for the whole page. Custom items are handed over by that server straight away: into the inventory, and whatever doesn't fit drops at the player's feet. Gatcha storage stays open while it's off. Nothing is held on the game server, so a lost reply loses nothing: whatever was won is in the storage.
  • Portal. /gatcha and /wish (signed in, linked account; the menu link says Gatcha) show the same odds and pity, wish 1, 3 or 10 times, and list the gatcha storage. Global coins, badges, global values and subscription days can be collected there; items and commands are collected in game.
  • The latest 50 wishes are listed on the staff page with who won what, where and whether it's collected.

Stock market #

Stock market (/stocks in game, and /stock, /stockmarket and /shares; network/Economy/Stocks.sk; StockService): players invest global coins, and only global coins, in stocks staff make. Prices move on their own every 5 minutes; selling for more than was paid makes coins, selling for less loses some. It's off until staff turn it on, and it was not tried on a live server yet. (/market is the marketplace, so it isn't an alias.)

  • Settings. Economy and store → Stock market (/manage/stocks, permission stocks.manage): on or off, the trade fee (a percent of each buy and sell, up to 2 decimals, rounded up; 0 is none), the most shares a player can hold of one stock (0 is no limit), the most shares in one trade, and how many days of prices to keep. It can be turned on once there's a stock that's on. Every change is in the audit log (stocks.settings, stocks.created, stocks.updated, stocks.deleted).
  • Stocks. Each has a name, a ticker (2 to 6 letters, unique, like NEU), a menu icon (a 1.8 material name), an optional one-line description, a starting price, a floor it never goes below and an optional ceiling it never goes above, a volatility (the biggest random move each update, either way, in %; small moves are more likely) and a drift (a steady % added each update; negative trends down). Changing Price now sets the price straight away. A stock that's off can't be bought and its price stands still, but players who hold it still see it and can sell it. A stock players still hold can't be deleted; turn it off instead. The page shows each stock's price, 24 hour change, a small chart, its limits and how many shares players hold, and the latest 50 trades.
  • Prices. The stock-prices scheduled task (network:stock-prices, every 5 minutes, Servers → Scheduled tasks) moves every stock that's on by one random step while the market is on, and forgets prices older than the history setting. Prices are kept in hundredths of a coin, so a share can cost 12.34. Every price is kept for the charts and the 24 hour change.
  • Coins. Buying costs shares × price, rounded up, plus the fee; selling pays shares × price, rounded down, minus the fee. The coins and shares change in one transaction with the player's row locked, and each trade carries a request ID, so a click sent twice is one trade. Trades show in the player's coin history as "Stocks: bought 10 NEU at 12.50" and "Stocks: sold 4 NEU at 25". Buying stocks doesn't count as spending for quests and badges, since the coins can come back. Each holding remembers what was paid for it (fees included); selling part of it takes that share of the cost off, so profit and loss stay right.
  • In game. /stocks opens the market on every server (Pit on 1.8 too): the balance and fee, every stock with its price, 24 hour change (green up, red down), the shares held, what they're worth and the profit. Clicking a stock opens its trade menu: buy 1, 10 or 100 (with the cost, or how many coins are missing), sell 1, 10 or 100 (with what you'd get) and Sell all. Your portfolio lists only the stocks held, with what they're worth altogether, what was paid and the profit. Nothing is held on the game server, so a lost reply loses nothing.
  • Portal. /stocks (the menu link says Stock market) shows every stock with its price, change and a 24 hour chart to anyone signed in; with a linked account, the balance, the portfolio, buying and selling any number of shares, and the last 20 trades.

Money without Essentials #

In-game money is {coins::<uuid>}, saved on the panel. Survival used Skript's player's balance, which only loads while an economy plugin (Essentials) is registered with Vault. It now reads Vault's API directly (Net_Economy, Net_EcoBalance, Net_EcoChange in core/Support/Compat.sk): with an economy plugin, SurvivalBridge.sk keeps it in step with {coins::} both ways, so other plugins' shops still work; without one, {coins::} is the balance. Removing Essentials loses no money, since {coins::} already held the same amount. /balance [player] (/bal, network/Economy/Coins.sk) shows it; while Essentials is installed its own /balance may answer instead, with the same number. There's no /baltop or /eco yet, and other plugins that need a Vault economy need an economy plugin.

Store and Premium page #

Economy and store > Store and Premium (/manage/paypal) is the one place for everything players pay for. Each part is a section that folds open, and staff see the parts their permissions cover: Player Premium, Player and Crew: Premium for global coins and Crew: Premium (premium.manage); Pets Premium, Island subscription, Discount codes (a link to its own page), Products, PayPal settings and Recent payments (store.manage); and Gift cards (giftcards.manage, a link to its own page). The old Premium page (/manage/premium) opens this page at Player Premium.

Player Premium #

One paid tier, shown in gold (a gold name in chat and on the portal, and {premium} in the chat format). The Player Premium section of the Store and Premium page (premium.manage) chooses what it gives:

  • homes per server (10, unless a rank gives more) and friends (unlimited)
  • the marketplace fees Premium sellers pay (none by default; empty uses the category's fees)
  • every chat colour, /fly on servers whose category is ticked Lobby, and early access
  • no chat spam limits, and gradient text in chat, while those are set that way under Moderation > Chat filter > Chat text and spam (see Moderation)
  • which custom messages are Premium-only, and rewards on each paid purchase or renewal
  • the player API limits (150 a minute, 300 with Premium)

Buying Premium with global coins. Off by default. On the Store and Premium page, in the Player and Crew: Premium for global coins section, tick the box and set up to 6 offers each (days and price) for Player Premium and Crew: Premium. Players buy them in-game with /store (or /premium), which also shows how long they and their crew have left, or on the website store (/premium), where each section gets an Or pay with list of the same offers. On the website they need to be signed in with a linked Minecraft account, because the coins are that player's (POST /premium/coins, premium.coins). Player Premium is for the buyer; Crew: Premium is for the crew they're in (any member can buy it). The coins are taken first, then the days are added to what's left, like a store purchase. These grants show as Paid with global coins; Premium's purchase rewards aren't given for them. A price changed while someone had the menu open is refused, not charged.

Premium is a list of grants (premium_grants): stretches stack, lifetime wins, and players.premium_until keeps the end. Staff give or take it on a player's page. Servers get premium.until at login and on changes and work out expiry themselves (network/Economy/Premium.sk). Players who linked Discord can also get a Premium role there (see Discord Premium roles).

The whitelist page has an Access column for each scope: In development (staff only) or Early access (staff and Premium players). The most specific scope that sets one wins.

Store (PayPal) and credits #

The store takes PayPal only (Tebex was removed; the website's /store and its old links redirect to /premium, and the old staff pages to the new one). The Products and PayPal settings sections of the Store and Premium page (store.manage) set up PayPal and the products: Premium for some days (one payment, also payable with credits), monthly Premium (a PayPal subscription), Crew: Premium for some days (one payment or credits, for a crew by its tag), and credit packs. Island subscriptions can also be paid for with PayPal, off by default and set up on Survival → Island subscriptions (see Survival → Island subscriptions). So can Pets Premium, set up in the Pets Premium box on the Store page (see Island subscription and Pets Premium in the store above). Nothing can be bought until a business email is set (and, for subscriptions, the REST app, secret and webhook ID).

  • One-time payments use PayPal Standard and IPN (/api/v1/paypal/ipn). Each message is posted back to PayPal to check it, then the receiver, currency and amount must match. A transaction ID is used once; refunds and reversals take back what it gave.
  • Subscriptions use the REST API. Webhooks (/api/v1/paypal/webhook) are checked with verify-webhook-signature; each PAYMENT.SALE.COMPLETED adds a period. Cancelling stops renewals; Premium runs to the end of what was paid.
  • Credits are a prepaid balance on the player (players.credits, credit_transactions), never below zero. Staff give or take them on a player's page (credits.grant).

Players buy at /premium (Premium for any username, Crew: Premium for any approved crew's tag, credits only for their own signed-in account) and see Premium, subscriptions and credits at Account > Premium and credits.

  • The store shows a free-against-Premium table for Player Premium and for Crew: Premium, built from the live settings (App\Support\StorePerks): only perks with a free side go in the table, and the rest follow as "Plus some extras: ...". A perk staff turn off isn't listed.
  • Crew: Premium bought in the store adds its days to what the crew has left (crew_unlocks.expires_at); one given for good by staff stays for good. A refund takes its days off again, and network:expire-perks ends it when it runs out.
  • Each purchase posts to Discord webhooks with Store purchases ticked. The last few PayPal purchases show under Recent purchases, without prices, unless the player turned off "Show my store purchases".

Island subscription and Pets Premium in the store #

The in-game store (/store, or /premium; network/Economy/Premium.sk) has a fourth row under the Premium offers: the island subscription and Pets Premium. Each shows what it gives, its lowest coin price and how many lengths there are, and the player's status (Active until a date and time in UTC, or that they don't have it). Left-click opens a menu with one item per length (days, price and the staff label), then a confirm screen like Premium's, with a Back arrow to the store; right-click, when the portal store takes PayPal for it, sends a clickable link to the store section. The website store (/premium) lists both too, in their own sections (#island and #pets-premium), with a coin button per length (its label shown as a tag) and a Pay with PayPal button when that is on. Both need a signed-in account with a linked Minecraft account, because they are that player's. A purchase adds its days to what's left. A price changed while the menu was open, or a length staff removed, is refused, not charged.

Lengths for global coins. Each of the two has up to 6 options, set as rows of days (1 to 365), price (above 0, up to 2 decimal places) and an optional label of up to 30 characters (for example "Best value"). Leave a row empty to remove it. Saving is refused when a row has days out of range, a price of 0 or more than 2 decimal places, or the same day count as another row, and when no row is left. Rows are kept shortest first (App\Support\CoinOffers, saved as offers in the islands.subscription and pets.premium settings). Until staff save rows, the single price and length from before is the only option. The shortest option is also kept as coin_price and coin_days, so /island subscribe keeps selling the shortest length. Unticking Can be bought with global coins keeps the rows for later. PayPal still sells one length each.

  • Island subscription uses the island settings (Survival → Island subscriptions: the lengths for coins, and the PayPal option). The Store page shows its current prices with a link there. See Survival → Island subscriptions.
  • Pets Premium (App\Services\PetPremiumService, table pet_premiums) gives the Premium pet looks (size, trail, glow, level stars, chosen on the portal's Pets page) without Player Premium. Player Premium still gives them too. Staff set it in the Pets Premium section of the Store and Premium page: buying with global coins on or off (on by default), its lengths for coins (30 days for 500 by default), and the PayPal option (off by default: on or off, price and days). The PayPal option is a store product of kind pets_premium, kept in that box rather than the product list. PayPal goes through the same IPN as the rest of the store. Refunds and chargebacks take the days back. When Premium pet looks is off on Pets → Settings, Pets Premium gives nothing, so it isn't for sale.
  • Coin purchases are in the audit log (islands.subscription.coins, pets.premium.coins), as are paid ones and settings changes (pets.premium.paid, pets.premium.settings).

Gift cards #

Gift cards (/manage/gift-cards, permission giftcards.manage, opened from the Gift cards section of the Store and Premium page) are codes that add account credits when redeemed (App\Services\GiftCardService, table gift_cards).

  • Buying one: players buy a card at /premium/gift-card (linked from the store) while signed in. Staff choose what's sold under What the store sells: on or off, the amounts (for example 5, 10, 25, 50 in the store currency), optionally any amount between a lowest and highest, and how many credits each 1 of the currency is worth (100 by default). A card keeps the credits it was bought with if that rate changes later. The buyer sends it to a Minecraft username or an email with a message, or keeps the code. Payment is a PayPal one-time payment through the same IPN as the rest of the store: the card waits as Waiting for payment until PayPal confirms the right amount and currency to the right account, then becomes redeemable. Needs PayPal one-time payments on the Store page.
  • Delivery: the recipient gets an email with the code (to the email given, or to a username's verified account email) and, for a username, an in-game notification and the card waiting on their Account > Gift cards page with a one-click Redeem. The buyer gets a receipt by email, with the code only if they kept it. Email uses the panel's mail settings; if mail fails, the card still works and the code is on the buyer's page (kept cards only).
  • Refunds and chargebacks (PayPal Refunded or Reversed): an unused card is disabled; a used one has its credits taken back (never below zero). A reversal is also handled as a chargeback like any store payment.
  • Making cards by hand: Make gift cards makes one card or a batch of up to 500, each with the same credits, an optional last day it can be redeemed and an optional staff note. The full codes are shown once, right after; a batch can be exported straight away.
  • The list shows every card with its code masked (XXXX-XXXX-XXXX-AB12), credits, balance, who bought or made it, who redeemed it and its status (Waiting for payment, Not redeemed, Redeemed, Disabled, Expired). Search by a full code, its last four characters, a batch, a player, an email or a note. Disable stops a card that hasn't been redeemed. Export these as CSV downloads the cards on the list; it has full codes only for cards staff made, never for bought ones.
  • Redeeming: on the portal at Account > Gift cards (/account/gift-cards), or in-game with /redeem <code> (network/Economy/GiftCards.sk, POST /api/v1/server/gift-cards). Case, dashes and spaces don't matter. The whole card goes to the account's credits at once: credits are already a balance, so cards don't keep a partial balance. The account needs a linked Minecraft account.
  • Security: codes are 16 characters from an alphabet without 0, O, 1, I or L (about 79 bits). The panel stores an HMAC of the code (keyed with APP_KEY) to look it up, plus the code encrypted for the buyer, recipient and staff export; lists only show the last four. Redeeming runs in a transaction with a row lock, so a code works once. Wrong tries are limited to 5 per account and 10 per IP every 10 minutes (in-game, per account only, since the server's IP is shared); while locked out even a right code is refused. Every creation, purchase, redemption, disable, export and settings change is in the audit log.

Discount codes #

Discount codes (/manage/discount-codes, permission store.manage, opened from the Discount codes section of the Store and Premium page) take money off what the store sells (App\Services\DiscountCodeService, tables discount_codes and discount_code_uses).

  • A code has its text (3 to 40 letters, numbers, - and _; case doesn't matter), a staff note, and either a percentage off or a fixed amount off. A fixed amount is set for each way of paying it works with: an amount in the store currency for PayPal, credits, and global coins (up to 2 decimal places). Prices are rounded to the cent (whole credits), and a code never makes anything free: it costs at least 0.01 (1 credit).
  • What it's for: any of Player Premium, Crew: Premium, Pets Premium, the island subscription, credit packs and gift cards, and/or chosen store products; paid with any of PayPal, credits and global coins. Recurring PayPal subscriptions can't take a code (their price is fixed on the PayPal plan).
  • Limits: an optional last day (the code works until the end of it), uses in all, and uses for each player. On turns it off without deleting it; a code that has been used can't be deleted, only turned off.
  • Unlock conditions (App\Support\DiscountConditions): up to 20, and the player needs all of them or any one. Each reads data the panel already keeps: quests finished (any or one quest), daily quests finished, quests finished this week, network level, playtime (hours), days since first joining, age verified, email verified, Discord linked, dungeons cleared (any or one dungeon), dungeons cleared of a difficulty, bosses beaten (the boss_kills stat), Tag wins, in a crew, crew level, rank (any of a list), Player Premium (has it or doesn't), votes, vote streak, job level (any or one job), a badge, badges earned, pet level, and first purchase only (never paid with PayPal, never spent credits, and never bought Premium, Pets Premium or an island subscription with coins). A player who doesn't meet them is told what's missing.
  • Using one: the player must be signed in with a linked Minecraft account (conditions and limits are theirs; they can still buy Premium for a friend with it). On the website store, Discount code at the top applies it for the visit (?code=, kept in the session; Take it off removes it): every price it works on shows crossed out with the new one, and every buy button sends the code and the price shown. The product page (/premium/{product}) and the gift card page have their own code field. In game, /store code <code> (or /premium code <code>) does the same in the /store menu, where a name tag says what the code does (click it to take the code off); /store code on its own takes it off.
  • The price shown is the price charged. The store sends back the price it showed; when it doesn't match the price with the code now (the code ran out, the offer changed), nothing is taken and the player is told the price has changed. For PayPal, the checkout keeps the discounted amount (store_checkouts.amount; a gift card's own price is the discounted one) and the IPN checks the payment against it, so paying the full price or anything else is refused like any wrong amount.
  • Never overused: using a code locks its row in the purchase's database transaction and checks the limits again, so two purchases at the same moment can't both take the last use. A PayPal checkout holds a use (Waiting for PayPal) for 2 hours; the IPN marks it used. A checkout that's never paid stops holding it, and starting a new checkout with the same code lets go of the old one. A payment that arrives after the hold ran out still counts, since the discounted price was paid. Refunds don't give a use back.
  • Wrong codes are limited to 10 per player every 10 minutes.
  • Uses: each code's page lists who used it, on what, the price before and after, how they paid and the payment reference (coins:, credits: or paypal:).
  • Reward templates: tick Reward template to make a code that can't be used itself. The Store discount code (one-time, personal) reward type (RewardService, type discount_code, value the template's ID) gives a player a personal copy with a random code (R-XXXX-XXXX): one use, only by them, ending Each copy lasts days after it's given (or on the template's last day). It's offered wherever rewards are set: quests and quest steps, daily quest bonuses, dungeons, level rewards, job levels, votes, events, referrals, achievements, quizzes, the reward inbox, Premium purchase rewards and Gatcha prizes (not feedback forms). Players see their unused codes on Account > Premium and credits (with a link that applies it on the store) and in game with /store codes. Staff see personal codes under Personal codes given and can turn one off.
  • Audit log: making, changing, turning on or off and deleting codes (discounts.created, discounts.updated, discounts.enabled, discounts.disabled, discounts.deleted), every use (discounts.used, and discounts.held when a PayPal checkout starts), and personal codes given (discounts.given). Coin purchases with a code also note it on their own entry (premium.coins, pets.premium.coins and so on).

Marketplace replies that never arrive #

Servers take the buyer's money (or the seller's item and fee) before asking the panel. Each buy and sell carries a request ID (<unix>-<random>): the panel never does one twice and refuses it after a minute. If the reply is lost, the server keeps it pending ({market::pending::*}) and asks (check) after 90 seconds, giving it back only if it didn't happen. Before, a lost reply was refunded straight away, so a buyer could get the item and the money back, and a seller could copy an item.

Currency name #

The network-wide currency (global_coins in the database) is called Neuco. Game > Currency (currency.manage, owners only until you add it to a role) renames it, and saving it empty goes back to Neuco. The name is used as it is for any amount (1 Neuco, 500 Neuco), so letters, numbers, spaces, ' and - only, up to 24 characters.

Panel pages and replies use App\Support\CoinName. Game and panel text say {currency}, or {CURRENCY} for capitals in tags like &6&lNEUCO. Servers get the name with their config (currency in the group wire) and fill it in through Tr_Currency in network/Chat/Translations.sk, so they need the updated core/Support/Compat.sk, core/Players/Storage.sk and network/Chat/Translations.sk. Translations saved before the rename still have the old wording until staff change them to use {currency}.

Currency decimals #

Global coins can have up to 2 decimal places (12.50 Neuco). This covers the balance (players.global_coins), its history (coin_transactions), and what gives coins: the "{currency}" row of any rewards list (quests, levels, badges, dungeons, feedback and so on), staff Give or take on a player's page, feedback rewards, payroll, /pay and the coin exchange limits and amounts. Prices in shops, pets, effects, auctions, bounties, stocks, gatcha, islands and Premium stay whole numbers; a decimal balance pays them as usual.

  • Stored as decimal(16, 2) and read with the decimal:2 cast, so PHP sees exact text like "12.50". All sums go through App\Support\Coins in whole cents (integers), never floats, so no fraction is lost or made up. Every coin change still goes through CoinService.
  • Typed in with up to 2 places (Coins::rule(), numeric): 12, 12.5 and 12.50 work; 12.345 is refused, not rounded.
  • Shown as 1,250 or 1,250.50: .00 is hidden, any other fraction shows both places (Coins::format). Player pages show the exact amount under 1,000, then short like 1.2K (Coins::short).
  • Sent to servers as JSON numbers (1250, 12.5) by Coins::wire. Servers send amounts back as text with 2 places (Net_CoinsWire in core/Support/Compat.sk), so a double's extra digits never reach the panel. In game, Net_Coins(n) shows an amount exactly and Net_CoinsShort(n) shows it short over 1,000.
  • Multipliers (the weekly dungeon multiplier, hardcore x3) and percentages (combat logging's "lose 10%") round down to the cent, in integer maths, so they never make up a fraction. The coin exchange rounds money paid out down and money charged up, as before, now from the exact coin amount.
  • Quest and badge counters for coins spent count whole coins only.

To change the number of places, change Coins::PLACES and Coins::SCALE, the migration's column scale, the decimal:2 casts, Coins::PATTERN, and the Skript Net_Coins* functions.

Item Shop categories and stock #

/shop (network/Economy/Shop.sk) opens on its categories when a group sells from more than one: Weapons, Armour, Tools, Food and potions, Blocks and Other, set per item under Game > Loadouts and shop. Each category lists its items, with a button back. A shop with one category opens straight on its items.

An item can have a stock: how many lots /shop has left, shared by everyone in that group. Leave it empty for unlimited. Buying takes from it (a stack is cut down to what's left), selling to the shop puts lots back, and staff can top it up with Add stock on the item's page (audited as shop.item_stock). Saving the item form with the stock box unchanged keeps the live count, so sales made while the page was open aren't undone. When it runs out, the item either shows as Out of stock or is left out of /shop, as chosen on the item. Loadouts don't use stock.