The currently biggest downside with /schedule is that schedule command always run as the console. IF you want to execute from a certain location or at/as a certain entity but not in the same gametick, you can only do so with significant overhead and continuously reading and writing to storage, tagging, etc.
For most application, where you just want to delay and spread out the executions of commands, but in the same "scope" this is not feasible.
I propose and optional "inherit" parameter to /schedule that just passes on the current scope of the schedule command (executor, location, rotation, etc) to the function that is being scheduled.
Example:
#this would run as the console in the next tick.
/execute as lerokko run schedule test:test 1t replace
#this would run as the player lerokko in the next tick cause the /schedule command was explicitly set to be ran as lerokko.
/execute as lerokko run schedule test:test 1t replace inherit
Please sign in to leave a comment.
1 Comments