Project: Aura Tools

Tools on this wiki are checklists, not cheat GUIs. Project: Aura just launched. A “pity calculator” would be fiction because luck-relief has no public number. A “secret RNG predictor” would be a script with extra steps. What actually helps on launch week is remembering whether RELEASE is done and giving each login one job.

• Code checklist — RELEASE, group gift, Like/Favorite, next weekly string.
• Session planner — roll, tree, explore, or craft. Not all four badly.

After you tick the code, spend Prism with how to get Prism and a starter build job, not a plaza panic.

If you wanted an auto-roller, go read script safety instead of looking for a hidden download on this hub.

Why a checklist beats a bot

Redeeming RELEASE takes seconds. Forgetting it for three days because the > control is tiny takes longer. The checklist is the tool that matches the actual HUD. Same for the Rival Ducks gift, which people skip because they think the code covered it.

The planner exists because Rival Ducks shipped nearly ten systems. Getting started already told you not to mash them. The planner is that advice in a box you can reuse on the first biweekly patch.

What we will not ship

• A 42-name DPS spreadsheet with invented stats
• A drop-rate simulator
• An executor
• A “luck lock-in optimizer” for the Like button

When official numbers exist, they will land in guides and tier lists as numbers, not as a flashy widget that pretends to be more precise than Rival Ducks.

How to use the two tools together

Before login: glance at the code checklist. After login: pick one line on the session planner. After logout: tick what relief paid you, so luck-relief becomes visible instead of mythical.

That is the whole tools philosophy. Small, honest, reusable when Friday’s content tries to reset your brain.

How these tools sit next to the rest of the wiki

The guides hub teaches systems. The tier list ranks jobs. The codes hub holds the live table. Tools do not replace those pages. They shrink them into ticks you can finish in a loading screen. If a tool ever disagrees with a guide — for example a planner cap versus a new official auto-skip — the guide and updates win.

Use the checklist on every account you play, including alts. Use the planner on the account you care about. Throwaway script accounts do not need a planner; they need safety.

What a “tool” is allowed to be here

A list. A cap. A log line for luck-relief. Not a drop-rate graph with made-up percentages. Not a character DPS sheet with invented names. Not an overlay that auto-clicks >. If you want overlays, you are in the scripts category, which is a warning label, not a toolbox.

When Rival Ducks publishes real numbers — node costs, ticket drip, a pity figure they swore they would not copy — those numbers go into guides as facts. Tools can then gain a row like “tree node X costs ___ Prism.” Until the number is public, a calculator is fan fiction.

Suggested weekly rhythm

Monday: planner job “craft” or “explore.”
Patch day: checklist first, then planner job “patch reread.”
Any other night: one job, caps written, logout when a cap hits.

The tools hub is small because the game is already large. Use it to stay small on purpose.