search

Moerill / fvtt-find-the-culprit

MIT License
8 stars 10 forks source link

Does not Reload on clients' side #38

Open Weissrolf opened 1 year ago

Weissrolf commented 1 year ago

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 commented 1 year ago

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 commented 5 months ago

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