Contact
Corrections, missing facts, image takedowns and access questions all go to one address. This page explains what to send so a correction can be checked and applied quickly, and what will not be actioned.
The address
One inbox, read in order of severity. A factual error on a live page is handled before a suggestion for a new page.
What to send for a correction
A correction is actionable when it contains four things:
- The page — the URL or the page title.
- The sentence — quote it, so there is no ambiguity about which claim is wrong.
- The source — a link to the official page, store listing or developer statement that contradicts it.
- The correct fact — what the sentence should say instead.
Corrections with all four are usually applied the same day. Corrections with one or two are read and often cannot be acted on.
What counts as a good source
| Source | Accepted for |
|---|---|
| Official Astellia 2 site | Everything |
| Google Play / App Store listing | Availability, price model, disclosure |
| Official social channels | Announcements, dates |
| Developer statements to press | Dates and features, labelled as reporting |
| Player screenshots | Only for clearly visible UI facts |
Not accepted: other guide sites, wikis, YouTube commentary, "everyone knows" claims. Those are leads, not sources.
Image and takedown requests
All game imagery on this site is official material published by the developer on its own site or store listings. If you are a rights holder and want an image removed, say which image and which page, and it will be removed without argument.
What will not be actioned
Requests to add a tier list. No damage data is published; a tier list would be invention.
Requests to add story spoilers or endings. The game is a live service and the site covers systems, not plot.
Requests to promote a token, shop, gold seller or account sale. Not published, not answered.
Requests to "improve SEO" or exchange links. No.
Reporting a broken page
If a page 404s, an image fails to load, or a table renders wrong, mention the device and browser. Layout bugs on mobile are the ones most worth reporting, because that is where the site is most often read.
Response times
This is a one-person site. Most corrections are handled within a day or two; questions that need a fact checked against a primary source take longer, because the fact gets checked before the reply.
There is no support for the game itself here. For account, purchase or technical problems, use the developer's own support channel — the Google Play listing carries a developer contact address.
Before you write
Three questions answer most of the mail this site receives, and they are already on the site:
- "Is it out?" — yes, since 5 November 2026. See launch status.
- "Which class?" — see the class picker.
- "Is the token worth it?" — see tokenomics, which explains why the answer is "not yet decidable".
If your question is not one of those three, the mail is welcome — and if it is about the game rather than this site, the developer's support channel will answer it faster than I can.
What happens to your email
A correction email is read, checked against the source you provide, and then either applied or answered with the reason it was not. There is no tracking system and no ticket number — the reply is the receipt.
If the correction is right, the page changes and the check date stays the same, because the date records when the facts were verified, not when the page was edited. If the correction requires a fact the official material does not cover, the page will say the fact is unpublished rather than adopt your version — that is not distrust, it is the same standard applied to everything else here.
Takedown requests are actioned immediately, without a discussion about fair use.
Corrections that have already been made
The most common correction this site receives is about dates — a launch time converted into the wrong timezone, or a store date read from a different region's listing. Those are applied quickly, and the timezone table on the launch page exists because of them.
The second most common is about class wording. The official descriptions are written in a particular order — role first, weakness second — and paraphrasing them badly turns a design statement into marketing. If you think a class sentence overstates a strength, say so with the official line and it will be re-read.
The third is screenshots. Images are chosen for what is visible, not for what is flattering, and an alt text that claims more than the frame shows is a bug worth reporting.
What a good correction looks like
A single sentence, a link, and one line saying what it should say. That is enough. Long explanations are read but rarely change the outcome, because the source does the persuading.
One last thing
If you are writing to ask whether the game is worth your time, the honest answer is that two days is too early to know — the first balance patch will tell you more than any review written this week, including this site.
Checked 6 November 2026.
