Game rules

Game Rules — Aleryos

Last modified: 10/08/2026.

Preamble

Aleryos is a real-time multiplayer space strategy game based on long-term progression, empire building, space warfare, ground warfare via Pillars, exploration, trade, alliances, and diplomacy.

These rules are intended to ensure a competitive, clear, and sustainable universe. Conflict, espionage, raiding, rivalry, and military pressure are part of the game. Cheating, exploiting vulnerabilities, automation, harassment, circumventing the rules, and behavior intended to degrade the collective experience are not.

By creating an account and playing Aleryos, each player accepts these rules, the Terms of Use, the moderation rules, and the decisions of the administrative team.

These rules apply to all universes, all players, all alliances, and all communication channels integrated into the game: public channels GLOBAL, ALERYOS, QUESTIONS, and language channels, alliance chat, private messages, groups, public profiles, planet names, ship names, alliance names, banners, descriptions, and any other content displayed in-game.

The published French version constitutes the reference version. Versions published in other languages are applicable translations of these rules.

In the event of ambiguity, discrepancy, or difficulty of interpretation between a translation and the French version, the French version should be consulted, without depriving the consumer of the mandatory protections applicable in their country of habitual residence.

1. Accounts and Access to the Game

1.1. One Account per Player and Universe

Each player may own only one account per universe.

It is forbidden to:

• create multiple accounts in the same universe;
• use a secondary account to produce resources, transfer units, spy, attack, recycle, protect, or benefit their main account;
• play another player's account;
• log into an account in order to alter its progression, fleets, planets, alliance, or resources.

An account must be controlled by a single natural person. Account sharing is forbidden, even temporarily.

1.2. Multiple Accounts and Shared Connections

Two accounts may be considered linked when they regularly use the same IP address, device, network, technical fingerprint, or highly similar behavior.

Players belonging to the same household, shared accommodation, institution, public network, or mobile connection may play in the same universe, but they must comply with strict restrictions.

Between linked accounts, it is forbidden to:

• conduct direct or indirect commercial exchanges;
• send resources, units, ships, or specialized devices;
• attack, spy on, or recycle debris resulting from an arranged battle between linked accounts;
• use a third player to circumvent this prohibition;
• organize a defense, crash, raid, or exchange that benefits one of the linked accounts.

Linked accounts may belong to the same alliance, provided that no prohibited material or military advantage passes between them.

The Aleryos team may request additional checks in case of doubt. Failure to declare the link does not exempt a player when the facts show abusive use.

1.3. VPNs, Proxies, and Anonymization

Using a VPN, proxy, anonymizing browser, technical relay, or any other means intended to conceal the true origin of a connection may result in verification, restricted access, or a temporary block.

These tools are forbidden when used to:

• circumvent a sanction;
• conceal multiple accounts;
• create or manage multiple accounts;
• conceal automated activity;
• disrupt security checks.

The Aleryos team reserves the right to block connections deemed incompatible with the security of the game.

1.4. Joint Account Management, Lending, and Gifting

Joint account management is prohibited.

Account sharing is forbidden in all forms. No player may log into another player's account, even temporarily, even during an absence, even with the account owner's consent, or even within the same alliance.

Account lending is forbidden. A player may not entrust their account to another player to start a construction, recall a fleet, activate a defense, launch an attack, manage an alliance, collect a reward, or perform any other action.

Gifting, selling, exchanging, or taking over an account is forbidden without explicit administrative approval. Any transaction involving real money, material goods, services, an external account, or an out-of-game advantage is strictly forbidden.

The account remains attached to its original owner and to the identification methods used when it was created.

1.5. Account Security

Each player is responsible for the security of their account.

It is forbidden to share one's password, login link, access tokens, or any information that would allow a third party to log in.

The Aleryos team will never ask for a player's password. Any such request must be considered fraudulent and reported immediately.

An account compromised because of a weak password, intentional sharing, or player negligence does not automatically entitle the player to restoration, refund, or compensation.

1.6. Pseudonyms, Identity, and Impersonation

Pseudonyms must remain readable, appropriate, and distinct.

It is forbidden to:

• impersonate another player;
• deliberately imitate the pseudonym of a player, staff member, or alliance;
• use a misleading pseudonym to cause confusion;
• use an insulting, discriminatory, sexual, extremist political, hateful, or unlawful name;
• use characters, symbols, or typographical variants intended solely to circumvent moderation.

