David Kleiner

Never mind, they decided to start working properly as soon as I reported the bug. How does that even work!?

It stopped acting like that in 1.13-pre5 (except for when I'm lagging or something like that), so I think this can be classified as "Solved". Thanks for the help <3 😃

Thanks 😃 I think this can be classified as solved now

Oh. So how do I target a random non-player entity?

I understand. Thank you

I've checked a little, changed the commands, all that. I think the @r selector doesn't work. I have this command:

/execute as @r[name=LuckyBlockSelector] run execute at @s run tp ~ ~10 ~

That does nothing. And I'm pretty sure it's supposed to work (please tell me if it's not like last time). That does work, although it always targets the same one:

/execute as @e[name=LuckyBlockSelector,limit=1] run execute at @s run tp @s ~ ~10 ~

So... yeah. What do I do?

(BTW the output is "Added 2 members to team [LuckyBlock]. If I do "/team join LuckyBlock @r[name=LuckyBlockSelector]", the output is "No entity was found")

No output. I have the game rule SendCommandFeedback set on false. I'll go check it (although I checked, and the entity's name is LuckyBlockSelector).

I'm not sure I understand. This is not a crash bug.