From f71e02e7ed96739eab3d2ddfc911c8503ee44a08 Mon Sep 17 00:00:00 2001 From: Chuck <33324927+ChuckBuilds@users.noreply.github.com> Date: Wed, 30 Sep 2026 21:13:00 -0400 Subject: [PATCH] docs(common): sports_plugin_host keeps the plugins' note on why Vegas weighting exists The scoreboards' manager.py introduced get_vegas_priority_weight with a section comment; the adoption drops it with the copies, so it moves here. Co-Authored-By: Claude Opus 5.5 --- src/common/sports_plugin_host.py | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/common/sports_plugin_host.py b/src/common/sports_plugin_host.py index ed5a487c..bccc024e 100644 --- a/src/common/sports_plugin_host.py +++ b/src/common/sports_plugin_host.py @@ -129,6 +129,13 @@ class SportsPluginHostMixin: thread.start() # ---- Vegas weighting: is a favourite playing? ----------------------- + # + # With display.vegas_scroll.live_in_ticker set, the marquee keeps running + # through a live game and plugins can claim more than one slot per cycle. + # The core already gives any plugin with live content `live_weight`; this + # exists for the one thing the core cannot work out for itself, which is + # *whose* game is live. See PLUGIN_API_REFERENCE, "Vegas scroll hooks", + # and ADVANCED_FEATURES, "Live content in the ticker". def get_vegas_priority_weight(self): """Slots per Vegas cycle: more when a favorite team is playing.