Responder ManualNMRiH2 · Unofficial

Hub · 7 role builds + planner

No More Room in Hell 2 Builds: pick a role, get a loadout

Compare seven role presets or open the five-question planner, which maps the same normalized inputs to the same stored base Build.

ToolBuild plannerMode, difficulty, team size, role, preference → one deterministic build you can save.Open

Comparing published fields instead of choosing a role? Open the Responder tools index to select the relevant database.

Choose a No More Room in Hell 2 Build path

The hub exposes seven stored roles: Executioner, Crowd Control, Marksman, Breacher, Mule, Medic, and Scout. Each editorial row shows up to three referenced skills, the first declared strength, primary weapon, and listed map field from that preset. Open the row for the complete local record, including every referenced skill, weapon, equipment item, map, strength, limitation, and source-backed boundary.

Use the planner for a deterministic selection

The planner asks for mode, difficulty, team size, role, and preference, normalizes those answers, and resolves one base preset. Identical normalized inputs return the same base result; the tool does not generate a new statistical Build or learn from other visitors. Use it when the question is which stored role record matches the five selected conditions, then inspect the result before saving it.

Read preset links as declared membership

A skill, weapon, equipment, or map shown on a Build comes from that preset file and must resolve to a real local entity route. Membership does not prove that the item is mandatory, optimal, available in every run, or numerically superior. The hub intentionally avoids rankings and unsupported substitutions; it shows the captured grouping and lets the linked database records carry their own fields and dates.

Manage saved Builds without an account

Favorites and saved Build variants remain in browser-local storage. Saving a planner result records the selected local configuration; it does not change the seven published presets or sync to a game account. A shared planner URL carries normalized input state so another browser can resolve the same base preset, while personal names and saved records stay within the local data workflow.

Keep the source boundary visible

Role groupings are bounded to the captured specialist Build reference and reconciled with the official Armageddon feed only for the release context. Every entity reference is validated against this site's local inventory. The manual omits unsupported performance ranks, damage totals, replacement recommendations, and success guarantees, even when adding those values would make the rows appear more complete.

Move from a role summary to checkable records

Use the row summary to choose a candidate role, the detail route to review all declared components and limitations, and the linked entity pages to inspect individual fields. Open Maps separately when the unresolved question is an objective chain. That sequence keeps a Build recommendation, a database fact, and a map checklist from being presented as the same kind of evidence.

Choose between a preset, the planner, and database tools

The seven role rows are published preset records, while the planner selects among those same records from five normalized inputs. Neither surface edits a source record or calculates a new loadout. When the question is about fields across maps, skills, weapons, equipment, enemies, or achievements rather than one role, use the appropriate database comparison. Keep the result scoped to the displayed fields, because comparison does not add rankings, live game state, or performance values that the records do not contain.