Build the list from observable traits
The official experience confirms unique infected and rare cosmetic loot, but it does not publish a complete current roster. Community lists help discover possible entities, while names and locations can become stale. Record the exact visible description and current map before accepting a nickname as official.
A useful entry includes verified or reported name, type, appearance, map, environment, observed behavior, detection notes, observed drop categories, event status, evidence, and last checked date. Leave health, damage, probability, and respawn blank without controlled evidence.
Working type lookup
These categories are descriptive. Use the live game or current official source for exact terminology.
Observe detection
Approach from cover and watch the infected before entering its path. Record what happened when you stood, crouched, moved, broke line of sight, or used concealment. Change one variable at a time. Another player, gunshot, vehicle, or nearby infected can invalidate the observation.
Do not publish a fixed detection distance from an uncontrolled encounter. Terrain, stance, sound, and update state can matter. Use qualitative notes until a repeatable method supports more.
An agitated infected can serve as an alarm. Avoid clearing every target automatically if their reaction provides useful information about other movement.
Fight safely
Use quiet melee on an isolated target only when you have room to approach and recover. The official description says quiet melee improves unique-infected loot chance, but no exact bonus is given. Multiple infected, uncertain behavior, or limited escape can make a firearm safer despite the noise.
After gunfire, reload and scan for players before looting. If the target looks rare, assume others may know the location. Do not stand over the body while reading an item.
For tougher encounters, use Boss Infected and prepare cover, retreat, healing, and supported ammunition.
Record drops
Write what appeared exactly. Include map, location, infected description, kill method, event state, and date. One result proves possibility only. Separate cosmetic, weapon, ammunition, utility, and ordinary-supply categories.
Use observed, officially described, community reported, or unverified-after-update evidence labels. A community list can identify a lead while the actual drop remains unverified. Never convert a small sample into a precise rate.
The Rare Drops guide provides a repeatable log format.
Map and event scope
Keep Beta and Reimagined entries separate. Seasonal clothing or behavior may belong to a temporary variant. Old Alpha and Apocalypse Rising 1 entities should not enter the current roster without a live match.
Link exact route information through Map and time-limited variants through Events. Mark expired event entities as history instead of deleting them or presenting their route as current.
Maintain the Dex
Recheck after map, infected, event, loot, or combat updates. Preserve the previous observation date and mark uncertain fields rather than silently overwriting them. If two sources disagree, keep the common observable description and list the disputed name or source for testing.
Avoid fake completeness. The experience has a large dynamic world, and a partial verified roster is more useful than an exhaustive copied table.
Verification status
Unique infected, rare cosmetics, and quiet-melee loot advantage are official. Type categories and potential entities use community references as leads. Complete roster, proper names, behavior, locations, health, damage, pools, and probabilities require current observation. Last reviewed September 18, 2026.
When two names conflict
Keep the visible description and location as the stable identity. Add each reported name with its source and date, then inspect the current interface, official changelog, and recent footage for a match. Do not create two Dex entries until separate appearances or behaviors prove they are different entities. The same infected can also receive seasonal clothing, which should become a variant or event state rather than a new permanent type. This method prevents a community nickname, spelling variation, or old map label from inflating the roster and sending players to duplicate routes.