froxxxy/bscscore
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

14.1 Game: Phase 1 - Foundation and Turn-Based Input #18

New Issue
Closed
opened 2025-06-20 14:25:50 +02:00 by cursor · 2 comments
cursor commented 2025-06-20 14:25:50 +02:00
Collaborator
Copy Link

This is the first phase for the 14.1 Endless implementation.

Parent Issue: #15

Tasks

  • Clone Existing Game View: Start by cloning the UI from an existing game mode to ensure consistency.
  • Player Management: The existing player name and target score input fields will be used.
  • Turn-Based Input:
    • Instead of adding points per ball, create an input field for the current player to enter the number of balls remaining on the table at the end of their turn.
    • The app will calculate the score for that turn based on the difference from the previous state (15 balls or the last player's remaining ball count).
  • Turn Indicator: A clear visual indicator for whose turn it is.

Acceptance Criteria

  • A new game view for "14.1 Endless" can be created from the main menu.
  • It uses the same player selection and target score components as other games.
  • The main game screen clearly shows which player is active.
  • An input field is available for the active player to enter the number of balls left on the table.
  • A "Submit Turn" or similar button calculates the score for that turn, updates the player's total score, and switches the turn to the opponent.
This is the first phase for the 14.1 Endless implementation. **Parent Issue:** #15 ### Tasks - **Clone Existing Game View**: Start by cloning the UI from an existing game mode to ensure consistency. - **Player Management**: The existing player name and target score input fields will be used. - **Turn-Based Input**: - Instead of adding points per ball, create an input field for the current player to enter the number of balls *remaining* on the table at the end of their turn. - The app will calculate the score for that turn based on the difference from the previous state (15 balls or the last player's remaining ball count). - **Turn Indicator**: A clear visual indicator for whose turn it is. ### Acceptance Criteria - A new game view for "14.1 Endless" can be created from the main menu. - It uses the same player selection and target score components as other games. - The main game screen clearly shows which player is active. - An input field is available for the active player to enter the number of balls left on the table. - A "Submit Turn" or similar button calculates the score for that turn, updates the player's total score, and switches the turn to the opponent.
froxxxy commented 2025-06-20 14:42:38 +02:00
Owner
Copy Link
  • there is already a game creation mode for all games available, in which 14/1 can also be selected. use this.
  • before the game starts there should be a modal asking "Welcher Spieler fängt an?" to determine first active player.
- there is already a game creation mode for all games available, in which 14/1 can also be selected. use this. - before the game starts there should be a modal asking "Welcher Spieler fängt an?" to determine first active player.
cursor commented 2025-06-20 14:43:44 +02:00
Author
Collaborator
Copy Link

Based on your feedback, here is the updated plan for this issue:

Updated Plan for Phase 1 (Issue #18)

  • Integrate into Existing Game Creation:
    • Locate the existing game creation flow where "14.1 Endless" is already an option.
    • Ensure selecting "14.1 Endless" proceeds to the new game screen logic.
  • Starting Player Modal:
    • Before the game view loads, implement a modal that asks: "Welcher Spieler fängt an?" (Which player starts?).
    • The modal should contain buttons for "Player 1" and "Player 2".
    • The selection will set the first active player for the game.
  • Game View:
    • The game view itself should load after the starting player is selected.
    • It must have a clear indicator for the active player.
    • It needs an input field for the active player to enter the number of balls remaining on the table.
    • A "Submit Turn" button will calculate the score and switch turns.
Based on your feedback, here is the updated plan for this issue: ### Updated Plan for Phase 1 (Issue #18) - **Integrate into Existing Game Creation**: - Locate the existing game creation flow where "14.1 Endless" is already an option. - Ensure selecting "14.1 Endless" proceeds to the new game screen logic. - **Starting Player Modal**: - Before the game view loads, implement a modal that asks: "Welcher Spieler fängt an?" (Which player starts?). - The modal should contain buttons for "Player 1" and "Player 2". - The selection will set the first active player for the game. - **Game View**: - The game view itself should load *after* the starting player is selected. - It must have a clear indicator for the active player. - It needs an input field for the active player to enter the number of balls remaining on the table. - A "Submit Turn" button will calculate the score and switch turns.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
cursor froxxxy
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: froxxxy/bscscore#18
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?