Skip to main content
Run a controlled test before you use server delivery for live purchases. Use a dedicated product and test account so the result cannot affect a player’s normal inventory or progress.

​
Run a controlled delivery test

1

Confirm the delivery connection

For a plugin or script executor, run gamecart status from the server or proxy console. For RCON, confirm that the server integration’s RCON settings are correct.
2

Prepare test data

Create a test product and use an account identifier that you can inspect on the target server.
3

Place the test order

Use a safe payment or test path that is available to your store. Complete the controlled order through your storefront.
4

Follow the command

Open Commands in the dashboard and watch the command status.
5

Verify the result

Check the target server for the expected result. A console that accepts a dispatch does not prove that the command worked as intended.

​
Understand command states

Command queue with scheduled, failed, and executed statuses highlighted

Use the Commands page to distinguish queued, failed, and completed delivery attempts.

​
Troubleshoot common symptoms

Resend creates a new delivery attempt and may duplicate a command that already ran. Stop any duplicate executor installations, inspect the server, and confirm the dashboard warning before you proceed.
Resend warning dialog with the duplicate-delivery message and confirmation action highlighted

Read and accept the duplicate-delivery risk only after you verify the original attempt.

If the problem continues, record the visible command status and safe runtime information before you contact support. Do not share tokens, credentials, or buyer data.