Collection is not a rarity name
Collection and rarity answer different questions in an item card. Collection groups designs; rarity is a separate grade. Keep them apart in spreadsheets and filters. When one field is missing, do not fill it with the other field's value. A familiar collection name cannot automatically assign a grade to every member, and a rarity color cannot identify the collection. Exact matching requires the complete attributes supplied for the item.
Test the filter combination
Begin with one collection, then add a desired rarity category. If results shrink, record precisely which filter was added. Do not interpret removed results as items disappearing from the collection. Restore the broader search and check whether the desired designs appear. Review weapon model and exterior separately: an extra restriction can explain an empty search independently of collection. Change one condition at a time so the cause remains visible.
One color does not establish one grouping
Two finishes may share a rarity strip while differing in collection and weapon model. That can support a grade search but does not make them identical listings. If your goal is a collection-based set, confirm each position's collection. If the goal is a coordinated palette, review the actual finishes rather than the administrative marker color. Those are different ways of building a shortlist and should use different inclusion criteria.
Keep independent attributes in a table
| Attribute | Purpose |
|---|---|
| Collection | Design grouping |
| Rarity | Item category |
| Weapon model | Specific equipment position |
| Finish palette | Visual compatibility |
| Exterior | Separate specimen filter |
Do not infer price or acquisition probability solely from a collection name and colored strip. Read a case's contents and conditions separately. Search model and design name in the finder; verify collection and rarity separately in the available item details. See the cross-weapon palette guide for design color versus administrative labeling.