Ever noticed a skin looks different on C5GAME, Steam Market, and in your own client? It's not filters—it's because weapon cases, collections, and agent skins are three separate resource lines with different indexing logic. Here's how they really work.
If you've opened a lot of cases, you've probably wondered: why does the same skin for the same gun look slightly different on C5GAME's listing page, on the Steam Market page, and when you press F to inspect it in your own client? Most people's first guess is "screenshot filters" or "seller edited the image." But most of the time, the issue is that weapon cases, collections, and agent skins are three resource lines that simply don't share the same indexing logic.
Weapon Cases: One Case File Manages an Entire Drop Table
In game resources, a weapon case is essentially a "container definition." Inside, it holds several drop entries, each pointing to a specific weapon + finish combination. What you unbox isn't "a certain gun"—it's "a finish entry that gets randomly hit and then instantiated into a gun with wear and pattern seed."
This leads to two often-overlooked consequences. First, the finishes inside a case can be individually replaced or added—so old cases occasionally get "same case, different batch" talk, which is really just the entry table being modified. Second, the case itself doesn't store wear; wear is calculated from the seed at instantiation. So any wear range you see on a trading page is a statistic at the entry level, not a property of the case.
When comparing in-game resources, the correct approach is: lock onto the case first, then look at its current entry table, and only then compare the specific gun. Skipping the middle layer and directly comparing wear numbers of two guns easily leads to the illusion of "how can 0.15 be so different?"—because different pattern seeds mean different pattern placement.
Collections: Independent Mapping, No Shared Namespace with Cases
Collections are another line. They don't drop from cases; they're directly tied to a map or event. In resource structure, a collection is more like a flat list, each item directly stating weapon and finish, without the "container → entry → instance" nesting.
This explains a common phenomenon: why the same finish can appear in both a case and a collection, yet prices differ. Because at the resource level, they are two independent records, and the market prices them separately. When you filter "Collections" on C5GAME, you're filtering this flat line; when you filter "Weapon Cases," you're filtering the container line. The two don't interconnect, so don't apply the average price of one line to the other.
Another detail: collection inspect pages often lack a "case source" label, because there is no case. If you see someone pricing a collection item based on "which case this gun came from," you can ignore it—that's mixing two resource lines into one.
Agent Skins: They Use Model Slots, Not Finish Slots
Agents are most easily misclassified. It's not "applying a finish to an agent"—it's replacing the entire model + textures + some voice resources. In resource structure, agents use model slots, completely separate from the texture mapping system for weapon finishes.
So you'll see: the concept of "wear" barely exists for agents, and there's no pattern seed reveal like weapons. Their visual differences come mainly from the model's own materials and lighting response, not wear values. Applying weapon experience of "wear affects pattern" to agents will inevitably fail.
When comparing in-game resources, the correct entry for agents is model preview, not finish preview. If C5GAME's agent listing page differs slightly from the client preview, it's likely due to different rendering environments, not a resource error.
How the Three Lines "Merge" in the Client
When the client finally displays, it unifies these three lines into "inspectable items." But what's unified is the display layer, not the data layer. Guns from cases, guns from collections, and agents are still three sets of indexes underneath. What you see when pressing F is the display layer's calculation based on current lighting and angle; what you see on a trading page is the display layer's calculation based on another set of rendering parameters. If they don't match, it doesn't mean one is wrong—it just means they were never the same calculation.
One practical tip: when comparing prices, wear, or patterns, first confirm you're comparing the same resource line. Case to case, collection to collection, agent to agent. Cross-line comparisons, no matter how close the numbers, won't hold up.
Next time you browse listings on C5GAME, ask yourself: which line am I looking at? Once you're clear on that, many "mystical price differences" will instantly become unmystical.