A Roster You Cannot Read Is a Raid You Will Not Win
Transformers Earth Wars alliance combat demands roster decisions made fast: which bots go in the wave, what ability levels are currently active, which units are maxed and which are mid-upgrade. A competitive alliance leader pulling 15 bots for a raid does not have the cognitive bandwidth to hold every unit's current DPS, health pool, and range classification in working memory while simultaneously coordinating attack waves in the alliance chat.
The roster database is the answer. Not a screenshot gallery that requires opening each image individually — a filterable, sortable record per bot where the combat-relevant data is visible in a single view.
The Combat Numbers That Determine Wave Composition
The Damage (DPS) field captures the bot's damage output at current level, not the theoretical max. This distinction matters because a maxed 3-star Grimlock has a different DPS profile than an in-progress 4-star unit that is currently sitting at lower star deployment. The Power field combines power plus level into a single numeric indicator — the in-game composite that determines your team power score for matchmaking and base defense assignments.
Health is the other half of the attritional calculation. A high-DPS Gunner with a fragile health pool may be less useful in sustained ground combat than a Warrior with moderate DPS and a deep health pool that survives the defensive turret rotation long enough to reach the nexus. The Speed field adds the third variable: a fast Air unit can close ground before defenses rotate, but a slow AoE bot needs a clear engagement window that faster units create.
The Range field is where the tactical nuance lives. Long-range Gunners engage from outside most defensive perimeters. Short-range Warriors need to be within melee distance. Understanding the range profile of each unit in your roster before composition is not optional at the competitive alliance level.
Ability Levels and the Maxed Flag
The Ability Level field tracks the current upgrade state of the bot's special ability, separate from overall power. A bot at Class 4 with an Ability Level of 1 is fundamentally underperforming its potential. The Maxed boolean tells you immediately which units are at ceiling without scanning through individual entries. Filter on Maxed = false and sort by Power — that is your priority upgrade list.
The Abilities field carries the specific ability descriptions: what the ability does, its cooldown behavior, its interaction with specific defensive building types. This is the context that turns a roster database into a tactical reference. Knowing that a specific bot's ability bypasses shield generators informs wave composition against shield-heavy bases.
The Class field runs 1–5 stars. A five-star maxed Warrior is a different asset from a two-star maxed Warrior, and both are different from an in-progress three-star. The class filter lets you quickly isolate your five-star roster for priority raid deployment while tracking the development status of lower-class units.
The BIO field carries faction lore and mode descriptions. The Bot Mode and Alt Mode photo fields display the unit's two visual states. These are not combat-critical, but in a collection database that you also use to track character acquisition completeness — knowing which Decepticons you are still missing from a full faction lineup — the visual reference per unit is the fastest identification method when scanning the alliance roster against your own records.