Absent Future
Assigned
Reported
Comments
Alright I'll try, but I honestly have no idea why it happens, so reproducing it will be quite... Difficult. I do have proof that it happens though.
This has happened to me several times so I can confirm. It has only affected certain worlds though and it doesn't happen until the world has been played on for a while (so I assume, but not sure). Should I create a new ticket, or how would I add pics and such? I'm going to record a video too. As of now I have no idea how to reproduce it, but testing some things it certainly looks wrong.
Well sort of the same. It might be. However with this bug it's the fact that you become completely untrackable when using @e or @r[type=Player]. The bug doesn't occur until you update the player after you've entered unloaded chunks.
And in this case the update requires the player to move at least 100 blocks. If they move 50~ blocks the player will still be trackable due to not being updated. Here's a vid: https://www.youtube.com/watch?v=x0JeQQ0X2Mw&feature=youtu.be I use an objective here but the same happens regardless of objective, tag or any of that. Then there's the fact that you can apply eg: speed, but it doesn't actually modify the player in any way.
So method 1 has a decent work around, but this doesn't seem to work for me when trying method 2.
Actually, if I move in any direction whilst in the air, but keep on holding it until 2~ blocks above the ground it'll trigger anyway because it appears that the move score will have gone past the 'min=X' score, eg: XXX_min=5 as you provided. Can you reproduce? Just move to a high height so that you have enough time to move in the air. Then let go a few blocks before landing. If it's the issue I'm having it'll most likely exceed a score of 5.
I apologize if this is unclear.
Right, now I remeber I did do that a while ago. Thanks for reminding me! Seriously though it's a bit annoying (the bug).
So do you have any sort of work arounds or other systems for this? If so would you please let me know?
Ok. It seems to be a bug with the mod Optifine, so I would assume this can be closed.