Stark

Stark is the Frieren-themed ability — Stark is the Hero Apprentice from the Frieren: Beyond Journey’s End anime. He places in A-tier per PGG and Beebom roster mentions, but neither source provides a detailed per-skill damage table.

Why this entry is needs_check

Stark sits in a documentation gap:

• Tier 1 / Discord faq: not listed in Foong’s Best Abilities Damages base-damage table (2026-05-12)
• Tier 1 / Discord faq: not in Rolasyum’s Best Traits on Abilities category breakdown (2026-05-10)
• Tier 2 / aggregator: PGG and Beebom name Stark as A-tier in their roster overview but give no kit details, no m1/z/x/c/g/v damage breakdown, no recommended trait

The site flags this as needs_check until either a Discord developer post or a written aggregator deep-dive surfaces concrete data. Until then, treat the A-tier placement as roster-mention only — actionable only as “Stark exists and isn’t bottom-tier.”

What we DO know

• Stark’s rarity is not enumerated by Tier 1 (Discord faq) or any Tier 2 aggregator we cross-referenced — left as null rather than fabricated
• Stark shares no IP with any other ability in the current roster — it is the only Frieren ability documented
• Stark is not on any of the three meta builds (Reaper Burst Raid / Flash Wave Survival / Early-Game Infinite) per the official Discord meta build threads

When to revisit

This page will be promoted to verified once any of the following lands:

1. A Discord faq entry from Foong / AE / Shiroo with the Stark base-damage table
2. A FRVR / BloxInsider / FFBooyah deep-dive with the Stark kit
3. An in-game UI screenshot of Stark’s slot text

How Stark compares to the other Tier-1-absent abilities

Stark is one of three abilities in the roster that does not appear in Foong’s 13-ability base-damage table (the other two are Ninja and Blade). All three share the same documentation gap, but Stark’s third-party placement is materially different from the other two:

• Stark — A-tier (PGG): roster-mentioned as A despite no kit detail surfacing
• Ninja — D-tier (FRVR): bottom band on single-source assessment
• Blade — D-tier (FRVR): bottom band on single-source assessment

This A-tier placement is why Stark gets a kit-data placeholder (“needs_check” with a clear revisit plan) rather than the roster-completeness treatment used for Ninja and Blade. The site treats Stark’s A-band placement as directionally meaningful but mechanically un-actionable until Tier 1 data surfaces.

docs/04-tier-list.md §4 logs the Stark existence question explicitly in the source-vs-source conflict table — PGG says yes; FRVR doesn’t mention the ability at all; Foong’s Tier 1 base-damage table has no row for it.