From c21e8b4c181098b83eae0f00bf2478b159b72bef Mon Sep 17 00:00:00 2001 From: Chuck <33324927+ChuckBuilds@users.noreply.github.com> Date: Wed, 23 Sep 2026 10:50:53 -0400 Subject: [PATCH] docs: don't link SKIN_SYSTEM.md from the core-properties page #615 deletes SKIN_SYSTEM.md; with this link, whichever of the two merged second would break test_doc_links. The skin/skin_options entries go when #615 removes the keys. Co-Authored-By: Claude Opus 5.5 --- docs/PLUGIN_CONFIG_CORE_PROPERTIES.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/PLUGIN_CONFIG_CORE_PROPERTIES.md b/docs/PLUGIN_CONFIG_CORE_PROPERTIES.md index f887dff4..753c8430 100644 --- a/docs/PLUGIN_CONFIG_CORE_PROPERTIES.md +++ b/docs/PLUGIN_CONFIG_CORE_PROPERTIES.md @@ -28,9 +28,8 @@ is `CORE_PLUGIN_PROPERTIES` in `src/plugin_system/schema_manager.py`): 4. **`skin`** (string, object or null; no default) - Description: Visual skin id, or a per-mode mapping like `{"live": "my-skin"}` - Not an enum, so a stored value keeps validating after the skin is - uninstalled. Skins do not render with the current scoreboard plugins yet - (see [SKIN_SYSTEM.md](SKIN_SYSTEM.md)); the key is kept so stored values - keep loading and saving + uninstalled. Skins do not render with the current scoreboard plugins; + the key is kept so stored values keep loading and saving 5. **`skin_options`** (object; no default) - Description: Options passed through to the selected skin