From ee971f57bdf34052a0aef9d653cd3999efe96eb6 Mon Sep 17 00:00:00 2001 From: WarmUpTill Date: Wed, 14 Aug 2024 22:06:32 +0200 Subject: [PATCH] Updated Scripting (markdown) --- Scripting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Scripting.md b/Scripting.md index 7410946..7b2f45e 100644 --- a/Scripting.md +++ b/Scripting.md @@ -82,7 +82,7 @@ As you can see the frequency at which this condition returns true depends on the Registering an action would be identical to the example above, but instead of passing a function which returns a boolean value to `advss_register_condition`, you would pass a function performing your desired actions to `advss_register_action`. -The boilerplate code mentioned above can be found [here](https://github.com/WarmUpTill/SceneSwitcher/blob/master/scripting/examples.py#L115-L305). +The boilerplate code mentioned above can be found here for [Python](https://github.com/WarmUpTill/SceneSwitcher/blob/master/scripting/examples.py#L115-L305) and [Lua](https://github.com/WarmUpTill/SceneSwitcher/blob/master/scripting/examples.lua#L111-L283). Usually you can just copy it directly into your script without any modifications. Note that if you should choose to unload the scripts, which define custom macro segments, while custom macro segments are still in use, the plugin will no longer be able to query settings of those custom macro segments.