This rule also applies to planet names, ship model names, alliance names, tags, ranks, descriptions, and public messages.

1.7. Account Deletion

A player may request deletion of their account according to the procedures provided in the interface or through support.

An inactive game account may also be automatically deleted according to its effective point total: 0 points after 2 days of inactivity, from 1 to 49 points after 7 days, from 50 to 999 points after 14 days, and from 1 000 to 9 999 points after 21 days. Accounts totaling at least 10 000 points are not affected by this automatic procedure.

Any identity that has completed a real-money purchase of Astrium in the universe concerned is permanently excluded from this automatic deletion, even if the purchased Astrium was subsequently spent. This protection does not prevent voluntary closure, a sanction, an anti-fraud measure, or a legal obligation.

Account deletion may be delayed for technical, security, anti-fraud, dispute-processing, or legal-compliance reasons.

Deleting an account does not automatically cancel sanctions, moderation records necessary to address abuse, or obligations under the Terms of Use.

2. Pause Mode, Protection, and Unavailability

2.1. Pause Mode or Vacation Mode

Pause mode allows a player to temporarily suspend their account in the universes where it is active.

Unless otherwise indicated in-game:

• the minimum duration of pause mode is 48 hours;
• after leaving pause mode, it cannot be activated again for 72 hours;
• the account is placed in complete pause for the entire activation period;
• passive production of resources, soldiers, and RT is stopped;
• already-started constructions, technologies, defenses, ships, and queued populations continue according to their normal timers;
• no incoming hostile action may target the account;
• no attack, espionage, transport, deployment, colonization, exploration, or military action may be launched from the account;
• paid bonuses and temporary effects follow the rules displayed in-game;
• account reactivation follows the delays and restrictions displayed by the interface.

It is forbidden to use pause mode through a bug, desynchronization, or technical workaround in order to cancel a game consequence that has already been initiated.

2.2. Banned, Frozen, or Protected Accounts

In certain exceptional operational or maintenance circumstances, the team may apply temporary universe protection. This protection must not be used to cancel a game consequence that has already been initiated: missions already in progress before its activation continue to resolve normally, while new incoming actions against protected accounts may be blocked during the announced window.

An account that is sanctioned, banned, frozen, or placed under administrative protection may not be attacked, spied on, or used as a source of advantage.

It is forbidden to attempt to benefit from an account under sanction, an account affected by a technical anomaly, or an account temporarily protected by the team.

2.3. Protection of New Players

Automatic protections for new players, weak accounts, or accounts outside the points ratio must be respected.

The protection ratio is x3 in PvP and x3 for PvE interactions with the Errants: a player may not attack a target whose points ratio exceeds the limit authorized by the system, in either direction.

This protection covers space attacks, ground attacks via Pillars, and hostile interactions subject to power limitations.

It is forbidden to circumvent a strong/weak protection by:

• transferring resources;
• artificially modifying points;
• organizing a crash;
• using a third-party account;
• artificially changing alliance or breaking a pact;
• using an inactive account.

Any deliberate circumvention of a protection will be considered a serious violation.

The team may activate a temporary boost reserved for new players based on a minimum player creation date in the universe. This boost may increase production and construction, research, and shipyard speeds according to the universe parameters; it does not modify fleet speed.

2.4. Production sanctuary for inactive planets

An inactive planet may benefit from a technical sanctuary covering its recent natural production. During this window, naturally produced resources not yet caught up by the server are not visible to espionage and cannot be looted by an attack.

This protection covers only the natural production of Iron, Crystal, and Aether. It does not suspend construction, research, production queues, fleet returns, incoming transports, rewards, or direct credits, which must be applied normally.

It is forbidden to seek to exploit a synchronization delay, session closure, refresh, or presence anomaly to circumvent the rules governing combat, looting, or espionage.

3. Trade, transfers, and anti-push

3.1. General principle

Trade is permitted when it constitutes a real, balanced, and traceable exchange between two players.

Trade must never be used to artificially supply a player, accelerate a main account through secondary accounts, or circumvent game limitations.

Any unjustified transfer to a more powerful player, any unbalanced exchange, any disguised donation, or any arrangement involving multiple accounts may be considered pushing.

3.2. Required pact

Any transaction between players must be based on an active pact whenever the system requires it.

Transport or deployment missions between players must be carried out only within the framework authorized by diplomatic pacts.

A commercial pact authorizes trade but does not prohibit attacks or espionage.

