[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.

Comments 13

[Mod] violine1101 2019-06-10T20:09:33Z

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.

tryashtar 2019-06-10T20:31:47Z

[media]

This was posted on the minecraftcommands discord. Good enough for WAI/FR?

CubeTheThird 2019-06-11T14:23:42Z

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?

FaRo1 2019-06-11T14:48:37Z

I don't understand what you mean. @s gets ignored completely, that's the point of this report.

CubeTheThird 2019-06-12T00:48:35Z

Ahh thanks for clearing that up. Wasn't written in this report.

3 more comments

user-a4a49 2020-06-12T08:28:23Z

Confirmed in 1.16 Pre-release 4.

SoloAlguien 2022-02-02T02:31:43Z

Can confirm in 1.18.1.

Richard G Way 2022-08-15T21:27:27Z

Can confirm in 1.19

user-f2760 2022-08-15T21:51:42Z

I think @unknown'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?

FaRo1 2022-08-15T22:21:54Z

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.