Add support for custom games (shard 3): split game logic between standard and custom games - #3
Open
dejabot wants to merge 1 commit into
Open
Add support for custom games (shard 3): split game logic between standard and custom games#3dejabot wants to merge 1 commit into
dejabot wants to merge 1 commit into
Conversation
dejabot
force-pushed
the
custom-games-shard-3
branch
from
July 14, 2026 08:41
0054cdd to
4802d46
Compare
dejabot
force-pushed
the
custom-games-shard-2
branch
from
July 14, 2026 08:41
e10b967 to
4450a85
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds support for custom games. Builds off of
custom-games-shard-2This shard splits the game-specific logic between the standard FRC game and custom games using the
custombuild tag, and wires the custom side to the generated sources from shard 2. For each affected area — scoring (Score,ScoreSummary,RankingFields), rules, fouls, rankings reports, event settings, TBA/team-sign integrations, and the scoring-panel websocket handlers — the existing implementation is tagged !custom and a custom counterpart is added that consumes the generated types.This is where the generated code is actually used, so it builds on shard 2's generator: after
go generate ./..., the custom build compiles. The custom UI it dispatches to isn't generated until shard 4, so the feature only comes together end-to-end once that lands.