Upgrade Tree in Project: Aura

The upgrade tree is one of the named systems on the Project: Aura experience page, sitting next to exploration and merchants in that “nearly ten systems” pitch. Incremental hybrids live or die on this board. If you treat it as wallpaper behind the roll button, you will reroll forever and still feel slow. This guide is how to spend Prism on purpose.

You will not find a leaked screenshot of every node cost here. Launch week does not need that to make good decisions. You need a rule for which kind of node you buy, and a rule for when you stop buying.

What the tree is for

In an RNG × incremental hybrid, a tree usually does three jobs:

• Makes the roll loop cheaper, faster, or less punishing.
• Makes the build loop (runes, potions, food) cheaper to feed.
• Makes the map loop (exploration) less of a chore.

If a node does none of those, it is a cosmetic or a trap for people who click the brightest icon. Walk away. Weekly content can add better nodes in two weeks. A bad node is Prism you cannot put into a merchant recipe.

How to read a node without a wiki table

Hover, inspect, or open the node and ask:

1. Does this help the job I named in build crafting?
2. Does this help me take more standard tickets without starving lucky ones? (See how to roll.)
3. Does this help me leave the plaza?
4. Is this a one-time unlock or a repeatable sink?

If you cannot tell, do not buy it yet. Open getting started and finish HUD literacy first. Buying mystery nodes is how launch currency vanishes.

First-tree priority

With the 500 Prism from RELEASE (and whatever the group gift adds):

• Priority A: a node that clearly supports inventory, rolling quality of life, or movement.
• Priority B: a node that feeds potions, food, or rune access — the grammar of a build.
• Priority C: a node that looks like a power spike but only if it matches your equipped character’s job.
• Not a priority: a node you cannot explain in one sentence.

Two good nodes beat six random ones. Incremental games reward depth on a path. Spreading Prism like confetti makes every path anemic.

Tree versus merchants versus tickets

These three fight over the same wallet:

• Tree — permanent (or long) multipliers. Buy when the sentence is clear.
• Merchants — stock that completes a recipe. Buy when the composition test fails without that item.
• Tickets — more questions. Buy last.

If you are arguing with yourself, the tree wins on account one. You can farm more tickets through codes and weekly drops. You cannot un-skip the early nodes that make every later drop feel better.

Synergy with luck-relief

Luck-relief already pays you during dry streaks. That means you do not need to dump the entire tree into “more luck” as a panic. Look for nodes that make relief rewards or roll QoL better, not a fake 90-pity that does not exist. If a node claims to be luck and nothing else, read it twice. RNG games love a luck tax.

When weekly patches hit the tree

Rival Ducks has promised new content every week and bigger gameplay updates every two weeks. Trees in this genre often:

• Add a new branch for the new character role.
• Discount an old branch so veterans are not bricked.
• Insert a merchant-only node that looks like a tree node. Check whether you are still in the tree UI.

Read roadmap before you respec in your head. There is no public respec promise. Assume purchases stick.

Practical session

Open the tree once per login. Buy zero or one node. Then go explore or roll with a target. If you live in the tree UI, you are playing a spreadsheet. The session planner has a “one node” box on purpose.

If a friend sends a “must buy these 15 nodes” image from a different Roblox incremental, ignore it. Project: Aura is a new title with its own board. The tier list hub does not rank tree paths until the community has a stable screenshot of the real board. Until then, the four questions above are the guide.

Climb slowly. The cavern key art is a vibe. The tree is the engine.