> 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/competitive-play.md).

# Future modes & community

More ways to put your squad to the test. The next format is still open.

We are exploring both **cooperative boss challenges** and **competitive squad battles**. Community interest and playtest feedback will help us decide which to prototype and prioritize. Neither is a confirmed release commitment.

## Take on a boss together

Raids or smaller party encounters could bring players together against a shared threat: learn its attacks, coordinate your squad and overcome a fight that rewards teamwork.

The [raid concepts](/docs/the-world-ahead/raids.md) explore this direction. Party size, controls, progression and rewards are still design questions, not announced features.

## Put your squad against another

A squad-versus-squad auto-battler is another possibility: choose your team, prepare its lineup and watch it fight another player's squad under shared rules. Adjust after each match and try a different approach.

![Arena concept with opposing squads and animal companions supporting the cyan team](https://3818559274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfbWB9ze38f652e3SYGCC%2Fuploads%2Fgit-blob-33c16deb152b53e0eed3a47374264a9eccb2da05%2Feverfall-competitive-concept.png?alt=media)

*Illustrative concept, not a playable PvP mode. Team size, companion roles and match format are not final.*

Drafting, shops, rerolls and a tactical board are possibilities rather than selected systems. A full TFT-style format has not been chosen. If we pursue ranked competition, fair rules and the role of collection progression will need dedicated testing.

## Help shape what comes next

Would you rather tackle a boss with friends, test your squad against other players, or try both? Share what interests you and what you enjoy in playtests through [Discord](https://discord.com/invite/RQhc2cXngQ) and [X](https://x.com/playeverfall).

We will weigh that feedback alongside playtest results and development scope, then announce the chosen direction. This is not a promise to ship both modes or a vote with a guaranteed outcome.

## What exists today

The current squad dungeon system is **PvE**: your squad fights monsters with player-triggered skills and short challenges. Its rankings compare PvE runs; they are not head-to-head PvP matches. Multiplayer raids are also a future concept, separate from the current dungeon mode.

We are also developing an **action-combat proof of concept** with a first dungeon where you directly control your character, move, aim and use abilities. This is separate from the squad dungeon system and is currently in development.

[Prepare a squad](/docs/first-light-and-progression/squads-and-gear.md) · [Explore raid concepts](/docs/the-world-ahead/raids.md) · [Roadmap](/docs/discover-everfall/roadmap.md)


---

# 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/competitive-play.md?ask=<question>&goal=<user_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.