A total pact authorizes trade and prohibits attacks and espionage between the parties throughout its duration.

3.3. Applicable resources

Tradable resources are those provided for by the system, including:

• Iron;
• Crystal;
• Aether;
• transportable ground units;
• authorized specialized craft;
• ships or deployable forces when permitted by the system.

Astrium, universal fragments, artifacts, chests, Iris, packs purchasable with Astrium, and any inventory item not provided for by the trading system cannot be exchanged between players.

3.4. Recommended trade rates

To assess the fairness of an exchange, the reference values are as follows:

• 1 Iron = 1 base value;
• 1 Crystal = 1,5 Iron;
• 1 Aether = 3 Iron.

The value of a craft, unit, component, or ship is calculated from the total production cost converted into Iron equivalent.

The Trade catalog applies two specific values: 1 Soldier = 7 Iron equivalent and 1 Weave Resonator = 100 000 Iron equivalent.

An exchange is considered balanced if the difference in value between the two parties remains within a maximum margin of 25 %.

Example: if a player receives the equivalent of 1 000 000 Iron, they must provide consideration within the margin authorized by the system. Exchanges deliberately inflated to exploit the 25 % margin are forbidden.

3.5. Balancing period

An exchange must be balanced within a maximum period of 48 hours after the first delivery.

If an exchange remains unbalanced beyond this period, the players concerned must immediately regularize the situation or contact support.

A player cannot justify pushing through a vague promise, an undated future reimbursement, an alliance debt, military compensation, or an unverifiable oral agreement.

3.6. Prohibited pushing

The following are notably forbidden:

• sending resources to a stronger player without fair consideration;
• regularly supplying the same player;
• using an inactive account as a resource farm;
• organizing arranged attacks to transfer resources;
• deliberately crashing a fleet or units to generate a Debris field for another player’s benefit;
• using a third-party account to circumvent multi-account restrictions;
• transferring units or craft to indirectly strengthen a player outside the authorized framework;
• deliberately causing losses to benefit an ally;
• exploiting PvE bots to generate an abnormal advantage.

3.7. Inactive account

An inactive account is an account that no longer genuinely progresses and whose main activity consists of producing or accumulating resources, units, craft, or ships to transfer them to another player or alliance.

Using an inactive account is forbidden.

Players who benefit from an inactive account may be sanctioned in the same way as the owner of the inactive account.

3.8. Triangular trading

Triangular trading is forbidden when it is used to circumvent a trade, multi-account, pact, points-ratio, or sanction rule.

A player may not act as an intermediary to legitimize an exchange that would be forbidden directly between two other accounts.

4. Attacks, espionage, and hostile operations

4.1. General principle

Attacks, espionage, looting, recycling, and ground incursions are at the heart of Aleryos’s competitive gameplay.

A hostile operation remains legitimate when it complies with system limits, game protections, and fair-play rules.

A hostile operation becomes abusive when its primary purpose is to harass, prevent a player from playing for a prolonged period, circumvent a protection, manipulate a resource transfer, or harm the experience outside a strategic context.

4.2. Types of hostile operations

The following are considered hostile operations:

• space attack by fleet;
• ground attack via Pillars;
• space espionage by probe;
• ground espionage by drone;
• opportunistic recycling following an arranged battle;
• diverted hostile deployment;
• any operation intended to cause a loss, capture, looting, or direct military pressure.

4.3. Prohibited targets

It is forbidden to attack or spy on:

• an account in pause or vacation mode;
• an account that is banned, frozen, or administratively protected;
• an account belonging to staff, except in an explicitly open test universe;
• an account technically linked to yours;
• a player protected by a strong/weak limitation;
• a player bound by an active total pact;
• a target protected by an announced general truce;
• a target whose attack manifestly requires exploiting a bug or vulnerability.

4.4. Attack limits under normal conditions

To prevent bashing, the attack limits are as follows:

• the first uncanceled individual PvP attack opens three UTC calendar days, from day J to day J+2;
• maximum 3 uncanceled attacks against the same player per UTC day, fleets and Pillars combined, for a maximum of 9 attacks during this window;
• attack days must not be consecutive, and a day without an attack remains available until it ends;
• a new cycle may begin after two complete calendar days without an attack following the last uncanceled attack;
• the truce is individual and directional: the cycles A → B, B → A and C → B are independent;
• maximum 1 Pillar attack per day against the same planet;
• space and ground attacks are combined within the general limit of 3 daily attacks;
• espionage does not count as an attack, except in cases of manifest abuse or prohibited automation.

