On C5GAME, case names, collection tags, and agent factions sit in one column—but in-match inspect and persona swaps follow separate resource chains. This guide maps shop labels to pool source, series keys, and persona slots.
Lead-in
Open a skin on C5GAME or in your inventory and the page stacks case name, collection tag, agent side, and wear slider like one flat checklist. Step into a server, hit F to inspect, or flip sides and your agent model updates—the client is not reading a single master table. Weapon cases answer which commercial drop or unbox pool the item entered through. Collections answer where it sits in the series taxonomy and some high-tier appearance grouping. Agents occupy their own persona slot. Once you know which in-game resources each chain touches, “same gun, different origin, identical model in-game” stops feeling like a bug.
Weapon cases: pool entries, not skin filenames
On marketplaces the case is cover art and key price; under the hood it is a bundle of entries inside a specific unbox configuration. The “covert from this case” or “knife from this box” is usually item definition + allowed paint kits / special item types for that pool—not the case name baked into the weapon material.
Handy mental model:
- “Contained in case” on the detail page marks which commercial drop or unbox pool first listed this item (historical batches may differ by case revision; in-game it is still the same item id + paint index).
- In-match inspect and kill-feed drops care about the concrete instance (wear, pattern seed, StatTrak, etc.). They do not swap inspect animations because the skin “came from case A vs case B”—animation binds to item type and model, not case branding.
- “Filter by case” on the site filters pool provenance and market narrative, not a hidden in-game parameter.
So two AKs with the same paint kit—one tagged Revolution Case, one Snakebite Case—share identical read order, wear distribution, and default lighting in-game. The gap is circulation story and opening-day pricing, not an extra “case-only highlight” on F.
Collections: series keys for taxonomy and some premium lines
Community talk often blurs “collection” with “case,” but in resource terms a collection is closer to a series / collection key: it groups knives, gloves, and some limited finishes under one display and drop narrative, and sometimes gates whether an item uses a separate pool (classic knife lines, gloves tied to a case family, etc.).
In-game alignment:
- Knives and gloves: the collection name on the listing usually maps to that category’s series row in the taxonomy table. In-match they remain distinct items with dedicated model/material paths—you do not inherit another knife’s inspect track just because the series label differs (unless it is literally a different item).
- Rifle and pistol finishes: for most skins the collection tag is series membership plus drop context. In-game it is still paint kit + wear—no “collection-only second wear formula.” How high float reads still follows that paint’s UV and seed; the collection label does not change that.
- Filters and “complete the set”: filtering by collection on C5GAME helps set completeness and trade-up logic. Equipping a full “same collection” loadout in a match does not trigger extra VFX unless the instance itself carries counters, souvenir flags, or similar fields.
Short version: cases = which pool, collections = which slot in the series map; what you see in-game still resolves to concrete item + paint.
Agent skins: persona slot, fully separate from gun skins
Agents get rarity tiers and detail pages like weapons, but they do not share unbox pool entries with gun skins. An agent is faction + persona (variant / operator skin): side swaps, round intros, and MVP cameras pull character mesh, voice references, and UI portrait—not paint kits.
When cross-checking listings vs match:
- Agent items in inventory unlock one persona look. There is no automatic map from “I unboxed a red from case X” unless an event sold them as a bundle—that is merchandising, not one item id splitting two ways.
- Third-person and demos show agent model and textures. If inspect lets you spin the operator, pivot and specular follow skeleton and character shaders—not the gun’s wear-slider semantics. Agents typically have no wear float; differences are variants and accessories (patches, masks, etc.).
- C5GAME agent pages vs match: pages stress faction and variant name; in-server behavior follows the persona equipped on the pick screen. Owning an agent skin you never equip will not randomly appear mid-round.
Quick reference
| What the page shows | Closest in-game resource | Changes look in-match? |
|---|---|---|
| Case | Unbox / drop pool tag | No (same paint = same look) |
| Collection / series | Taxonomy + some pool story | No (unless different item) |
| Agent name & rarity | Persona unlock | Yes (only if that persona is equipped) |
| Wear, seed, StatTrak | Instance fields | Yes |
When buying, writing guides, or building inspect shots: split instance fields first (wear / seed / special counters), then layer pool and series story; treat agents as persona lookups—do not infer extra animations from case logic.
Closing
Cases, collections, and agents share one rarity vocabulary on shop pages, but the client splits them into pool source, series taxonomy, and persona unlock. Keep that fork in mind and your C5GAME filters for case, collection, and agent each land on the in-game layer that actually drives what you see.