Arrows shot by a player on our realms server can sometimes lose their ownship when the owner disconnects from the server.
I’m having a hard time nailing down exactly what’s going wrong and how to reproduce it easily. I have a machine that uses the fact that arrows knock wind charges in the direction you’re looking at to remotely activate redstone, however when I log out and in again with another player online the machines break and no longer knock the wind charges where I’m looking, which I assume is an arrow ownership problem. The machines stay broken until I shoot a new arrow into them, and then they work again until I log out again.
I’ve tried to test this out with a single arrow shooting up and down on a slime block and can’t get the same results consistantly, It’s difficult to reproduce without making the entire redstone machine, but the machines are consistantly broken when I log out with another player on the server, and they worked flawlessly in 1.21.5. Haven’t had any of these issues on singleplayer. I’m sorry I don’t have any more clear steps to reproduce this, I can link the video to the machine I’m using if that would help.
It’s a bummer that these machines are broken, I built a lot of infrastructure around them so it would be great if this arrow ownership problem could get patched.
Thank you!
Linked issues
relates to 1
Comments 3
This bug is new in 1.21.6… in the versions before, it was only present in other servertypes like papermc/purpur
This is a “bug” due to the arrow checking for its owner if it hits something or it gets deflected. If the Owner is offline, while the arrow is deflected e.g. by a player holding a shield, or the arrow is hitting the slime block (and afterwards getting bumped up again), minecraft checks for .getOwner(). But as the Owner is offline, the Owner of the arrow gets .setOwner(null)