Comments 7
This issue has been temporarily closed as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Sorry, forgot to check back on this. What I'm referring to is that piston heads have a hitbox that slightly protrudes past a 1x1 block space (to connect with the piston base) which in current stable versions will remain while the piston retracts, clipping through the back of the block, which can push entities back from the piston.
You can test this by pushing yourself up against the back of a sideways piston with a redstone block above and then removing the redstone block - in stable versions, you'll be pushed backwards slightly, whereas in snapshots you won't.
That behaviour was noted since 1.11.2 in bugpost MC-114304 "Retracting piston pushes entities standing behind the back of it", which was resolved as fixed for 20w06a (fix of MC-93631), it seems.
Up to Mojang, of course, to resolve this bugpost, but I'll take the opportunity to say a few things, as I really liked the way you wrote up this bugpost.
Personally, I doubt they (always) reimplement what they apparently considered a bug.
Some previous piston behaviour seems to be retained/reimplemented in some occasions, thus it does indeed not hurt to ask kindly though, like you did 🙂
That doesn't necessarily mean that the reimplemented behaviour will be here to stay forever (would be over and over maintained to be kept, such as e.g. currently QC and block dropping), but that's up to Mojang to be (hopefully) communicated towards the tech community.
Years ago, some Devs said it isn't easy to add tech features due to the state of the code, where stuff breaks easily. ("I'd love to add many features, but the code crumbles underneath my fingers")
What I take from this is, as soon as the code is sufficiently "sane", Mojang might be finally able to add more features without breaking or influencing the whole Redstone system, as so many components interact with each other, for better or worse; maybe even things which once where bugs, but then would be a properly coded feature. Not necessarily in the same way, e.g. not reintroducing piston backs pushing entities, but if it's for you about specifically aligning entities, maybe that might be part of another tech component.
If you could think up a component that does some helpful actions like, amongst others, aligning entities and is, preferrably, not solely a thing for the advanced tech community (considering it's fairly small versus over 100 million players worldwide, and Mojang tries to have as much parity as possible), then propose it to Mojang.
Sorry for long text, just wanted to express that we don't know the future of TechMC yet, and that there is always hope, as long as conversation remains civil and constructive.
Have a good Sunday.
Thanks for the explanation. I agree with what @unknown said.
If you would highlight some things in this ticket that are no longer possible because this behaviour was removed and would explain why it would be worthwhile to keep, it might convince the devs more to reintroduce this behaviour if possible.
Edit: To add to what was said, I'll keep this open because MC-114304 was not resolved by a dev and might (or might not) have been an unintended side effect. If it would have been intentionally closed by a dev, this ticket would be invalid.
Thank you very much @unknown 🙂
I thought at first it was some kind of side effect of fixing piston warping ("translocation"), but I checked the according fix versions as well as first occurrence for related bugposts to this one here, and it just does not line up perfectly. That being said, pistons were changed some, also during the 1.11 snapshots, so who knows.
Thank you again for keeping it open, as no Dev has resolved the mentioned other bugpost.
Could you provide some more information about what the actual issue is? From your report I don't know what you're talking about and why it is an issue.