A canceled attack does not count toward these limits. Canceling an already recorded attack recalculates the window and may shorten or eliminate the truce. An uncanceled attack remains counted even if the defender suffers no losses or the attacker loses the battle.

During an individual truce, a normally attackable target is marked in purple with a shield. A target that is too strong remains red, a target that is too weak remains green, and other special statuses retain their display.

Deliberately exceeding these limits, or circumventing them through an alliance, a third-party account, multiple accounts, alternating planets, or an arranged attack, may result in a sanction.

4.5. Attacks via Pillars

Pillars form a second strategic front. Their offensive use is permitted, but it is subject to the same fair-play rules as space attacks.

The following are forbidden:

• launching repeated ground incursions without a genuine strategic objective;
• targeting a planet solely to artificially capture wounded units or transporters in an arranged setup;
• using Pillars to circumvent a pact, multi-account, or protection rule;
• exploiting Pillar activation or deactivation through a bug or desynchronization.

4.6. Espionage

Espionage is permitted, except against targets protected by these rules or by the system.

Because ground espionage is more intrusive and, by design, always detectable, it must remain within a strategic context.

It is forbidden to automate espionage, mass-scan a universe by script, collect coordinates using an automated external tool, or circumvent game limits.

4.7. Recycling and Debris fields

Recycling is permitted when it results from a real battle or a normal gameplay opportunity.

It is forbidden to deliberately organize a crash, fleet loss, defense loss, or arranged attack for the purpose of creating a Debris field for the benefit of a specific player.

Debris fields generated by PvE, bots, or abnormal circumstances must not be exploited to circumvent anti-pushing rules.

4.8. Pact Termination

After a pact is terminated, the former partners must observe a minimum truce of 6 hours before any attack or espionage.

During this truce, the former partners may not recreate the pact or send each other a new pact request.

After a commercial pact is terminated, the former partners must also ensure that no open or unbalanced exchange is still underway.

Terminating a pact solely to trap a commercial partner or launch an attack prepared during the diplomatic relationship may be sanctioned.

4.9. General Truce

The Aleryos team may declare a general truce in a universe, including:

• during exceptional maintenance;
• following a critical bug;
• during a specific event;
• during a beta stabilization period;
• in the event of a major imbalance affecting combat or movement.

During a general truce, no attacks are allowed. Espionage may be allowed or prohibited depending on the truce announcement.

If an attack was launched before the truce but is due to arrive during it, the attacker must recall it if the system allows this. Deliberately failing to recall a disputed attack may result in a sanction.

5. Alliance Wars

5.1. Regulatory Effect

An alliance war has a specific effect under these rules only when it is officially declared, regulated, or recognized in an announcement by the Aleryos team.

In the absence of an official announcement, no alliance war allows the normal attack limits to be exceeded, protections to be bypassed, a truce to be lifted or specific moderation treatment to be obtained.

An alliance may symbolically declare war on another alliance for diplomatic or roleplay reasons, but this declaration has no specific regulatory effect unless it is officially recognized.

5.2. Rules Applicable Outside an Official War

Outside an officially recognized war:

• standard attack limits remain applicable;
• anti-push rules remain applicable;
• strong/weak protections remain applicable;
• pacts and truces remain applicable;
• harassment remains sanctionable;
• no alliance may invoke an unofficial war to justify abuse.

The Aleryos team reserves the right to declare, regulate or suspend alliance wars through an official announcement.

6. Alliances

6.1. Creation and Responsibility

Any player may create an alliance if they comply with the conditions set by the game.

The founder or leader of an alliance is responsible for:

• the alliance name;
• the tag;
• the description;
• the banner;
• the logo;
• the ranks;
• group messages;
• the permissions granted to members.

Granting a member editing or management rights entails assuming responsibility for the consequences.

6.2. Alliance Content

Alliance content must remain appropriate, readable and compliant with the rules.

The following are prohibited:

• insults;
• hate speech;
• discrimination;
• pornography;
• shocking images;
• real threats;
• doxxing;
• impersonating staff;
• fraudulent links;
• unauthorized advertising;
• content intended to harass a player or an alliance.

The Aleryos team may modify, hide or remove any alliance content that violates the rules.

6.3. Internal Alliance Rules

