Owner setup
Owners configure the trader files, shop channel, delivery rules, restart handling and forced trader location. The setup file controls item names, prices, attachments and supported shop entries.
Trader cart system
Shoppi Trader and Cart Commands
Shoppi is the trader/cart workflow for Legion economy servers, designed to convert Discord shop orders into Object Spawner JSON files that can be picked up by the server-side spawn flow.
Shoppi is documented here so owners can understand the intended flow, command surface and file behaviour. It should not be presented to players as an active production feature until it is re-enabled.
What Shoppi is meant to do
Player cart
Players browse item/pricing output, add items to a cart, view the cart, clear it or checkout. Checkout is designed to charge the linked economy account and prepare the order file.
Object Spawner output
The checkout flow converts the cart into Object Spawner JSON entries so the bought items can be spawned by the server-side process instead of staff manually placing every order.
How the internal proxy flow works
At checkout, Legion builds an order from the player’s cart, item attachments and delivery rules. It
creates an Object Spawner JSON file named for the Discord user, such as LK_123456789.json,
uploads it into the server mission custom folder and records it in the scheduler/proxy list so the server
can load the order at restart.
When delivery is forced to a trader location, the order uses the configured trader position and a
per-user spawn slot. When delivery is allowed by player location, the player uses
/shoppi delivery or a linked location command flow to set where the object-spawner file
should place the items. The system checks server state and restart timing so orders are not uploaded into
a restart window that is too close to safely process.
Settings that control it
| Area | Control | Purpose |
|---|---|---|
| Trader setup | /trader setup |
Uploads the shop configuration file and assigns trader channels. |
| Config seed | /trader config start |
Sends starter/config files for owners preparing the trader setup. |
| Restart rules | /trader config restarts and /shoppi mode |
Controls the restart timing and whether Shoppi-managed restart handling is active. |
| Delivery point | /trader config location, /shoppi delivery and
/locate |
Controls forced trader delivery, player-selected delivery coordinates and last-known-player location support. |
| Player purchase | /shoppi cart add, /shoppi cart view,
/shoppi cart clear and /shoppi cart checkout |
Builds the cart and turns it into the JSON order when checkout is allowed. |
Command paths
| Command | Options | Use |
|---|---|---|
/trader config start |
Starter config flow. | Sends the base files for trader setup. |
/trader setup |
Configuration file and channel setup. | Uploads shop items and assigns trader channels. |
/trader config restarts |
Restart interval and bot restart handling. | Controls restart timing used by checkout upload flow. |
/trader config location |
Trader location or disabled forced location. | Controls where Shoppi orders spawn when using fixed trader delivery. |
/shoppi pricing |
Pricing output. | Posts pricing information for players. |
/shoppi items |
Item lookup. | Shows item details, attachments, ammo and magazines. |
/shoppi cart add |
Item and quantity flow. | Adds configured shop entries to the cart. |
/shoppi cart view |
No required options. | Shows current cart before checkout. |
/shoppi cart checkout |
Checkout flow. | Pays, uploads the Object Spawner JSON order and queues the proxy/spawn flow when enabled. |
/shoppi status |
Status view. | Shows Shoppi state and pending order information. |
/shoppi mode |
Enable or disable bot-managed restart handling. | Controls whether Shoppi manages its restart/spawn cycle. |
/shoppi delivery |
Coordinates for item spawn. | Sets player delivery coordinates when fixed trader delivery is not forced. |
/locate |
Linked player location lookup. | Supports delivery/location checks from stored player position data. |