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

Make sure everything syncs properly for the location board. #12

New Issue
Closed
opened 2025-07-13 04:10:20 -04:00 by ActualHorse · 2 comments
ActualHorse commented 2025-07-13 04:10:20 -04:00
Owner
Copy Link

Syncing locations and loot image needs to be fully tested, and ideally reworked to be even more reliable. Do something similar to the map data, where we use synced arrays to copy the data to all clients, and only sync everything after randomising locally.

Syncing locations and loot image needs to be fully tested, and ideally reworked to be even more reliable. Do something similar to the map data, where we use synced arrays to copy the data to all clients, and only sync everything after randomising locally.
ActualHorse added this to the v0.5 milestone 2025-07-13 04:10:20 -04:00
ActualHorse added the
Type
Testing
Priority
A
 labels 2025-07-13 04:10:20 -04:00
ActualHorse self-assigned this 2025-07-13 04:10:20 -04:00
ActualHorse commented 2025-07-13 20:38:21 -04:00
Author
Owner
Copy Link

For some reason, material colours are completely random for everyone, despite having its own synced values. This is being investigated, but is considered low priority, so it's probably fine to adjust this bug status accordingly.

For some reason, material colours are completely random for everyone, despite having its own synced values. This is being investigated, but is considered low priority, so it's probably fine to adjust this bug status accordingly.
ActualHorse added
Priority
C
 and removed
Priority
A
 labels 2025-07-13 20:38:42 -04:00
ActualHorse commented 2025-07-13 22:30:35 -04:00
Author
Owner
Copy Link

This appears to be fixed now. Material randomness is synced just like everything else, and most things reset properly when the game is reinitialised.

This appears to be fixed now. Material randomness is synced just like everything else, and most things reset properly when the game is reinitialised.
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
C
Type
Testing
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#12
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?