Merge docs for 'player() returns consistently on player scoped apps.'

This commit is contained in:
github-actions[bot] committed 2020-12-23 15:56:27 +00:00
1 parent 6225e5f632
commit f0a52fc751
1 file changed
+4 -1
+4 -1
View File
@@ -2893,7 +2893,10 @@ In this case - entities would need to be re-fetched, or the code should account
### `player(), player(type), player(name)` ### `player(), player(type), player(name)`
With no arguments, it returns the calling player or the player closest to the caller. Note that the main context With no arguments, it returns the calling player or the player closest to the caller.
For player-scoped apps (which is a default) its always the owning player or `null` if it not present even if some code
still runs in their name.
Note that the main context
will receive `p` variable pointing to this player. With `type` or `name` specified, it will try first to match a type, will receive `p` variable pointing to this player. With `type` or `name` specified, it will try first to match a type,
returning a list of players matching a type, and if this fails, will assume its player name query retuning player with returning a list of players matching a type, and if this fails, will assume its player name query retuning player with
that name, or `null` if no player was found. With `'all'`, list of all players in the game, in all dimensions, so end that name, or `null` if no player was found. With `'all'`, list of all players in the game, in all dimensions, so end