Pillar Pursuit has official HUNTED PvP badges for Win as a Monster In Pillar Pursuit (ID 1630834715379634) and Win as a Mortal on Pillar Pursuit (ID 244598414739361). Both were created in August 2026, after the July story-stage badges, making them current evidence for the competitive map. They do not define a tier system or role rules.
Recheck the newest competitive layout
Because Pillar Pursuit is a newer addition, do not assume an older PvP overview includes it. At match start, identify the current objective, major pillar or room landmarks, connected lanes, and blocked routes. Compare them with the story map only for orientation.
Create short callouts that distinguish similar pillar spaces. Add direction or objective context when the same prop appears in multiple rooms.
Monster learning run
Read the current Monster kit and locate where Mortals must commit to an action. Test one pressure route and its counter-rotation. Do not claim the story stage’s illusions or StunOrb are part of PvP unless the live mode shows them.
Record ability descriptions and results under the current date. A newly added map can change rapidly.
Mortal learning run
Locate the objective, teammate indicators, and two escape lanes before committing. Watch how Monster pressure crosses the pillar areas and avoid stacking every Mortal in one dead end. Confirm whether any progress or pickups are shared.
Use the first match to map, then make a badge attempt with the correct role and active map.
Do not confuse story badges
Pillar S Rank and Illusion Breaker belong to the story stage. The PvP badges require role wins. An illusion count, StunOrb action, or story completion does not substitute for the Monster or Mortal victory record.
Verify the award
Stay through the result screen, note the role and map, and check the corresponding badge ID on your profile. If no award appears, verify that the match counted as a win and that the map was Pillar Pursuit rather than another rotation entry.
Common mistakes
- Applying story Illusion Breaker instructions to PvP without live evidence.
- Using an older PvP guide that predates the August badges.
- Giving ambiguous callouts in similar pillar rooms.
- Assuming team size, role abilities, or tier progress from another map.
- Switching roles before the result is registered.
Current unknowns
Map rotation, team size, role assignment, Monster and Mortal kits, items, objective, timer, win condition, tiers, rewards, late joins, and balance require current in-game testing. The official badges confirm only both role wins on Pillar Pursuit.
Opening-minute checklist
Confirm the live map label, role, objective, and current ability or interaction text. Choose a central landmark that is visually distinct from the surrounding pillars, then name two connected lanes by their destination or objective context. Check teammate indicators and blocked routes before assuming the story-stage layout transfers to PvP.
For Monster, observe which current objective forces a Mortal to commit and keep a route back toward the other lane. For Mortal, locate pressure before the team enters a one-exit space. Do not assign the story StunOrb or illusion interaction to either role unless the competitive interface directly presents it.
Review the match as current evidence
Stay through the result and record map, role, winner, objective state, one decisive lane, and badge outcome. Because the paired badges are newer than the story-stage set, older PvP coverage can omit this map entirely. Date the observation and verify the badge by ID rather than trusting an outdated list.
If no badge appears, first verify that the session counted as a completed win with the expected role. Do not infer a tier requirement, minimum action count, or reward boundary from one result. Repeat under comparable conditions before escalating the issue.
Improve one pillar decision
In the next matching session, change one choice: clarify a repeated-room callout, preserve a second route, cover an objective approach earlier, or retreat before a dead end. A practical note should state the landmark and visible outcome. It should not turn a newly observed ability, timer, or rotation into a fixed rule without repeated tests or creator documentation.