From 10952ae47bab6ba752bb4d6f404e596860c38562 Mon Sep 17 00:00:00 2001 From: Griatch Date: Sun, 11 Sep 2022 11:44:47 +0200 Subject: [PATCH] Clarifying the search lock defaults to True --- docs/source/Components/Locks.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/source/Components/Locks.md b/docs/source/Components/Locks.md index 1981d63f80..42728c7e91 100644 --- a/docs/source/Components/Locks.md +++ b/docs/source/Components/Locks.md @@ -112,7 +112,8 @@ something like `call:false()`. - `search` - this controls if the object can be found with the `DefaultObject.search` method (usually referred to with `caller.search` in Commands). This is how to create entirely 'undetectable' in-game objects. - Note that if you are aiming to make some permanently invisible game system, + If not setting this lock excplicitly, all objects are assumed searchable. + Note that if you are aiming to make some _permanently invisible game system, using a [Script](Scripts) is a better bet. - `get`- who may pick up the object and carry it around. - `puppet` - who may "become" this object and control it as their "character".