We often lump weapon cases, collections, and agents together on C5GAME, but in the game's resource tree they are distinct nodes. This article breaks down their structural differences and how they intersect.
Many players browsing cases on C5GAME tend to treat weapon cases, collections, and agents as the same thing—containers that yield skins. But in the game's resource tree, these are not at the same level. Today, we'll dissect these three treasure-hunting paths from the perspective of the resource tree structure.
Weapon Cases: Independent Nodes Under the "Container" Branch
Weapon cases belong to the weapon_cases or similar container category in the resource tree. Their characteristics: a defined drop pool, a key to open, and a unique serial number. When you open a Dreams & Nightmares case, the system first checks the container's contains field, which lists the reference IDs of 17 items.
A commonly overlooked point: the drop pool of a weapon case is a static reference. What can be unboxed is already written in the resource files when you obtain the case. The "possible contents" shown on C5GAME's listing page is simply a rendering of this static table, using the same data source as the scrolling icons in the in-game inspect window.
So when someone says "this case no longer drops a certain item," they're likely confused—the case's contents don't change; what changes is the market's valuation of the drop probability.
Collections: Sets Under the "Map Drop" Branch
The biggest difference between collections and weapon cases is: a collection is not an interactive container but a tag set. For example, the "Ancient Collection" is essentially a set of item IDs that enter the game through map drops, souvenir packages, or upgrade drops.
In the resource tree, the collection node's role is categorization; it doesn't distribute items. When you open the "Collections" page in-game, you see a preview of this set, not a clickable unboxing button. This is evident in C5GAME's filters: collections usually appear as a filter dimension, not as a standalone product page.
Souvenir packages are special—they hang under both "Collections" and "Containers" branches in the resource tree, so they can be opened like cases and are also grouped into the corresponding map's collection. This is why the price logic of some souvenir packages differs completely from regular cases.
Agent Skins: Appearance Replacements Under the "Character" Branch
Agent skins are the most unique of the three paths. They are not under the weapon container branch but under agents or character-related nodes. What you unbox is not a gun but a character appearance replacement.
The structure of an agent node in the resource tree is: agent_id → model + voice + patch_slots. This means agents don't participate in wear calculation (no float value) but have an extra dimension: patch slots. When you see an agent listing on C5GAME with a "patched" note, that means a patch reference is attached to the character node.
Interestingly, the display logic of agents in the inspect window is completely different from weapons—weapons rotate 360 degrees, while agents use fixed angles with gesture animations. The reason: character models have far more polygons than weapon models, making real-time rotation rendering too costly, so pre-rendered inspect animations are used instead.
Intersections of the Three Paths
Although the three paths belong to different branches in the resource tree, they intersect in two places:
First, the drop system. Weekly upgrade drops can give weapon cases, collection items, or graffiti, but not agents. Agents mainly come from specific weapon cases (like the Broken Fang case) or direct purchase.
Second, market display. Platforms like C5GAME, when rendering product pages, pull data from different branches of the resource tree and piece them together—weapon cases pull the contains table, collections pull the collection tag, agents pull the model preview. The three types of items you see on the same page actually come from three different data structures.
Once you understand this structure, you can instantly tell when browsing C5GAME: which items are "unboxed," which are "dropped," and which are "traded." This isn't mysticism; it's the branch logic of the resource tree speaking.