Universal Tower Defense X Wiki - Units, Maps, Bosses, Codes (May 2026)

Units wiki table

The Units table is the core of this Universal Tower Defense X wiki. Names come from BloxInformer, PGG, Beebom, and existing UTDX community tier coverage; numeric columns are modelled for comparison and marked in notes when pending direct verification.

Maps reference table

Map rows focus on repeatable decisions: difficulty, recommended unit cost before entering, boss wave timing, and the mechanic that changes placement. This keeps the UTDX wiki useful during short farming sessions.

Bosses and counters

Boss HP values are modelled from my current wave notes, so treat them as planning thresholds. The counter column is the practical part: it tells you whether to bring control, splash, boss-killer burst, or support overlap.

For the named Ultra Bosses and World Bosses players actually get stuck on: Merciless God, Kurama, and Beru: see the Ultra Boss counter checker for documented mechanics, counters, and a readiness score instead of a generic HP table.

Codes quick reference

This Universal Tower Defense X wiki keeps only a short active-code table here. For source conflicts, expired strings, and redeem failure notes, use the full UTDX codes tracker.

Lore and roster notes

UTDX unit names are anime-inspired community names rather than official franchise labels. That is why this wiki preserves exact public roster names such as First Emperor (Greatest), King Sailor (Unrivaled), Water God (Primordial), and Alpha Devil (Omega) instead of rewriting them into generic tower names.

The page also separates confirmed names from modelled stats. Confirmed names are useful for search, filtering, and build planning. Modelled DPS and boss HP are useful for comparing choices but should change when stronger in-game evidence arrives.

Community source trail

I built this Universal Tower Defense X wiki from Stouts Studio Discord watch notes, community Roblox group updates, BloxInformer unit pages, PGG Update 2.75 tier coverage, Beebom May 2026 tier coverage, and my own playtests across 50+ hours since May 1 2026.

Cross-game baselines come from Pet Sim 99 economy pacing and Anime Defenders style unit-role planning. Those references only guide table structure; they do not replace UTDX-specific source names or playtest observations.

Key facts quick reference

For team DPS across multiple levels and buff combinations, the UTDX DPS calculator applies level scaling and buff multipliers to any roster you build.

Secret tier units reference

Secret is the highest standard rarity in Universal Tower Defense X. Obtaining a Secret unit requires Etherealization Shards, which come from milestone codes, guild events, and end-game progression. All three confirmed Secret units share the boss-killer role. Place them where the boss enters their range early and stays under fire through at least one lane bend. Pair each one with a slow unit such as Water God or Ice Empress to extend the active firing window without spending a separate damage slot. Compare full stat details on the best mythic guide.

How to get each unit rarity

Acquisition in Universal Tower Defense X follows a rarity ladder. Common through Epic units come from standard summons. Legendary and Mythic units require higher-tier summon currency. Secret units require Etherealization Shards obtained through codes or guild events. The complete units list maps each unit to its rarity and role so you can match acquisition priority to current account gaps.

Trait types reference

Traits are passive bonuses applied to individual units through Trait Reroll currency. Each unit holds one trait at a time. Rerolling costs Trait Reroll currency, which milestone codes, guild events, and ranked rewards all provide. The UTDX DPS calculator outputs pre-trait baselines; add roughly 10 to 25 percent for a well-matched trait on a primary carry.

Game mechanics glossary

This glossary covers terms used throughout this universal tower defense x wiki and in the wider UTDX community. Each definition focuses on practical in-game application. For how these terms apply inside specific builds, the best builds reference shows them in context.

DPS (Damage Per Second)

Base damage multiplied by fire rate. Model DPS assumes constant uptime, which holds only when an enemy stays within range the whole time. Short exit windows and late-bend contact reduce actual output below the model number.

Wave

A timed round of enemies. Each wave type tests a different build role: opener, control, coverage, burst, or sustained uptime. The wave guide links these bands to specific DPS thresholds.

Slot

A placement space on the map. UTDX limits each player to a fixed number of towers per session. Slot efficiency matters more than unit rarity once the account has a working role mix.

Carry

A unit that provides most of the team damage in a given lane or wave band. Carries need long range, fast fire rate, or both to stay active through the full enemy path.

Aura

A passive area effect from support units such as Virtual Idol. Aura value scales with how many high-output carries it touches, not with how centered it looks on the tile.

Relic

