From reference to a usable plan
Give each slot a reason to be there.
Team Builder records a plan. It does not certify a legal loadout, reproduce every buff, or predict a win.
Read the effect before choosing the unit
Write down four things
- The trigger: what event activates the ability?
- The target: self, an ally, a position, or another defined group?
- The value at the level and form you plan to use.
- The lifetime: does the description say permanent or battle-only?
Use the reference, not a name alone
Two units with the same type can have different triggers and targets. A type label does not establish an interaction.
Read the current entry's normal and shiny values. An unavailable field is not permission to fill it with the nearest familiar value.
Open the Batomon catalog →For example, Furnadon's description ties additional Burn to owned trinkets. Before planning around it, inspect its level values and your chosen trinkets. That relationship does not establish a preferred lineup or win rate.
Read Furnadon's printed effect and levels →Use an observed Comp as a starting point
Check the window, rank band, and number of players first. Then open the phase view instead of copying only the final representative team.
The Comp grid represents common units, not verified combat positions. Do not infer an ally-above or adjacency interaction from its display order.
Use Modify build in Lab to keep supported selections. Check each slot's level and form before changing the plan.
Understand the sample before comparing results →Keep unknown information visible
A plan can preserve an unknown ID
Imported builds may come from another patch. The builder warns about unavailable units, equipment, levels, or forms instead of silently replacing them.
Decide whether to keep that historical plan or deliberately update a selection. Do not mistake current reference art for proof of the old statistics.
A transferred board is partial
A Companion example can transfer supported species, level, form, trainer, and trinket fields. Unknown equipment and buff sources remain unresolved.
The example is synthetic. It is useful for learning the controls, not evidence of an actual player's result.
Try the labeled example →