An alliance may define its own internal rules.

These internal rules may never contradict the Aleryos rules. They may not authorize pushing, arranged attacks, harassment, insults, threats, the use of scripts or any other prohibited practice.

6.4. Permissions and Rank Abuse

Alliance permissions must be used solely in the normal interest of the alliance.

It is prohibited to:

• use a rank outside normal gameplay to steal from, destroy, sabotage or deliberately hijack the alliance;
• exploit a permission bug;
• modify an alliance to circumvent a sanction;
• use applications or alliance messages to spam, trap or harass.

Internal alliance disputes generally fall under player management. The Aleryos team intervenes only in cases of rule violations, bugs, impersonation, threats, harassment or fraud.

6.5. Alliance Technologies and Donations

Donations to alliance technologies must be made through the features provided by the game.

It is prohibited to manipulate donations, tokens, permissions or contributions through a bug, script, secondary account or arrangement intended to generate an abnormal advantage.

7. Diplomacy and Pacts

7.1. Commercial Pact

A commercial pact allows exchanges between two players or two alliances when the system permits it.

It does not prohibit attacks, espionage or military rivalries, except where the parties have an informal agreement. An informal agreement not enforced by the system does not have the force of a moderation rule.

7.2. Total Pact

A total pact represents a strong diplomatic relationship.

During a total pact, attacks and espionage between the parties are prohibited.

Trade remains allowed if the exchanges comply with the anti-push rules.

7.3. Negotiation and Termination

All diplomatic negotiations must remain respectful.

A pact may be terminated freely, but it must not be used to trap a player during an open exchange or circumvent a protection.

After a pact is terminated, a truce of 6 hours applies before any attack or espionage, as well as before any new pact request or recreation of a pact between the same players.

7.4. Deceptive Diplomacy

Betrayal, deception and diplomatic manipulation are part of the game as long as they remain within the scope of gameplay.

They become sanctionable when they involve:

• real threats;
• harassment;
• out-of-game blackmail;
• demands for real money;
• impersonation;
• fake accounts;
• circumventing the rules;
• exploiting a bug or technical vulnerability.

8. Exploration, PvE and AI Bots

8.1. Exploration

Space exploration and ground exploration are risky mechanics.

Losses resulting from a normal exploration outcome are not eligible for reimbursement.

It is prohibited to:

• exploit a vulnerability in the draw system;
• retrigger or duplicate a reward through technical manipulation;
• circumvent exploration quotas;
• artificially modify a mission's weighting through a bug;
• use a script to automate explorations.

8.2. PvE and AI Bots

AI bots, Breaches, PvE events and non-player entities are part of the universe.

AI bots may be attacked or spied on when the system permits it. They are not destinations for trade, transport, stationing or player support.

A player becomes a potential target for outgoing AI/PvE attacks only if they have launched an attack against an AI/PvE entity during the current UTC day. Spying on an AI/PvE entity is not sufficient to enable this targeting.

A player may not be subjected to more than 2 AI/PvE attacks per UTC day, counting space attacks and ground attacks via Pillars together. Canceled attacks do not count toward this limit.

It is prohibited to:

• exploit abnormal bot behavior;
• deliberately generate Debris fields through abusive use of bots;
• circumvent PvE quotas;
• cause desynchronization to duplicate loot, losses or rewards;
• use PvE to indirectly push a player.

8.3. PvE Rewards

PvE rewards, chests, artifacts, Astrium, fragments, Iris or resources obtained normally are retained by the player.

Rewards obtained through a bug, abuse, duplication or manifestly abnormal behavior may be removed without compensation.

9. Ships, Models, Components and Units

9.1. Ship Design

Ship design is unrestricted as long as it complies with the limits provided by the game.

It is prohibited to:

• save an invalid model through client-side manipulation;
• circumvent technology or building prerequisites;
• exceed the authorized volumes;
• exploit a calculation error involving cost, speed, shields, cargo capacity or crew;
• deliberately create models intended to crash the interface or server.

9.2. Production Queues

Construction, research, shipyard, unit, component, defense and recycling queues must be used only through the game's normal interface.

Any manipulation that allows queue limits to be exceeded, times to be artificially reduced, actions to be canceled at no cost or production to be duplicated is prohibited.

9.3. Recycling

Voluntarily recycling one's own ships or craft is allowed when the system permits it.

It is prohibited to use recycling to generate more resources than the authorized cost, circumvent a refund, duplicate resources or indirectly fund another account.

