I see a lot of requests for multiple ship docking. I've thought long and hard about this, and one solution keeps standing out to me, not just for it's usefulness, but of it's ease of implementation, and minimal risk of destroying the balance of existing ships. Most importantly, no changes would need to made to existing ship classes, outside of compatibility with the existence of the new ship class, of coarse. I've decided to put this suggestion into one single comprehensive thread, instead of posting it in every relevant thread, to be lost on the umpteenth page. This ship class, as it's name implies, is a vessel almost exclusively for dropping gear and other vessels down to planets. It serves a distinct purpose from other ships. It's designed to be piloted down to a planet, then left until you are ready to leave the planet. It is not a combat vessel, though it should have turrets to defend itself from minor threats. The docking of this ship is most important! It can dock TO CV and BA. (Just like existing SV and HV class) And it can be docked BY SV and HV. (Just like existing CV class) It is VERY important that it can not be docked BY CV or other DVs, because then players can start "stacking" docks within docks within docks. This is one of the most important features of this vessel, since it not only severely limits abuse of awkward design out of the gate, but it also limits the testing and bug fixes for this new feature to mostly just this one new class! Limitations on the class would need to be in place to keep it as what it's suppose to be! If you just let CVs dock to CVs you will get some wacky results. This Drop Vessel should be given important limitations to restrict that wackiness away, without at all limiting what the CVs are and can do. (in fact, it gives the CV MORE freedom, by untethering it from planets) - Use of CV blocks, (or at least CV style) for simplicity sake. - Minimal Speed. Hardly any thruster upgrades. (It can't run away) - Reasonable size limitations. They shouldn't be near as unrestricted as CVs, but should be big enough to house multiple large HV/SVs or it's useless. - Long idle time. Minimal idle resource consumption. - Minimal weapons, but must have turrets. Perhaps remove manual front firing weapons altogether? As long as it has some turrets for self defense. Not the big, hugely damaging Plasma or Artillery turrets though. - No mining devices. This ship is a transport ship, not a utility one. - No garden plots. This was a hard decision, but it would be unbalancing to the CV/BA class! - No warping abilities! - Most other things like full sized constructors, fridges, healing stations, clone chambers, etc. ARE available! Finally, this ship would also allow the other classes to become more different and distinct! The CV could have more freedom to be a giant space fairing mothership class, the SV could keep it's strong focus on being like a fighter jet, Drop Vessels giving it a nice new slow target to hassle. HVs aren't really effected to much, besides being much easier to deploy onto the surface, which just makes them better at doing what they do. ------- I am a (small indie) game designer myself, and I've made balanced suggestions to developers that made it into games before, including 7 Days to Die! I have a pretty strong grasp of balance, and I've put a lot of thought into this. I think something exactly like this would be the quickest, easiest, most painless solution to a complicated problem that has the potential to be quite painful to both users and developers as it's implemented. As such, most of these suggestions are made for the developers themselves, and may not sound like the ultimate solution you as a player have been looking for, and I apologize if that's the case.