Access and accounts. Retro Space is for people aged 18 or over. Each person may have one main account and at most one own participation per universe. Different real people in the same household may play; sharing an IP address alone is not a violation. Selling, giving away or permanently transferring accounts is prohibited.
Sitting. A prior request takes effect only after explicit operator approval for a named delegate using their own main account, one participation and at most seven days. Building, research, production and securing the owner's fleets to their own destinations are allowed. Attacks, foreign deliveries, purchases, account changes and destructive actions are forbidden. Every action checks the grant; expiry and revocation affect open tabs. Owner and operator can end it. No password sharing or automatic renewal. Inactivity alone deletes no account.
Attack limits. Each attacker may execute at most five fleet attacks, including moon destruction, against each target body in each universe within a rolling 24-hour window. A separate allowance covers five executed missile salvos. Planets and moons are counted separately; there is no midnight reset.
Counting. Pure espionage and fleets recalled or failed before execution do not count. In an ACS event, each actual participating attacker counts once. An executed missile salvo counts once even if every missile is intercepted. Alliance wars do not lift these limits. Further loot waves after destroying a large fleet require an explicit individual exception; they are not automatically allowed.
Earlier and other trades retain their applicable rules. Trade and moon attempts. Fair exchanges and agreed moon attempts remain allowed; deliberate feeding and intentionally inadequate returns are forbidden. The starting model values actual deliveries as W = 2 × metal + 3 × crystal + 6 × deuterium. Returns within an inclusive 72 hours count; only afterward does a missing return or ratio below 75% trigger a review hint. Exactly 75% passes. Receipts are not counted twice. Uncertain assignment, historical scores and assistance, alliance supply or moon-attempt context remain explicit. Versioned operator parameters and hints impose no automatic sanctions; the operator decides the case. Once this rule starts in a universe, a stronger player who receives deuterium from a lower-scoring player owes that sender at least the same value in metal and crystal within 24 hours of actual credit. For 1,000 deuterium, 3,000 metal, 2,000 crystal or 1,500 metal plus 1,000 crystal suffice. An arrival at or before the deadline counts once credited. Uncertain evidence stays under review. There is no automatic ban.
Tools and bugs. Manual spreadsheets, calculators and display-only aids are allowed. Player scripts that automatically build, fly, farm, save fleets or vote are prohibited. Report bugs. Deliberate advantageous exploitation and concealment may lead to a ban; reporting does not permit continued exploitation.
Communication. Harassment, outside advertising and unauthorized external links are prohibited in user content, including private messages. Own game/report links, official help/legal pages and the exact official Discord invitation remain allowed. Other destinations require explicit operator approval. Blocked new content is not delivered; the link filter creates a communication restriction and review case, not an automatic full ban.
Measures and appeals. Ordinary violations first receive warnings or graduated measures; serious cases may be banned immediately. The operator explains scope, duration and protection treatment. Bashing is generally universe-specific; serious bug abuse or advertising may affect the main account. Serious bans may have no vacation protection, while other attack rules remain valid. No fixed penalty schedule is created here.
Notices, support and appeals remain accessible. Signed-in players see only active sanctions explicitly approved for publication, with necessary player name, scope, factual reason, start and end. Private notes and data remain hidden; expiry or revocation removes the entry immediately. Bans do not automatically seize DM or officer time. Protection requires an explicit choice per sanction; existing vacation and other valid protection causes retain their established precedence.
Evidence boundary. Technical attack recording began on 26 October 2026 at 22:25:17 CET. It does not establish a complete earlier history. Missing data does not become a retroactive violation. DM belongs to the main account; officer bookings definitively apply only in the explicitly selected universe. The wiki explains implemented rules.