Anime Origins Characters and Observed Roles
A source-backed Anime Origins character list covering visible launch units, observed jobs, and what still needs live confirmation.
Units shown in public previews
The https://www.youtube.com/watch?v=QLhQ_SaxZ1k tour shows a launch roster containing anime-inspired versions of Yuta, Meliodas, Ichigo, Vegeta, Naruto, Kenpachi, Goku, Toji, Bulma, Choso, Estarossa, Trunks, King, Nell, Diane, Nobara, Miwa and Kakashi. Another recording uses Shinobu for poison and obtains Akeno to cover flying enemies.
| Unit shown | Observed job or mechanic | Practical use |
|---|---|---|
| Bulma | Income generation | Fund upgrades only after the opener is safe |
| Toji | Cone damage and manual target position | Aim down a long lane; do not assume buff support works |
| Yuta | Limited placements, evolution and copied actives | Build around allied active abilities after evolution |
| Akeno | Hill/flying-target coverage | Prevent air waves from bypassing ground damage |
| Shinobu | Poison damage-over-time | Place early so the effect has time to tick |
What the list does not prove
Preview banners are snapshots, not permanent availability tables. A unit visible in the index may rotate out, change rarity or receive a different translated name. The useful conclusion is its demonstrated role. Check the current in-game banner and ability panel before spending; do not use this page as proof that a named unit is currently obtainable.
Other visible names in the reviewed roster include Meliodas, Ichigo, Vegeta, Naruto, Kenpachi, Goku, Choso, Estarossa, Trunks, King, Nell, Diane, Nobara, Miwa and Kakashi. Their presence proves they appeared in that preview index; it does not establish today's rarity, banner rotation or best build. Open the current ability card and assign each one a role before replacing a known utility unit.
A safe roster note should record target type, initial cost, placement limit, final attack shape and whether evolution changes the job. Those five fields are more actionable than a letter tier because they explain where the unit belongs and what kind of stage exposes its weakness.
Treat this as an observed roster, not a promise of current availability.
The watchlist should group characters by job, not by excitement. Bulma belongs in an economy column because the reviewed videos use her as an income signal. Toji belongs in a restricted-damage column because his visible tradeoff changes whether support buffs are useful. Yuta belongs in an evolution and active-ability column because copied abilities make team context matter. Akeno belongs in the air-coverage column, while Shinobu belongs in damage-over-time testing. That structure gives players a useful roster table even while public access remains restricted.
Add one more field to every watchlist row: why the unit was observed. A unit seen only on a banner should not receive the same confidence as a unit placed in Story. A unit seen in a trait panel is evidence for trait interaction, not necessarily for clear speed. A unit seen in a boss fight can support a damage note, while a unit shown in the lobby may only support identity. This confidence field keeps Bulma, Toji, Yuta, Akeno and Shinobu useful without pretending every value is final.