Rules

The rules on the discord server will ALWAYS override the rules written here as it takes time to update this page.

Not reading/knowing them is not an excuse to ignore/break them.
Attempts to skirt or evade rules or the spirit of the rule is akin to breaking the rule
Changes will be noted in ⁠public-changelog

---

Any grid that violates building rules is subject to deletion without compensation. Players who break rules are subject to differing lengths of bans and/or mutes.
Please video record and/or screenshot and report any interaction you find suspicious

Section 1) Community Rules

• 1) Respect others - If you think that making fun of people in a malicious way or trolling people is fun, then you should show yourself the door, or have it be shown to you.
  
• 2) No NSFW - NSFW content will not be tolerated. Nobody knows who could be watching someone's screen on the other side. This applies to in-game grids / builds, character backstory, and day-to-day interactions.
  
• 3) Advertising - If you wish to advertise something, open a ticket. Generally if it's something like a twitch or YouTube channel permission will be granted. If you advertise without permission, your message(s) will be deleted and you will be muted for increasing amounts of time for each offense. Permitted advertisements may be posted at most once per week.4) Use Relevant Channels - If there's a specific channel for a topic, put messages/content of that topic there, not in ⁠general or other channels.
  
• 5) Ruling - @Server Head word is final, if you have a problem with an @Admin ruling, then bring it to the @Server Head directly, but do not do so lightly.
  
• 6) Pinging - Pinging @Server Manager, @Moderator , @Admin or @Server Head repeatedly, especially without good cause is not allowed. Only ping these roles if you need help that only they can give. This also extends to pinging individual members of these roles such as @[SKA] Skye Meadows (SkyeCat).
  
• 7) Names - Inappropriate and real life political character names are not tolerated. Your Discord name in this server must match your character name, but may have your original discord name after it.

Section 2) Game Rules - General

• 1) Exploits & Hacks - Using known exploits to gain an advantage is strictly not allowed. If you want to use it for purely RP purposes, ask permission first, otherwise you may find the grid or yourself removed from the server. Using Plugins to do things like clip your camera through an asteroid is also considered an exploit. Hacks of any kind are not tolerated and will be instant ban. If you are unsure if something is an exploit or hack, open a ticket to ask staff.
  
• 2) Unintended Mod Behavior - If a mod is not behaving as intended, you are expected to report this behavior to Admins. You are not allowed to use that behavior to your advantage. For example if you take over an MES grid that doesn't shoot back due to a bug (and you don't tell me), that grid may be deleted.
  
• 3) No Clang Devices - Clang weapons such as rotor guns are strictly prohibited, as well as clang drives and anything that falls in-between. Gravity weapons are allowed.
  
• 4) Safe Zones - Players are not allowed to construct safe zones, and abuse of safe zones such as hiding inside one to "wait an enemy out" is not allowed.
  
• 5) Drones - A Drone is considered any grid that has AI blocks (move, fight, defend, etc) and/or has the ability fully function automatously. (For example, AI blocks to auto-dock a player piloted ship are not a drone) Only certain classes of ships are allowed to carry/launch drones. Grids such as RDAV or LAMP missiles do not count as drones. See Rules 9 & 10 for more details on drones.
  
• 6) Station Placement - Having station grids within 15km of another PLAYER station grid (friendly, enemy, or neutral) is not allowed.
  
  • 6.a) Moons are instead limited to ONE station grid for EACH FACTION in a 15km area. On moons, and moons only, you are allowed to build within 15km of a station grid of a neutral or hostile faction, just not within 15km of your own faction's static grids.
    
  • 6.b) Weapon Pods and Weapon Platforms (Classes) are allowed to be placed inside this radius, but must be a static grid and not attached to other grids via any means.
  
  
• 7) Aimbots & Cheesy Scripts - Scripts such as aimbots and other scripts that give the player an unequal advantage are not allowed and classify as exploits or hacks.
  
• 8) BaR Spam - Having more than one construction class ship with a Build and Repair in one location is not allowed as this is seen as circumventing the block limits.
  
