Apocalypse Rising 2 Infected Dex

Treat infected as information

Infected are threats, but they also reveal what is happening around a location. An agitated infected can indicate recent noise or movement. An unusually empty area can mean another player cleared it. A distinctive outfit or behavior can suggest a special variant worth observing, but appearance alone should not be turned into a guaranteed name, location, or drop.

The official experience confirms unique infected, rare cosmetic loot, and an increased loot chance when they are defeated quietly with melee. It does not publish a complete current roster, fixed spawn map, or exact probability. This Dex therefore focuses on observable behavior and safe decisions. It leaves unsupported percentages blank.

Read detection before committing

Approach an occupied area slowly enough to watch movement. Use cover and avoid crossing several infected at once. Crouching, line-of-sight breaks, concealment, and quiet movement may reduce exposure, but exact detection distance varies with conditions and needs live testing. If one infected reacts, assume the encounter can pull attention from both AI and players.

Choose melee only when the target is isolated, the approach is controlled, and you have room to recover. Quiet kills conserve ammunition and can support the official loot bonus, but a failed melee engagement can trap you in the open. Firearms are appropriate when distance or multiple threats make safety more important than silence. Every shot creates a second problem: another player can now locate the fight.

After the encounter, scan before looting. The body is not cover, and a rare-looking infected can attract other players who know the same location.

Practical infected classes

Use descriptive classes until the live interface or a current official source supplies a stable proper name.

Ordinary infected establish the baseline for movement and detection. Location-themed infected appear associated with a role or place and may wear recognizable clothing. Unique or special infected have distinctive appearance, behavior, equipment, or loot association. Boss and mini-boss infected require more deliberate preparation and may be tied to a specific environment or event. Seasonal infected belong to a temporary event state and should be marked expired when the event ends.

These labels prevent a community nickname from being mistaken for official terminology. A record can include a reported alias while keeping the verified description and source separate.

Boss preparation

Do not start a tougher encounter while hungry, injured, overloaded, or without an exit. Clear nearby ordinary infected quietly when possible. Identify hard cover and a retreat line that does not pass through another group. Check weapon condition, loaded state, supported ammunition, healing access, and whether the sight picture works in the available space.

During the fight, preserve distance and cover rather than chasing damage. Watch for behavior changes and additional infected. If another player arrives, the objective changes from defeating the target to surviving a three-sided encounter. Retreating does not waste the preparation; it protects the character and the information you gathered.

The Boss Infected guide offers an observation sheet for name, map, location, trigger, behavior, control response, and drops. Damage values, stun immunity, and respawn timing require controlled current-build tests.

Rare-drop tracking

Record what actually appeared, not what you hoped would appear. A useful observation includes date, map, location, infected description, kill method, event state, server context, and exact item name. One drop establishes possibility, not probability. Several failures do not prove removal.

Separate categories such as cosmetic, weapon, ammunition, utility, and ordinary supplies. Mark the record observed, officially described, community reported, or unverified after update. For event items, also record the official start/end window where available. Never label a drop “guaranteed” unless a current official source says so and the live result matches.

The Rare Drops guide explains how to build a useful log without false precision.

Map and event scope

A spawn report must say whether it belongs to Beta, Reimagined, or a seasonal map variant. The same landmark name may not have the same layout or infected population across versions. Event updates can add, remove, or dress infected differently. Old Alpha and Apocalypse Rising 1 references are discovery leads only.

Link a location to the Map hub and a limited source to the Events hub. If the event is over, retain the historical record but mark it expired. This helps collectors understand an item’s origin without sending them on a current route that cannot work.

Fight or avoid?

Fight when the infected blocks an essential route, threatens your retreat, protects a resource you genuinely need, or is part of a verified objective. Avoid when ammunition is scarce, health is low, another player can exploit the noise, the target’s behavior is unknown, or the supposed rare reward comes from an outdated report.

A quiet bypass often preserves more value than a successful fight. In a survival loop, not spending healing and ammunition is equivalent to finding supplies. If the target matters for collection, return with a deliberate kit and a recorded route instead of improvising while vulnerable.

Dex record fields

Each entry should include visible description, verified or reported name, broad type, map scope, environment, observed behavior, detection notes, observed drop categories, cosmetic/weapon link, event status, evidence level, and last checked date. Unknown fields remain blank. Avoid probability, health, damage, respawn time, and immunity claims until they have a documented method and sufficient repeated observations.

Community wiki pages help surface possible variants, but completeness is not assumed. Official Roblox and changelog language establish the system; the live build establishes the encounter.

Sources and freshness

Unique infected, rare cosmetics, and the quiet-melee loot advantage come from the official experience description. Official update notes establish event and map context. Community catalogs provide working entity leads but may be incomplete or outdated. Locations, behaviors, pools, control responses, and all probabilities remain live checks. Last reviewed September 18, 2026.