A setup like this:
Will not allow contact docking.
It works if 1 of the 2 sticks out. But if none stick out, you can't dock.
This works:
This doesn't:
A setup like this:
It works if 1 of the 2 sticks out. But if none stick out, you can't dock.
This works:
This doesn't:
<replace this line with the file content>
<replace this line with the file content>
-Validated- & -Confirmed-
It works if 1 of the 2 sticks out. But if none of the 2 stick out, you can't dock.
will have to wait a bit. flat surfaces can't produce a contact point. brute force testing close ones would be a performance hell
Alright, but let's put it in the delayed column instead of getting rid of the issue entirely
Perhaps they dont need to touch? When the "Distance to re-dock" code is implemented, a much lower ranged one could be used to snap rail dockers onto rails when they are 1-2 blocks away. That is unless the code for distance stems from the entity itself, and not where the dockers are placed
"brute force testing close ones would be a performance hell" AKA "We cannot detect dockable entities without considerable performance loss unless there is a defined point of contact to do checks on."
Might it be possible for Rail Dockers to project an extra 1/4 block slab collision area, or automatically place an invisible placeholder 1/4 slab on top of the docking surface? That would give you a nice, neat defined point of contact.