search

PaperMC / Paper

The most widely used, high performance Minecraft server that aims to fix gameplay and mechanics inconsistencies
https://papermc.io/
Other
10.04k stars 2.34k forks source link

the special rails are cut off when the sticky piston pulls back #4335

Closed graycat27 closed 4 years ago

graycat27 commented 4 years ago

What behaviour is expected:

when the sticky piston pulls back the special rails... (special rails ::= powered rail, detector rail, activator rail ) the rails are still connected with both beside.

photos taken in 1.16.3 vanilla STEP1 set rails on the blocks 2020-09-17_19 27 57 STEP2 push up the rail with the sticky piston 2020-09-17_19 28 07 STEP3 pull back the rail 2020-09-17_19 28 14 all rails are connected

What behavior is observed:

in paper server, at STEP3 written above, special rails placed beside are broken. 2020-09-17_19 29 38

Steps/models to reproduce:

see the 3steps written in "What behaviour is expected:"

Plugin list:

nothing

Paper version:

Paper version git-Paper-197 (MC: 1.16.3) (Implementing API version 1.16.3-R0.1-SNAPSHOT)

Anything else:

I tested the behavior in vanilla and also spigotgit-Spigot-2740d5a-890130b (MC: 1.16.3) (Implementing API version 1.16.3-R0.1-SNAPSHOT) Both seems works as I wrote in "is expected"

graycat27 commented 4 years ago

add information to reproduce

STEP1 first place blocks and rails as see.. image STEP2 push up image STEP3 pull back image the rails which placed besides are broken when the special rails pulling back.

aikar commented 4 years ago

Try enabling TNT duplication option in unsupported options in paper.yml It's possible this behavior is dependent on a piston bug.

graycat27 commented 4 years ago

thanks @aikar it worked well!

changed just this yml config, from false to true: settings: unsupported-settings: allow-piston-duplication: true then, all types of rails stay connected!

chickeneer commented 4 years ago

I have created a short video to demonstrate a vanilla rail mechanic which appears to be somewhat consistent with the behavior seen on Paper. https://youtu.be/VY_2PHm7k1c

To explain in my own words, it is consistent with vanilla for the ascending shaped rails to break when the supporting block is no longer there. This is shown in the first example. The second example demonstrates what happens when the supporting block becomes a rail and the upper one drops due to no lower supporting block - which looks like the paper mechanic.

My only point in bringing this up is to normalize that rails drop quite frequently (when sticky pistons are not involved). I think the vanilla mechanic shown is unexpected in context of all of the ways that rails break. Yes it is inconsistent with vanilla. But the behavior of rails are not generally friendly to reshaping... this issue would not keep me up at night.

I would either want Mojang to implement a fix to the piston duping issue so the Paper behavior is normal AND/OR Mojang to make rails less prone to breaking in general - just more reshaping. Both of which would be for Mojang to do, not Paper. (assuming it is not feasible to solve this issue in the blocking piston duplication patch).

aikar commented 4 years ago

what chicken said, but regardless, any unknown side effects of stuff depending on the dupe bug will be (Won't Fix) and people will have to decide if that behavior is worth letting people duplicate things.