Skip to content

Fixed the cabinets not opening interactive session issue#145

Open
coderranger2 wants to merge 1 commit into
GDSC-RCCIIT:mainfrom
coderranger2:stija/gamesessionquery
Open

Fixed the cabinets not opening interactive session issue#145
coderranger2 wants to merge 1 commit into
GDSC-RCCIIT:mainfrom
coderranger2:stija/gamesessionquery

Conversation

@coderranger2
Copy link
Copy Markdown
Contributor

Closes #105

Bug found

Clicking Play on arcade cabinets only updated coins/xp and showed a placeholder state. No interactive game session opened for the selected cabinet.

Root cause

  1. playCard() only handled rewards and score updates.
  2. No active game state was being stored, so the UI never rendered a playable session component.

Fix applied

  1. Added activeGame state and updated cabinet click handlers to pass the full card object instead of only reward values.
  2. Updated playCard() to:
  • set active game
  • start game session
  • switch to mini games view
  1. Added conditional rendering for interactive gameplay screen using selected cabinet data.

Testing done

  1. Reproduced the bug before applying fix
  2. Confirmed fix resolves the issue
  3. Verified existing features are not broken
  4. Tested on Chrome 147/1920 x 1080 desktop

Screenshots (before / after)

  • Before:
    On clicking play on neon runner displays the stale state:
image

After:
On clicking play on neon runner displays the interactive game-playing screen:
image

@coderranger2
Copy link
Copy Markdown
Contributor Author

Would appreciate some insights on how to fix the "This branch has conflicts that must be resolved." issue here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Interaction Blockers: Input Layer Lock and Double-Click Launch Requirement

1 participant