Skip to content

Commit

Permalink
Better wording regarding enabling an disabling restrictions
Browse files Browse the repository at this point in the history
  • Loading branch information
fwsGonzo committed Oct 16, 2024
1 parent 5f7c682 commit 2fefce5
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/godot/restrictions.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ When passing objects as arguments to function calls into the Sandbox, those obje

:::

Setting the property to true will set each Callable to a function that returns false, but only for the callables that haven't been set before. Setting the property to false will set all callables to an empty (invalid) callable, disabling restrictions.
The act of setting the `restrictions` property to true will set each Callable (mentioned below) to a function that always returns false, resulting in every interaction with anything external failing. However, it only sets the callables that haven't been set before. In other words, if you have set a custom callable, it will not get overwritten. Setting the property to false will set all callables to an empty (invalid) callable, disabling restrictions. This currently includes your own set callables.

## Fine-tuning restrictions

Expand Down

0 comments on commit 2fefce5

Please sign in to comment.