Content policy
What the wiki and the forum accept, and how they are kept that way.
01The wiki
The wiki documents the game and the science it stands on. Every page carries one of five words: ObservedMeasured or catalogued in the real sky, with its source cited. ModelPublished physics or a published model, applied as written. SimWhat the simulation generates or renders; it may depart from reality and says where. SpeculativePlausible but unproven; an extrapolation the science does not yet settle. FictionInvented for the setting. True in-universe, says nothing about the real sky.. Science pages state the science and cite their sources; what the game does is in its own box. Wrong science is fixed, not published.
Lore pages document the setting and are marked as fiction. The community documents canon; it does not write it. Spoilers for the story are kept out of public pages or behind a marked spoiler block.
Edits from new accounts go through pending changes and are reviewed before they become the stable version.
02The forum
- Be civil. No harassment, no slurs, no threats, no doxxing.
- Mark spoilers. Use the spoiler tag for anything past the public canon.
- Cite sources when you make a science claim; corrections are welcome and expected.
- Screenshots from the game carry their metadata; other people's art and other games' assets are not accepted.
- No spam, no advertising, no vote manipulation.
03Scripts and API clients
Edits made through the API or the MCP endpoint follow the same rules as edits made on the site. They act under a token tied to an account, carry that account's name, and go through pending changes until the account is trusted. Tokens can be revoked at any time from account settings.
04Difficult material
The setting includes war, slavery and loss. Pages that carry such material say so at the top. Graphic detail that serves nothing is removed.
05Moderation and reports
Moderators can remove content, lock threads and suspend accounts, and each action is logged with a reason. Every post and page has a report control. Repeated or serious breaches lead to a ban. Takedown requests for copyright or personal data go to the contact address published with the first public build; until then, the terms of use apply.