In my 1.12.2 world, I had a command block system which is basically a move towards mechanism. It will make a huuuuuuge red tailed hawk (Armor stand wearing custom white carpet model riding a bat) come after and follow you when you are within 25 blocks. It works great in 1.12.2, and I just put all of the commands into a function and converted the function to 1.13.
there were no syntax errors, so I tried it out in the snapshot. It would almost work alright except for the fact that
data merge entity @e[distance=3..,limit=1,type=bat] {Rotation:[0.0f,0.0f],Motion:[-0.05982d,-0.1d,0.29397d]}
No longer works.. I either get the error message that the entity was not found, or that nothing changed while I knew the bat was within range.
I even tried a simple motion tag all by itself on a creeper and could not force it to move at all. Has the nbt for the Motion tag changed at all somewhere in these snapshots? or perhaps is this some sort of bug..
In my 1.12.2 world, I had a command block system which is basically a move towards mechanism. It will make a huuuuuuge red tailed hawk (Armor stand wearing custom white carpet model riding a bat) come after and follow you when you are within 25 blocks. It works great in 1.12.2, and I just put all of the commands into a function and converted the function to 1.13.
there were no syntax errors, so I tried it out in the snapshot. It would almost work alright except for the fact that
data merge entity @e[distance=3..,limit=1,type=bat] {Rotation:[0.0f,0.0f],Motion:[-0.05982d,-0.1d,0.29397d]}
No longer works.. I either get the error message that the entity was not found, or that nothing changed while I knew the bat was within range.
I even tried a simple motion tag all by itself on a creeper and could not force it to move at all. Has the nbt for the Motion tag changed at all somewhere in these snapshots? or perhaps is this some sort of bug..
Did you specify where that command is gonna be executed? If that command is in a function, I don't know if distance=3.. can detect it.
However, if this isn't the case, try to remove the d in the Motion tag. Cuz mine works fine.
Did you specify where that command is gonna be executed? If that command is in a function, I don't know if distance=3.. can detect it.
However, if this isn't the case, try to remove the d in the Motion tag. Cuz mine works fine.
The origin for functions will be (0,0,0), so "3.." will be based on that location.
The "d" is just an explicit declaration of a double and does not have bearing on success.
Otherwise the command works just fine for me. Not really sure what could be wrong other than the command is not actually running.
execute as @e[type=armor_stand,name=MoveTowards1,scores={Move=1}] at @s run execute as @a[limit=1,scores={Nearest=1}] run data merge entity @e[distance=3..,limit=1,type=bat] {Rotation:[0.0f,0.0f],Motion:[-0.05982d,-0.1d,0.29397d]}
I'll double check the rest of the function, to check for anything I may have overlooked, and I'll check to see if the armor stand is getting set to Move=1
execute as @e[type=armor_stand,name=MoveTowards1,scores={Move=1}] at @s run execute as @a[limit=1,scores={Nearest=1}] run data merge entity @e[distance=3..,limit=1,type=bat] {Rotation:[0.0f,0.0f],Motion:[-0.05982d,-0.1d,0.29397d]}
I'll double check the rest of the function, to check for anything I may have overlooked, and I'll check to see if the armor stand is getting set to Move=1
Got it.. Turns out that it actually wasn't executing at all because the hawk was being teleported to my location instead, because the functionality of /tp for the vertical guidance component has changed, therefore the hawk was always less than 3 away every time the code would have set Move to 1 on the closest armor_stand.
With a little bit of playing around with the Motion tag outside of the function, I realized that it works just the same, earlier, I thought it hadn't because I hadn't played around with sort=nearest,limit=1 yet.. didn't realize that limit=1 now just limits the target entities to only 1 selected based on sort.
With a little tweaking of sorting and tweaking the /tp so it's executed as the bat at the bat for bat, it's working as it should now Thank you all for your ideas!
In my 1.12.2 world, I had a command block system which is basically a move towards mechanism. It will make a huuuuuuge red tailed hawk (Armor stand wearing custom white carpet model riding a bat) come after and follow you when you are within 25 blocks. It works great in 1.12.2, and I just put all of the commands into a function and converted the function to 1.13.
there were no syntax errors, so I tried it out in the snapshot. It would almost work alright except for the fact that
data merge entity @e[distance=3..,limit=1,type=bat] {Rotation:[0.0f,0.0f],Motion:[-0.05982d,-0.1d,0.29397d]}No longer works.. I either get the error message that the entity was not found, or that nothing changed while I knew the bat was within range.
I even tried a simple motion tag all by itself on a creeper and could not force it to move at all. Has the nbt for the Motion tag changed at all somewhere in these snapshots? or perhaps is this some sort of bug..
Did you specify where that command is gonna be executed? If that command is in a function, I don't know if distance=3.. can detect it.
However, if this isn't the case, try to remove the d in the Motion tag. Cuz mine works fine.
-
View User Profile
-
View Posts
-
Send Message
Retired StaffThe origin for functions will be (0,0,0), so "3.." will be based on that location.
The "d" is just an explicit declaration of a double and does not have bearing on success.
Otherwise the command works just fine for me. Not really sure what could be wrong other than the command is not actually running.
Minecraft-things: http://skylinerw.com
More Minecraft-things: https://sourceblock.net
Guides for command-related features (eventually moving to Source Block): https://github.com/skylinerw/guides
I primarily hang out in the /r/MinecraftCommands discord, where there's a lot of people that help with commands: https://discord.gg/QAFXFtZ
Their corresponding subreddit: https://www.reddit.com/r/MinecraftCommands/
I think this is the case...
He forgot /execute at. Am I correct?
(PS: Gained knowledge. Thanks again.)
Well here's the full command
execute as @e[type=armor_stand,name=MoveTowards1,scores={Move=1}] at @s run execute as @a[limit=1,scores={Nearest=1}] run data merge entity @e[distance=3..,limit=1,type=bat] {Rotation:[0.0f,0.0f],Motion:[-0.05982d,-0.1d,0.29397d]}I'll double check the rest of the function, to check for anything I may have overlooked, and I'll check to see if the armor stand is getting set to Move=1
Got it.. Turns out that it actually wasn't executing at all because the hawk was being teleported to my location instead, because the functionality of /tp for the vertical guidance component has changed, therefore the hawk was always less than 3 away every time the code would have set Move to 1 on the closest armor_stand.
With a little bit of playing around with the Motion tag outside of the function, I realized that it works just the same, earlier, I thought it hadn't because I hadn't played around with sort=nearest,limit=1 yet.. didn't realize that limit=1 now just limits the target entities to only 1 selected based on sort.
With a little tweaking of sorting and tweaking the /tp so it's executed as the bat at the bat for bat, it's working as it should now Thank you all for your ideas!