FAFrontier ArcanaField Dossier

Bosses

First-Season Boss Roster

The selectable Meteor Fall boss variants, their combat jobs, reward lanes, and when a town should choose each fight.

Linked item: meteor_core - legendary - event

06Dossier 4Sections 26Field notes 6Linked pages

How Boss Selection Works

Players can summon a specific boss with /event summon <boss> after preparing the required town supplies. Natural bosses do not start first; a town has to choose its first summon.

  • meteor_warden costs a Meteor Report and Warden Lure.
  • cinder_mauler costs a Meteor Report, Warden Lure, and Cinder Flask.
  • astral_sentinel costs a Meteor Report, Warden Lure, Beacon Lens, and Rally Charge.
  • obsidian_colossus costs a Meteor Report, Warden Lure, Ward Foundation, and Stonework Bundles.
  • rift_weaver costs a Meteor Report, Warden Lure, Cleansing Charm, and Ward Pulses.
  • These materials come from Scout, Hunter, Mason, Alchemist, Ward, and Beacon station work, so boss calls become town logistics.
  • Before that first deliberate summon, ambient corruption can still appear as warning pressure.
  • Operators can still start free tests with /event start <boss> or /faadmin spawnboss <boss>.

Town Readiness

Different bosses solve different town bottlenecks. Choose the fight that feeds the next civic requirement instead of farming the easiest encounter forever.

  • Fight Meteor Warden when the town needs first Sigils, Meteor Cores, and basic event mastery.
  • Fight Cinder Mauler when Alchemists and Forge Bellows are blocked by cinder materials.
  • Fight Astral Sentinel when Astral Beacon, rally routing, or ward projects need lenses and threads.
  • Fight Obsidian Colossus when Mason work, roads, ward foundations, and structure defense are the bottleneck.
  • Fight Rift Weaver when corruption cleanup, ward pulses, and cleanse supplies need to become a real town discipline.

Encounter Roles

Boss variety is meant to create different field roles. The Warden splits miners and damage dealers, the Mauler tests spacing and recovery supplies, the Sentinel tests interrupts, the Colossus tests structure defense, and the Weaver tests cleanse discipline.

  • Bring recovery and fire readiness to Cinder Mauler attempts.
  • Bring ranged weapons and mobility to Astral Sentinel attempts.
  • Bring Mason stock and defenders to Obsidian Colossus attempts.
  • Bring Cleansing Charms, Ward Pulses, and Recovery Kits to Rift Weaver attempts.
  • Keep all bosses near the event crater to avoid leash resets and structure pressure.

Operator Testing Checks

Stress-testing active bosses is easiest when stale entities are removed between runs, and health feedback stays tied to the real boss and its bossbar.

  • Bosses use a hidden real Warden as the AI/health brain (`frontier_boss_brain`), a resource-pack display rig as the visible body, and `Interaction` hitbox proxies (with explicit size and responsive settings) to route player hits into boss health.
  • Boss name tags are hidden on purpose; the bossbar carries name, phase, health, and timer so repeated tests do not stack unreadable labels across the fight space.
  • Bosses keep per-boss colored `fa_boss_<boss>` scoreboard team identity and glow during combat, with readable health and phase on the bossbar.
  • Runtime event budgets cap Meteor adds at 10 active minions, per-site danger defenders at 6, and danger-site minions at 36 total; cleanup also removes legacy custom-named boss bodies from older broken test builds.
  • After repeated boss or station trials, run `/faadmin cleanup` to remove orphaned Frontier event mobs, stale boss model rigs/hitboxes, inactive event minions, legacy event mobs, stale `fa_boss_<boss>` scoreboard teams, and station display/worker entities whose station row no longer exists while preserving the active boss.
  • Startup resume runs the same orphan sweep for station entities, so restarting should keep station visuals from duplicating after a prior invalid record state.
  • Use `/event status` and hit the active boss once after cleanup; the bossbar should update immediately to the real boss health.
  • Before starting the next operator shortcut (`/event start <boss>`), run cleanup again if labels, models, or minions from previous tests are still visible.

Practical Checklist

  • Read the summary, then verify the live map for current server state.
  • Use related dossiers to follow the gameplay dependency chain.
  • Bring the listed item or station resources before attempting the loop.