Define “special” by source
A special weapon is best understood through its acquisition context, not an automatic power ranking. It may be tied to a limited event, a unique infected, a random event, a cache or unusual container, a named update, or a legacy state. Exact damage or rarity should not be inferred from the label.
For each item record the exact name, class, ammunition, source category, map, event, current/expired/legacy status, official or observed evidence, and last checked date. Keep performance separate from availability.
Source lookup
Event example and status
The official August 13, 2026 Soviet Takeover update introduced a limited AN-94 during an event announced through September 7. This confirms a historical event weapon and its window. It does not prove the weapon now spawns normally, has returned, or is obtainable by the old route.
Mark the acquisition expired/historical unless a newer official update or live client confirms availability. Existing player ownership does not prove current acquisition. Apply the same logic to winter, Drying, anniversary, or other limited additions.
Search without fake coordinates
Begin with the source category and correct map. For random events, inspect current temporary scenes and radio/map signals. For infected, identify the entity and environment. For caches, verify the container family and landmark. For event weapons, confirm the event panel is active before traveling.
Approach from observation cover and plan an exit. These sources attract other players. Do not repeat an exposed check merely because an old guide calls the weapon guaranteed. One empty search may reflect prior looting; one successful search does not establish a rate.
Use Random Events, Rare Infected Drops, and Containers for the systems that own those observations.
Evaluate the find
Confirm ammunition and loading method before replacing a supported primary. Check sight, fire mode, attachment compatibility, inventory size, and reserve. A special weapon with scarce ammunition can become a liability on a long route.
Do not fire a celebration shot. Move to cover, inspect it quietly, and decide whether the item solves the next engagement. If it is an event collectible rather than a practical upgrade, plan a safe exit instead of extending the loot run.
Performance belongs in a test record with build, range, ammo, setup, and platform. “Special” is not a damage statistic.
Verify an infected drop
Record date, map, exact location, infected description or verified name, event state, kill method, and exact weapon result. The official experience says quiet melee can improve unique-infected loot chance but provides no percentage. Never turn that statement into a guaranteed weapon route.
Repeat observations across fresh servers before describing a pattern. Separate an observed possibility from a claimed pool. If a newer update changes the infected or location, mark the record unverified until retested.
Availability states
Current means a reproducible live source. Event-limited means the official event is active. Expired means the published window ended. Legacy means historical ownership exists without a current source. Returned requires new official or live evidence. Unverified after update means the previous route predates a major change.
These states answer the collector’s real question without deleting history or promising a stale route.
Evidence standard
Prefer official changelog additions for identity and dates. Use a current live observation for source and map. Use community videos or discussions as leads, noting their date and version. Keep screenshots of the item name and source context where practical. Never require glitches, scripts, downloads, or account credentials.
Verification status
Special-source categories are supported by official event additions, unique infected, random events, and community catalogs. Exact roster, locations, pools, probabilities, stats, and current availability require live checks. The AN-94 example is historical to its official event window. Last reviewed September 18, 2026.