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

Final round marker seems to check for non-collisions too quickly on occasion. #23

New Issue
Closed
opened 2025-07-20 20:37:51 -04:00 by ActualHorse · 1 comment
ActualHorse commented 2025-07-20 20:37:51 -04:00
Owner
Copy Link

I'm too excited to check this further right now because the bugs with the final round syncing are finally resolved to my satisfaction, but one other bug appears to have shown itself. If a marker detects no collisions, it will occasionally fire the event too quickly, rather than waiting the designated eight ticks.

This could possibly be dependent on the number of synced players, which would be a very annoying bug, but is theoretically possible, I guess.

I'm too excited to check this further right now because the bugs with the final round syncing are finally resolved to my satisfaction, but one other bug appears to have shown itself. If a marker detects no collisions, it will occasionally fire the event too quickly, rather than waiting the designated eight ticks. This could possibly be dependent on the number of synced players, which would be a very annoying bug, but is theoretically possible, I guess.
ActualHorse added this to the v0.5 milestone 2025-07-20 20:37:51 -04:00
ActualHorse added the
Type
Bug
Priority
A
 labels 2025-07-20 20:37:51 -04:00
ActualHorse self-assigned this 2025-07-20 20:37:51 -04:00
ActualHorse commented 2025-07-20 21:40:53 -04:00
Author
Owner
Copy Link

Another simple fix. The markers were being activated on every client, and therefore running the collision check loop once for every player in the game, for every marker. Only activating the marker on its owner fixes this issue.

Another simple fix. The markers were being activated on every client, and therefore running the collision check loop once for every player in the game, for every marker. Only activating the marker on its owner fixes this issue.
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#23
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?