• 9) Combat Drones - A drone is considered deployed if it has active AI blocks or has a programable block running that allow it to operate fully without direct player control. Up to 20 SG drones may be deployed by each player at any given time if the class of the ship permits. The amount of drones a ship can carry is not limited.

  Each class is limited to deploying a certain number of drones at once, detailed below. (unlisted = 0)
  

  • Cruiser: 1
    
  • Battlecruiser: 2
    
  • Light Carrier: 12
    
  • Battleship: 4
    
  • Carrier: 20
  
  LG Combat drones are allowed as the Corvette class only, which is limited to 1,000 blocks. Up to 1 Corvette and 4 Corvettes per faction are allowed.

  The max SG drone size is 12,500 blocks
  Limits are per Player
  

• 10) Non-Combat/Utility Drones - A drone is considered deployed if it has active AI blocks or has a programable block running that allow it to operate fully without direct player control.
  
  • Up to 2 LG Non-Combat or Utility drones (such as PAM miners, automated cargo drones, etc) may be deployed by each player at any given time.
  • Up to 3 SG Non-Combat or Utility drones may be deployed by each player at any given time.

  The max drone size is 12,500 blocks.
  Limits are per Player
  

• 11) JB (Jump Bridge) Build Restrictions - Players are not allowed construct or relocate static grids (including Weapon Pods & Platforms) to within 50km of a Jump Bridge.

Section 3) Game Rules - Script & Building Limits

• 1) Be mindful of scripts - Keep an eye on server performance when using your programmable blocks, especially more intense scripts such as Isy's Inventory Manager. If you notice a dip in performance, attempt to slow down the script and/or don't use that script. Programmable Blocks may be turned off automatically if they exceed limits defined in ⁠scripts-cleanup.
  
• 2) Livable Conditions - All large grid ships must be pressurized on the inside, at least where the pilot is. (with the exception of drones) I.e. you can't just stack 10x oxygen bottles for a fight, you have to be able to survive naturally while piloting your ship.
  
• 3) Realistic Entrances - Entrances must be realistic in how to get in them. For example, you can not have a maze of thrusters to get in the door. This applies to both ships and stations.
  
• 4) Meta-armor - Using blocks that can take more damage than armor (gates, gyros, hangar doors) as the armor of your ship is strictly prohibited.
  
• 5) Grid Weapon Size - Small grids are not allowed to use or control any large grid weapons through any means unless said small grid is a subgrid of the main Large grid. Large grids may only use Large grid weapons, and can not have small grid weapon subgrids, with the exception of reasonable SG Player-Made-Turrets (PMTs) on LG ships.
  
• 6) Beacons - All grids MUST have a beacon that is well protected. The broadcast range is controlled by the class system. Grids without a beacon will be removed automatically every hour.
  
• 7) Disabled/Banned Blocks
  
  • Jump Drive (Use Framshift Drive)
    
  • Safe Zone

Section 4) Game Rules - Combat

• 1) Reasons for Combat - ALL Hostile engagements must have some kind RP tied to it, attacking someone because you wanted to OOC is not allowed. Examples of RP reasons include but are not limited to: War over IRP politics, Encroaching on "territory", Suspicious behavior by a vessel (said behavior must be documented for proof if required by admins). Piracy in the sense of always being at war with everyone or attacking random ships is not allowed. Currently, Piracy as a reason for war (i.e. I declare war on you to steal your loot) is allowed, but is like any another war and peace can only be reached by one side's surrender or a mutual peace agreement
  
• 2) No meta-building - Warships must have some form of a reasonable interior for their size, i.e. you can't just throw a cockpit down a tube in a 10k block warship and call it good. A ship that size would need to have at least a small bridge. THIS IS CRITICAL. Any warship found to be a meta-build, especially a min-max shield build, may be deleted with or without warning and without compensation. Mining/Industrial ships are exempt. If you have a question if something is "too meta" please ask. If you tell the admins about it, they will be much kinder.
  
