Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not Reload on clients' side #38

Open
Weissrolf opened this issue Oct 3, 2022 · 2 comments
Open

Does not Reload on clients' side #38

Weissrolf opened this issue Oct 3, 2022 · 2 comments

Comments

@Weissrolf
Copy link

Weissrolf commented Oct 3, 2022

Hello. Thanks many times for this useful module.

Yesterday we tried to hunt down which modules causes everyone's clients to occasionally freeze, so I use FtC during our session. Unfortunately it turned out that FtC does not reload the browsers of my connected players, but only my (GM) browser. So we ended up with my browser instance having the modules disabled, but their browsers still running the parts that were in their memory. So FtC should also induce a Reload on every connected client to make sure they run in sync.

(Curiously enough that still fixed the freezes.)

@esheyw
Copy link

esheyw commented Jun 30, 2023

Hi, just would like to +1 the request to please have all clients reload when the one running FtC does. adds a bunch of extra alt-tab/f5ing to an otherwise very streamlined process.

@mclemente
Copy link

Add a game.socket.emit("reload"); before both instances where debouncedReload is called.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants