Skins are an officially advertised Retro Tower Defense feature, but the public experience description does not publish a complete cosmetic catalog. A useful skin list records the exact compatible tower, live acquisition route, availability window, and whether the item changes appearance only or has separately documented behavior.
Separate a skin from a tower
Open the inventory card and record skin name, base tower, compatible tier or path, rarity label, event tag, and whether the skin is tradable. Do not list a cosmetic as if it grants the underlying tower. Confirm whether equipping it changes only visuals, sounds, animations, or any live card text.
If the game uses bundles, record every included item separately. A thumbnail can show several characters without proving all are usable skins or that the bundle is still on sale.
Record current acquisition sources
Inspect the Skins interface, shop, event track, missions, codes, badges, passes, and trade panel. Mark each source Active, Rotating, Closed, Return unknown, or Community reported. Save the exact currency and price only when displayed now.
The official experience description mentions Skins and Events, while public Forsaken badge descriptions name rewards delivered in Forsaken. Do not merge a reward for another experience into the RTD skin inventory.
Official badge-linked names
Official collaboration badge descriptions reference 4x4x4x4, Hyperlaser Chance, and RTD Jane Doe as rewards in Forsaken after qualifying RTD accomplishments. These names are Official cross-experience reward evidence, not proof that each is an equippable Retro Tower Defense skin.
Other official badge data may use character or map imagery without naming a skin reward. Read the full description and destination before adding an entry.
Community-reported shop and event skins
Community documentation reports skins associated with c00lkidd and 1x1x1x1 and describes event or shop bundles. Treat names, prices, availability, and compatibility as Community reported until the live interface confirms them.
When a community page shows a catalog, check its last update and compare every card. Preserve stale rows as historical rather than silently presenting them as active.
Cosmetic versus gameplay testing
Equip the skin and compare the same tower card before and after. Confirm placement cost, upgrades, range, attack interval, target count, ability text, and placement limit. If no fields change, label it Cosmetic based on the tested version.
If a value changes, reproduce it in a match and determine whether the cause is the skin, tower tier, trait, or patch. Do not claim a competitive benefit from an animation, color, or larger visual effect.
Trading and collector notes
Trading is official, but not every skin must be eligible. Check the live tradable marker and exact final panel. Collector scarcity, visual preference, acquisition cost, and battle performance are separate fields.
Use the Value List only as dated community evidence. A closed event source may return, and a high asking price is not a completed trade.
Skin-list record
For every verified cosmetic, store:
- Exact skin and compatible base tower.
- Visual theme and changed assets.
- Current acquisition route and cost.
- Start/end time or rotation state.
- Tradable status and variant details.
- Cosmetic-only test result.
- Evidence source and UTC verification date.
Do not use a screenshot filename as the official display name. Capture the text card.
Find focused catalogs
Use Forsaken Skins for the collaboration evidence boundary and Event Skins for temporary-source checks. The Events hub tracks whether a route is still available.
Confidence boundary
The game supporting Skins and Events is Official. The three named Forsaken rewards and their badge destinations are Official. Any RTD skin catalog, c00lkidd/1x1x1x1 association, shop bundle, price, compatibility, tradability, or current availability needs in-game verification or remains Community reported.
Mobile visual check
Preview a verified skin at the normal gameplay camera distance, not only in a full-screen collection model. Confirm that attack indicators, target cues, placement circles, and upgrade buttons remain readable on a small screen. Record visual obstruction as a usability note rather than calling the cosmetic stronger or weaker.
Also test whether another player sees the same appearance and whether lowering Roblox graphics quality removes particles or changes animation visibility. These presentation differences belong in the cosmetic record, while tower statistics remain tied to the underlying live card.