/forceload cannot be run by functions or command blocks
The new `/forceload` command replaces and improves upon `/chunk` however it still cannot be run from functions or command blocks. Attempting to use this command inside a function will results in the attached parser error.
The assumption is that, because the command was rewritten to allow for relative coordinates, it should be runnable by functions and command blocks.
Tweet from [Mojang] Nathan Adams
So that only the server owner can use it. It could really bring any server to its knees very easily.
Created Issue:
/forceload cannot be run by functions or command blocks
Environment
The new `/forceload` command replaces and improves upon `/chunk` however it still cannot be run from functions or command blocks.
The assumption is that, because the command was rewritten to allow for relative coordinates, it should be runnable by functions and command blocks.
The new `/forceload` command replaces and improves upon `/chunk` however it still cannot be run from functions or command blocks.
The assumption is that, because the command was rewritten to allow for relative coordinates, it should be runnable by functions and command blocks.
The new `/forceload` command replaces and improves upon `/chunk` however it still cannot be run from functions or command blocks. Attempting to use this command inside a function will results in the attached parser error.
The assumption is that, because the command was rewritten to allow for relative coordinates, it should be runnable by functions and command blocks.
is duplicated by
The new `/forceload` command replaces and improves upon `/chunk` however it still cannot be run from functions or command blocks. Attempting to use this command inside a function will results in the attached parser error.
The assumption is that, because the command was rewritten to allow for relative coordinates, it should be runnable by functions and command blocks.
Tweet from [Mojang] Nathan Adams
The new `/forceload` command replaces and improves upon `/chunk` however it still cannot be run from functions or command blocks. Attempting to use this command inside a function will results in the attached parser error.
The assumption is that, because the command was rewritten to allow for relative coordinates, it should be runnable by functions and command blocks.
Tweet from [Mojang] Nathan Adams
The new `/forceload` command replaces and improves upon `/chunk` however it still cannot be run from functions or command blocks. Attempting to use this command inside a function will results in the attached parser error.
The assumption is that, because the command was rewritten to allow for relative coordinates, it should be runnable by functions and command blocks.
Tweet from [Mojang] Nathan Adams
So that only the server owner can use it. It could really bring any server to its knees very easily.
is duplicated by
relates to
Thank you for your report!
However, this issue is a Duplicate of MC-136112.
If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
According to MC-136112 it is intended that /forceload can not be run from functions or command blocks because of how much damage could be done with it.
However /forceload query only delivers information but can't be run either.
It could however be useful to at least know if a chunk is forceloaded or not, be it just for debugging reasons or to notify the server owner of missing forceloaded areas they need to re-add to keep a datapack working.
I would also argue that datapacks can only be installed by the server owner to begin with and that there is commands that can do worse damage than /forceload.
https://twitter.com/Dinnerbone/status/1030108572447858688?s=09
@tryashtar
it's also don't work in singleplayer
What if a map maker wants to, say, teleport a marker armor stand thousands of blocks away and perform actions through the armor stand later? The chunk will not be loaded any more and the armor stand cannot be accessed through execute. I don't see why there is a limitation to this. If the server owner decides to add some random data pack or give someone a command block, they WILL have consequences. One command doesn't make a difference.
"Put the server on its knees" can be any other console command.
Maybe prohibit execute?