Verified code status
No redeem code is published as verified in this edition. Checked October 29, 2026. That means we did not establish an official code string, region, valid period, and claim path from the sources reviewed. It does not prove that no code exists anywhere or that a later official campaign will not introduce one.
We do not populate a launch page with guessed strings, recycled test codes, or a fake redemption form. This site never asks for your game password, payment details, one-time login code, or account token to unlock a reward. Use the official game and its linked channels for any claim.
Milestone rewards are a different category
The official home page displays pre-registration and social milestones, including a Raya reward and currency or training-item images. A milestone display is not the same thing as a redeem code. It also does not by itself establish your account’s eligibility, delivery time, expiry, or exact regional claim route.
| Reward category | Evidence checked | What remains to confirm |
|---|---|---|
| Raya milestone | Raya appears on the official milestone display | Account eligibility and actual receipt |
| Contract and resource milestones | Official page shows reward icons and quantities | Current regional terms and delivery |
| Social campaigns | Official channels are linked from the game site | Each event’s valid period and conditions |
| Redeem codes | No verified string recorded in this edition | Official source, region, validity, and claim path |
Check the game’s current notices and reward screen before deciding a gift is missing. A pre-registration milestone, a social participation campaign, and a launch mailbox reward may have different conditions. Do not assume one player’s screenshot proves that every account should already have the same receipt.
A safe claim checklist
Open the official game website and use its links to reach the relevant store or social channel. Check that the campaign names Monster Hunter Outlanders, applies to your region, and is still active. Read whether a step is required before the reward can be delivered. If you cannot find the terms, leave the claim unverified rather than entering credentials into an unrelated page.
Record the reward only after your own client shows receipt. A website saying achieved is campaign evidence, not account-delivery evidence. If the official claim fails, preserve the error and contact official support through the game’s channel. This guide cannot inspect mailbox state or resend a reward.
For Raya, treat the milestone as a reason to check an available option before spending contracts. It is not a promise that the character is universally free forever. Even a successful character claim does not provide every upgrade material or prove that the weapon rhythm will suit you.
Our update policy
We add a code only when its exact string and official origin can be recorded. The entry must include a verification date, region or stated eligibility, known expiry if published, and a current claim path. A successful claim in a real account would be labeled separately from merely finding the official announcement. We do not claim account-tested redemption in this guide.
When a code expires, it should move to a dated expired section rather than remain presented as working. When validity is unknown, it should be labeled unknown. Copying a competitor’s working list would not satisfy this policy, and no competitor reward table has been scraped for this build.
Reward questions
Are there working codes listed here?
No. This launch edition has no officially verified redeem code entry. Check the official channels for new campaigns; do not treat an empty verified list as proof that no campaign exists.
Is Raya automatically on my account?
The official milestone display references Raya, but account eligibility and actual delivery must be confirmed in your game. This site does not read your account.
Where should I ask about missing rewards?
Use official in-game support or the contact listed on the official site. The published game-support email is support_mho@proximabeta.com. It belongs to the publisher, not this guide.