Role & planning notes
Vejita (Ultimate Majin) is the fully named form used by this directory. It should not be confused with unrelated early-game characters whose names resemble Vegeta. The main planning issue is the total investment required to reach the intended role, especially when a strategy also depends on a second developed unit.
How to get Vejita (Ultimate Majin)
The historical DBZ update guide describes summoning the Majin base and evolving toward Ultimate Majin. It also describes a separate in-match fusion involving an evolved Goko. Verify both the current evolution recipe and the actual fusion controls before collecting materials. A temporary battle transformation should not be advertised as a permanent unit automatically added to your inventory.
Skills & verification status
The historical fusion route combines fully upgraded Goko and Vejita, followed by a summoned boss encounter. That is a conditional mechanic, not an always-active bonus from merely owning the pair. Current availability, costs, and requirements need an X-version test. We do not assume that the old trait interaction or fusion behavior survived unchanged.
How to use this form
Budget the complete setup before evaluating a fusion plan. Count the cost of both units, all prerequisite upgrades, and the defensive resources needed while preparing the encounter. Compare that with a simpler squad spending the same money on ordinary damage. If a stage ends before the setup is ready, the impressive late result may not help that particular mode. Record the earliest safe activation point rather than only the final damage.
Team pairings to compare
Goko is the historical mechanic partner, but his detailed page is outside this first batch; locate the exact form in the tier list. Use Speedcart or Loid as alternative economy tests. Useless Goddess is a conditional support candidate if the current damage classification and range rules match. Do not assume that a support affecting the unfused unit also affects a transformed form identically.
What to record in a test
Document both unit names, their upgrades, the ability prompt, the triggered encounter, and the resulting form. Note whether the transformation persists after leaving the match. Keep a separate record for ordinary Vejita performance so a reader without Goko can still evaluate their own copy. A useful comparison includes preparation time and survival, not just the biggest number shown after the transformation.