The Build and Kill Zombies skill tree should be read from the current menu before Cash is spent. Current guides repeatedly document Luck, Gold Roll, and More Support branches, but public first-party sources do not list every node, prerequisite, cost, effect, maximum rank, or reset rule. This page gives you a dependable way to map what your account actually shows.
Skill record fields
Map the visible branches
Open the Skills menu and capture the full tree before buying. Trace each branch from the first visible node through locked ranks. Do not assume a line indicates a prerequisite until the UI explains the connection.
Group nodes by player-facing job: acquisition or Luck, roll behavior, support capacity, vehicle performance, income, or another explicitly displayed effect. Keep an unknown group when the wording is not clear.
Currently documented branch names
Luck is Community corroborated across current guides and is generally described as improving acquisition outcomes. Gold Roll is reported as a later roll-related upgrade. More Support is reported as increasing support capacity. Exact ranks and values are not frozen here because different pages publish changing numbers.
If your current menu uses another name or no longer shows a branch, preserve the live label and update date. Do not force the UI into an old guide’s taxonomy.
Verify a purchase
Record Cash before pressing confirm. Capture the confirmation text. After purchase, record Cash again, reopen the Skills menu, and check the node state and newly available branches. This proves the transaction and current tree relationship.
Then test the relevant outcome. For a capacity node, inspect the builder or slot display. For a Luck or roll node, use a controlled sample in one roll category. For a vehicle node, repeat a known route. Do not use a different build and attribute every change to the skill.
Avoid common tree mistakes
Availability is not priority. A bright node may simply be unlocked. A higher rank can cost more without solving the current bottleneck. A long-term acquisition upgrade can be good but still delay the engine, fuel, or defense needed for the next productive run.
Do not copy a precise cost from an old screenshot. Do not call a node permanent until rejoining confirms it or the live menu says so. Do not test reset behavior on valuable progress without reading the warning.
Decide the next node
Write the current bottleneck in one sentence. If poor available parts block several builds, compare Luck or roll progression. If you own an unused support that would improve a measured route, compare More Support. If the build itself fails, fix it before buying an unrelated acquisition node.
The Best Skills guide ranks choices by goal. The Luck and Rolls guide explains why an odds claim needs more than a handful of rolls.
Keep version history
Attach a checked date to each node record. When the official experience timestamp changes, reopen the tree and compare name, rank, prerequisite, cost, and effect. Keep the prior snapshot dated rather than silently presenting it as current.
Use screenshots only for verification; write the player-facing result in your own words. Avoid copying another site’s entire tree layout or table, because its order can be proprietary and may already be stale.
Link the tree to actual play
A skill matters when it changes a decision. Link acquisition nodes to the roll category tested, capacity nodes to a build that uses the slot, and performance nodes to a repeatable route. The Parts Dex supplies part roles, while Builds supplies the outcome test.
For Cash planning, estimate the number of reliable runs needed at your observed net income. Do not use an unsupported universal farm rate. That keeps the tree useful across inventories and patches.
Confidence
Upgrades are Official as a core loop. The currently documented Luck, Gold Roll, and More Support branches are Community corroborated or reported as of September 25, 2026. Complete nodes, costs, effects, caps, persistence, and reset behavior need in-game testing.