These rules apply to all areas of Draconis, in-game and out.
Community Rules Page
These rules apply to all Space Engineers servers, unless otherwise specified by that servers rules. Servers should include a copy of these rules on their specific rules page as well so you should always be able to find these rules there as well.
- Players are required to belong to a faction.
- You may create your own or join an existing faction.
- Factions must be set to hostile in-game before engaging in any hostile actions (IE: Declare War button in-game), being in an alliance with someone and then declaring war MUST have a 24 hour window between any hostile actions. Note: By default all factions are set to enemies
- Player action (Clang, recoil abuse, friction guns, rotor displacement turrets/ rotor drives, massive Builds, heavy scripting, exploits, etc…) that negatively affects the server are banned completely. Non-compliance will result in the removal of offending grids without compensation. (further infractions may result in a ban from the server).
- All blocks must be owned by an active player at all times and must abide by our block limits.
- Limited use of "share with all" is allowed for non-combat reasons such as a shared refueling station, however, the following rules must be followed.
- No grid may have all functional blocks set to "share with all", there must be some functional blocks that do not use that setting.
- Beacons and weapons may not be set to "share with all" for any reason
- "Share with all" must be disabled for all blocks on a grid when it is intentionally being taken into combat.
- Grids (and attached subgrids) are limited to 100 total functional blocks of each type. I.E 100 Thrusters, 100 Gyros, 100 hydro tanks (any combination of large/small) etc.
- Players may not "ransom" or "hold" the limited blocks of another player against their will. A player may have on their grid: limited blocks owned by themselves and blocks owned by their faction members. You may never hold a limited block under another player's ownership against their will. It must be hacked, destroyed, or otherwise transferred to legal ownership (
!claim).
- “Limited” blocks are blocks we restrict via BlockLimiter plugin. Please see a clusters home area for their list of limited blocks
- Non-limited blocks (like beacons) can be held hostage
- DIE specific: remote block removal is enabled, so the other player can remotely delete blocks anyway (see Capturing grids, and also note the fairplay rule).
Reminder - If you are unsure if something will break the rules, just open a support ticket and ask.
- First and foremost this is a game, this server therefore bans any type of chat involving the below topics;
- Politics
- Identities
- Sex
- Gender
- War
- Hate
- Anything not related to the game.
Attempts to circumvent the above topics by skirting the boundaries will be met with the same punishment as the above topics. We have no time for people thinking they are smart by talking/referencing above topics in a indirect way to provoke a response.
You wanna discuss the above topics do it out of our Discord and our Game Servers.
- Banter is allowed, however remember this is a game so keep it friendly. If you are unsure if something would be considered not friendly then assume its not.
- White on white hostile actions (i.e. attacking someone who is neutral to you) is against the rules: it's considered to be an exploit of the games faction mechanics. While setting turrets to target neutrals isn't specifically "against" the rules, there is absolutely no need to have this setting on and it could cause you to fall fowl of the white on white rules. So we recommend not having it set.
- Salvage Rights: The white on white rule can be voided if a player wishes to salvage a grid from an ally who is not currently playing.
Please follow the steps below:
- Tag owner in die-general-chat requesting Salvage Rights
- Await response
- If "Yes" then proceed
- If "No" then leave it
- If no response after 1 week then escalate to server lead for approval, if “Yes” then proceed, if “No” then give up.
- Seal Clubbing, i.e. advanced players attacking new players, is forbidden.
If you (or anyone in your faction) have been to space, you are no longer considered a new player (aka “seal”) and are therefore not allowed to attack anyone on the starters, new players or not.
PvP for players who have been to space is to be done outside of the starters, in space or on other planets.
Your status resets if you (and all members of your faction) have lost all your grids, emptied your hangar, and restarted in a new spawn pod - you are a new player again until you (or anyone in your faction) go to space.
We keep logs of all PvP, anyone caught violating this rule will have to answer to staff and the penalty may include, but not limited to, a reset for you (and all members of your faction).
If a seal or any player parks or builds within 2.5kms of a safe zone, non seals will be allowed to take out your guns however no raiding will be allowed.
- Beacon targeting during Offline or Online PVP is frowned upon as it is an abuse of cleanup mechanics. We ask players not to do this, and anyone seen doing this intentionally risk sanction up to ban from DIE.
- TopGrid: Any grids that exceed 50k pcu will go top grid, that means your grid will broadcast to the whole server.
- Capturing enemy grids to avoid Weaponcore locks allowing you to attack without triggering defenses is forbidden.
- DIE carries with it a black and white policy for what is and is not eligible for grid restore. Unless a server crashes and caused a grid to disappear, a grid is not eligible for restore.
Examples:
- Eligible restore: Loading from hangar, server crash, grid just poofs into thin air because it wasn't saved
- Not eligible for restore: Any mistakes made by the owner of the grid, grid deleted by cleanup (lacking beacon, not renamed, less than 20 blocks, no power), PVP or NPC (drones) attacks, basically anything non related to server side issues.
We fully understand it can be frustrating to lose things through no direct fault of ones own actions. This policy is not all about it being hard -- the support load required to handle DIE without this policy is also simply too high for us to handle at this time, hence the black and white policy of "if a server crash didn't delete the grid, it's not eligible for restore". Regardless of why this happened - a server crash did not delete the grid, thus it is not eligible for replacement. That is the flat policy DIE has right now across the board. This policy is not treated as a grey area, and we are not saying it was your fault / something you did or that it wasn't a server hiccup as a root cause. This is currently the most fair way to apply a grid restore policy to DIE for things that all players are affected equally by.
- Remote block deletion fairplay rule: if you were just part of a battle and lost grids, you are not allowed to immediately remotely delete the grids. You must give them at least 1 day (24h from the end of the battle) to salvage and claim, then after that if it's still not claimed and you want to remotely delete, you can. See Capturing grids for more details.
- Parking at Trade Stations are allowed however logging off with your rover/ship still in the safe zone is not allowed. If caught your grid will be moved outside the bubble and may get destroyed by NPC's or from PVP and you will not be compensated for this, you have been warned.
(Grids in Hangar do not count against these)
- Players are limited to 9 ship tools per type (drills, welders, grinders) total personal ownership/per grid
- Factions are limited to 9 ship tools per type
- Players are limited to 8 Farm blocks total personal ownership
- Players are limited to 5 half Solar panels total personal ownership (These panels don't require Ai cores)
- Players/factions are limited to 3 Survival kits total (Unlimited building for Med bays)
- Players are limited to 1 BioReactor total personal ownership
- Grids are limited to 15 production blocks (Assemblers, Refineries, H2/O2 Generators)
- Players are limited to 5 production blocks per type (5 refineries, 5 Assemblers, 5 H2/02 Generators)
- Gravity generator - 3 per grid, 6 per player total
- Space Ball / Mass Block - 10 total (combined)
Blocks will shut off when you go over these limits.
Programable blocks are generally used for adding custom scripts and scripts found off the workshop however every Engineers needs to know a few things before using them;
- You must request a Scripter role through tickets on the Sigma Draconis discord page, then click on die tickets, and ask for the role and make sure to mention the server you need this for.
- After you get a Scripter role, you will notice in game that a star is by your name in the players menu, this means you have the scripter role, if you do not see this star then reopen a ticket or if your ticket for the original request isn't closed, inform them there.
- Now what scripts can you use, well not all scripts are good for servers, some can help and some can cause a lot of issues, like speed and lag. The best thing to do if your unsure is to see what scripts other players like to use, by requesting help in Die general chat or you can always ask through a ticket.
- Once you have a script add it to the programable block and follow the scripts guides on how to use it, that's it
- Warning: If your script uses to much resources from the server, an admin may come by and turn it off or delete it. If this does not happen, it does not mean your script is ok, it only means that we have missed it, which is why Sigma Draconis uses a plugin PB LImiter that will detect the tick rate on a script, this plugin will damage your Programable Block and you will be responsible for its repair. In order to find out how much resources your script is using, you must ask for help or if your familiar with how to edit scripts you can change the rate of ticks yourself.
- For safety and not risking damage to your programable block: Best to turn off programable blocks that use scripts that you don't need at the moment and also turn them off when you go offline
We understand that players may need to take a break (work, family, etc), and saving your grids outside of the game world, in a hangar away from other players and drones, can give you peace of mind before returning.
We offer 3 hangar options:
¶ 1. Self-service hangar commands
- it costs credits to save a grid to the hangar:
- first you need to deposit Space Engineers physical credits item to your virtual bank account by saying in chat
!eco deposit (from CrunchUtils plugin)
- note: the deposit command has no amount argument, it will deposit all physical credits in your character inventory, and in the inventory of the grid you're looking at, if any
- then say in chat
!hangar save while looking at your grid
- cost: 10 credits per block for small grid and 100 credits per block for large grid
- tip: don't forget to empty your personal inventory to your grid before storing it in the hangar if that's your last grid in the area
- note: the virtual bank account is deposit-only, and only used for hangar, as we want players to use physical credits in game for trade, with the risk of losing them if destroyed; in the future we may remove the bank account to directly use credits
- loading saved grids from hangar is free, list your saved grids with
!hangar list and load with !hangar load <#> ; you can unhangar from anywhere but the grid will be loaded at its previous location
- cannot save or load next to an enemy or other players (the error will tell you)
- cannot hangar on the starter planets (Corpus, Greer), only in space and other planets (the error will tell you)
- limited to ship grids only, no station grids; since we can't just disable station hangar, this is implemented in QuantumHangar by requiring an impossibly large price for stations
If you do not connect to the game in 30 days, your grids will be automatically hangared for free (if they were not already destroyed by drones or other players). This is primarily to save server resources.
If neither previous options are suitable, you can apply for a manual vacation hangaring where a staff member will help you hangar your grid while you're away.
The rules are as follow:
- Minimum vacation hangaring is 1 week (*)
- You must provide an estimated time frame when you are coming back
- You must wait at least 1 week after the last vacation ended before requesting a new one, e.g. if you requested vacation hangaring from 1st to 7th, you must wait till the 15th before you can request another vacation hangaring (*)
- You must be the majority owner of all the grids you want to hangar:
- if the grid is owned by other players (e.g. a faction mate), you must be the majority owner
- if the grid is partly owned by NPCs, you must first claim full ownership (using
!claim which requires 70%) so you are the majority owner
- You can request to hangar maximum 10 grids (*)
- Your grids may not be returned to the same place as before, e.g. if the area is now occupied by another player nearby
- If any of your grids are partially or entirely in voxels (e.g. underground), we will not restore it at the same location due to voxel reset, but elsewhere on the surface, then it's up to you what you do from there, e.g. dig again (*)
(*) this is to reduce staff support load and limit abuse
If you agree with the rules above and meet all the criteria:
- Open a ticket, state that you'd like a DIE vacation hangaring and include the link this page
- List the names of the grids you want to hangar (max 10)
- State when you expect to be back (minimum 1 week from now)
- Write down the ticket number
If your vacation hangaring was accepted and processed, when you come back:
- Open a ticket again, state that this is a DIE return vacation hangaring and mention the previous ticket number
If you have any questions, ask on #die-general-chat.