Game benefits have not arrived

Find where processing stopped: purchase, benefit activation, Agent, RCON destination, or command.

Payment completion and delivery inside a game are separate stages. Follow the checks for buyers or server operators below.

When a timeout leaves the result unknown

Do not repeatedly run processing whose result is unknown.

A command may already have run in the game even if no response was received. Check the player's items, permissions, and game logs to avoid granting the same benefit twice.

Do not delete the Agent's state file to force another execution. If you cannot determine what happened, contact support with the processing ID and execution time.

Checks for buyers

Log in with the Discord account you used for the purchase.
In purchase management, check the server, product, and payment status.
Check that the game ID registered for the product matches the intended in-game account.
Ask the server operator who sold the product about its benefits and delivery inside the game.

Include your purchase number, product name, purchase date and time, and a description of the problem. Do not send connection passwords or Agent credentials.

Copy and fill in this template when contacting the server operator.

Inquiry template

Purchase number:
Product name:
Purchase date and time:
What happened:

Checks for server operators

Open the relevant server and review its purchases and processing history.

Stage	Main checks
Purchase	Payment status, product, and buyer
Benefit	Whether it is active and whether its validity period has ended
Delivery processing	Agent, destination, command, buyer ID, and result
In the game	Whether the intended player actually received the benefit

Check the Agent and RCON separately

The Agent is a connection program that runs on the game-server side. An online Agent does not necessarily mean that it can connect to the game's RCON service.

Agent is disconnected: check whether the Agent is running and can communicate.
Destination connection error: check the address, port, password, and game-side RCON settings.
Command execution error: check the command, target ID, required plugins, and the game's execution requirements.

For initial setup, see Agent preparation and game-specific examples.

After correcting the cause

Retry processing when the interface offers a retry action. Acceptance of a retry is separate from success, so check the new result and the actual state inside the game.

Multiple commands run from top to bottom. If one fails, later commands stop. Lines that already succeeded are excluded from retry. Check how far execution progressed before continuing recovery.