Universal Tower Defense X Sources
Every changing fact should keep a source URL, source name, checked-at timestamp, and verification status.
SEO trust rule: codes, Discord-only announcements, and update-dependent claims need fresh source timestamps. Stable wiki facts can be source-backed, but still keep their source URL visible.
Official place page and canonical game source.
Used for live game metadata, player count, visits, favorites, and update timestamp.
Used for creator group, owner, member count, and verified badge.
One of four code reconciliation sources. Active and expired lists are not treated as official.
One of four code reconciliation sources.
Used as a reference source only because its active list kept older codes active.
Used for unit, relic, trait, map, and some code data.
Primary Update 2.75 tier-list source.
Comparison source only; it covers Update 2.5 and misses later units.
Used for public Discord member and online counts. Internal channels were blocked and are not treated as verified.
Used for search-intent clustering and page-priority decisions.
Used for demand signals and content topics, not official game facts.
Used to build the update archive. One referenced doc returned 401 and was excluded.
Universal Tower Defense X source FAQ
The ledger separates official evidence, source-backed evidence, and claims that still need checks.
What does the Universal Tower Defense X source ledger track?
It tracks source name, source URL, checked-at time, verification status, and notes for game metadata, codes, tier lists, wiki facts, update logs, and demand research.
Which sources need the most frequent checks?
Codes, Discord-only announcements, and update-dependent claims need the most frequent checks because those facts can change faster than stable wiki data.
Does source-backed mean official?
No. Source-backed means the claim has an accessible source. Verified is reserved for official Roblox, official API, public Discord invite, or similarly direct evidence.