Latest stable version Checking...
    • Aug20

      Starmade v0.194 - Shipyards

      Hello players,


      This is one of the bigger updates as shipyards are finally done. Their main purpose is to create a bridge between normal game play and a new creative mode. But it has a lot more functions than that. You can automatically construct or deconstruct ships, repair ships according to a design, test out ideas, and much more.


      Creative Mode for Blocks


      Before we talk about shipyards themselves, we shortly want to talk about a long anticipated feature: Creative Mode.

      This can be either in the game startup settings (below Tutorial) for single player, or via the admin command ‘/creative_mode <playername> <true/false>’ for multiplayer.

      This mode adds an extra tab in your inventory with unlimited amounts of every block type in the game.

      In future updates the sorting option as well as the assignment to the hotbar will improve, as at the moment the nicely sorted blocks quickly get unsorted when used.

      In this absolute creative mode you can also drop as many items as you want into other inventories like chests.




      Now for the main part of this update. Shipyards are now available for stations.

      They come in 3 blocks:


      • The shipyard computer, from where the shipyard is controlled and managed.

      • The shipyard module, which defines the shipyard physically

      • The core anchor, which defines where ships in a shipyard will be docked.


      How to create a shipyard


      In future updates, build mode will be enhanced not only for shipyards but also to give a visual guide on how to construct different systems. At the moment, the shipyard will give feedback in the form of text raising from the shipyard computer or the modules if it was constructed incorrectly.


      Shipyards are the most advanced entity in terms of structure next to warp gates. It has to be built as a series of arcs.


      So here is a guide on how to construct your first shipyard:


      1. Place down the shipyard computer and select it. (All shipyard modules have to be connected to it)

      2. Place down an arc, or a U shape. Both end points have to be in one straight line.

      3. Place down another arc that looks exactly like the first one to create a corridor. (The maximal distance from arc to arc is currently 50 blocks, but it is configurable in the blockBehaviorConfig.xml)

      4. Place down exactly one shipyard core anchor anywhere in the corridor. You can orientate this block in all 24 directions like a rail block.


      And you are done already.


      The size of ship you may dock is unlimited but the shipyard will not work if the length of the yard is too small (the other dimensions don’t matter as long as the docked ship doesn’t overlap with any block except the anchor).


      Keep in mind that docking your ship will put its core directly into the anchor. There are plans for the functionality to be able to add multiple anchors to serve multiple shaped ships.




      Ship designs are a new type of meta items. They are bound to a concept of a ship and can be loaded in shipyards to edit or to construct.


      Shipyard functionality


      A shipyard has several features. To access them, just hit ‘R’ (Activate/Open) on the shipyard, and press the “Place Order” Button.

      Here you can choose from several commands depending on the shipyard’s current state (e.g. if a ship is docked or not)


      Create New Design


      This will create a new design meta item, and load its content into the shipyard. A core will be placed exactly where the shipyard anchor is. A design is just a projection, so while you are able to edit it in the shipyard, you are not able to undock it. The huge advantage of editing a design is that you can edit a ship in creative mode.


      Unload Design


      This will unload the currently loaded design so the shipyard can be used for other tasks. This can also be done by right clicking on the currently loaded design meta item.


      Load Design


      You can either choose a design from a dropdown, or you can right click on any design that is currently placed in the inventory of the shipyard to load it.


      Construct Design


      This will create a real ship from the currently loaded design. It will calculate the required resources and collect them from the shipyard inventory. You can also activate item pulling for the shipyard to acquire blocks it needs from inventories that are connected to the shipyard computer. Once a ship is done constructing, you can undock it and use it like any other normal ship.


      Test out Design


      If you want to test out your loaded design before collecting the resources to build it, you can use this order. It will teleport you and the design into a virtual test sector. In future updates the test sector will contain several targets as well as an option to spawn in AI waves.


      Create Blueprint from Design


      You can also create a normal blueprint catalog entry from a loaded design.




      This can be used if a normal ship is docked to the shipyard. You have the option to either deconstruct a ship completely, or to create a design from it. All blocks the ship consists of (as well as the content of all chests) will be placed into the shipyard inventory and connected chests. All items that have no room to be placed in the inventory, are going to spawn in space beside the shipyard.




      This option restores a ship according to a design and places any leftovers into the inventories/space. In future versions, an option will be added to assign a design directly to a ship’s core to make repairing even more streamlined.


      Future Functions


      There are many more tools we want to add to shipyards, including being able to move a ship’s core, and connection to the logic and rail system for automatic deployment.


      Create Docking Tool


      There is also a new feature in the advanced build mode. You can now create a new dock in any shape and orientation. Just click on the button, select a rail surface to spawn it on, place the core and select its orientation with the mouse wheel.




      There were some optimizations in physics and rails to decrease the resting load of structures with a lot of them. Also, the collision routines of anything non cube (wedges, players, etc) has been improved.


      Furthermore, planet generation has been optimized a bit so it will be faster and put less total load on the cpu.




      Continued textural improvements include:

      Cleaner PlexDoor texture.

      Cleaner Metal Mesh texture.

      Revised computer back face.

      Revised Effect module tessellation.

      Revised Factory textures to fit the same theme as Shipyard blocks.

      New Motherboard textures.

      New Circuit textures.

      New Charged Circuit textures.

      New Decorative Fan texture.

      New Shipyard Computer / Shipyard Module / Shipyard Core Anchor textures.


      In preparation for coming graphical updates, we have performed a full overhaul of our normal maps and it’s shader for more accurate results. Accurate texture padding has also been added to avoid unsightly seams on block edges.

      For more information and samples see this post;


      Bugfixes + small config change


      There have also been some bugfixes like a softlock in the tutorial, and several crash fixes.

      Power penalty has been reduced for missiles (10% -> 2.5%) and disabled for damage pulse.


      Server admins can also now choose to not let players spawn directly from blueprints (mostly interesting for Role Playing or servers with harder settings). Also, it’s now possible to combat heavily modified blueprints by enabling a check in the server config that will remove any ship that has disallowed blocks on it (e.g.jump gate on a ship)

      Here is a list of other fixes:

      Starmade (Private) | T488 Ships that are piloted dissapear and eject the pilot when pilot fires weapons
      Starmade | T483 Nullpointer with "T" weapons menu
      Starmade | T467 Highlighting/selecting sectors on galaxy map
      Starmade (Private) | T450 Fix for entity-flag exploit does not affect already created entities.
      Starmade | T444 Turrets shoot at targets out of range in "Selected Target" mode
      Starmade | T417 Moving stations as admin by using /change_sector or /change_sector_for breaks territory claims
      Starmade | T400 Warpgate faction issue
      Starmade | T398 Ships can instantly use the cloaker or jammer after they have been revealed by a scanner
      Starmade | T313 JVM Crash detected: incorrect dialog
      Starmade (Private) | T225 radarjammer pirate exploit
      Starmade | T215 Players on docked rail entities are left behind during sector changes or jumps
      Starmade | T14 mouse sensitivity sync

      That’s all for now. If something is is broken, please report it and a hotfix will attempt to fix it as soon as possible.


      Thanks for playing StarMade,

      - schema and the Schine team

    • Aug2

      StarMade v0.19361 Flash Light, Ship Scores, On-Ship Spawning & Bugfixes

      Hello players,

      We have another bugfixing update while bigger features are in work.

      Fixes contain a lot of things that have been a pain for some time, but there is also a new item: the flashlight. You can buy it from the shop clerk.

      Spawn on ships

      Another feature is also the functionality that you can now spawn on moving ships. Even if the ship is moved after you logged out, and then in a sector that is currently not loaded, you will still spawn on your ship. This will work as long as you are in any way aligned to the ship while logging out: Pilot, in gravity, or simple spacebar alignment.

      This currently is limited to spawn after logout, but mechanics will come for respawning on ships after death. There still have to be some gameplay aspects discussed, as you wouldn't want a player to spawn on a ship you just stole.

      Ship Scores

      Another larger feature which is still in the making is ship score.

      This is basically a way to automatically classify ships.

      Ship scores are aggregated from multiple simpler scores.

      As for example weapons generate scores from:

      • damage per second

      • hit probability (projectile speed, reload, spread)

      • distance

      • power consumption

      These scores are then aggregated with the power score, and other scores to generate 4 main scores:

      • Offensive Score

      • Defensive Score

      • Mobility Score

      • Support Score

      Since it's fairly obvious that these values have to be balanced, the main scoring process has been externalized to a LUA script to change it on the fly.

      After a few iterations of initial balance not only will they make it easier to classify ships in the blueprint/website, we can also then use the scores to determine pirate spawning by difficulty, and adapt it depending on how powerful the combined scores of the players in an area are, which should lead to a lot better scaling difficulty and therefore more fun.

      Exploit Fixes and Optimizations

      There also have been lots of small optimizations in various parts of the game. For example, framerates on very large structures should go up a bit when higher max-segments are set in the options.

      There also have been some fixes to exploitations of game mechanics like the shield drain/supply being overpowered. Also cloaking/jamming now has a reload sequence when switched off.


      The block behavior config received some minor changes:

      • Power consumption per second was changed to power consumption per tick, all related values were changed accordingly.

      • EMP power damage was doubled, the power damage dealt to a ship is 2 times higher than the power consumed to fire that weapon.

      • Shield drain, supply and power drain received some value changes, it should be balanced:
        Shield drain has the same shield DPS and power use as any other basic weapon but it gives you 50% of the drained HP.
        Shield supply is set to power supply levels, its power consumption is 10 times lower though since a supply transfers 100% of your own shield.
        Power drain, drains 50% less power than an equal EMP weapon but you gain 50% of the drained power.

      • Shield drain and supply now allow supports.


      Here is the list of all fixed bugs:

      1. T452 planet plate alignment odd when astronaut logout restart on planet surface

      2. T444 Turrets shoot at targets out of range in "Selected Target" mode

      3. T439 Blocks/items in crafting slots aren't deleted on death when inventory drop on death is enabled.

      4. T424 Kicking someone out of the core with torch let Navigation Point disappear

      5. T422 Block information not wrapping lines like shops do

      6. T421 Missiles do once again damage mother entities (turret base and motherships)

      7. T417 Moving stations as admin by using /change_sector or /change_sector_for breaks territory claims

      8. T416 Entity flag editing

      9. T414 Loot is not generated when the entity is destroyed by an AI/Turret

      10. T412 Logic blocks with multiple inputs loose connections when pasted using the copy/paste feature

      11. T407 windowPositionAndSizeConfig.tag sporadically corrupts.

      12. T406 Attempting to place a block with nothing in slot will crash the game.

      13. T405 Check if the player has a ship-core in the inventory is performed after the player is requested to enter the new ship's name.

      14. T401 Pressing Left ctrl and left alt will drop the framerate to 10

      15. T400 Warpgate faction issue

      16. T397 AI ships can not use anti missile turrets

      17. T396 Pirate AI does not work

      18. T395 Missiles ignore shield sharing

      19. T393 damage numbers don't show correctly for cannons, missiles and damage pulse

      20. T391 Client logs show confidential information

      21. T389 docked warheads don't explode on contact

      22. T377 Failing Alignment after exiting docked entity

      23. T374 faction inheriting mechanics override faction ID's

      24. T366 Option for Personal faction enemy broken

      25. T355 ship and armor HP is capped

      26. T343 entering occupied build block causes several issues

      27. T331 Redo/undo doesn't work correctly with Replace

      28. T326 Astronaut mining bonus notice doesn't show correct bonus

      29. T313 JVM Crash detected: incorrect dialog

      30. T312 ship speed while being pulled into a wormhole can be limited by pressing a movement key

      31. T310 Network data too large: priceUpdateBuffer, controllerKeyNameBuffer and controllerKeyBuffer

      32. T278 Leaving a C aligned ship causes issues with searching a safe exit position

      33. T238 Display Module text; shadow effect makes writing non-legible

      34. T233 Chat kick and ban options

      35. T225 radarjammer pirate exploit

      36. T222 Can reset cool down of long cool down weapon systems

      37. T215 Players on docked rail entities are left behind during sector changes or jumps

      38. T203 Typo in /sector_chmod help

      39. T173 Completely mined asteroids not properly saved / respawn of half mined asteroids

      40. T166 Block list not working on Blueprint Catalog

      41. T165 Trading Guild Resupply Convoys will resupply player-owned shops.

      42. T148 Wrong warning when kicking Player from Faction

      43. T136 Turret AI does not always follow its setting

      44. T100 shield supply/drain beams are invisible

      45. T89 Item Duplication Using Asteroid Respawn

      46. T79 map filter shows text for turned off filters

      47. T44 Rail enhancers consume power but running out of power does not change anything

      48. T39 several menus allow background interaction

      49. T37 abandoned stations don't have decaying turrets

      50. T34 Phantom weapon and effect computers

      51. T32 admin command mistakes: /sector_info /ship_info /last_changed

      52. T24 Godmode does not transfer through rail docks

      53. T14 mouse sensitivity sync

      54. T6 shield damage applied by shield sharing is multiplied per chain

      I’m currently a little ill, but I’ll do my best that for the next update, the shipyard mechanics will probably be done, as well as more portions of the fauna.

      Thanks for playing StarMade,

      • schema and the Schine Team

    • Jul11

      StarMade v0.19318 New Explosions, Tools, and Bug Fixes

      Hello players,

      This update contains a brand new system for explosions, as well as new tools, updated textures, and a ton of smaller features and bug fixes.

      #hotfix 0.19319: Some player shops caused server crashes
      #hotfix 0.19320: Fixed AI not working and causing high server load. ALso fixed explosions ignoring shield sharing


       New Explosion System


      For the longest time, explosions were a big headache, not only because they were incredibly hard to balance, but also because their damage was unrealistic. Some visible cases of this are ships being hit inside hangars and players being killed inside ships, without the damage penetrating.


      Since a system with actual rays doesn’t scale well, a completely new and unprecedented algorithm was developed to make explosions, in a fully three dimensional environment with any number of obstacles, as realistic as possible. With the help of complex data structures, it’s possible to approximate the explosion as if raytracing was used. Not only that, but also the whole system works fully asynchronously so that most of the work can be done multithreaded.


      The performance can be finetuned through a server option which determines the maximal count of possible explosion threads. Server owners can increase that value by some, as it is currently set for a mid-level CPU.


      Additionally, a new update system for transporting the data to the clients has been developed which means a lot less network bandwidth being used.


       New balance for missiles and pulse


      The new explosion system gave us a ton of new possibilities to balance explosions, especially for shield damage, effects, and scaling. Since now damage to blocks is exact, the damage will only penetrate as far as the rays can possibly go.


      Missile damage has been adapted to compensate for the fact that on average half of a missile’s energy goes into the void of space if, for example, the missile is impacting a flat wall. They have also been adapted for armor on both ship and blocks.


      All explosive style systems have been upgraded including the pulse, which will now also emit in front of it’s output block. Pulse will also do some piercing damage. This makes it an excellent weapons to bypass armor when you get close to a target.



       AI targeting improvements


      AI no longer targets the center of mass of an object. It will now specifically target blocks of ship systems. Of course target-seeking missiles will now also do the same.


       Build Inhibitor


      Another little tool for boarding is the build inhibitor. This useful tool is turned on in the hotbar and prevents any building within a radius of 32 (which of course can be upgraded in the future).

      The tool is available to buy from all shop keeps.


      Note that there will be a lot more tools and gadgets coming for astronauts.


       Rebooting/Repairing Stations


      Rebooting stations either over structure tab or by pressing the reboot hotkey will now also repair all armor HP.

       UI Text Box Fixes


      The text boxes now have variable sizes. They also now automatically dock to the radar or build mode, so they will no longer block the advanced build mode when building.




      Kupu has updated some textures. We are also updating some Hud elements soon to give pilots better information when flying.


       Council Applications for Next Term now open

      Applications for the Council of Intergalactic Representatives are now open! (You must sign in with your StarMade Registry account to apply) Everyone is free to apply. Applications have no set date for closing at the moment, but will not be closed before the 19th of July 11:59 PM UTC. You can learn more about the council here and be sure to check out the applications news post for further details.


       Music Submissions Update

      In the v0.19282 news we announced we’re currently looking for someone to create SFX and soundtrack for StarMade. We’ve received an overwhelming number of emails, thanks must go out to everyone who has showed interest in the open role. We’ll still be accepting submissions till the 17th of July at 11:59 PM UTC. So, if you have the skills and are interested, be sure to send an email to!

       Other things

      Work on Fauna continues and focus on it increases with this update. There will also be some graphical upgrades to the block engine to make it more and more shiny (always in the philosophy: make the game fun first, then make it pretty)

       Bug Fixes


      As always a big thanks to all the devs and testers!


      • T394 unable to repair armor and ship HP for stations

      • T387 Moving CBS links and vanishing blocks leaving behind links

      • T388 kick option broken for factions

      • T383 EMP effect power drain is multiplied by penetration depth

      • T376 Indestructible Warhead

      • T375 LOCK_FACTION_SHIPS = false on client, overrides server setting

      • T368 hitting an unshielded entity with damage pulse crashes game

      • T367 group power penalty does not work for most weapons

      • T321 EMP effect doesn't drain all power

      • T316 power supply/drain computer expected firing direction reversed from ‘normal’

      • T310 Network data too large: priceUpdateBuffer, controllerKeyNameBuffer and controllerKeyBuffer

      • T308 escape options menu, controls sub menu doesn't scale

      • T307 Ships can't undock from Rail Basics via Logic in certain directions

      • T284 forcefield and scaffold wedges don’t have icons

      • T277 overheating does not disable AI

      • T275 Storage box filter menu bug.

      • T274 Item duplication issue

      • T270 /shop_restock_uid and /shop_restock_full_uid do not work on player shops.

      • T269 Replace block with Active Slot - Factories

      • T265 Undeathinator not functional / Spawn point save broken

      • T247 Strange behavior on turrets attached to rail rotators

      • T222 Can reset cool down of long cool down weapon systems

      • T189 Blueprints incorrectly save wireless logic links

      • T180 Renamed planet. Name doesn't show on the galaxy map

      • T165 Trading Guild Resupply Convoys will resupply player-owned shops.

      • T146 "Destroyed" ship core blocks weapon projectiles

      • T142 Placing a salvage beam computer on an Asteroid causes Nullpointer

      • T108 build mode camera issue when hitting escape

      • T98 missile damage radius on nearby entities significantly higher than direct impact

      • T95 missiles hit behind a wall

      • T74 creating a new universe sets all blueprints to enemy usable/others and owner to none

      • T65 Turrets get stuck in collisions

      • T44 Rail enhancers consume power but running out of power does not change anything

      • T33 moving through walls exploit

      • T26 stack split item loss

      • T20 Logic Rail Detection on docking doesn't trigger

      • T14 mouse sensitivity sync

      • T11 Enable/Disable all AI only works for last chain

      • T6 shield damage applied by shield sharing is multiplied per chain

      • T4 controller block system exploit




      Thanks for playing StarMade,

      - schema and the Schine Team

    • Jun19

      StarMade v0.19282: Putting more fun into battles. Also, boarding!

      Hello Players,

      #hotfix 0.19289:

      We forgot to announce that Kupu updated the Pixel texture pack, so check that out ;)

      • fixed beam aiming for AI turrets
      • fixed missing logic signal when docking to a rail block
      • fixed defeated ships not being salvageable when overheating
      • fixed defeated ships not giving errors
      • fixed several issues in Galaxy Map.

      this update is all about fixing a lot of things that still felt wrong in the game, and adding some more fundamental design changes, which will once again change a part of the game’s meta completely.

      We redesigned how ship battles work, adding a completely new system, called the “HP-System”. There are also a lot of other enhancements and fixes in the update.


      Here is a video that explains the new features:






      One of the biggest constructive criticisms we get for the game is that ship battles are basically a race on who can take out the core of the other ship. Which makes it a single focus point for everything. We long wanted to fix this problem, but first had to solve a lot of other problems along the way, ensuring that the new system is not more boring or broken than the old one, but intuitive and fun.


      A Hit Point System was the goal, but while it sounds easy on paper, it actually required a lot of problems to be solved for integration.

      Here are some of the problems that came up along the way:


      HP is always represented by two values: Maximal HP which indicates how many Hit Points an entity has, and current HP which indicates how many Hit Points the entity currently has left.

      The first problem was with determining how to keep track of HP.


      One idea that seems natural was to keep a copy of the ship in the status of full hp. This however would cause a lot of problems, as it would essentially double the size of ships in RAM, on disk, and cause problems managing it, as every change that modifies max HP would also modify that copy. All that for just two values seemed a very bad deal in cost-value.


      To combat that problem we are using a block count system, which has existed anyway. This however means that HP is based on the blocks, so if a block is damaged it still provides HP as long as it’s not destroyed.


      This means we can have a very small and fast way of keeping track of maxHP vs currentHP.


      Now, what is the max HP based on? If you would add a block to a ship, you would want your maximumHP to go up based on what you have placed. The same would have to happen if you removed a block.


      This all works fine, but what happens if you lose a block due to damage. Naturally you wouldn’t lose maximumHP, but only current HP of course. However, what happens then if you place a block? Would you get the HP back? Would that mean if you place another you would have more HP than maximumHP, would both HP and maximumHP go up? What is the actual ship’s state that the max HP is based on?


      • If your HP is at 100% adding and removing blocks will instantly update your HP keeping your HP at 100%.

      • If you are below 100% placing a block will NOT give you any HP, but still increase your maxHP.

      • If you are below 100% removing a block will deduct from your current HP, but not decrease your max HP. This means you will lose percentage when removing blocks from a damaged ship.

      • If you reach certain damage below 100% you will get negative effects like power/shield regeneration loss, loss of thrust, control, and at the end the “overheating” state. This means that you don’t have to kill every single block to kill a ship, but only a certain percentage.


      So, what can you do to get back to 100% once you have lost blocks? The solution was to add a mechanism called “Reboot”.

      A reboot takes your max HP to what the ship’s blocks currently represent, and also brings your current HP to 100%.

      You probably already saw the potential problem that brings: Just quickly reboot in battle and you will be at 100% again. However, rebooting actually takes time. The time is based on the damage taken, as well as the overall mass of the ship. You also can neither modify or fly a ship that is currently being rebooted, and power and shields go down to 0. It is also canceled if more damage is done. All these things make it relatively silly to try to reboot in combat.


      The most Hit Points are provided by system blocks like power, weapons, support, etc. So ships now have actual weakpoints.


      Furthermore on overheating you will no longer die instantly. You will get thrown out of your ship (it is now implemented that you automatically align to a ship when exiting it) and you can get to your escape pod, or stay and fend off a possible boarding party. You can’t enter your ship while it is overheating, and your only way to stop it is to reboot by pressing ‘r’ on the core. When a core is rebooting from overheating, you will not be able to enter it until it is done overheating.




      To further add more depth to ship battles, armor HP has also been introduced. Armor HP is the complement to System HP. The only blocks providing armor HP are actual armor blocks like hulls.


      Armor HP provides a damage reduction to all damage taken to an armor block. Upon damage, 50% (config value) of the damage is going to Armor HP and the other half will be the damage on the ship, as long as there are any Armor Hit Points left.


      Armor HP does NOT reset with a reboot, and can only be repaired at ships (or future ship yards) for credits. Ships can also reboot instantly at shops for credits.


      Losing armor HP will not give you any negative effects, but they are a vital resource to have on a good ship.


      Both System-HP and Armor-HP give a whole new feeling to ship battles, making them a lot more fun and exciting. All values of course are not final, because as always we took care that all essential values are available in the blockBehaviorConfig.xml. You can also go back to ship core based combat from the serverConfig if you would like to do so.


      Center of Mass


      Center of Mass is also no longer the core. It will now calculate the center of mass of a ship precisely on any mass placed anywhere.

      This doesn’t yet include docked entities, but it will soon. Also, in the future there will be options to have a more realistic physical model based on the shape of the ship in terms of being able to turn the ship.

      Implementation wise, the new Center of Mass system doesn’t cost any performance and is updated immediately (best to try it out on a planet)

      AI has also been updated to now aim at the Center of Mass which gives them a much better chance to hit something vital.

      You can also switch on an indicator for center of mass in the advanced build mode.


      Individual Block Mass


      With the new center of mass implementation it was also time to integrate individual block masses. This means, decorative elements will now barely add any mass to the ship, while armor and other blocks will add more than usual. Of course the center of mass will also reflect individual masses.


      Cannon and Beam damage rework


      Since now every block counts in terms of a ship taking damage, the missile seemed really superior as while it has similar total damage, it just takes out blocks a lot faster.


      Cannons now do damage to multiple blocks by default. The more damage a projectile has, the more blocks will be affected. Starting at 100 - 900 damage goes one block deeper per 100, from 1000, every 1000, and so forth.

      The damage is then distributed so that the first block hit will take the most and the last one the least damage. Accurate numbers can be looked up in the structure panel.


      A beam will do the exact damage no matter if the block got taken out or not (what in the past the piercing effect did), but it is stopped by any block that provides armor HP.

      The cannons has to take out a block to get to the next one, so if the damage of 1 block deep is not enough, the damage that would go in the second block will be used on the first until it is taken out. Any damage more that it took to take out a block is however still lost. Overall this still means a lot less damage is lost from cannons and more blocks are taken out per shot.


      All values are of course still not in a final state and are available in the config.


      New tools and boarding mechanics


      Two new tools have been added and are now available from the shop keeps. These keeps can now also be respawned in the middle of the glass area of Shops that had them.


      Grapple Beam


      This beam aligns you to an object on a very far range. It doesn’t automatically reel you in (yet), but you will have time to get to the object before the grapple expires. This makes it possible to get on objects from a good distance and board them.




      This useful tool does little damage but has a very distinct advantage: It bypasses armor and shields and throws the pilot out of the core if the core was brought down to 0 HP with it.

      This means you can use the torch to take over enemy ships. Be warned though: The pilot will receive a warning if a torch is being used on his ship.


      New Turret AI option


      Since with the new mechanics, you not only have to defend your ship from the outside, but also from the inside. This new AI option makes turrets only target astronauts.


      Ship info window now customizable


      It is now possible to resize and move the ship info while holding control in build mode. You can now also change the size of the text so it is much easier to read on higher resolutions. A general size option will also come later for all menus.

      Multiple weapon hot bars


      Another requested feature was the addition of more places to put weapons, especially with inner ship logic now being a thing, so we added 9 more hotbars. There are multiple ways to switch through them.


      • Pure mouse scroll: upon going to the end of a hotbar you will switch to the next one. This can be disabled in the ingame options.

      • Control+Mousewheel switches through hotbars

      • Control+number selects a hotbar directly (with ‘0’ being the 10th)


      Additional Chat Controls


      More chat options have been added to enhance the experience.


      • Client-side ability to ignore other players

      • Admin Mute Command


      They are usable via the right click context menu.


      New bug tracker


      We switched to a new bug tracker, which will make tracking a lot easier and streamlined with the development process.


      Colored Missile Trails


      The trailed of colored missiles are now also colored.


      Bug Fixes


      A lot has been done since the last update. Thanks to all the testers!

      One thing to note is that missile turrets have been upgraded to now being able to hit missiles a lot better. Turret rotation is now mass based, so smaller missile turrets are better in aiming and leading a target. Also the “aim at selected” AI option has been fixed.

      1. T255 can't load old templates
      2. T253 Old docking system makes astronauts stop moving
      3. T213 Numpad Enter causes newline in dialog, instead of "submitting" the value
      4. T196 Blocks dropped on death do not spawn properly
      5. T184 Diaply.Hide Help Screen typo
      6. T160 TAB + F8 nullpointer
      7. T155 texture faces are rotated
      8. T139 Damage Pulse modules listed as "beam unit" in Weapons menu
      9. T132 Hotbar indicators are missing
      10. T131 Selected waypoint sometimes wrong color after closing Navigation menu
      11. T130 Cannot access ship storage after removing named chest
      12. T127 "Killing" the ship core kicks pilot out
      13. T125 removing blocks as astronaut doesn't update ship or armor HP
      14. T123 Destroyed entity will cause you to go back to where you got in.
      15. T114 blocks discarded on deletion as astronaut when not enough inventory space
      16. T112 HP System - tiny ships and cores cannot be killed
      17. T110 shooting factioned planet with missiles crashes all players not in that sector
      18. T88 Area triggers are invisible
      19. T77 escape key does not close options menu
      20. T60 Inner Ship Remote labels don't work until weapons menu is opened
      21. T58 Joining a faction when not being in one causes all factionless players to recieve a "<playername> has left your faction" notice
      22. T49 Crash when holding weapon menu items in your cursor and opening inventory
      23. T48 rail basic acts like turret axis block
      24. T38 Faction systems do not work for all 12 planet segments
      25. T35 Scan history nullpointer
      26. T31 Oculus Rift DK2 Error
      27. T30 Anti-missile turrets ineffective
      28. T23 Station not saving
      29. T21 /explode_planet_sector explodes planets in all loaded sectors
      30. T15 Serverlist ping-check only trying TCP
      31. T13 Ship HP damaged systems does not change anything
      32. T12 Rail turret blueprint and nullpointer issue
      33. T10 Rail entities are not properly synced across clients
      34. T7 Ship always inherits faction after reloading sector
      35. T5 local rail blueprint errors with multiple chains
      36. T3 Require auth + not uplinked does not show a clear enough error-message on connecting



      We're currently looking to create SFX and a soundtrack for the game, if you're interested and have the skills, please send an email to with some samples and info about yourself. We're aiming for orchestral, classical and ambient elements, however any sample you think will impress us is fine.

      Coming up


      There is a completely new launcher nearly done. It will be built to make the installation of java for the game absolutely obsolete. It will also eliminate any java version problems, as well as add a lot of other features. It will also be the starting point for finally having an ingame menu, as well as ingame server switching (which are easy to do but held off for solving other problems around the game). Also, work on the creature system will now switch into full focus.


      Thanks for playing StarMade,

      - schema and the Schine Team

    • May10

      StarMade v0.19226 Rail System and more

      Hello and welcome to StarMade,

      EDIT: fixes in 0.19228: New blocks now have recipes. Lag should be much less for other players when someone mines (still will be optimized even more). Also:
      #RM1788 Cannot delete waypoints
      #RM1961 Fix hidden error message for faction names too short.
      #RM1127 Fix float rounding causing imprecise build helper values.
      #RM1692 Fix escape key not closing all windows, and sometimes closing parent window.
      #RM156 Fix build mode flashing issues
      #RM337 Fix outer radius size of atmosphere.
      #RM2039 planets and asteroids now have a default power capacity of 501

      Finally the time has come to release the much anticipated Rail System. This update contains a full redesign of the docking and turrets system, as well as a lot of new features. The new rail/docking system also solves a lot of old problems.  

      Furthermore, thanks to the new devs, a lot of work has been done to fix bugs. With them getting more and more familiar to the huge codebase, bugfixing and work on new features will continue to pick up the pace.

      Here is the news in youtube form:

      Here you will also find a list of tutorial youtube videos by bench:

      Rail System


      Here is a short overview of all the systems. They are explained in detail at the bottom.


      Complete Redesign

      Due to the lack of usability and dynamic in the old docking system, we have decided to completely redesign the system from the bottom up. The new design is a lot more suited for all the current demands, as well as things to come.


      The old system is still functional and no ships, blueprints, or other structures will break. The only restriction is that the docking beam is replaced with a pure activation beam, but if necessary the docking can be turned back on in the server config.


      Rail basics (docking)

      The new Magnet block can be docked to any Rail so long as the docking ship will not encounter a collision by doing so. This means no more docking zone boxes. Also, the orientation of your docked vessel can now be fully customized.


      Rail movement

      In addition to the removal of the docking zone, Rail blocks can be chained together in paths to allow for docked objects to move along them. The system is completely dynamic and allows for full control with the logic system.


      Rail rotation

      Rails are not the only new block allowing for docked objects and movement. Rotor blocks can be placed in your rail designs, or separately from them. The direction and angle of rotation can also be customized.


      Rail interaction

      Logic signal interactions and linked speed control blocks can dictate the direction, distance and speed of movement/rotation of the new Rail and Rotor blocks. Also, power and some of the shields are now shared between the rail-docks and the mothership, as well as every object in between.


      Rail logic

      The new rail blocks also come with complete integration with the the logic system in Starmade.  

      New Turret System

      Since the old docking also included the turret system, it now has also been redesigned. Turrets can now be divided into multiple rotational axes. In the most common example that would be a turret base that can rotate horizontally, and a turret top which would rotate vertically.


      New logic blocks

      Several new logic blocks were added to expand the functionality of the logic system with StarMade’s gameplay and to help integrate the new Rail system.  These new blocks include:


      • Button block (Provides a short (0.5 sec) ON signal then deactivates)
      • Flip-Flop block (Will only change its output when receiving an ON signal)
      • Wireless block (Allows logic systems to connect from ship to ship)
      • Remote block (Allows access to ship logic to be triggered from your action bar. Each block’s label can be changed by hitting ‘R’ on it)


      Bug fixes


      An issue has been resolved that caused lag spikes whenever a new player join on more populated server. Also the configuration for the hotbar is now set by ship. That means when you load a blueprint after setting it, you will get the exact hotbar you saved the blueprint with.

      This unfortunately had the effect that currently all hotbars reset once, but in the long run the new system is a lot more comfortable.


      The login procedure on servers that require authentication has been improved so that non-uplinked players now get an explanation as well as a prompt to enter their credentials or go to the registry to setup a new account. Also, the pesky error messages which blocked the real message have been gotten rid of.


      We fixed some bugs probably causing a lot of java version errors, making the code more strict to its version dependencies, so hopefully a lot less problems for new players will occur related to that.



      • Dis-Integrator do not work on asteroids
      • unable to track down path calculation failed
      • Map: Interface skips the sectors near a system border
      • Sniper rifle can zoom in the galaxy map
      • Admins getting revoked of admin after logging on/off of server
      • Logic on asteroid crashes the game (ClassCastException)
      • IndexOutOfBoundsException with some handheld weapons
      • Non-linear camera movement speed
      • Ending tutorial brings you back to global spawnpoint
      • Weapon menu not refreshing correctly
      • Tab + F10 - Can be used to see cloaked entities
      • Asteroid name mismatch (Zerkaner & Zercaner)
      • Large, nearly complete blueprint quotas round to 100%
      • NEW claimed systems do not get saved
      • Overdrive power consumption doesn't scale with ratio
      • 1th and 2th typos in Faction Rank
      • Renamed entities cannot be searched for
      • cloaked ships still have the "pilot" marker visible
      • Cannot enter build block on asteroid - prevent placing it, not entering it
      • docking module on asteroid crashes game on activation - prevent placing it, not activating it
      • Lag/Freeze on autocomplete
      • Tutorial fails to import sector correctly
      • Launcher's world manager has no scrollbar
      • /search only searching loaded entities



      • Gui Error - faction menus refresh too fast and endlessly


      (All bugs fixed caused with the rail system itself are unlisted)


      Rail Docking Explained


      This part will serve as an in-depth explanation and reference for all new systems.

      Rail docking basics


      The simplest kind of rail docking, which essentially replaces the old docking system, requires two blocks:

      • Rail Basic
      • Rail Docker

      Rail Basic

      The basic rail block serves as a docking access. You can dock to it using your rail docker. Placing only one basic rail serves as a static dock. Using more than one in a line produces a track a docked entity can run on.


      Rail Docker

      This block is needed on the entity that you want to dock to a Basic Rail block. Each placed Rail Docker contains a docking beam that can be assigned to your hotbar in the weapons panel of the ship. On firing, this block emits a docking beam. When that beam hits the Basic Rail Block of another entity, it will attempt to dock to that block.


      All rail blocks have a direction not only indicating the direction of the track, but also determining the docking orientation. On docking, the arrow of the docker as well as the direction of the Basic Rail, or any other dockable rail block, will be matched together like aligning the poles of two magnets so they will stick together.


      The only restriction that docking has is that the docked entity has to fit. This means no block of the docked entity may overlap with any block of the structure it wants to dock on, as well as any other already docked entities.


      Upon docking, a ship will also retrieve the faction ID of the structure it is docked to. This however now only lasts for the time it is docked and will revert to its old id when undocked. Also any ship docked to a rail block that has a public exception block next to it will keep its original faction while docked.


      The docker has one logic input and one output. Linking an activation block to the Docker will cause that docker to undock on activation. Placing an activation block next to the docker will cause it to activate on docking, and deactivate on undocking.


      Rail Movement

      As said, you are now able to make rail tracks by using the basic rails as well as the rail rotators explained below. Movement can be done in all three dimensions, and the rail docker will move on, as long as it has a tail track it can go to. It will stop if anything is in the way, or if there is no more rail to go onto. The direction of the rail to go onto can be different from the rail the block moves from as long as the primary face of the rail still touches the rail docker block.

      Rail Rotator

      There are two types of rail rotators. Clockwise and counterclockwise. Upon docking or moving onto this block, the docked entity will do a 90 degree turn, and then move on in the direction the rotator block is pointing if it can. The amount as well as the degree of the block can be dynamically modified with the logic system. Connect up to 9 activation blocks to any rotator block to control the amount of rotation. The amount of active activation blocks determine the block’s rotation. Each active block will add 45 degrees. If all 9 are active, the block will constantly rotate.


      Keep in mind, that to re engage a rotation, the logic system as explained below can be used.


      Rail manipulation

      Rail manipulation allows for full control of rails. It works like a template copy & paste system:

      All logic blocks that are placed next to a rail block have this rail block as an input to overwrite other rail blocks.

      That means if you place an activation block with a basic rail block pointing forward next to it, and then connect that activation block to one or more other rail blocks, upon activation, all connected blocks will be replaced with the rail block pointing forward. If more than one rail block is next to an activation block, the system will take one pretty much randomly, so that is not recommended. The same also works for rail rotator blocks. Using it on a rotator block also resets it so if there is an entity currently on the rotator block, it will then rotate again with the new parameters. Basic rail blocks and rail rotator blocks are also interchangeable, allowing for more control over how docked entity move and rotate on a single rail layout.


      Rail Logic

      Everything rails is controllable via the logic system. The rails have inputs which is the rail manipulation mentioned above, but they also have outputs. Every activation block that is next to a rail is activated when the rail docker block of the docked entity moves on it, and deactivated when it leaves it. The new button block also works in this way to detect a docked entity, sending out a 0.5 second on signal when the rail docker block passes over the rail next to it.


      Rail Speed Control

      The rail speed controller is another block that can be used to manipulate how fast a rail moves a docked entity. It can be connected to any amount of activation blocks. The ratio of active blocks to inactive blocks determines how fast the rail will move in percent of the maximal speed. So connecting 5 active and 5 inactive is 50% speed, the same as connecting 100 active and 100 inactive. The rails that should be under influence of the speed controller also have to be connected to it. Using shift-V on rails connects straight lines of rails quicky. Also, mass plays a role in rail speed. Should the mass get too high, the speed of the rail will get slowed down eventually to a minimum. To combat this speed decrease, rail mass enhancer blocks have to be placed to increase the load every rail on the ship can take. These blocks do cost a little power.


      Reasoning why rail controls work this way

      Some people might think: “Why can’t I just set the amount of rotation and speed in a menu?”. The reason is, that it would be then a static value, unless scripting is used. The rail system is fully dynamic and gives visual feedback. So you can change speed, rotation, and rail directions at any time manually or triggered by the logic system. Having it in a script would firstly be harder to understand and learn, secondly break with the game’s principle of using block architecture to solve problems, and lastly would be more a simulator or programming studio than a game.

      Allowing dynamic control through logic enables a lot more control of movement.

      Here’s one example of this as created by Crimson-Artist


      Rail Turret

      With the rail system, turrets have been completely redesigned, too. Over are the times where turrets would glitch into the ship, and would look awkward with limited options to manipulate and control them.

      The new system works with a 2-axis system. That means you can use at minimum one and at most 2 separate entities to form a turret.

      The first one is the turret basis. This one can only be moved horizontally (rotate left/right), probably best imagined like a turret works on a battleship. The second one is the turret’s barrel, that, again like on a battleship can move vertically (rotate up/down). The cool thing is, that if you enter the turret on the barrel, you will have control over both parts at the same time, which would allow for turrets with full 360% freedom in all directions. However be aware that the turrets also now check the collision with its mothership and other docked entities and will restrict its movement in doing so.

      The AI is fully integrated as well, and will work with almost any turret when placed on the barrel part. While in the turret its rotation can be reset by pressing ‘C’. You can also reset all turrets to the orientation they were in when you docked in the structure menu (under ‘rail system’).

      AI will also reset the turrets after a while of not fighting. Currently it’s instant movement on reset to avoid getting stuck, but in the future the reset will also be smooth.

      Please not there are still some minor issues with some turrets controlled by AI getting stuck. We are trying to fix that ASAP. Meanwhile please use teh reset feature.


      Power and Shield Sharing

      To provide even more freedom when designing rails, you can now use the full power provided by the mothership and any docked entity in between.

      The same goes for shields: If a turret or other dock gets hit, the chain to the mothership will check if any ship in between can take the hit. The requirement for overtaking a hit is that the ship must have above 50% of its shields and at least as many shields to take the full hit for the turret.



      Thats all for now,

      Thanks for playing StarMade,

      - schema and the Schine Team