---
title: World Bosses
description: Fractara's realm-scale encounters, beginning with Vaelthar, the Rift-Crowned, and the implementation evidence required before a boss is live.
---

<div className="prose">
  World bosses are named, realm-scale encounters built for many Claimants at
  once. They are not ordinary creatures with larger health bars. Each one owns
  a world event, an unmistakable silhouette, a reason to exist in Fractara's
  lore, and simultaneous objectives that a small group cannot simply outgear.
</div>

<div className="callout callout-rift">
  <div className="callout-title">Design status</div>
  <p>
    Everything on this page is a <strong>proposal</strong>. Vaelthar has a named
    identity, lore direction, encounter outline, and approved concept artwork.
    No world boss runtime, spawn lifecycle, combat phase, reward, or live
    deployment is being claimed yet.
  </p>
</div>

<section className="boss-hero" aria-labelledby="vaelthar-name">
  <div className="boss-hero-copy">
    <p className="boss-kicker">First proposed world boss</p>
    <h2 id="vaelthar-name">Vaelthar, the Rift-Crowned</h2>
    <p className="boss-title">The Dragon Who Survived Seven Worlds</p>
    <p>
      A colossal ancient dragon fused from seven shattered versions of
      himself. Vaelthar is not merely displaced by the Fracture—he is a living
      wound in it.
    </p>
    <dl className="boss-facts">
      <div>
        <dt>World event</dt>
        <dd>The Shattered Sky</dd>
      </div>
      <div>
        <dt>Encounter target</dt>
        <dd>20–30 players</dd>
      </div>
      <div>
        <dt>Creature</dt>
        <dd>Ancient Dragon</dd>
      </div>
      <div>
        <dt>Current state</dt>
        <dd>Design and approved art</dd>
      </div>
    </dl>
  </div>
  <figure className="boss-portrait">
    <img
      src="/world-bosses/vaelthar-rift-crowned.webp?v=worldbreaker-ascendant-v2"
      alt="Vaelthar, a basalt-black ancient dragon with a lightning-crystal crown, opposing frozen and burning wings, oceanic armor, and a living-heartwood tail"
      width="1382"
      height="1382"
      loading="eager"
    />
    <figcaption>Approved concept artwork — not yet a registered runtime sprite.</figcaption>
  </figure>
</section>

## The world-boss contract

<ul className="contract-grid">
  <li>
    <strong>Named and remembered</strong>
    <span>A singular character with motives and history, not a generic species tier.</span>
  </li>
  <li>
    <strong>Announced by the world</strong>
    <span>A realm event gives players enough warning and direction to assemble.</span>
  </li>
  <li>
    <strong>Many players by design</strong>
    <span>Simultaneous fronts create the group requirement instead of inflated health.</span>
  </li>
  <li>
    <strong>Rewarded fairly</strong>
    <span>Damage, tanking, healing, control, and support must all qualify for personal rewards.</span>
  </li>
</ul>

## Lore

<div className="prose boss-lore">
  <p>
    Vaelthar was ancient before the Fracture. When reality broke across his
    mountain, he did not flee. He wrapped his wings around the rupture and
    attempted to claim it.
  </p>
  <p>
    The Fracture divided him across seven collapsing dimensions—and then fused
    every version back together. Vaelthar returned larger, wounded, and
    fundamentally impossible. His scales reflect skies that no longer exist.
    Broken fragments of mountains form the crown above his skull. When he
    spreads his wings, one bears the cold of a dead world and the other the
    furnace of a world still burning.
  </p>
  <p>
    For centuries, Vaelthar slept beneath the scar created by his
    transformation. Now the growing network of Lanterns and Anchors draws
    dimensional energy away from him. He has awakened to destroy them before
    the world becomes too stable to sustain his fractured body.
  </p>
</div>

<blockquote className="boss-quote">
  He is not attacking because he is hungry. Vaelthar believes Fractara belongs
  to him because he survived all the worlds that died to create it.
</blockquote>

## Encounter proposal

