How delivery works

Why goods arrive a moment later rather than instantly, what the delivery states mean, and when to ask.

Store and deliveryUpdated 4 September 2026about 2 min

The direction things move#

This is worth understanding once, because it explains every question people
have about timing.

The game server fetches. This website does not push.

The website and the game run on different machines. If the website pushed
commands, it would need a permanently open console port on the game server
reachable from the internet, and the protocol that would use transmits without
encryption. Fetching needs no open port at all — the game server asks, with a
token, and takes what is waiting for it.

The trade: delivery is not instantaneous. It happens on the next fetch.

The two things that get created#

When a payment is confirmed, two records appear:

An entitlement — the record that says you are owed this. It is created
immediately and it does not disappear if something goes wrong later. This is
the thing that means "you paid, we owe you", and it survives everything.

A delivery job — the command that hands it over in game. This is what runs
when the game server fetches.

They are separate on purpose. If the second one has trouble, the first one is
still there, and the team can act on it.

The states you will see#

On Account → Ranks and on your order:

StateMeaning
QueuedWaiting for the game server to fetch. Normal.
RunningThe game server has taken it and is executing.
RetryAn attempt failed and it will be tried again.
FailedIt gave up after repeated attempts. A human needs to look.

Retry is not an error you need to report. A failed attempt is usually the
game server restarting, and the next one succeeds. Up to five attempts are
made before anything is marked as failed.

Failed is worth reporting, with your order number.

Do you need to be online?#

No. Deliveries do not require you to be in game — a rank or a key waiting for
an offline player is applied the same way.

When something cannot be delivered#

There is a case where nothing is even attempted: when the command could not be
built. The most common reason is a Minecraft name that cannot be used —
a typo, or characters that are not valid in a name.

That is deliberate. A guessed command would burn five delivery attempts and end
as failed, while you sat there waiting. An entitlement with no job stays
visibly open instead, and the team can fix the name and requeue it.

Which is the practical reason to get the name right the first time:
Your Minecraft name.

Discuss this

The wiki explains it. The forum is where you can ask about it.

Open the topic in the forum

Related