On C5GAME or Steam Market, the weapon case line and collection line in the footer are not the same index. Learn to verify drop pools, finish groups, and agent model slots before you pay a premium.
Start With the Two Footer Lines
Open a restricted skin on C5GAME or the Steam Market and the footer often shows two labels side by side: which weapon case it came from, and which collection it belongs to. Many buyers treat them as one story—where the gun came from. In the game data they are different indexes: the case line points at the drop pool / key economy chain; the collection line points at the item set / collection finish group. The same rifle can sit under a one-time Operation track while also rotating in a permanent case’s rare pool. Unbox weights and trade-up contracts read the case chain; some filters and souvenir copy read the collection tag. Checking only the case name is how you mis-price “same pattern, different origin” or pick the wrong upgrade tier.
Weapon Cases: Pool First, Gun Second
When you cross-check in-game assets, the first question for a case entry is whether the pool tied to that key is still active on the path you care about. Cases listed on trading sites are tradable containers; the client still has legacy pools you can open without a live key line, plus non-key pools reachable only through packages or commemorative channels. A practical habit: in Steam inspect, read Exterior / Collection in item info (wording varies by locale), then match strings against series / collection on the C5 listing—no need to memorize internal IDs, but do not swap “case name ⇄ pool” for “collection ⇄ finish group.” Knives and gloves often sit on separate rare lists; “from X case” in the footer is historical source, not proof your wear tier is still common in that pool’s current roll table.
Collections: Finish Families and Same Art, Different Pedigree
At the resource layer, a collection is closer to a catalog of paint kits bundled with weapon defs. The same pattern index can enter multiple collection tags depending on how it was added to the economy—hence “same pattern, different origin price” on listings. Lock pattern + wear tier first, then use the collection name to explain premium; do not reverse-engineer the pattern from case price. StatTrak™ and Souvenir are modifiers stacked on the weapon finish. Agent skins never use the weapon rare pool—they live on character definition + model variant tables. Float narratives for guns will not line up for agents.
Agent Skins: Model Slot and a Third Verification Path
Agents on C5 sit under Agent; in a match they occupy the faction custom player model slot, built from model index, patches, balaclava UV, and similar fields—not the weapon 0–1 wear line (except odd event items). Verify in inspect animation: sleeve patches, radio gear, and mask should match the preview source; some agents ship their own buy menu / MVP voice lines. If the detail page says “agent from series X,” that is a display set tag—it does not boost any case drop weight. Case, collection, and agent chains do not auto-link in the backend.
Pre-Purchase Checklist (Weekly Habit)
When you stock your inventory, use three columns: market name | collection or Agent set | what inspect shows for quality and name slots. If the middle and right columns disagree, do not pay a “complete the set” premium yet. Block time around the top of the hour for a full footer pass: is the case still keyed, does the collection explain the pattern, did you run agents through the model slot alone—three ledgers, not one vague “origin,” keeps listing copy and inspect from fighting each other.