I am unable to decide with this one, yes it can be useful, but I am not sure if using a separate raildocker is the best solution.

In T1681#65732, @Megacrafter127 wrote:

I am unable to decide with this one, yes it can be useful, but I am not sure if using a separate raildocker is the best solution.

i had a similar idea to this that would've involved using the weapons menu to slave docked entities but since Schema prefers block based solutions I figured that this might be the better alternative at least in concept, the details can be worked out later.

Yeah I would love to have a way to denote that certain docked entities are part of that ship and should be treated as such and not docked entities but I'm not sure having three different dockers is the solution.

Having 2 dockers would suffice (I think)
1 for normal
1 for decoration stuff on ships that would be part of the ship.

Mind you that when an entity is docked onto a turret using the latter docker, the docked entity should gain full stats of the turret, as if it is part of the turret. otherwise there might be an exploit to cover your turret with an entity to provide 100% mothership protection.

after reading the post again i figured that the three dockers is unnecessary. however the ship part one is something that could work. think of this as a partial suggestion.

Personally I would love to remove the core entirely from docked ship parts to denote that they are actually part of the main ship and not ever able to operate on their own. So in that end you would not need any additional docks, as turrets and ships can easily use the same dock and you denote a ship part from removing the core but that's really it's own suggestion and more or less off topic but I think I'll vote no.

I can neither come to a definitive yes or a definitive no, so I'll skip.

I say yes to either a special docker to become part of the mothership or a possibility to remove a core in total. the other turret dockers and such I disagree with.

In general possible,