Automatic redemption can reduce repeated manual work, but it is not a promise that every code will reach every player. Code eligibility, expiry, service availability and correct setup still matter.
Manual redemption
The official wiki instructions direct players to find their Player ID, enter it and the code in the publisher's Gift Code Center, then check in-game mail for rewards.
Follow the publisher's current form and error messages. Never give a bot your account password. A code listed on HQ's gift-code page may stop working after its last recorded check; its status is not a guarantee of eligibility for your player.
What alliance setup requires
These steps describe the repository implementation, not a verified test of every live installation:
- Start with bot installation information and ask the operator to confirm the relevant features are available.
- An authorized bot administrator needs access to the alliance in the bot. In the settings menu, Gift Operations → Auto Gift Settings controls whether automatic processing is enabled for that alliance.
- Configure the alliance's notification channel and the gift-code channel used for code intake. The bot must be able to access the relevant channels and send messages.
- Make sure intended players are present in the alliance roster with the correct FID and state. Signing into the website or joining Discord alone is not the same as being in that roster.
- Where registration is configured, use /register and follow the wizard. It can involve language, rules, FID and verification steps; it is not a one-command guarantee of completion.
Registration needs working channel/thread permissions. Role assignment and nickname changes can also fail because of Discord permissions or role hierarchy. A registration thread may fall back from private to public, so inspect its visibility before sharing information. Ask an administrator for help if the workflow stops.
What automatic processing actually does
The checked gift-processing code reads enabled alliances, looks up their roster, checks prior redemption records and processes players. It reports progress and distinguishes successful, previously used and failed outcomes.
Processing is not a guaranteed-delivery queue or a deadline commitment. Timeout retries can keep a batch waiting, and missing alliance/channel configuration can stop it before distribution begins. A “process complete” summary may still contain failures.
Troubleshoot the actual outcome
| Outcome | Next check |
|---|---|
| Already received or same-type exchange | Read the publisher's response; this is not proof of a new reward |
| Expired, invalid or usage limit | Check the code's current eligibility; automation cannot override it |
| NO_KID | Ask the operator to check the player's stored state |
| WRONG_STATE | Correct the stored state before retrying |
| TIMEOUT_RETRY or another error | Ask the operator to inspect the batch; completion time is unknown |
| No progress message | Check alliance setup, enabled processing and channel access |
After a transfer or account change, verify the roster's FID and state. Do not assume a state transfer creates a new FID or resets code eligibility. Confirm success through the actual response and in-game mail, not merely a queued request.
What still needs review
Live installation, permission combinations, queue recovery and end-to-end redemption need authorized testing. No redemption was performed for this guide. The earlier timing guarantees, competitor prices and universal free-service promises have been removed; confirm current availability and terms with the operator.