You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Info for the DM know when the player is ready to play.
The Solution you'd like
A simple message in GMs chat would be enough. Maybe some time down the road actual ClientMessages with handlers and events to show in a nice separate panel what zone each player is in and their loading progress.
Alternatives that you've considered.
Asking several times every player if they are in yet every time the map changes 🤢
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Tested. The connection indicator shows the number of connected clients (including the one running the server). It typically shows the number of loaded clients as well, though the number can cycle a lot during loading. Interestingly, when I loaded a large campaign, it sometimes showed 0 loaded clients, even after the server client has already loaded. Very minor though, can be addressed separately if it turns out to be a real problem.
It's not clear to me whether the connection indicator gives the expected information in the context of this FR. It does not show the number of clients on the GM's map, rather it shows the clients that have their own current map loaded. But this seems good to me as not all games require players to be on the same map, and the Connections window can be used for more detailed information if needed.
Feature Request
Info for the DM know when the player is ready to play.
The Solution you'd like
A simple message in GMs chat would be enough. Maybe some time down the road actual
ClientMessages
with handlers and events to show in a nice separate panel what zone each player is in and their loading progress.Alternatives that you've considered.
Asking several times every player if they are in yet every time the map changes 🤢
Additional Context
No response
The text was updated successfully, but these errors were encountered: