Define the specific decision
Separate the list into two sides and shared entries so the same wish does not appear twice in the plan.
For candidates relevant to “Split a CS2 inventory plan between CT and T”, use the skin finder. Keep this task separate from your broader inventory plan.
Read the worked example
A fictional set contains one shared pistol, two separate primary weapons and a shared knife; the knife is counted once.
The point of the split is to expose repetition, rather than to force identical totals for both sides. When an item belongs to the shared group, put a reference to it in the side lists instead of creating a second full record. A change to the shared candidate then needs only one edit. Give each side one entry that sets its visual direction and one supporting entry. Avoid assigning contradictory roles to a shared item. Test the structure by temporarily hiding the shared group: the CT and T plans should remain understandable. Restore it and check that the combined total rises only by the shared entries.
| Entry | Interpretation |
|---|---|
| CT | an independent anchor entry |
| T | a separate main accent |
| Shared | one record instead of two copies |
Use this task checklist
- Create CT, T and shared columns.
- Assign every entry one main group.
- Check shared entries before adding totals.
Recognise the failure condition
Copying the same item into both lists and adding its value twice.
Each side has a short independent list, with shared entries recorded separately.
Apply the additional check
Use three subtotals for reconciliation: CT, T and shared entries. References to a shared pistol in both side groups do not enter the arithmetic. Fictional values of 25 for CT, 30 for T and 10 shared produce a combined total of 65, not 75. Check that an export preserves this logic. The shared item's caption can identify the two entries it visually connects, helping preserve that combination during a later replacement.