> 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/information/faq.md). # Frequently asked questions ## What is Everfall? Everfall is an upcoming browser RPG built around squad adventures, character progression and a shared world, with a full MMORPG as the long-term ambition. First Light is the working name for the opening playable chapter. ## Is it an idle game or an MMORPG? The first public phase is referral-only onboarding. The first playable chapter then starts in The Reading Room and the beach hub. Semi-idle adventures are part of the development direction; cooperative boss challenges and a competitive squad auto-battler are possible future modes. Community interest, playtest feedback and development scope will help determine which direction we prioritize. Neither format is confirmed. A full MMORPG remains the long-term ambition. ## What is the release order? Referral onboarding first, then First Light's tutorial and beach. Deeper adventures and competition follow in stages, then Winterveil, squad expeditions, the connected MMORPG and raids. There are no announced dates. The collection and seasonal events have separate timing; [follow the roadmap](/docs/discover-everfall/roadmap.md). ## Is Winterveil the first map? No. The tutorial lobby and current beach hub are the opening chapter. Winterveil is a later destination, with a winter town and seasonal activities. ## What do referrals earn? Referral ranking rewards are currently shown as **???**. After 10 successful invitations, you can choose a custom referral code. See the [referral phase](/docs/discover-everfall/referral-phase.md) for the ranking table. ## Are all previews playable today? Some systems are playable in local previews. They aren't all connected into a public release yet. Follow the roadmap for the planned release order. ## Is a Ring required? The proposed direction is an accessible base game with optional collection benefits. The final access policy is still undecided. ## Will holders receive gameplay benefits? Planned benefits include cosmetics, extra saved squads, expedition opportunities and faster progression. Selected systems may include leaderboard multipliers. Rings do not directly add damage or health. Holding multiple Rings is intended to offer additional benefits. See [Firstbound Rings](/docs/collections/firstbound-sigils.md) for details. ## Is the mint open? No. Firstbound Rings remains a proposed collection. Its artwork, benefits and sale details are still being developed. ## What is already web3 in the build? EVM wallet sign-in, character creation and account-linked progress are implemented. The current main lobby requires wallet sign-in; some local development previews work separately. Combat and resource balances are processed by the game, rather than making every action a blockchain transaction. ## Could collectible items be traded? Selected collectible items and player exchange are possibilities, not implemented features. Stardust and Star Shards are currently game resources. ## Are the mint benefits final? No. The final package, delivery status, price and supply will be published before sale. --- # 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/information/faq.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.