ActualHorse/CarmenSandiego
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

Host card causes an exception on non-owner clients during round 2 gameplay #72

New Issue
Closed
opened 2026-04-17 14:46:08 -04:00 by ActualHorse · 2 comments
ActualHorse commented 2026-04-17 14:46:08 -04:00
Owner
Copy Link

The issue appears to stem from HostCardRecoverTheLootInterface.ActivateAllPanelButtons(). Something about it can't handle being called on clients that aren't actively operating the game. Look into this one later.

The issue appears to stem from `HostCardRecoverTheLootInterface.ActivateAllPanelButtons()`. Something about it can't handle being called on clients that aren't actively operating the game. Look into this one later.
ActualHorse added this to the v0.5 milestone 2026-04-17 14:46:08 -04:00
ActualHorse added the
Priority
A
 label 2026-04-17 14:46:08 -04:00
ActualHorse self-assigned this 2026-04-17 14:46:08 -04:00
ActualHorse added the
Type
Bug
 label 2026-04-17 14:58:45 -04:00
ActualHorse pinned this 2026-04-17 14:59:10 -04:00
ActualHorse commented 2026-04-17 15:51:23 -04:00
Author
Owner
Copy Link

This appears to happen because the responses to the location board panel reveals runs on all clients, and tries to access things that are only valid on the host's end. Figure out how to make this work without causing this issue. Perhaps a check to make sure the host is the owner of the GameManagerRound2 object before executing any functions.

This appears to happen because the responses to the location board panel reveals runs on all clients, and tries to access things that are only valid on the host's end. Figure out how to make this work without causing this issue. Perhaps a check to make sure the host is the owner of the GameManagerRound2 object before executing any functions.
ActualHorse commented 2026-04-21 23:06:37 -04:00
Author
Owner
Copy Link

This seems to be fixed now, and doing so made a few other bugs go away, too. So that's neat.

This seems to be fixed now, and doing so made a few other bugs go away, too. So that's neat.
ActualHorse unpinned this 2026-04-21 23:08:07 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Priority
A
The priority is critical
Priority
B
The priority is high
Priority
C
The priority is medium
Priority
D
The priority is low
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Type
Breaking
Breaking change that won't be backward compatible
Type
Bug
Something is not working
Type
Documentation
Documentation changes
Type
Enhancement
Improve existing functionality
Type
Feature
New functionality
Type
Security
This is security issue
Type
Testing
Issue or pull request related to testing
No Label
Priority
A
Type
Bug
Milestone
No items
No Milestone v0.5
Projects
Clear projects
No project
Assignees
Clear assignees
ActualHorse
No Assignees ActualHorse
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ActualHorse/CarmenSandiego#72
No description provided.
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?