Merge branch 'master' into future
This commit is contained in:
commit
4db1c9540a
1 file changed
+3
-2
@@ -5826,7 +5826,7 @@ Function example:
|
||||
<pre>
|
||||
script run create_datapack('example',{'data/test/functions/talk.mcfunction'->'say 1\nsay 2'})
|
||||
</pre>
|
||||
### `enable_hidden_dimensions()`
|
||||
### `enable_hidden_dimensions()` (1.18.1 and lower)
|
||||
|
||||
The function reads current datapack settings detecting new dimensions defined by these datapacks that have not yet been added
|
||||
to the list of current dimensions and adds them so that they can be used and accessed right away. It doesn't matter how the
|
||||
@@ -5834,7 +5834,8 @@ datapacks have been added to the game, either with `create_datapack()` or manual
|
||||
`/datapack enable` on it. Returns the list of valid dimension names / identifiers that has been added in the process.
|
||||
|
||||
Fine print: The function should be
|
||||
considered experimental. There 'should not be' (famous last words) any side-effects if no worlds are added. Already connected
|
||||
considered experimental. For example: is not supposed to work at all in vanilla, and its doing exactly that in 1.18.2+.
|
||||
There 'should not be' (famous last words) any side-effects if no worlds are added. Already connected
|
||||
clients will not see suggestions for commands that use dimensions `/execute in <dim>` (vanilla client limitation)
|
||||
but all commands should work just fine with
|
||||
the new dimensions. Existing worlds that have gotten modified settings by the datapacks will not be reloaded or replaced.
|
||||
|
||||
Reference in new issue
Block a user