Command Delivery

When a customer completes a purchase, FluxStore queues the associated commands and delivers them to your Minecraft servers over WebSocket. If the target server is offline or the player isn’t online (for commands that require the player to be present), commands stay queued until conditions are met.

Command Lifecycle

Each command has one of three statuses:

Managing Commands

From the order detail view (Dashboard > Orders > click an order), you can manage individual commands:

• Resend queues a failed or executed command again. The command gets a fresh pending status and is delivered on the next opportunity.
• Edit lets you modify the command string of any pending command before delivery. Once a command has been executed or failed, it can’t be edited, but you can resend it.
• Cancel removes a pending command from the queue so it won’t be sent to the server.

Bulk Resend

If commands failed during a server outage, you can bulk resend all commands from a specific time window. Go to Dashboard > Orders, click Bulk Resend, and select a start and end date. All failed or pending commands within that range are queued again for delivery.

Global Commands

Global commands execute on every connected server rather than a specific one. This is useful for announcements across your whole network, or running a command on all servers at once (for example, granting a permission on every server in a BungeeCord network).

When configuring a package command, select All Servers as the target instead of a specific server.

Variables

Commands support placeholder variables that are replaced with values from the order at execution time. See the variables reference for available placeholders.

Example Commands

give {player} diamond 64
lp user {player} parent set vip
say {player} just purchased VIP for ${price}!

Next Steps

• Managing Orders to view and manage your store’s orders
• Server Setup to connect your Minecraft server to FluxStore