<ol className="phase-grid">
  <li>
    <span className="phase-number">I</span>
    <div>
      <h3>Break the Crown</h3>
      <p>
        Three groups attack separate crown fragments while Vaelthar remains
        mostly airborne. All three must break within the same window.
      </p>
    </div>
  </li>
  <li>
    <span className="phase-number">II</span>
    <div>
      <h3>Seven Worlds</h3>
      <p>
        Teams enter burning, frozen, and void-touched breaches to destroy the
        dimensional echoes sustaining him.
      </p>
    </div>
  </li>
  <li>
    <span className="phase-number">III</span>
    <div>
      <h3>The Rift-Crowned</h3>
      <p>
        Vaelthar lands. His head, wings, and tail become separate tactical
        threats whose attacks can be disabled temporarily.
      </p>
    </div>
  </li>
  <li>
    <span className="phase-number">IV</span>
    <div>
      <h3>This World Is Mine</h3>
      <p>
        His seven selves overlap. Echoes repeat his attacks as the battlefield
        collapses into a final coordinated burn.
      </p>
    </div>
  </li>
</ol>

## Implementation ledger

<div className="table-wrap">
  <table className="implementation-ledger">
    <thead>
      <tr>
        <th scope="col">Area</th>
        <th scope="col">Status</th>
        <th scope="col">Evidence or next gate</th>
      </tr>
    </thead>
    <tbody>
      <tr>
        <th scope="row">Identity and lore</th>
        <td><span className="status status-defined">Defined</span></td>
        <td>Named boss, motive, visual identity, and world-event title recorded here.</td>
      </tr>
      <tr>
        <th scope="row">Concept artwork</th>
        <td><span className="status status-review">Approved</span></td>
        <td>The Worldbreaker Ascendant concept is published here; runtime sizing and registration remain separate.</td>
      </tr>
      <tr>
        <th scope="row">Authoritative lifecycle</th>
        <td><span className="status status-missing">Not implemented</span></td>
        <td>Needs durable activation, rally warning, placement, persistence, timeout, victory, and reset rules.</td>
      </tr>
      <tr>
        <th scope="row">Combat encounter</th>
        <td><span className="status status-missing">Not implemented</span></td>
        <td>Needs server-owned phases, simultaneous-objective authority, scaling boundaries, and regression coverage.</td>
      </tr>
      <tr>
        <th scope="row">Client presentation</th>
        <td><span className="status status-missing">Not implemented</span></td>
        <td>Needs world announcement, rally marker, boss HUD, telegraphs, mobile density limits, and reduced-motion behavior.</td>
      </tr>
      <tr>
        <th scope="row">Contribution and rewards</th>
        <td><span className="status status-gated">Design-gated</span></td>
        <td>Personal any-role rewards required. No new drop activates without a verified sink.</td>
      </tr>
      <tr>
        <th scope="row">Release proof</th>
        <td><span className="status status-missing">Not live</span></td>
        <td>Requires committed source, deployed SHA, public readiness, and a real multi-player playtest.</td>
      </tr>
    </tbody>
  </table>
</div>

<div className="callout">
  <div className="callout-title">Current technical boundary</div>
  <p>
    Fractara parties currently cap at <strong>15 players</strong>, while the
    bounded contribution ledger supports up to <strong>32 entries</strong>.
    Vaelthar's proposed 20–30-player target deliberately fits between those
    boundaries: larger than one party, but not larger than the reward authority
    can currently represent.
  </p>
  <p>
    Sources: <code>packages/shared/src/types/party.ts</code> and
    <code>server/internal/world/mobs/behavior/threat.go</code>.
  </p>
</div>

## Proposed rewards

<div className="prose">
  <p>
    The first victory would grant the title <strong>Crownshatterer</strong>.
    Qualified participants would receive personal rewards based on damage,
    tanking, healing, control, or support—not highest-damage priority.
  </p>
  <p>
    A <strong>Rift-Crown Fragment</strong> remains only a proposed material. It
    must have an authoritative crafting, exchange, equipment, consumption, or
    unlock sink before it can become an active drop.
  </p>
</div>