Boss Summons

Status: Planned

This page locks in one of the strongest influence points from Necesse:

boss summons should feel like adventure, not admin

The project should keep the pleasure of figuring out how a boss is called, where it belongs, and why the ritual or trigger fits the region.

Design Goals

• Summon access should feel like exploration progress
• The summon method should teach the region's story, ecology, or danger pattern
• The player should not need an external wiki to understand the first kill
• Re-fights should stay atmospheric without becoming busywork
• Boss calling methods should add anticipation, not inventory clutter

Core Rules

• Every major boss should have a clear summon or trigger language
• The summon method should usually belong to the local biome, structure, weather, or threat family
• Major bosses should deliberately declare whether they are biome-locked, cave-locked, landmark-locked, arena-locked, or hybrid
• Discovery should come from drops, chests, landmarks, rumors, contracts, or quest clues
• Re-fights should be easier to prepare than first kills, but still feel thematic
• Multiplayer should not let one player accidentally consume the whole team's progress item without warning

Summon Method Families

Found Ritual Item

The player assembles or restores a local object from biome materials or elite drops, then uses it at the right place.

Best for:

• Grove guardians
• Tomb or shrine bosses
• Region leaders tied to local offerings

Structure Trigger

The boss is called by interacting with a regional landmark, seal, gate, beacon, or ruin mechanism.

Best for:

• Archive bosses
• Fortress defenders
• Temple or breach wardens

Ecological Trigger

The boss appears because the player disturbs a nest, hunting ground, brood patch, feeding site, or territorial chain.

Best for:

• Beast bosses
• Swarm bosses
• Ambush predators

Event Trigger

The boss arrives during a crafted or world-state event such as a Stormfront, breach pulse, raid signal, or sky anomaly.

Best for:

• Invasion leaders
• Late-game weather threats
• Worldshift escalations

Hunt Trigger

The player tracks signs, gathers bait, follows sky or cave routes, and deliberately draws out the target.

Best for:

• Mobile aerial bosses
• Dune or tundra hunters
• Mount-relevant pursuit fights

Geography Locks

Boss location rules should vary by fight fantasy:

• Biome-locked: the boss belongs to a specific surface biome and should not be equally valid everywhere
• Cave-locked: the boss belongs to a specific cave layer, cave biome, or underground route family
• Landmark-locked: the boss belongs to a generated shrine, ruin, nest, arena, or seal site
• Arena-locked: the intended fight space is part of the encounter contract, not an optional decoration
• Hybrid: crafted summon object plus the correct biome, cave, or landmark

This should be treated as a deliberate part of boss identity, not an implementation afterthought.

Readability Rules

• The first summon should be understandable from normal play
• A quest clue can reinforce the answer, but should not be the only answer
• Region props, item names, and tooltips should all point in the same direction
• If a summon requires a special time, weather state, or location, that requirement should be clearly surfaced
• Locator items or boss maps should point to real landmarks or destination spaces whenever the fight uses one

Re-Fight Rules

• First discovery can be slightly ceremonial
• Re-fights should cut out unnecessary friction
• Re-fight materials should usually come from the same biome loop or from boss-adjacent content
• Useful Summon Objects can come from mobs, elites, chests, or boss reward chains as long as the loop stays readable
• A failed attempt should not feel like losing an hour of setup

Arena Rules

• Some bosses should shape the arena when called
• Some bosses should prefer a found natural arena rather than a player-built box
• Summon logic should support mounted, airborne, or vertical play where that fight fantasy benefits from it

Anti-Patterns

Avoid:

• Generic altar spam reused for every boss
• Flat summon items with no regional identity
• One-drop lottery gating for first kills
• Boss access items hidden behind mostly worthless loot pools
• Overly obscure recipe chains that feel like puzzle-box homework
• Re-fight methods that are much more tedious than the actual boss

Mount and Traversal Synergy

Some summon methods should reinforce the project's traversal identity:

• Chase a target through the sky before the real fight begins
• Use a mount to cross hazards fast enough to complete the ritual
• Reach a sealed perch with a grapnel or climb mount
• Trigger an ambush by disturbing a nest network in vertical cave space

Current Direction by Phase Band

These are direction markers, not final implementations.

• Greenwake: grove idol restored from rootshards and placed at a buried standing stone
• Frostweb: brood disturbance trigger built around cocoon clusters and nest pressure
• Black Archive: sealed archive mechanism unlocked by recovered sigils
• Windplain Cairns: cairn offering made from storm-worn relic fragments
• Mireglass: lure-and-ambush setup using marsh bait and idol smoke
• Sunscar Dunes: ruin trigger mixed with a roaming sky-hunt setup
• Blackwake Reach: raid beacon or war flare to call a coastal flagship encounter
• Deep Frontier: altars, urns, drowned gates, and lair disturbances for deeper bosses
• Breach Band: event summons, anomaly lures, and arena activations for late phases

Current Implementation Note

Phase 01 now follows this rule in code:

• the Ashroot Effigy only works at generated Root Groves or Ashroot Shrines
• the summon target snaps to the nearby landmark arena instead of trusting the clicked block