10. Communication and Conduct

10.1. General Respect

Aleryos is a competitive game. Light provocation, rivalries, roleplay threats and diplomatic tensions are tolerated as long as they remain within the scope of the game.

The following are prohibited:

• severe insults;
• harassment;
• racist, sexist, homophobic, transphobic or discriminatory remarks;
• pornographic content;
• shocking violent content;
• real threats;
• incitement to suicide or self-harm;
• disclosure of personal information;
• defamation;
• blackmail;
• out-of-game intimidation;
• repeated personal attacks.

10.2. Roleplay Threats and Real Threats

Threats made within a clearly roleplay or strategic context are allowed.

Authorized examples:

• “Our fleet will raze your outpost.”
• “Your alliance will pay for this betrayal.”
• “We are launching a military campaign against you.”

All threats targeting a player in real life, their family, home, employment, personal data, physical safety or life outside the game are prohibited.

The moderation team determines the boundary between roleplay and a real threat.

10.3. Public GLOBAL, ALERYOS, QUESTIONS and language channels

The public GLOBAL, QUESTIONS and language channels are community and strategic spaces. ALERYOS is an announcement channel visible to everyone, and only the Aleryos team may post there. A player's access to these channels may be moderated, restricted or revoked without blocking access to the rest of the game.

Publishing military information is allowed in public channels. Players may share coordinates, espionage reports, fleet compositions, alerts, targets, calls for mobilization or strategic information, provided that this remains within the framework of the game.

This freedom does not permit harassment outside the game, real threats, insults, doxxing, spam or campaigns deliberately aimed at degrading a player's experience outside a normal strategic objective.

The following are prohibited in public channels:

• spam;
• flooding;
• insults;
• repeated provocation without game-related content;
• advertising another game, service or server without authorization;
• aggressive political or religious debate;
• dangerous or fraudulent links;
• calls for harassment outside the game;
• disclosure of personal information.

10.4. Private messages, groups and alliance

Private messages, groups and alliance chats remain subject to the rules.

An insulting, threatening, discriminatory, fraudulent or harassing private message may result in a sanction.

Repeatedly sending links, advertisements, solicitations or identical content to multiple players via private messages, groups or alliance channels is prohibited. This may result in a temporary block on conversations and a moderation sanction.

Moderation may access the in-game communications necessary to process a report, fraud, dispute or violation, in accordance with the Terms of Use and the privacy policy.

10.5. Abusive reports

Reports must be made in good faith.

The following are prohibited:

• filing false complaints;
• manipulating a conversation to get a player sanctioned;
• deliberately provoking an insult and then reporting it;
• submitting multiple tickets without any new information;
• misusing moderation to settle a normal strategic conflict.

11. Bugs, errors and exploitation of vulnerabilities

11.1. Reporting obligation

Any bug, error, calculation inconsistency, security vulnerability, duplication, combat anomaly, resource anomaly or suspicious technical behavior must be reported promptly to support or reported through Aleryos's official Discord.

The report should include, wherever possible:

• username;
• universe;
• date and time;
• planet or relevant coordinates;
• relevant mission;
• screenshot;
• error message;
• reproduction steps;
• observed outcome.

Promptly reporting a vulnerability will always be viewed more favorably than exploiting it, keeping it secret or sharing it with other players.

11.2. Prohibited exploitation

Using a bug to one's advantage is strictly prohibited.

The following are prohibited in particular:

• resource duplication;
• duplication of ships, units, components or rewards;
• abusive mission cancellation;
• bypassing construction or research times;
• combat manipulation;
• manipulation of Debris fields;
• synchronization abuse;
• manipulation of the client, WebSocket, network requests or local storage;
• using a known bug without reporting it.

Deliberate non-disclosure of an exploitable bug may be sanctioned even if the player claims not to have benefited from it directly.

11.3. Compensation and rollback

Losses caused by a bug do not automatically entitle a player to compensation.

The Aleryos team may, depending on the severity:

• correct the issue without compensation;
• partially restore a state;
• remove abnormal gains;
• compensate certain players;
• perform a global rollback of the universe;
• cancel a battle, mission or transaction;
• temporarily suspend a feature.

A global rollback may result in the loss of legitimate actions performed during the period concerned. This loss does not automatically entitle a player to compensation.

11.4. Beta and instability

