Obsidian Knight Redeem Code Not Working: Checks and Fixes

Category Account and Technical IssuesUpdated 10/26/2026

★

この記事の結論

Find the redeem field, check spaces, capitalization, prior use, and expiry, and record results when public active-code lists disagree.

Bottom line: separate input, prior use, and expiry before retrying

When an Obsidian Knight redeem code does not work, the code itself is not the only possible cause. Check the exact text, whether the same account already claimed it, and when the source last verified it.

As of October 26, 2026, public code lists disagree about which codes are active or expired. This guide does not guarantee any individual code. It explains how to verify the result in the current game screen.

Basic redemption steps

Return to the game's main screen.
Open `Settings` in the upper-right corner.
Select `Redeem`.
Paste the complete code.
Press `OK` and read the result shown by the game.

Use the labels on your current screen if the button name or position differs. If `Redeem` is absent, record the device, OS, app version, and visible Settings options instead of repeatedly pressing unrelated buttons.

Check these items in order

1. Remove spaces and line breaks

Check for a space or line break before or after the copied text. If you typed the code manually, copy it again from the source and compare the two strings.

2. Preserve capitalization

Enter the code exactly as displayed. Do not replace similar-looking characters, and make sure you did not copy a label or sentence along with the code.

3. Record the in-game result

Write down the exact message, such as invalid or already used. Similar-looking failures may not reveal whether the cause is an input error, a previous claim, or expiry.

4. Check whether this account already claimed it

If the code may have been used before, do not submit it repeatedly. Check the reward history or compare the relevant resource balance.

5. Compare verification dates

A page can still call a code active after the publisher disables it. Record the page update date separately from the time you tested the code.

When public code lists disagree

Current public sources classify some of the same codes differently. MetaLore Guide therefore does not label a code currently active without an in-game verification result.

Keep these five fields when you test one:

Field	What to record
Code	The exact submitted string
Checked at	Date and time
Device	iPhone or Android device
App version	Version shown in Settings or the store
Result	Success, already used, invalid, or no entry field

Avoid these actions

Repeatedly submit a code whose status is unknown.
Enter a password or authentication code on an external code site.
Assume an old reward amount is still current.
Delete app data or reinstall the game only because the code field is missing.

If the problem remains unresolved

Use the floating feedback button to send the device, OS, app version, visible Settings label, and exact result. Do not send passwords, authentication codes, or full payment details.