Skip to main content

Shop system

This page describes how server admins maintain the shop catalog, orders, and subscriptions in daily operations.

For behavior from the player perspective and the overall concept, see:

Admin areas involved​

Navigation paths:

  • Server Admin -> Items
  • Server Admin -> Item categories
  • Server Admin -> Orders
  • Server Admin -> Transactions
  • Server Admin -> Subscriptions -> Available
  • Server Admin -> Subscriptions -> Active

Maintaining item categories​

  • Create categories and keep names unique per server.
  • Control category ordering (move up/down), which also drives frontend grouping order.
  • Restrict whole categories by allowed groups.
  • Deleting a category does not delete item sets; those item sets lose their category assignment and appear in the Without category tab in Server Admin -> Items.
  • Category restrictions are marked with a shield icon in Server Admin -> Item categories and on category tabs in Server Admin -> Items. Hover the icon to see allowed groups.

Maintaining item sets​

  • Create and edit item sets with:
    • name, description, image URL,
    • price,
    • item list,
    • availability flag,
    • per-player max orders and period (lifetime/daily/weekly/monthly),
    • allowed groups,
    • assigned category.
  • Deleting an item set removes it from future purchases; historical orders stay visible in order history.
  • Item-set restrictions are marked with a shield icon in Server Admin -> Items. Hover the icon to see allowed groups.

Order operations for admins​

  • Overview supports filtering by players, item names, and item sets.
  • Manual order creation supports:
    • target player (optional),
    • place-based or manual coordinates,
    • item sets and manual item lines.
  • Order details provide three key operations:
    • Cancel (undelivered only): marks order canceled.
    • Refund (delivered only): partial or full by quantity, with required reason and player balance credit.
    • Redeliver (delivered only): creates zero-cost follow-up order linked to original order.

Operational notes:

  • Redelivery is quantity-capped by prior redelivery history.
  • Refund tracking is quantity-based per order item to avoid over-refunding.

Transaction overview for admins​

  • The overview is read-only and meant for auditing money flow across the server.
  • Filters support player, description, date/time range, amount range, and category.
  • Use it to trace refunds, transfers, automated payouts, or admin balance adjustments before drilling into a specific player.
  • Direct balance changes still happen in Server Admin -> Players -> Player details -> Transactions.

Subscription operations for admins​

  • Available subscriptions (offers): template definitions players can purchase.
    • Create, edit, activate/deactivate, remove.
  • Active subscriptions: concrete spawn subscriptions currently used by players/factions.
    • Create/edit/remove, reassign owner, and update location details.
    • Filtering by search, owner, faction, or map radius helps with operations at scale.

Permissions and access rights​

  • Shop catalog maintenance uses itemsets.view, itemsets.edit, itemsets.delete.
  • Order operations use orders.view, orders.create, orders.refund, orders.change, orders.redeliver.
  • Transaction overview uses players.view. Balance changes on player details use players.change_money.
  • Subscription maintenance uses subscriptions.view_active, subscriptions.create_active, subscriptions.edit_active, subscriptions.delete_active, subscriptions.view_available, subscriptions.create_available, subscriptions.edit_available, subscriptions.delete_available.
  • Player-facing subscription usage is separate: subscriptions.use.

Make sure role templates include the required action-level rights, not just broad section visibility.