During a beta phase, the universe may undergo fixes, balancing, partial resets, interruptions, slowdowns or rule changes.

Participating in a beta means accepting a higher level of risk than in a stable version.

12. Automation, scripts and external tools

12.1. Prohibited bots and scripts

It is prohibited to use a bot, script, macro, add-on, extension, external tool or automated program that plays, produces, scans, spies, attacks, transports, recycles, explores or collects information on behalf of the player.

The player must play through the official game interface.

12.2. Prohibited actions

The following are prohibited:

• click automation;
• automatic scanning of galaxies, systems or planets;
• automated fleet monitoring;
• automated alerts obtained by unauthorized reading of network traffic;
• sending direct requests to the server;
• WebSocket manipulation;
• client modification;
• code injection;
• exploitation of local storage;
• mass scraping;
• sharing or selling a cheating tool;
• use of AI or an automated agent to control the account in real time.

12.3. Permitted tools

The following are permitted:

• personal spreadsheets;
• strategic notes;
• manual calculators;
• screenshots;
• alliance documents;
• planning tools not connected to the account;
• Discord or forum discussions without automation.

A tool becomes prohibited as soon as it interacts automatically with the game, reads game data on a massive scale or provides an advantage impossible to obtain through normal use.

13. Shop, Astrium and paid content

13.1. Astrium

Astrium is a rare resource shared across the account.

Unless an explicitly provided feature permits it, Astrium cannot be transferred between players.

It is prohibited to sell, buy, exchange or promise Astrium in exchange for real money, goods, services or advantages outside the game.

13.2. Packs, items and benefits purchasable with Astrium

Packs, items, benefits and content purchasable with Astrium grant only the effects described in the game before confirmation.

Astrium purchases are not random. No Astrium purchase may rely on a draw, hidden probability, paid chest or paid loot box.

13.2bis. Echoes

Echoes are a global resource belonging to the player. In V1, they may notably be obtained through a validated vote on external game-promotion platforms.

Unless an explicitly provided feature permits it, Echoes cannot be transferred between players and cannot be sold, bought, exchanged or promised in exchange for real money, goods, services or advantages outside the game.

Packs, items, benefits and content purchasable with Astrium, as well as Echoes, do not grant any right to:

• circumvent the rules;
• obtain a moderation favor;
• cancel a sanction;
• automatically recover normal losses;
• harass other players;
• exploit a vulnerability.

A player who has made a purchase is subject to the same rules as a player who has made no purchase.

13.3. Artifacts

Artifacts are permanent account bonuses upgraded with universal fragments.

They apply only the effects described in the game. Some artifacts may modify displayed gameplay limits, including the maximum colony limit.

13.4. Payments and disputes

Payment-related issues must be reported to support with the necessary supporting documents.

Any payment fraud, abusive chargeback, exploitation of the refund system or use of stolen payment methods may result in immediate account suspension.

14. Data, privacy and moderation

14.1. Technical data

To ensure security, combat cheating, and maintain game stability, Aleryos may use technical data such as:

• IP addresses;
• session identifiers;
• connection logs;
• mission histories;
• trade histories;
• reports;
• messages necessary to process a violation;
• server events;
• security traces.

This data is used in accordance with the Terms of Use and the privacy policy.

14.2. Communications privacy

In-game communications must not be considered absolutely private spaces.

In the event of a report, fraud, threat, harassment, suspected cheating or dispute, the Aleryos team may access the information necessary for moderation.

Conversations outside the game are taken into account only if they are voluntarily provided as evidence and directly concern security or compliance with the rules.

15. Staff, support and complaints

15.1. Staff role

The staff handles:

• moderation;
• support;
• bug investigation;
• combating cheating;
• dispute resolution;
• enforcement of sanctions;
• communication of truces, maintenance periods and specific rules.

Staff decisions must aim to ensure game stability, fairness across the universe and community protection.

15.2. Staff accounts

Staff accounts, test accounts, technical accounts or administrative accounts must not be attacked, spied on, harassed or used as game targets, except during an officially announced event.

A staff member playing with a normal player account remains subject to the rules like any other player.

15.3. Filing a complaint

A complaint must be clear, factual and supported by verifiable evidence.

It should include, wherever possible:

• complainant’s username;
• reported player’s username;
• universe;
• date and time;
• description of the facts;
• screenshots or reports;
• relevant coordinates;
• relevant messages;
• how the complaint relates to a specific rule.

