HUNTED Badges

HUNTED’s official Roblox badge inventory is the best public source for confirmed goals. It proves that a stage, S Rank, challenge, Curse win, PvP role win, or event objective exists. It does not provide the complete route or scoring formula. This Dex keeps the official wording and ID attached to each goal so you can verify the correct badge on your profile.

Badge groups

Story and challenge Dex

Event and lobby goals

Candy Collector (ID 1253232809160660) is the current The Hollow badge. Its official description says candy comes from Trick-or-Treat doors in portals with the event tag, then directs the player to the main lobby’s Ring Alter. The text conflicts by saying both more than 75 and once 75 have been collected. Follow the live quest prompt and use the The Hollow guide.

Service, Please! (ID 2929093922399795) says to ring the service bell 10 times. The public record confirms the target, but the exact bell location, whether the actions must be in one session, and current trigger behavior need an in-game check.

Curse badge set

The official inventory includes five enabled badges: Win a game with No Map Curse! (ID 3036683731285356), Darkness Curse (1905550172537387), One Life Curse (1339925775651534), Fog Curse (3834079343937278), and Blinded Curse (2275421018629109). Their names prove the win condition exists. Their descriptions are empty, so the public API does not settle effects, cost, activation, random chance, or difficulty.

PvP win set

HUNTED has paired Monster and Mortal win badges for Monkey Business, Elementary Evil, Deadly Decadence, and Pillar Pursuit. That is strong evidence for the maps and both roles. The badge records do not define team size, item rules, role abilities, map rotation, or tier progress. Use the PvP hub for a role matrix and current verification boundaries.

How to pursue a badge

Open the official badge record and read the description immediately before the run. Choose one goal and use the matching map guide. For a challenge, map the required interactions before attempting a perfect run. For S Rank, complete normally and record the result screen. For a Curse or PvP win, confirm the selected condition and role in the live interface.

After completion, check your Roblox profile. An in-game counter or personal count is useful, but the awarded badge is the final proof. If it is absent, verify the exact condition, stage, mode, and current badge enabled state before assuming a bug.

How not to read badge statistics

The API exposes awarded counts and a win-rate field. Those values change and are not a drop rate, scoring threshold, or chance that your action succeeds. A low award rate can reflect difficulty, age, player interest, or the number of sessions; it cannot tell you a route.

Do not use an award percentage to invent a Curse probability or camera detection rate. Use the description for the goal and the current game for the mechanic.

Verification workflow

Keep the badge ID, condition, stage, date, mode, and result. If the game wording differs from the public record, capture both. A repeatable current observation may explain a mechanic, but it should remain distinct from the official condition.

Plan badge sessions without wasting runs

Group goals by the route knowledge they require, not merely by the page where they appear. A first-clear badge needs a dependable route and correct exit. An S Rank badge needs a completed baseline plus the live result fields. A perfect-condition challenge such as Camera Shy needs a route built around avoiding the failure trigger. A counted challenge needs a visible or carefully recorded interaction at each target. A PvP role badge needs the correct map, role, completed match, and registered win.

Before starting, choose one primary badge and one fallback learning goal. If a camera triggers, a streak breaks, or the wrong PvP map loads, stop treating the session as the primary attempt. Use the rest of the run to map landmarks, confirm objective wording, or observe the result screen. This avoids spending revives or time to rescue a condition that may already be invalid.

When several badge descriptions seem compatible, do not assume they stack. Complete each one independently first. Then combine them only if the live counters, result screen, and awarded profile records show that one condition does not invalidate the other. Keep badge IDs in the notes because similar completion names can refer to different stages.

Official source

• HUNTED universe badge inventory