Approved 2022/06/23 15:35

Dracverse Rules

Do not try to cleverly skirt the intentions of any of these rules or limitations while sticking to the letter of it.

1. Do not be an asshole; racism, bigotry, harassment, personal attacks, religion, politics, exploits, NSFW, advertising, explicit language, impersonating other players/factions/staff, or pinging/DMing staff will not be tolerated. No alt accounts are permitted, in game or in Discord. This server is run by adults who volunteer their time, we will not tolerate bullshit. In addition, all communication in public channels must be in English for ease of moderation.

2. Your Discord nickname must be set to match your In-Game name (case-sensitive) and you are required to create or join an in-game faction upon joining the server, impersonating factions, nations, or explicit names/tags is forbidden. Your Discord nickname may include your faction tag as long as it is after it in the following format: "Kontu [CAL]". Your faction status must be set to "at war" before you engage in hostile actions, including assisting in attack/defense. Creating your own solo faction after you spawn in a ship is fine.

3. All blocks must be owned by an active player at all times and must abide by our block limits. In addition our auto cleanup will delete any grids that meet any the following conditions:

  • Blocks on the grid owned by "Nobody"
  • Grids with "Grid" in the name. (Includes anything with letters G-r-i-d in that sequence)
  • No Beacon Block placed on the grid (unfinished/1 steel plate is enough)
  • Grids less than 20 blocks
  • 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.


4. Player action (Klang, 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. Learn more about performance considerations and gameplay restrictions here.

5. If you are unsure, open a ticket and ask first. Ignorance of the rules does not exempt you from them, we will usually be tolerant of first offenders but if you are uncertain whether a decision will qualify as a rule break, open a ticket and ask first. We will not tolerate boundary pushing, grey areas/technicalities do not skirt the purpose of the rules.

1. Setting any of your functional blocks to share with all during a combat scenario is considered an exploit of WeaponCore targeting. Any use of this during any combat situation PvP or PvE will result in punitive action.

2. Using a grid owned by an enemy to bypass WeaponCore targeting is considered an exploit of WeaponCore targeting. Any use of this during any combat situation either PvP or PvE will result in punitive action.

3. Capturing a grid and fleeing with it is acceptable but taking a disabled enemy ship into an active combat zone for the express purpose of bypassing weaponcore targeting is considered an exploit of WeaponCore targeting. Any use of this during any combat situation either PvP or PvE will result in punitive action.

To reduce strain on the server, we restrict the number of certain ship cores a player can have, as well as the BAR. All per-player restrictions are per-instance, so a player may have up to the maximum number of limited grid cores in each Nexus instance. Both player and grid limits apply at all times. Blocks must be owned by an active player. If a player is not online for 10 days, any blocks they own on grids they are not the main owners of will revert to the grid owner. Grid owners are responsible for their limits still when this occurs.

NOTE: Due to their being mechanically enforced by the ship core system, any attempt to circumvent these limitations will be viewed as exploiting and may result in a warning or ban.
ALSO NOTE: Should you believe your numbers are incorrect, you can use the !fixship and !blocklimit update commands found on the Player Commands page

These numbers are cumulative across all blocks of their type. For example, four basic refineries, two normal refineries, and four elite refineries would put a player exactly at their limit.

All block limited blocks on a grid must be owned by either the player or a member of the player's faction. These blocks must comply with the established block rules concerning grids and player totals. Any deviation from this rule will result in penalties including the possible deletion of the grid without warning. We expressly forbid the selling/renting/etc of block allotments.

Per Player Limitations:
Blocks are not limited per player in the same manner as previous iterations of Draconis. Rather, the ship cores contain pre-grid restrictions, and certain ship cores are restricted per player.
Per player limitations apply to EACH INSTANCE SEPARATELY. Restrictions are as follows:

  • One Ground Station Core
  • One Space Station Core
  • One Space Facility Core
  • One Factory Grid Core (cannot convert to station)
  • One Ground Facility Core
  • Three Ground Keep Cores
  • Three Space Keep Cores

All other ship cores are not limited.

Players may not "ransom" or "hold" the limited blocks of another player against their will. A player may have on their grid: 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.

Per Grid Limitations:

Per-Grid Limitations are determined by the core type of the grid they are placed on

  • Current per-grid restrictions are here

All block limited blocks on a grid must be owned by either the player or a member of the player's faction. These blocks must comply with the established block rules concerning grids and player totals. Any deviation from this rule will result in penalties including the possible deletion of the grid without warning. We expressly forbid the selling/renting/etc of block allotments.

In an effort to provide better transparency as well as consistency in support experiences, we have built this list of example restore / no restore situations that both Staff and Players will be able to reference.

If you are unsure if your scenario falls under one of the below you can always open a ticket and ask about a restore. We are always happy to at least look and confirm why a grid disappeared, as there is no way to learn from mistakes otherwise. We will work on evolving this list as time goes on to maximize clarity.

Note: Grid restores are only ever from server backups, *never* from a player provided blueprint. If a server backup does not exist, no restore can be provided. Players get a single “oops” restore every 30 days for player error. This cannot be used for combat (PVP or PVE) losses.

Non-exhaustive list of restore reasons for DRACVERSE ONLY: General examples we restore grids for:

  • Grids lost to new, confirmed bugs we have not warned players about via announcement (except for scenarios listed in the no-restore section)
  • If the bug is unavoidable even after announcement, we may still restore for it
  • Grids removed due to server crash
  • Grids lost due to sector transit
  • Grids that die immediately upon being loaded from Hangar (loaded into another grid, or loaded from hangar into voxels for example)
  • Grids lost for cleanup reasons (1 per 30 days permitted)

General examples we *DO NOT restore grids for:

  • Grid chunks cut off an auto-cleaned for being 2 blocks in size or less will not be comped/restored in any way
  • Grids cleaned up for being <20 blocks in size can not be restored as no backups are created of grids that small
  • Grids lost in a PvP encounter (regardless of bugs encountered during the PvP )
  • Grids lost in PvE encounters
  • Grids lost in high risk area's (Example: KotH, regardless of bugs encountered)
  • Player Inventories are not restored/comp on loss as we can not validate them in any way

We will usually not restore the following, but they are eligible for an “oops” restore, one per player per 30 days:

  • Grids lost to clang (physics issues, falling through planets, etc)
  • Grids lost to crashing (hitting voxels, whether they were visible client-side or not)
  • Grid jumped into an object (asteroid/trade station/other ship)

Note: Players who publish their ship blueprints from the live server do so at their own risk. No restores will be provided if players use your uploaded BP to get your gps location and find your base. You upload at your own risk

If you have a concern and need to contact a member of staff privately feel free to contact a community liaison. Do not directly message or ping members of the staff who do not have the Community Liaison role.
Otherwise, to contact staff go to #support and open a ticket by following the instructions in that channel. This will create a new temporary channel for you to speak privately and directly with staff.
NOTE: You must be logged in to the game server or ready to log in to the server before you pull a ticket for any matter that does not relate EXCLUSIVELY to Discord.
We will do our best to answer your ticket as quickly as possible, but please remember that our staff are people with day jobs that dedicate more hours then we are comfortable counting to maintaining the server and answering player concerns. Your patience is appreciated.

We MIGHT give you a warning if you break ANY of these rules, we reserve the right to kick or ban you from Discord and the Server. Attempting to circumvent a ban will be seen as a violation of rule one and your new account/IP will be banned as well.

  • sigma/serverrules.txt
  • Last modified: 5 days ago
  • by synirr