Dashboard
Operations analytics
Revenue, account activity and fulfilment trends.
- Claimed
- Pending
Server systems
Audit trail
Common tasks
Store products
Manage vehicles and purchasable server products.
Discount codes
Control active promotions, limits and usage.
| Code | Value | Applies to | Usage | Status |
|---|
Payment history
Detailed transaction data stored by the module.
Store categories
Categories used by products and store filters.
VIP memberships
Prices, benefits, reward pools and delivery rules.
Reward cases
Configure case prices and server-verified prize chances.
Lucky wheels
Daily spins, cooldowns and prize pools.
Lotteries
Ticket prices, prizes, deadlines and participants.
Auctions
Starting prices, bid steps and scheduled windows.
Recent gifts
| Gift | Recipient | Sender | Created | Status |
|---|
Configured assets
Administrators
Discord identities and scoped permissions.
Available roles
Audit log
Administrative configuration changes and system events.
MSX Bridge
One fulfillment contract for store orders, cases, lotteries, auctions, gifts, VIP access and player inventory claims.
Supported delivery
Delivery lifecycle
- 1Payment or rewardStore, case, lottery, auction or admin gift creates one payload.
- 2Claim inventoryThe player selects a character and confirms delivery.
- 3MSX validationSecret, identity, model and required fields are validated.
- 4FiveM fulfillmentFramework adapter writes the reward or grants it online.
- 5Idempotent receiptThe claim ID prevents duplicate delivery after retries.
Required configuration
MSX_BRIDGE_URL=http://127.0.0.1:30120/msx_bridge
MSX_BRIDGE_SECRET=replace-with-long-random-secret
MSX_WEB_CLAIM_SECRET=replace-with-long-random-secretset msx_bridge_secret "replace-with-long-random-secret"
set msx_bridge_framework "auto"
set msx_website_url "https://your-domain.example"
ensure oxmysql
ensure msx_bridgeModule control center
Manage public content, navigation, player features, visual language and integrations from one persistent workspace.
Every public system, one control surface
Settings are grouped by responsibility and persisted inside moduleSettings.operations. Existing product, VIP, reward, event and player records remain managed in their dedicated admin screens.
collections.navigationcollections.footerColumnscollections.socialLinkscollections.partnerRailcollections.announcementscollections.newscollections.rulescollections.wikicollections.teamcollections.careerscollections.mapMarkerscollections.updateLogscollections.quickFindcollections.emailTemplatescollections.webhookscollections.redirectscollections.featureFlagsDirect JSON editing bypasses individual field controls. Invalid structure can break storefront features.
