Automate live tournament flow and remove manual creation#7
Merged
Conversation
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.
This PR makes tournaments fully operator-driven and removes manual creation paths from the UI. PokerVault now tracks a single active tournament, restricts createTournament to the operator, and requires at least 4 players to start. The game runner now auto-creates open tables with default 0.1 buy-in and 6 seats, waits for entries, and starts games only after the minimum player threshold is met. Frontend routing/navigation was simplified to a single live flow (including redirecting /tournaments/create), with live feed polling reduced to 1s and updated deployed contract metadata.