> For the complete documentation index, see [llms.txt](https://everfall.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://everfall.gitbook.io/docs/the-world-ahead/raids.md). # Raids Some doors should take a whole party to open. Deep beneath ruined halls and beyond the paths of Winterveil, the biggest fights in Everfall await. The ambition: encounters that reward learning the boss, trusting your party and knowing when to strike. ## Built for a party The raid direction combines **boss fights, puzzles and room challenges**. Form a party, work through each room and take on encounters that need more than damage alone. * **Puzzle mechanics:** solve environmental puzzles and coordinate with your party to open the way forward. * **Room challenges:** tackle objectives and obstacles that change how each encounter plays. * **Boss fights:** learn attack patterns and use your abilities together. * **Group competition:** compare your party’s performance with other groups. Scoring and ranking rules are still being designed. These are planned systems. The scenes below show encounter concepts. ## The Ashen Citadel A fortress suspended above an ember-lit abyss. At its heart waits Stitchbound: a forgotten experiment that has outlived everyone who built it. [Explore the wider citadel](/docs/the-world-ahead/ashen-citadel.md) · [Follow the roadmap](/docs/discover-everfall/roadmap.md) ## Meet the threats Three very different nightmares. ![Stitchbound, Hollow and Cindermaw](https://3818559274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfbWB9ze38f652e3SYGCC%2Fuploads%2Fgit-blob-308f388b774b42579c99e1954e4f72eebf2a15f7%2Feverfall-raid-bosses.png?alt=media) ## Stitchbound · The experiment wakes A towering stitched brute in a worn coat. No sword. No shining armour. Just green fists and the machinery keeping him alive. ![A lightning strike redirected into a conductor while the party spreads out](https://3818559274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfbWB9ze38f652e3SYGCC%2Fuploads%2Fgit-blob-1a382afbdd0ac0b04e116ec46d44c8edfe60ed13%2Feverfall-raid-lightning.gif?alt=media) *Illustrated mechanic concept: redirect the strike.* **Draw the lightning.** A conductor marks one player before a bolt lands. Lead it into a charging coil to overload it; leave it near the party and everyone has to scatter. **Break the circuit.** When the coils power his next slam, the party must disable them to expose his seams. That short opening is the moment to commit your strongest attacks. **The final surge.** With his power supply broken, he tears free. Faster swings replace the slow slams, but each missed blow leaves him open. Bait the attack, step clear, punish the recovery. ## Hollow · A crown without a kingdom A hooded skeletal sovereign in black robes, carrying an enormous pale scythe. His court is gone. Its shadows still answer him. ![Hollow and translucent doubles surround the party; the real boss casts a dark shadow](https://3818559274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfbWB9ze38f652e3SYGCC%2Fuploads%2Fgit-blob-956ac025a429e793b4bd92cff62c504c860c6cd2%2Feverfall-raid-shadows.gif?alt=media) *Illustrated mechanic concept: find the solid shadow.* **Watch the real blade.** Spectral doubles repeat his wind-up, but only the real Hollow casts a solid shadow. Find him before the sweeping strike. **Pass the curse.** A marked player can pass a growing curse by touching an ally. Share it before it overwhelms one person, without passing it straight back. **Steal back the light.** During his eclipse, the party must relight the sanctuary braziers while avoiding the scythe. Each flame restores a patch of safe ground and weakens his shield. ## Cindermaw · Hunger beneath the ash An ash-skinned spellcaster consumed by phoenix fire. Dark hair and black robes frame a pair of ember-bright feathered wings. The fire is no longer something she casts; it is part of her. ![Cindermaw lands in a fiery impact as the party scatters to safe ground](https://3818559274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfbWB9ze38f652e3SYGCC%2Fuploads%2Fgit-blob-85ca78fc257443f485c328a7ab0ccf255226e529%2Feverfall-raid-breath.gif?alt=media) *Animated mechanic concept: survive the landing.* **Read the breath.** Her wings flare before she sends fire across a wide lane. Move to her flank; backing away along the lane will not save you. **Choose what burns.** Burning patches remain after each cast. Draw them toward the edges before they cut the arena in half. **Bring her down.** She rises on blazing wings and plunges into the arena, leaving only a moment to clear the landing. Survive the impact, then strike while her wings fold and the embers settle. *Future encounter and visual concepts, with working names. These mechanics are design ideas, not playable features or a confirmed raid specification. Party sizes, rewards and final appearances are still open.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://everfall.gitbook.io/docs/the-world-ahead/raids.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.