• 3) Build & Repairs (BARs), Welders, and Projectors - They are not allowed to be activated in combat whatsoever. Repairs must be done at a station, by another ship, or by hand if done in the field. You cannot jump out of combat to get away from this. I.e. you cannot jump out, activate welders & projector, and jump back in after you've repaired. Once your ship is damaged, it's damaged until you can have an external entity repair it.
  
  • 3.1) Light Carrier (CVL) and Carriers (CV) are an exemption to this rule, but their welders can only be used for production of Small grid fighter craft and not self-repair.
    
• 4) Hydromanning - You get ONE (1) attempt at hydromanning an enemy grid during a fight, this is a per-player per-ship basis, so if your ship is destroyed and you come back as a "reinforcement" you get another chance. Additionally, if you have another player on your ship, both of you may make a hydroman attempt. You may not "use" someone else's hydroman attempt, even if you are on the same ship.
  
• 5) No Offline Raiding - If a faction is offline, you may not attack any grid that belongs to them. You may also not camp an enemy's location to wait for them to log on unless RP permits (such as IRP leaked coordinates). Setting traps, moving or tampering with grids, or otherwise interfering with a grid or location while the owning faction is offline is also considered offline raiding. If your client crashes during a fight, you are encouraged to ping your opponent(s) on discord to inform them of the crash, and they are encouraged to stop shooting until you can log back in.
  
• 6) Combat Logging - If a player/faction logs off during combat, the attack on that specific location may continue. Attackers may not go on to attack grids at other locations, but may attack other grids at the location being attacked at the time of the combat log. If a player logs off as you arrive, please open a ticket to inform an admin and it will be noted. If a faction is guilty of doing this repeatedly, an attack with them offline may be allowed.
  
• 7) Shield Generators - Station shield generators may not be built on any vessel that is considered a ship (usually determined by having gyroscopes or being a dynamic (ship) grid).
  
• 8) Hangaring - Using the hangar to hangar grids while actively engaged in combat is not allowed. Even if you are beyond the check range of 5km, if you have someone actively hunting or shooting you, you are NOT allowed to hangar your grid.
  
• 9) Drilling - Drilling around defenses within 2km with either a hand drill or ship drills is not allowed. This applies to both player and NPC engagements.
  
• 10) Stoneaging - Only applies to planetary bases, If an attack on a faction could significantly hinder their ability to recover or if you are at all unsure, open an admin ticket to ask if an attack would be considered stoneaging.
  
• 11) Abuse of Quantum Hangar - Using the hangar to hide grids or loot while at war is not allowed. "Loot" is defined as anything that would not normally be on that ship or station (such as ingots on a cruiser). Hangaring non-empty grids (such as a full cargo hauler) is considered a violation of this rule except for in the case of warships.

Section 5) RP Rules

• 1) Value your characters life - Actions that pose a risk of Character/IRP Death should not be done lightly, for example you/your character should be nervous about meeting with a hostile faction, as things can go wrong and your character can end up dead.
  
• 2) Character Death
  
  • In PvP Combat: If your character dies at the hands of another player (or player's ship), they are dead and you can not continue to RP as that character, and must create a new character.
    
  • In PvE Combat: If your character dies at the hands of a hostile (i.e. enemy weapons fire), AND the ship your character was aboard has no respawn point, then your character is rendered "In Recovery" for 7 days. While In Recovery they cannot interact with other factions, and they are IRP confined to medical chambers as they heal. This means that they are unable to command a ship or other members IRP. Survivors Quarters is unaffected by this.
    
• 3) Character Capture - In PvP you are allowed to take a character captive should reasonable conditions permit (such as boarding), and you may hold them for up to 7 days before they must be released, ransomed, exectured, etc, so that the player is not locked out of RP for too long.
  
• 4) Access to RP Channels - In order to access RP channels (such as ⁠open-frequency) you must make a post in ⁠character-info and then an admin will give you the @Survivor role, which will allow you to post in those channels (You can still view them without the role). If your character dies, this role will be revoked until you make a new character.
  
