HUNTED has official S Rank badges for Monkey Business, Elementary Evil, Stranger Sewers, Mascot Mayhem, Bearly Buried, and Pillar Pursuit. The badge descriptions prove the rank goal but do not publish a universal score formula. Build your attempt from the current result screen instead of copying a threshold from original Dark Deception or an older HUNTED build.
Official S Rank badge map
Establish a baseline clear
Finish the stage normally before optimizing it. At the result screen, capture every displayed field: time, shards or objectives, deaths or captures, bonus conditions, difficulty, and final rank if those fields exist. The public API does not tell us which fields appear, so the live screen is required.
Keep the mode, difficulty, and group size fixed. A comparison is useful only when the conditions match. Write down the date because scoring can change after an update.
Improve one field per run
Start with route completeness. Remove repeated corridors and missed branches. Next reduce exposed map checks and avoid captures. Then improve speed without breaking the safe route. If the screen shows another scored field, test it separately.
Changing several things at once can produce an S Rank without teaching you why. A single successful video proves the result in that build, not the exact threshold.
Keep challenge badges separate
Shard Enthusiast, Open Gate Policy, Camera Shy, Teddy Defuser, and Illusion Breaker have their own descriptions. Do not assume they are required for S Rank, add points, or can be completed in the same ideal run. The live result screen must prove a relationship.
Learn the normal route first. Complete the optional challenge in a separate attempt. Combine goals only after both are repeatable and the current score evidence supports it.
Handle captures and revives
If captured, read the current result and checkpoint behavior. Official pass descriptions say relevant revives are capped at 2 per level, per run and disabled in PvP, but they do not state how a revive affects S Rank. Record the result rather than assuming the run is either safe or ruined.
When the route is no longer comparable to the baseline, use the remainder for practice. Do not spend more resources solely to preserve an unverified rank attempt.
Solo versus group tests
Public sources do not fully define shared score, shard credit, or rank calculation in group play. Solo gives you the cleanest measurement. If testing with others, keep the same group and compare everyone’s result fields before declaring a shared rule.
Troubleshooting a near-S run
Compare the result field by field with your best attempt. Identify the largest change rather than chasing rumors. If time improved but rank did not, another field may matter. If a cleaner run scores worse, verify difficulty, completion state, missed objective, or version.
Check that the correct official badge is enabled and verify the award on your profile. A displayed S Rank without an immediate pop-up may still award after a short delay; the profile record settles it.
Facts that still need testing
Exact thresholds for time, shards, deaths, streak, difficulty, optional challenges, group size, and revives are not public. There may not be one formula shared by all stages. Record stage-specific evidence and avoid publishing a universal table until every current result can reproduce it.
Before sharing a claimed threshold, reproduce it on the same current stage and retain the full result fields, not only the final letter. A lower-scoring run can reveal a boundary, while one successful run cannot show which requirement was decisive. If the build date, mode, or difficulty differs, keep it as a separate comparison.