“Is That a Redeem Code?”

Answers to a question players keep asking · page built

The short answer: in the games we track, the word “code” covers four different things. Only one of them is a string the publisher issued that you type into a redemption box. The other three were written by other players, attach two accounts to each other, or are not strings at all. Landing on the wrong family is the most common reason a “code” turns out to be unusable — and it is not the same thing as a code that has died.

Four families, one word

Every page on this site is built around one kind of code: a string the publisher put out, that a source still carries, that you type into a box and that is spent once. That is the family our tables cover. The other three show up in the same searches and in the same threads, and they are the reason a string can be perfectly real and still do nothing for you.

FamilyWho puts it outWhere it goesWhat it is not
Redeem code The publisher, on a channel or in the game A redemption box, in the game or on the web Not reusable — the first account to use it spends it
Sharing code Another player Shared between players, not entered for a reward Not issued by the publisher and not a gift
Invite or binding code A player, entered by another player Attaches two accounts to each other Not a reward drop, and the limits are about people, not time
Link The publisher or another player Opens the game, or opens a store page Not a string you type anywhere

The four rows above are our own split, made from the threads we keep in our source library. It is not a publisher's terminology — no publisher we track sorts its codes this way.

Four labelled cards in a row, each naming one family of things that get called a code. The redeem code card shows a string issued by the publisher going into a redemption box and being spent once. The sharing code card shows a player writing down a layout code and handing it to another player, with no publisher involved. The invite code card shows two accounts joined by a binding rule of one code per account. The link card shows a link opening the game or a store page instead of being typed into a box.
One word, four routes. Only the first card ends in a redemption box.

Sharing codes: written by players, for players

Two games in our set have a second kind of code that is not a gift from the developer at all. In AFK Journey the community posts these as homestead, layout and arcane codes — the thread titles say it plainly:

“Some Homestead codes!!” · “Sharing my first arcane codes.” · “New Layout Codes”

Nothing in that family is issued by the publisher, and nothing in it is entered for currency. It is a player handing another player a layout. The note that came with this material in our library is blunt about why we keep the two apart: half the people searching the term are not looking for a redeem code, and writing one up as the other is the mistake to avoid.

Reverse: 1999 has the same shape under a different name. The thread we follow is a player asking for one directly, and the answer is not a list:

“hello guys im just asking for a wilderness code for beginners cuz most of the codes ive searched i dont have a…”

“You can ask for help in the discord. Theres a chabnel there dedicated to wilderness”

Read those two lines together and the practical point is in the answer: this family is exchanged between people, in a place set aside for it, rather than published as a list. That is exactly why searching for it turns up nothing usable — and why a string from that family, typed into a redemption box, will never work.

Our AFK Journey page keeps the two families apart in its own section on the two meanings, and the Reverse: 1999 page carries the binding rules for the codes it does list.

Invite and binding codes: the rule is about people

The third family is the one that looks most like a redeem code and behaves least like one. A redeem code has a window; an invite code has a relationship. The thread we follow for Reverse: 1999 states the two rules in two replies:

“It doesn’t work when you’ve already bound yourself to someone else’s code.”

“Each code can only be used once. That means someone else already used that code. EDIT: You can also only bind to one account.”

So a string from this family can be brand new and still refuse you, because the account is already attached to somebody. Nothing about the string is wrong, and waiting will not help. The same family in Honkai Impact 3rd carries a second label instead — the server it belongs to — which is why the codes in those threads are always posted as a pair:

“107160394GP NA” · “EU server, 209326622AA” · “NA 108999276JY” · “SEA 20816403AA” · “Sea 21040205GW”

Both of those limits are worked through in more detail elsewhere on the site — the binding rule here and the server lock here.

How to tell which one you are holding

We cannot look at a string and tell you its family. What we can do is list the four questions that sort them, in the order that saves the most time:

  1. Is there a box to type it in? If no box exists in the game or on the web page, it is not a redeem code. That is the fastest filter of the four.
  2. Who wrote it down? If the post says “here are my codes” rather than naming a channel the publisher uses, it is a sharing code.
  3. Does it come with a person attached? If the post is a string plus a server, or a string plus a rule about how many accounts may use it, it is an invite or binding code. Waiting will not clear the refusal.
  4. Does it open something instead of being entered? Then it is a link, and the problem is the opening, not the code.

If all four answers point at a publisher-issued string, then the family is right and the problem is somewhere else — and that is the point at which our tables become useful, because the remaining question is whether a source still carries it.

What we cannot tell you about this

We do not publish a list of sharing codes or invite codes, and we do not track them. They are not issued by a publisher, they are not single-use in the same way, and there is no source we accept that carries them — so putting them in a table next to redeem codes would make both columns worse. We also cannot tell you what a sharing code is worth to you, because that depends on the game version and on the player who wrote it down.

The quotes above are player posts from our source library, kept as they were written. They are not official statements, and the four-family split is ours, not a publisher’s.

Frequently asked questions

Why does a code someone shared not work in the redemption box?

Because sharing codes and redeem codes are different families that the community calls by the same name. A sharing code is written down by a player; a redeem code is issued by the publisher and typed into a box. Only the second one is meant to go in a box.

Are homestead, layout and arcane codes redeem codes?

No. In AFK Journey they are posted by players for other players, under thread titles like “Some Homestead codes!!” and “New Layout Codes”. Nothing in that family is entered for currency.

Where do people find a wilderness code for Reverse: 1999?

In the thread we follow, the answer given to that exact question was to ask in the game’s Discord, in a channel dedicated to it. It is exchanged between players rather than published as a list, which is why a search turns up nothing usable.

Why does an invite code refuse me even though nobody has used it?

Because the limit is on accounts, not on the string. In the rules quoted in the thread we follow, an account may only be bound to one person’s code and each code may only be used once. If your account is already attached to somebody, a fresh code changes nothing.

Does Monopoly GO have redeem codes?

There is no string to type. What the boards post is a link, which is why the complaints in that community are about links not opening rather than about codes being dead.

How do I know a code is the kind your tables cover?

It is a publisher-issued string, a source on our list still carries it, and it goes into a redemption box — in the game or on the web. Our game pages give each one a status and the last date a source carried it, so the answer is on the row rather than in a paragraph.