Eternal Battle Legends Editorial Game Library Browse Library

Frequently asked questions · Navigation notes · Support context · Updated March 2026

FAQ

Questions usually appear in clusters, not one by one.

This page answers the practical questions that tend to come up after a first browse: what the site is, how the library is arranged, why title pages and launch pages are separated, where support context lives, and how policy information is surfaced without getting in the way of reading.

It is meant to feel like a working reference page, not a filler block. Some answers are short on purpose. Others carry a little more context because a useful answer often needs one extra sentence.

Site structure

The first questions are usually about what kind of project this actually is.

That is a fair place to start. The homepage uses a slower editorial rhythm, while the library moves faster. The two are related, but they are not trying to do the same job.

Platform framing

What is Storyforge Quest meant to be?

Eternal Battle Legends is presented as an editorial game library: a browse-first site with a homepage, library layer, category guides, title pages, support pages, and legal references. It is structured around reading, orientation, and routes through the catalog rather than around a hard sell or one-step conversion page.

Reading logic

Why does the homepage feel slower than the library?

The homepage sets tone, context, and useful entry points. The library page is denser because it is built for scanning. Keeping those functions separate helps the site feel less generic and easier to read on a second visit.

Editorial note

Why not put every answer directly on the homepage?

Because pages work better when they each keep a clear job. The FAQ page closes recurring questions, the updates page handles visible maintenance, and the guide pages explain how the library is meant to be used without overloading the front page.

House note

Useful FAQs reduce friction because they answer navigation questions before they turn into support messages.

That is why this page stays close to site structure, content scope, and route logic. It is not here to decorate the footer. It is here to close the small but repeated gaps that appear when a project starts to grow beyond a simple landing page.

Library routes

The library is built to be scanned in layers.

Users can move from broad shelves to category hubs, then to title pages, and then to launch pages where relevant. That sequence keeps the route readable and makes each stop more specific than the one before it.

Why are titles grouped into collections?

Collections help users browse by tone, pacing, and visual mood. That is often a better starting point than title names alone, especially when the library is growing.

Why do some shelves feel calmer and others more dramatic?

Different shelves are allowed to carry different energy. A library feels more believable when not every category is speaking in the same volume.

Can I browse from categories instead of from the homepage?

Yes. The category index exists for that exact reason. It acts as a second entry point for users who would rather start from a browsing map than from the editorial front page.

Why are some routes shorter than others?

Some pages are meant to orient quickly, while others give more reading depth. The site intentionally mixes shorter and longer routes so the whole experience does not feel mechanically repeated.

Title pages and launch pages

These are separated on purpose.

A title page gives context, summary, and adjacent routes. A launch page is narrower. Keeping them apart makes the catalog more legible and prevents every page from trying to do everything at once.

Title guide

What belongs on a title page?

Title pages carry description, tone notes, related routes, and a cleaner reading layer. They help users decide whether a title fits the mood they are already browsing.

Launch route

What belongs on a play page?

Play pages work as focused host pages. They hold the frame area, a short practical note, and a couple of same-shelf exits so a user does not hit a dead end after one page.

Practical point

Why not embed everything directly into the library?

Because the library is stronger when it stays readable. Heavy pages belong behind a cleaner intermediate layer so the overall route remains fast, flexible, and easier to maintain.

Contact and policy context

Support pages are part of trust, not just a footer requirement.

Contact, privacy, terms, cookie, disclaimer, and updates pages all help the site read as a maintained project instead of a single-purpose shell. They should be easy to find and calm to read. That is why policy language is surfaced clearly, but without turning every screen into a wall of compliance text.

Where should I go if a page needs clarification?

The contact page is the direct route. The updates page is useful when the question is really about what changed recently.

Does the site explain how content is organized?

Yes. The homepage, category hubs, how-it-works page, and this FAQ each cover a different part of that explanation.

Still need help?

The cleanest next step is still a direct message.

If the answer is not covered here, use the contact page. If you want to continue browsing first, the library and category index are the best routes back into the catalog.