Incomplete, abusive or clearly weaponized complaints may be closed without further action.

15.4. Challenging a sanction

A sanctioned player may challenge a decision through the channel provided by support.

The challenge must remain respectful, reasoned and supported by new evidence or a precise explanation.

Insulting staff, making threats, spamming or attempting to publicly mobilize the community against a decision does not strengthen the challenge and may worsen the sanction.

16. Sanctions

16.1. Sanction scale

Depending on the severity, repetition and impact of the facts, the Aleryos team may apply:

• reminder of the rules;
• warning;
• temporary or permanent mute;
• deletion of a message or content;
• forced renaming;
• removal of resources;
• removal of ships, units, components or objects;
• mission cancellation;
• combat cancellation;
• closure or correction of a trade;
• temporary suspension;
• permanent ban;
• blocking of a linked account;
• technical access block;
• beta exclusion;
• dissolution of the alliance in cases of serious abuse.

Chat mute blocks writing in public channels, language channels, direct messages and groups, as well as sending private messages in the messaging system. Alliance chat remains accessible to alliance members; sending limits and anti-spam controls continue to apply.

16.2. Aggravated sanctions

A sanction may be aggravated in the event of:

• repeat offense;
• concealment;
• lying to support;
• use of multiple accounts;
• deliberate exploitation of a bug;
• distribution of a cheating tool;
• real threat;
• harassment;
• significant harm to the universe;
• attempt to circumvent a sanction.

16.3. Illegitimate gains

Any advantage obtained in breach of the rules may be removed, even if the player is not banned.

Removal may concern:

• resources;
• ships;
• units;
• components;
• defenses;
• abnormally obtained Astrium;
• inventory items;
• points;
• mission rewards;
• technologies or constructions obtained through abuse.

16.4. Collective responsibility

An alliance may be sanctioned if several of its members participate in an organized violation or if its leaders encourage, cover up or exploit a prohibited practice.

Collective sanctions may include:

• removal of gains;
• content deletion;
• temporary suspension of diplomacy;
• administrative dissolution;
• individual sanctions against those responsible.

16.5. Automated sanctions

The Aleryos team may apply sanctions manually or automatically.

Some checks may be automated: detection of multiple accounts, exceeding attack limits, unbalanced trading, use of scripts, spam, bug exploitation, abnormal behavior or any other measurable violation.

The Aleryos team reserves the right to automate all or part of the checks and sanctions necessary to protect the game, without limiting its authority to intervene manually on a case-by-case basis.

17. Amendments to the rules

The rules may be amended at any time to account for:

• changes to the game;
• a technical fix;
• balancing;
• a new feature;
• an unforeseen abuse;
• a beta phase;
• a security requirement.

Important changes are announced in-game, on Discord, on the website or through any other official channel.

New rules apply from their publication, except in cases of cheating, exploitation of a bug, fraud or manifest abuse, for which the team may intervene retroactively to remove an illegitimate advantage.

18. Operational summary

Key points:

• one account per player and per universe;
• no account sharing, co-management or account lending;
• no bot, script, macro or automated scan;
• manual tools are allowed: spreadsheets, notes, calculators, Discord, alliance documents;
• trading must be balanced, traceable and within a margin of +/- 25 %;
• a trade must be balanced within 48 hours;
• a pact is required for transfers between players when the system requires it;
• no push, inactive account, arranged crash or triangular trade;
• protection ratio x3 in PvP and x3 for PvE interactions with the Errants;
• individual directional PvP cycle of 3 UTC days, with a maximum of 3 attacks per day against the same target, for up to 9 attacks, followed by up to 2 days of truce depending on the last day attacked;
• maximum 2 AI/PvE attacks suffered per player per UTC day, fleets and Pillars combined;
• maximum 1 Pillar attack per day on the same planet;
• 6-hour truce after a pact is broken;
• an alliance war has a specific regulatory effect only if it is officially recognized;
• vacation mode lasts at least 48 hours, blocks incoming actions and requires a 72-hour cooldown before it can be activated again after exit;
• military information may be shared in public channels open to discussion as long as it remains within the framework of the game;
• bugs and vulnerabilities must be reported to support or on the official Discord, never exploited;
• no purchase, pack or paid advantage provides moderation protection;
• staff may remove any abnormal gain and sanction on a case-by-case basis;
• sanctions or checks may be automated;
• during beta, everything may change: rules, balancing, features, compensation and sanctions.