ASTRA Rules
Find a specific situation in seconds. Search covers the title, full wording and category of every rule.
MARALYS / Rulebook navigation
A rule should be found before it is broken.
This server does not copy the rulebook of another MARALYS direction. The game, situations, categories and wording can change while the interface remains consistent.
Search for a mechanic, action, item or any part of the wording.
Categories
Showing 25 of 25 rules
Rule01
General
0. General provisions
0.1. These rules apply to MARALYS game servers, the website, Telegram and all other official MARALYS resources. 0.2. Not knowing the rules does not release a player from responsibility. 0.3. Players are responsible for all actions performed through their accounts. If you suspect that your account has been compromised, contact support immediately. 0.4. The administration may consider the severity and intent of a violation, the damage caused and the player’s history. A penalty may not be issued without citing the rule that was violated. 0.5. Server-specific rules supplement the general rules. If provisions conflict, the specific rule of that server takes precedence. 0.6. Changes take effect after they are published with an effective date.
Rule02
General
1. Accounts
1.1. Each player may use one primary account. Additional accounts are allowed only with prior approval from the administration. 1.2. Selling or transferring accounts, or impersonating another player or a project staff member, is prohibited. 1.3. Usernames may not contain insults, advertising or prohibited symbols, and may not imitate a staff member’s username. 1.4. Evading a penalty through another account, a VPN or a username change is prohibited.
Rule03
World & gameplay
2. Territory, claims and property
2.1. Actions involving blocks, containers, mechanisms and items are recorded in server logs. 2.2. A claim protects an area, but the absence of a claim does not make a build or property abandoned. 2.3. Theft, griefing, damage to another player’s builds and bypassing claim protection through bugs, fluids, pistons, explosions, physical contraptions or other mechanics are prohibited. 2.4. In ownership disputes, the administration considers logs, the date construction began and other evidence. 2.5. Claiming land for future use, blocking roads or claim exits, and obstructing the expansion of an existing base are prohibited. 2.6. An area belonging to a player who has been absent for more than 30 days may be cleared, restored or transferred after review. To preserve a base during a long absence, open a support ticket in advance. 2.7. Copying a build marked “АП есть” (author permission required) is prohibited. A build marked “АП нет” may be copied if the author is credited.
Rule04
World & gameplay
3. Building and infrastructure
3.1. Unfinished boxes, pillars, debris structures and other objects that spoil the area are prohibited near spawn, roads and public zones. 3.2. Temporary structures must be labelled and removed after the work is complete. 3.3. Damaging or blocking public roads, bridges, tunnels, stations and portals is prohibited. 3.4. The administration may require an unsafe or obstructive build to be corrected. If the requirement is not met within the stated time, the structure may be removed.
Rule05
World & gameplay
4. Farms, mechanisms and performance
4.1. Lag machines, mechanisms intended to reduce TPS, crash attempts and excessive concentrations of entities or items are prohibited. 4.2. Mob farms must be placed at least 128 blocks away from other players’ bases, spawn and permanently loaded public zones to preserve server performance. 4.3. Only chunk-loading methods explicitly supported by the project are allowed. 4.4. Farms that repeatedly place, move and dismantle a physical element to destroy blocks at scale are prohibited if they create excessive load or physics errors. 4.5. Silverfish farms are prohibited because of their high load on the server and players’ devices. 4.6. If stability is at risk, the administration may immediately stop a mechanism, remove a concentration of entities or unload a chunk. The action must be recorded. 4.7. Owners are responsible for the safety and optimisation of their mechanisms, including mechanisms built together with other players.
Rule06
World & gameplay
5. PvP
5.1. PvP conditions are defined by the rules of each server. 5.2. Cheats, bugs, dupes, lag and bypasses of server restrictions may not be used to gain an advantage in combat. 5.3. Traps near spawn, teleport locations and exits from safe zones are prohibited.
Rule07
World & gameplay
6. Economy
6.1. Players are advised to record trade terms with a screenshot or video. 6.2. Deception during a trade, substituting an item and refusing to fulfil confirmed trade terms are prohibited. 6.3. Selling in-game items, currency or services for real money without permission from the project is prohibited. 6.4. Donation fraud and deliberate destabilisation of the economy are prohibited.
Rule08
Community & safety
7. Communication
7.1. Harassment, discrimination, threats, publishing personal data and inciting hatred are prohibited. 7.2. Insults, provocation, flooding, spam, excessive caps and spreading false rules or messages on behalf of the administration are prohibited. 7.3. Advertising third-party projects and sharing malicious or phishing links are prohibited. 7.4. Political and religious discussions are allowed only while they do not create conflict or disrupt other participants. 7.5. NSFW material and shock content are prohibited across all project resources. 7.6. Deliberate shouting, harsh sounds and playing music without the consent of those present are prohibited in voice chat.
Rule09
Community & safety
8. Security
8.1. Cheats, X-Ray, dupes, malicious macros and exploitation of errors are prohibited. 8.2. Any discovered vulnerability must be reported to the administration through a ticket. Publishing or exploiting a vulnerability is prohibited. 8.3. DDoS attacks, hacking, phishing, falsifying evidence and distributing malicious files are prohibited.
Rule10
Administration & sanctions
9. Administrative actions
9.1. A penalty may be issued only when the violated rule and sufficient evidence are available. 9.2. A player has the right to know the rule cited, the duration of the penalty and the appeal procedure. 9.3. Emergency measures to protect the server may be taken without prior warning but must be recorded after the threat has been resolved. 9.4. Instructions to correct an unsafe mechanism, remove excessive load or stop a violation must be followed.
Rule11
Administration & sanctions
10. Penalties
10.1. Flooding, excessive caps and off-topic messages: warning → 30-minute mute → 2-hour mute → 24-hour mute. 10.2. Insults and toxic behaviour: warning or 2–12-hour mute → 3 days → 7 days. 10.3. Minor theft or griefing: property restoration and a 3–7-day ban; repeated violation — 14–30 days. 10.4. Large-scale griefing, fraud, RMT and major damage: 14–90-day ban; repeated violation — permanent ban. 10.5. Cheats, dupes, intentional server crashes, hacking, DDoS attacks or publishing personal data: a long-term or permanent ban across the entire ecosystem. 10.6. Intent, damage, cooperation with the administration and repeated violations are considered when determining the duration.
Rule12
Administration & sanctions
11. Reports and appeals
11.1. Reports and appeals must be submitted through a ticket and include the username, time, place and supporting evidence. 11.2. The standard review period is up to 72 hours. 11.3. An appeal may be submitted within 14 days. It will be reviewed by a staff member who was not involved in the original decision. 11.4. Public disputes do not replace the appeal process.
Rule13
Property restoration
12. Property restoration
12.1. Property is restored when the loss is confirmed by logs and was caused by a server-side technical error, another player’s violation or an administrative error. 12.2. Losses caused by fair PvP, high latency, the player’s own actions or permitted game mechanics are not restored. A paid restoration is the only exception. 12.3. A request must be submitted within 48 hours and include the time, item list and circumstances of the loss. 12.4. Restoration must not create duplicates. Items that were transferred, spent or retained are not issued again. 12.5. A paid restoration service applies only within its published description and does not override the prohibition on duplication. 12.6. When denying a request, the administrator must briefly state the reason. A denial may be appealed once if new evidence is available.
Rule14
ASTRA · PvP
A1. Core mode
ASTRA is a PvP server with land claims. Claims protect blocks, containers and mechanisms, but are not safe PvP zones by themselves.
Rule15
ASTRA · PvP
A2. Permitted PvP
A2.1. PvP is permitted throughout the world except at spawn and in specially marked safe zones. A2.2. Combat inside another player’s claim is permitted if server mechanics allow damage. Damaging property or physical structures is prohibited. A2.3. Items dropped after fair PvP become the victor’s loot and are not restored. A paid restoration is the only exception.
Rule16
ASTRA · Restorations
1.1. Paid restorations
1.1.1. Purchased restorations are completed without additional requirements unless the service description states otherwise.
Rule17
ASTRA · Restorations
1.2. Loss caused by a server-side technical error
1.2.1. Example: a player was flying an aircraft when the vehicle froze because TPS dropped, the player was disconnected and then died from falling after reconnecting. 1.2.2. Evidence is required for a restoration: the death message in chat, video and timestamps where available. 1.2.3. A restoration is not provided when the death was caused by high latency or an issue on the player’s side. 1.2.4. Even when sections 1.2.1–1.2.3 are satisfied, a free restoration remains at the administration’s discretion. The administration may determine that the case does not require restoration.
Rule18
ASTRA · Restorations
1.3. Theft and griefing
1.3.1. Restoration after theft, for example from a chest or workbench, is possible only if a claim or action logging system was present. 1.3.2. If the offender is identified and penalised, the affected player receives all items on the verified list. 1.3.3. Items taken from a player killed in PvP are not restored unless cheats were used.
Rule19
ASTRA · Restorations
1.4. Death in PvP
1.4.1. Inventory lost in fair PvP is not eligible for restoration. 1.4.2. An exception applies when the death was caused by a cheat, bug or administrative action.
Rule20
ASTRA · Restorations
1.5. Synchronisation errors and world rollback
1.5.1. If items created earlier disappear after a world rollback, they are restored individually based on logs. 1.5.2. Items that were spent or transferred to another player are not restored.
Rule21
ASTRA · Restorations
1.6. When restoration is not provided
1.6.1. Restoration is not provided in the following cases: — the player dropped the item; — the item was crafted and later smelted or destroyed; — more than 48 hours have passed since the loss, unless another period is stated in the rules; — the player cannot accurately describe what was lost and when; — the loss resulted from third-party software, including X-Ray or an auto-clicker.
Rule22
ASTRA · Restorations
1.7. How to submit a restoration request
1.7.1. Submit a request to MARALYS support through the ticket system. 1.7.2. The request must include the username, date and time, cause of the loss, list of missing items and supporting evidence. 1.7.3. Review may take up to 72 hours. An administrator may request additional evidence.
Rule23
ASTRA · Restorations
1.8. Limitations of responsibility
1.8.1. The administration does not restore resources spent on crafting or progression unless the process itself was cancelled by a bug. 1.8.2. Falsifying evidence results in a ban without the right to appeal.
Rule24
ASTRA · Restorations
1.9. Evidence example
For a request under section 1.2, provide a screenshot of the death message in chat, for example “Player X hit the ground too hard,” and state the exact time of the event. The request may be denied without these details.
Rule25
ASTRA · Restorations
1.10. Decision on a free restoration
1.10.1. The administration may determine whether an individual loss requires restoration. 1.10.2. A decision on a free request is made by the reviewing administrator based on the circumstances, even when the formal conditions of section 1.2 are met. 1.10.3. This rule does not apply to purchased restorations under section 1.1; those are performed within the published service description. 1.10.4. A decision on a free restoration is final. If a request was denied because of a technical error during the review of supplied evidence, one repeat submission is allowed without a guarantee that the decision will change. 1.10.5. Relevant circumstances may include knowingly entering a dangerous area during lag, a disputed bug that cannot be reproduced and the player’s history of violations.
MARALYS / Before connecting
Rules are part of the game, not fine print.
Joining the server means accepting its rulebook. If any wording could be interpreted in different ways, ask the MARALYS team before a dispute occurs.