Rotwood reference
Rotwood Weapon Gear Boss Reference
Use this after a failed hunt, a confusing update, or a tempting build post. Rotwood is built around weapon mastery, gear progression, boss pattern reads, and co-op recovery, so the best next choice is the one that fixes the layer that actually collapsed.
Quick answer
Translate every build into a job
If a build name looks strong, ask what job it solves before copying it. Does it create safer entry, shorten boss punishes, add reach, protect a mistake, cover co-op rescues, or abuse one current-version power interaction? If that job does not match your last failure, the build is noise.
Weapon and Power Matrix
Powers-A-Plenty made weapon powers a bigger part of hunt identity. Treat a weapon power as a rule change for the hunt, not just another damage number. The useful question is still the same: what does it let your weapon do more safely?
Gear Spend Matrix
Boss Pressure Matrix
Official Rotwood copy is clear about bosses: each one has unique patterns and mechanics, and victory grants loot for harder challenges. That means boss prep should start from the attack that breaks your run, not from a universal build label.
Build Signal Check
Steam guide demand shows players search for strong builds, endgame routes, Big Yammo, Gnarlic Head Stalk, Lich King co-op stacking, cosmetics, achievements, and Frenzy progress. Use those names as clues about what players are trying to solve, not as permanent answers.
Update and Current Build Check
Rotwood patch notes have changed weapon powers, power families, charge behavior, shield interactions, cold effects, minion scaling, boss phase stability, proto-weapon crafting explanations, and co-op joining behavior. Before following a build that claims to be broken, ask whether the exact power, weapon, boss, or save-state condition still exists in the current build.
- Check the visible screen first. If the current menu disagrees with an old guide, trust the game screen.
- Check the patch family. Weapon Powers, Electric, Shield, Summon, Cold, minions, and boss phase fixes have all changed recently.
- Retest one layer lower. If a build suddenly fails, retest entry, punish, reset, and co-op coverage separately.
- Keep the useful idea. Even outdated builds can reveal a player problem; rebuild the idea into a current role instead of copying the route.
Failure Checks
- If every weapon feels bad: diagnose entry, punish, and reset before swapping again.
- If gear feels wasted: you probably spent on a fantasy build instead of the layer that ended the last hunt.
- If bosses feel unfair: name one attack, one punish, and one exit before adding more damage.
- If co-op keeps wiping: assign coverage, rescue order, and target focus before copying a solo build.
- If an old build looks amazing: check current patch behavior, then keep only the role it solves.