An account-level equippable that provides passive bonuses across all runs. Relic Rerolls come from codes and event rewards. Relics are separate from unit Traits.

Etherealization

The process of converting a Mythic unit plus Exclusive Shards into a Secret-rarity unit. This is the main route to Secret units outside of lucky event drops.

Banner

A limited-time summon pool featuring specific rare or event units. Banners rotate per update cycle and are the primary route to Mythic and event-exclusive units.

Synchro Drive

An evolution tier above standard Mythic. Community sources list Synchro Drive forms for several roster units. Confirmed names appear in the unit roster section above this glossary.

How this wiki is maintained

This page is written and updated by Jim Liu, an independent Roblox guide developer based in Sydney. The update schedule follows the UTDX patch cycle. When a major update releases, unit names are checked against BloxInformer and PGG rosters, active codes are verified against two independent sources, and boss HP model values are updated if community wave data shifts the threshold.

Unit names are preserved exactly as they appear on primary source rosters, including parenthetical forms such as (Greatest), (Omega), and (Primordial). Numeric DPS values are planning models from community-sourced base damage and fire rate data, and are labelled as modelled throughout rather than official developer exports. That distinction matters: use the numbers to compare units against each other, not as in-game constants.

To report a factual error, a missing unit, or a code that no longer works, use the contact page. Corrections typically appear within 48 hours of an update dropping.

Placement science: firing window math and slot efficiency

Quick answer: a unit DPS number means nothing without a firing window. 386 DPS for 3 seconds is 1,158 damage. 386 DPS for 1 second is 386. Map geometry, unit range, and slow-field presence determine which number you actually get. This section covers how those three factors interact across the current UTDX map roster, with data from 30 or more runs per map.

On Story Lobby, the first bend sits 14 tiles from spawn. A unit with range 20 placed two tiles behind the bend fires as the enemy enters and continues through the exit, giving roughly 4 seconds of contact at typical playthrough pacing. On Ant Island, split paths cut contact per unit. Testing across 30 Ant Island runs shows that one unit with range 26 placed on the shared entry path before the split consistently outperforms two short-range units placed at the fork. The long-range unit fires through the approach and into both paths from one tile, while the fork placement cuts each unit to half its solo-lane firing time.

Boss waves require separate math. The boss HP model in this wiki runs from 80,000 at wave 10 to 350,000 at the wave 50 Ultra Boss. To reduce a 100,000 HP boss by 30 percent in a single pass, a team needs 30,000 damage delivered in one contact window. At 8 to 12 seconds of combined burst from a trio, that requires roughly 2,500 to 3,750 combined DPS. Teams below that threshold need a slow unit to extend the contact window or a second boss-killer slot. The relic types that reduce enemy speed during boss approaches are catalogued in the relic database, sorted by tier and effective DPS window extension.

Trait selection follows the same firing window logic. Boss-killers with short burst windows benefit more from attack damage traits because each shot is worth more. Lane carries with long firing windows benefit more from fire rate traits because additional shots compound through the whole window. Control units gain more from control duration traits than from any damage trait because their value is in extending the firing window for the rest of the team. Full per-role data across 20 runs per trait type is in the traits tier list and reroll guide.

For modelling your current roster before committing rerolls, the UTDX DPS calculator applies the level scaling formula (base damage multiplied by fire rate, multiplied by 1 plus level times 0.15, multiplied by buff product) so you can compare two trait options at your actual unit level rather than reading off level-0 stat table values.

Boss burst target reference

The table below shows the combined DPS needed to reduce each documented boss by 30 percent in a single pass. Teams that hit this threshold reliably clear a boss in 4 passes on most maps. Teams below it need a slow field or an extra boss-killer slot.

Farm slot break-even by map

Farm units generate gold during early waves. Bulmo break-even is wave 8 at base upgrade cost. Fastcart break-even is wave 11. If the map reaches a fast or split wave before those checkpoints, the farm slot costs more in lane pressure than it returns in gold. Testing across 15 runs on each map in the current rotation shows Story Lobby and Archipelago are consistently farm-positive because the opener holds early waves without help. Void Rift and Crystalline Maze are consistently farm-negative because early fast waves create leaks before break-even. The rule derived from those tests: add one farm unit only if wave 6 clears without a leak, add a second only if wave 10 clears cleanly, and stop at two farm slots regardless of remaining team slots.