Arrows will disappear 1 minute later when using:
/data merge entity @e[type=minecraft:arrow,limit=1,sort=nearest] {life:10}(on a fast clock and the same command but with life 11)
but still be in the game so you can still teleport to it or pick it up and relogging makes it reappear.
It is shot into a barrier block though the arrow will still disappear on other surfaces
Edit 14/5/17: Still not fixed, a light blue potion swirl particle effect will appear around arrows when the command is used.
Linked issues
Attachments
Comments
SunCat
Confirmed
This problem still exists right up into 1.9-pre2.
@unknown 1.9-pre2 is outdated, use pre4
wobst.michael
Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w42a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time.
I don't know for sure if the entity data command has changed at all but I used the same command
/entitydata @e[type=Arrow] {life:10}
^ In the same line not sure why it gets put down here
and the problem still exists
The arrows are still technically there in this version and do not completely dissapear
https://youtu.be/UMvAoorCSTA
Unlisted video of the arrows disappearing relogging and the arrows reappearing and then picking up the disappeared arrows.
1:02 is when the arrow disappears the first time
2:25 is when the arrows disappear after relog
Using the latest snapshot 16w42a
Confirmed for 1.13.1.
Updated command: /data merge entity @e[type=minecraft:arrow,limit=1,sort=nearest] {life:10}
[Mod] Neko
Forward-resolving to MC-71426, as that ticket has an assignee.
Thank you.
Why on earth are these mods so damn lazy lmao. this bug has existed since the release of nbt modification in 1.8 and yet mods come to this post every two years or so. "hurr durr does it still work" bruh I'm not testing this bug I haven't had mc installed for multiple years.
violine1101
Nobody did ask you for anything, this ticket has been resolved for over a year now.
way to prove my point lol. if you had taken 5 seconds to look the ticket still exists, just under a different person who reported it after me, and still under that ticket its the same "uuhhh is it updated guy who reported years ago"
Don't mark future versions as affected, because those are not released yet and can therefore still be changed. Mark the version you found the bug in instead. Also, moderator don't confirm everything. It's more a matter of whether they have time to try to confirm issues or need to keep up with new tickets.