MC-154325/schedule runs as server
Even when using /execute as, a function that is run with /schedule always runs as "Server", not as the real executioner.
MC-146603 was closed as "Invalid", but it was never mentioned that scheduled functions are supposed to be executed as the server (blog post here). This is inconsistent with every other command.
LowCreated Issue:
/schedule runs as server
Even when using /execute as, a function that is run with /schedule always runs as "Server", not as the real executioner.
MC-146603was closed as "Invalid", but it was never mentioned that scheduled functions are supposed to be executed as the server (blog post here). This is inconsistent with every other command.
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
Normal![[Mod] NeunEinser](../../../data/avatars/users/39263.png){kind=small}
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Helper] Misode](../../../data/avatars/users/93314.png){kind=small}
![[Mod] CubeTheThird](../../../data/assets/gravatar/cubethethird.jpeg){kind=small}
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
/schedule loses ALL command context see MC-154325; it's the server running the function when it is time; a server running a function runs as nothing facing as/at worldspawn.
Mojang has stated it found no good way to serialize the command context, thus just dropping it.
Invalid as /function (which you reported as not behaving correctly) works fine.
I definitely remember that a dev has mentioned that commands scheduled by /schedule need to run as the server because of technical reasons. However, I don't remember anymore where that was.
This was posted on the minecraftcommands discord. Good enough for WAI/FR?
Out of curiosity, if schedule were called using @s within the context of an execute command, does that get resolved when calling schedule, or when the function gets run?
I don't understand what you mean. @s gets ignored completely, that's the point of this report.
Ahh thanks for clearing that up. Wasn't written in this report.
Confirmed for 1.14.3
Confirmed for 20w21a
Confirmed in 1.16 Pre-release 3.
Confirmed in 1.16 Pre-release 4.
Can confirm in 1.18.1.
Can confirm in 1.19
I think [Mojang] Bartosz Bok's discord comment, as shown by |~tryashtar], is WAI/WF source enough. In fact, it directly states it doesn' t keep it because it was too hard to serialize. Why is/was this not resolved as such? I also recon this would be extremely problematic if "@s" were to vanish (IE unloaded, or player left server); how'd that be handled intuitively?
Just being hard doesn't mean that it won't be done. And it surely didn't make it WAI. You could maybe interpret WF into it, but there's already a Mojang priority on this, so it was triaged and not closed then, so it should stay open.