I wanted to build a turret with part of it covered by the main hull in order for better survival- but at the same time i want it to have a mimited upwards turning, like the old turret docking system- however, this casued the turret to clip into the hull. For example:

Regular turret:

Where:
"<--->" is x axis

"|" is the middle parts

" ^ " is the y axis translation

 |
V

Typical turret:

      ^
|     |
|    V

<--->

But I wanted it to be partially protected by the main hull of my ship, so I tried reversing the order. The result is that the turret clips the hull and gets glitched and stuck.

Could you please either:

-Create a y-axis rail with limited rotation (e.g max angle 45 degrees up and down, like the old turret docking)

-Create a new "turret docker" block

-Enable settings for rails to limit rotation

-Fix the old turret docker

-Cause turrets to respect other blocks and collide

• Or something else.

Old dockers will be removed shortly, they cause a lot of issues to keep them working at all.

Movement limiting should be done by physical movement limits.
As a GUI movement limiter would require additional metadata and thus cause problems in logic integration or general performance.

However the specific case in this report is as far as I know not planned to be used at all.
Just sending in the report to have it in the system and get a development decision on it.

Was also report there I guess : T805 - Reverse Built Turret Bug

Logs:

I add my case: got my turret clipped in the hull + the 4th dimensional phenomenon (one turret but two locations in same time of the same entity)
I made a turret with long arms (each one length ~27 blocks),
It was ship + Y arm axis and then X arm axis turret.

If I exited the core of yellow arm and entered the ship core, there was nothing across my view.

But the real situation was the clipped one since the turret was totally stuck in this movement (it's means both yellow arm and violent arm was blocked).