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

Floor map does not sync correctly, leaving no way to play the game for anyone but the instance owner. #11

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

Something isn't syncing right with the floor maps, even though I was pretty sure it worked at one point. In any case, this needs to be addressed.

Something isn't syncing right with the floor maps, even though I was pretty sure it worked at one point. In any case, this needs to be addressed.
ActualHorse added this to the v0.5 milestone 2025-07-13 04:00:07 -04:00
ActualHorse added the
Type
Bug
Priority
A
 labels 2025-07-13 04:00:07 -04:00
ActualHorse self-assigned this 2025-07-13 04:00:07 -04:00
ActualHorse commented 2025-07-14 03:32:01 -04:00
Author
Owner
Copy Link

This is really annoying. If the instance owner loads a case file, the map only loads in and shows up for them. But if a second player loads a case file, the map loads only for them. The variable to load the map is supposed to be synced, so I don't know what's happening there.

This is really annoying. If the instance owner loads a case file, the map only loads in and shows up for them. But if a second player loads a case file, the map loads only for them. The variable to load the map is supposed to be synced, so I don't know what's happening there.
ActualHorse commented 2025-07-16 04:23:51 -04:00
Author
Owner
Copy Link

This seems to all be figured out now that all the other sync issues have been resolved.

This seems to all be figured out now that all the other sync issues have been resolved.
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#11
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?