PhilAdams
November 11th, 2018, 23:47
This is for the N.E.W./W.O.I.N. ruleset.
A few weeks ago, I ran a short session using The Fall of Somerset Landing to get a feel for the system. We didn't experience any errors (other than the Luck dice pool using the Luck stat instead of the dice pool).
Today, I tried to start a mini-campaign and we encountered a major problem: Something that's changed in the last month has broken the client combat tracker; everything is fine on the server. Tokens don't show up in the client CT, and the client CT itself doesn't populate entries properly (the names are outside the window/box for them).
Any time you try to do anything in the client CT (adjust the size of the CT, for instance) or the server does something (moves through the initiative), the same error is generated:
Ruleset Error: window: Control(name) anchoring to an undefined control (token) in windowless (client_ct_entry).
We noticed really strange tokens behavior today, too (some clients were downloading all the tokens from the server, some were only seeing what was updated in the server CT...so if I dragged a token onto the CT, it downloaded the token to some clients).
We tested against a vanilla MoreCore session and did not see the CT problems.
The server was tested on Mac Parallels (Windows 10) and on the Mac OS (Mojave) side. Same problem.
The clients involved were Macs and Windows (7 & 10). Everyone was running the same updated version.
A few weeks ago, I ran a short session using The Fall of Somerset Landing to get a feel for the system. We didn't experience any errors (other than the Luck dice pool using the Luck stat instead of the dice pool).
Today, I tried to start a mini-campaign and we encountered a major problem: Something that's changed in the last month has broken the client combat tracker; everything is fine on the server. Tokens don't show up in the client CT, and the client CT itself doesn't populate entries properly (the names are outside the window/box for them).
Any time you try to do anything in the client CT (adjust the size of the CT, for instance) or the server does something (moves through the initiative), the same error is generated:
Ruleset Error: window: Control(name) anchoring to an undefined control (token) in windowless (client_ct_entry).
We noticed really strange tokens behavior today, too (some clients were downloading all the tokens from the server, some were only seeing what was updated in the server CT...so if I dragged a token onto the CT, it downloaded the token to some clients).
We tested against a vanilla MoreCore session and did not see the CT problems.
The server was tested on Mac Parallels (Windows 10) and on the Mac OS (Mojave) side. Same problem.
The clients involved were Macs and Windows (7 & 10). Everyone was running the same updated version.