Project: Aura Code and Rewards Checklist

Use this page as a physical list. Screenshot it, copy it, or shout it at a friend who swears they “already did codes” but never joined Rival Ducks. Steps for the typed string live on how to redeem. The live table lives on the codes hub. This tool is only ticks.

Launch stack (do in any order, finish all)

• Open the official experience (creator: Rival Ducks, place 129619503633658).
• HUD finished loading. Not mid-stream.
• Redeemed RELEASE in the > menu.
• Saw Prism land (official listing: 500) plus 10 Aura Roll Tickets and 5 Lucky Aura Rolls — or whatever the menu actually printed.
• Joined Rival Ducks on the same account.
• Rejoined a Project: Aura server once after joining the group.
• Confirmed the extra group gift in inventory (not in the code box).
• Optional: Liked the experience.
• Optional: Favorited the experience.
• Did not type AURA. codes, Aura Battles codes, or Steam keys.

If a box fails, do not mash Redeem. Diagnose with the redeem guide or group rewards.

After the stack — spend ticks

• Standard tickets parked until I have a roll plan.
• Lucky rolls parked until I can name a hole in the build.
• Prism not dumped into the first merchant icon.
• One upgrade tree node identified or skipped on purpose.
• Discord announcements unmuted — Discord.
• Prism plan exists: how to get Prism.
• One job named on starter builds.

Next weekly code (blank on purpose)

When Friday’s content ships, add a row. Do not invent the string here in advance.

• New code from Discord / Roblox description: ____________
• Redeemed on this account.
• Expired? If yes, the codes hub should already show it in expired. Tell us if we are late.
• Did not share the code inside a phishing “verify to claim” Discord.

Account hygiene ticks

• 2FA on Roblox.
• No executor on this account, or a throwaway exists for experiments — safety.
• No .ROBLOSECURITY pasted anywhere.
• This is not an alt you forgot; group + code are on the character you actually play.

Why a checklist is a tool

RNG hybrids drown you in menus. A list that is only twelve boxes will outperform a 40-tab hub GUI. When a second limited code exists, this page gains a row, not a new philosophy.

Print it. Tick it. Go explore or craft. The > menu will still be there tomorrow; the limited window on RELEASE might not.

How to run the list with a friend

Send them this page and the how to redeem HUD steps, not a screenshot of a different Aura game. Watch them tick the group join on the same username they spawn as. Most “my code failed” calls are alt mix-ups or trailing spaces from mobile autocorrect. The checklist’s hygiene ticks exist for that.

If they already redeemed RELEASE last night, skip to the weekly blank row. Do not make them smash Redeem “just in case.” Already-redeemed errors train people to think the menu is broken.

When a code expires mid-week

Tick expired on the blank row, then open the codes hub and confirm the table moved. If we are late, the Discord announcement is still the grant. The checklist is a memory aid, not the live database. Do not keep retrying an expired string; it will not resurrect luck-relief.

Alts and the same Wi-Fi

Each account needs its own copy of these ticks. Sharing a screenshot of a ticked list with your alt is fine. Sharing a cookie is not — safety. Join Rival Ducks on every alt you actually play, not on a graveyard of unused users.

The checklist is done when the launch stack is ticked and the weekly row is either filled or honestly blank. Then close this tab and pick a session job.