There is no official fixed Retro Tower Defense trading value list in the public game description. Values are community estimates shaped by supply, current availability, demand, exact variants, and what trades actually complete. This page deliberately avoids invented numbers and gives each observed value a date and confidence level.
Identify the exact asset
Record tower or skin name, tier or path, trait, level, serial, event label, and any lock or tradable state. Do not merge a base tower with an upgraded tier, a skin with its underlying unit, or two copies with different traits.
Open the live card at the time of the trade. If a field is not visible, mark it Unknown. A cropped chat screenshot cannot establish the exact item.
Separate value factors
Supply depends on how many eligible copies exist and whether more can enter. Availability asks whether the original banner, event, mission, code, badge, or shop route is open. Demand measures current buyer interest. Utility covers battle performance, while collectibility covers appearance, history, or serial interest.
These factors can move in different directions. A balance nerf may reduce combat demand without changing scarcity. An event rerun can increase supply even if the item remains popular.
Prefer completed observations
An asking price is not a completed trade. Record final trades where both exact offer panels are known. Keep bundle trades separate until every component has a reasonable reference; otherwise one unknown item can distort the whole comparison.
Use a rolling window and show the number of observations. One unusual trade should remain Low confidence. Several recent, independent, exact-variant trades can move a range toward Medium confidence, but they still do not create an official price.
Use external lists carefully
Community services such as Vaulted Values can be useful comparison points. Label the service, update date, unit, and exact variant. Never copy its number without checking whether its scope matches the live item and whether the original source has returned.
If two community lists disagree, show the disagreement instead of averaging it into false precision. Investigate differences in date, tier, trait, demand category, and completed-versus-asking evidence.
Apply confidence labels
Use High community confidence only for many recent matching observations with clear cards. Medium covers several consistent records or one reputable maintained index. Low covers sparse, old, bundled, or unverifiable reports. Unknown means no safe range.
Official refers only to facts such as the game supporting Trading or a live card’s exact text. A numerical trade estimate should not be labeled Official unless Plaything Games publishes it in the live system.
Track update risk
Record event end dates and whether the source may return. A collaboration title or public badge confirms historical context but not permanent retirement. Mark values sensitive to a rerun, new banner, balance patch, trade-eligibility change, or duplication incident.
When a major update lands, freeze the previous list and start a new dated snapshot. Do not silently blend pre-update and post-update observations.
Working value-list fields
Each row should contain:
- Exact item and variant.
- Current acquisition status.
- Community reference range and unit.
- Number and dates of completed observations.
- Demand and trend label.
- Battle utility versus collector premium.
- Confidence and known risks.
- Last live-card verification.
Use ranges rather than a single exact point when evidence is noisy. Avoid decimal precision that the market cannot support.
Make a trade decision
Compare the exact give and receive bundles with the Trading Calculator, then apply uncertainty. If a low-confidence item decides the outcome, wait or negotiate a safety margin. Read How to Trade before using the final panel.
Never trade only because a list shows a green trend arrow. Ask whether the item improves your collection or loadout and whether you can tolerate a rerun or balance change.
Confidence boundary
Trading’s existence is Official. Community value sites, observed offers, completed-trade ranges, demand labels, and forecasts are Community reported. Live eligibility, exact variant identity, and acquisition status need in-game verification on the same date as the valuation.