skj310
February 4th, 2018, 06:49
Ok I've attempted to search the forums, and haven't had luck with the keywords in the title of this post.
Specifically we are all running latest FG v3.3.3, as are our players. Everyone is using windows as the OS (10, or 7), and a couple use linux.
So a good number of GMs in a WM setting have players importing their character sheets into the host's server. When they do this, no problem, import success. Later in the session when the GM performs a long rest, some player's will see their character sheet reset their ability scores. The crazy part is that usually the GM notices this and the player's do not, as their stats remain fine from their client connection. The only fix is to have the player's type their stats back into the fields; at which point everything is ok. Why an issue, because even though the player's client connection looks ok, when they roll they roll with the stats on the server and lose their modifiers. Both Windows and Linux hosts servers have observed this behaviour.
None of the GMs in our WM setting have been able to pinpoint what's the cause behind the "Long Rest" trigger. Any ideas?
Specifically we are all running latest FG v3.3.3, as are our players. Everyone is using windows as the OS (10, or 7), and a couple use linux.
So a good number of GMs in a WM setting have players importing their character sheets into the host's server. When they do this, no problem, import success. Later in the session when the GM performs a long rest, some player's will see their character sheet reset their ability scores. The crazy part is that usually the GM notices this and the player's do not, as their stats remain fine from their client connection. The only fix is to have the player's type their stats back into the fields; at which point everything is ok. Why an issue, because even though the player's client connection looks ok, when they roll they roll with the stats on the server and lose their modifiers. Both Windows and Linux hosts servers have observed this behaviour.
None of the GMs in our WM setting have been able to pinpoint what's the cause behind the "Long Rest" trigger. Any ideas?