• 5) No Metagaming - Using information that your character would not know to determine or help determine your actions is not allowed. Example: If someone warns you OOC they're going to attack you. You cannot immediately run to your defenses, you must "play the part".
  
• 6) No Powergaming - Attempting to force another player (not character) to do things the way you want them to is considered powergaming, and is not allowed. However, if you have In-Character reason to their character to do something (such as a gun pointed at them), that is allowed.
  
• 7) No broadcasting IRP secrets OOC - You may not reveal secrets about a character (your own or someone else's) in a public OOC channel. Doing so ruins the ability for people to find out through RP, and encourages meta-gaming. If you decide to reveal a secret about your character OOC in a DM, that is up to you.
  
• 8) Multiple Characters - Having multiple characters at once or attempting to RP as different people without a closing to your previous character is not allowed.
  
• 9) Claims - While anyone may lay verbal claim to any section of space or planetary body, you are only allowed to enforce territory (i.e. attacking encroaching ships) within the forced broadcast radius of a station grid in the area. Combat without a different, valid, RP reason outside of the forced broadcast radius of a faction's station (and IRP claim) is not allowed.
  
• 10) Message Visibility - Anything said in ⁠open-frequency is considered to be seen by everyone. Anything in ⁠survivors-quarters is considered only seen if it is specified in the message (either OOC or IRP) that a character sees it. ⁠survivors-quarters is for RP flavoring to give a bit of a look of what's going on behind the scenes of factions. Posters in ⁠survivors-quarters are to indicate who, if anyone, can see what is playing out. ⁠secure-frequency is used for IRP faction-to-faction communication and faction/characters other than the designated sender/receiver cannot IRP read the contents of the message
  
• 11) Faction Lore
  
  • 11.a) Faction 'lore' is not able to give an advantage IRP or In-game. (for example, using faction lore to give yourself technology other factions don't have)
    
  • 11.b) A faction's lore is it's foundation; the idea that it is constructed upon. Due to this, faction lore cannot be changed once placed; unless conditions allow a change such as a rule.
    
  • 11.c) A faction's lore MAY be permitted to encompass areas outside the 'server' system. Such lore MUST be developed with an admin present to prevent it from interfering with server lore or breaching the rules.
    
  • 11.d) Faction lore can't circumvent Official Server Lore nor can it be used to circumvent rules in any manner
    
• 12) Character Lore - Character lore is generally seen as how a character would tell their own backstory, which means that they can tell it however they like. However, no server lore nor game mechanics will be changed to accommodate any character-specific lore backgrounds. Essentially you can "tell your story" however you want, but if you/your character start making up things that don't align with historical server events, they can be seen as a liar IRP and suffer any related consequences.

Section 6) Other Rules

• 1) Grid Restoration - If something strange happens to your grid, such as clang taking hold of it. You have 48 hours to notify an admin, AND for an admin to fix it before backups start being overridden and the grid risks becoming unrecoverable. If it disappears and is not on the grid list anymore, you have 14 days before every trace of it gone forever. If a grid is in need of restoration, it must remain unchanged by players after the incident occurs. Modifying the grid after an incident happens but before a grid restore request can be handled is grounds for the denial of said restoration request.
  
• 2) BP Disclaimer
  
  • 2.1) By using a public workshop BP or by publishing your own ship on the workshop, you accept the risks that someone might use the blueprint of it and find the weaknesses.
    
  • 2.2) By using a creation on the server you accept that someone may BP it, meaning if you don't want your creation appearing on another server, don't use it here.
    
• 3) BP Rules - Even if you obtain a ship on the server, you may not build more of it using a blueprint without permission from the faction that owns the ship IRP. You may repair it to the condition you found it in (i.e. use a bp of the damaged ship to repair after further damage). A captured ship is gone once destroyed, and cannot be rebuilt even to the state you obtained it in.