C5 shop filters for cases, collections, and agents are shortcuts to defindex, paint kit, and itemset tags—not display names alone. This guide ties loot lists, collection boundaries, and character slots to what you see in inspect.
Why the thumbnail is not the whole story
When you page through weapon cases, collections, or agents on C5, the grid shows wear tiers and icons. What actually decides pool eligibility, StatTrak rules, and whether inspect shows the right mesh is a single econ row: defindex plus the tags hung on it. Learning that mapping beats memorizing box names and cuts down on wrong listings.
Weapon cases: contents are defindex lists, not skin titles
Each case in data points at a loot list (often labeled contents): a list of item definition indexes, each with paint kit, wear range, and rarity weight. The shop label “Operation X Case” is human-readable shell only. If the same finish lives only in another case’s contents, the drop pool differs and StatTrak eligibility may shift with itemset rules.
A practical habit on C5: lock the case or series in filters → read the weapon base on the row (AK-47, M4A1-S, etc.) → confirm wear and specials (StatTrak, Souvenir) exist in that case’s tier table. Inspect glitches—pattern offset, wrong knife silhouette—often mean paint kit matches but item definition does not, or you are viewing the same pattern on a different base weapon.
Collections: itemset draws the line
A collection in econ uses itemset-style tags to group paint kits under one ruleset: which knives, gloves, and rifles share “born from this series” logic. Cover art on a collection page is usually a representative kit; not every tier in every related case shares the same special attributes.
When you buy or list, “in this collection” means the tag sits in that set—not that the art looks similar. C5’s series filters query that boundary; like the Steam market, the bound defindex + attributes win. Treating two near-identical finishes from different sets as interchangeable is a common trap at trade or showcase time.
Agents: separate defindexes, not the gun skin table
Agent cosmetics use character entries: model, default arms, voice, and badge hooks live in equip region / slot tied to T or CT. They usually do not appear in ordinary case contents; they come from agent packs, operations, or standalone drop tables. The agent column on C5 is another defindex family—do not apply weapon paint-kit logic.
In inspect, note full-model swap versus texture-only: some rows replace the jacket only; others change head mesh and glove interfaces. Before you write “same series agent” in a listing, match faction and slot. As with guns, same display name, different defindex means two distinct items in trade.
Takeaway
Cases govern which pool; collection itemset governs which rule boundary; agents govern human model slot and side. C5 filters are quick entry points on those fields. In-game inspect or a Steam listing check should follow defindex → paint kit → set/tag—that chain keeps case tiers, collection sets, and agent slots from blurring into one mental spreadsheet.