DFreds
commented
3 years ago Deactivated how? By toggling the effect via the app or removing the effect directly from a character sheet? I'll try to reproduce this though.
Closed Quixion closed 3 years ago
DFreds
commented
3 years ago Deactivated how? By toggling the effect via the app or removing the effect directly from a character sheet? I'll try to reproduce this though.
Quixion
commented
3 years ago Toggling via app, removing from the sheet directly, and timed effect expiration. I've been getting it via those means. It looks like I can get the effects to go away without error about 1/2 the time if I set them via the active effect "Macro dae.CE", but if I have literally anything else on the item, another effect, item macro, healing effect, basically anything, it will give me those errors again
DFreds
commented
3 years ago I am not able to reproduce this issue. You have a lot of modules, so it's possible something is conflicting. I see that you have the Find the Culprit module. Can you try using that and see if it narrows it down?
Quixion
commented
3 years ago Disabling item macros reduces but doesn't eliminate the issue. I'll keep digging though
Quixion
commented
3 years ago I still have no idea what is causing it, but it looks like effects are being applied twice at the same time. One is invisible, which is to say that I don't see any indication of a second effect application outside the fact that it's acting like it's applied twice. I'm still running through permutations of modules.
Quixion
commented
3 years ago It's advanced macros/furnace. I think. And automated animations somehow?
DFreds
commented
3 years ago Hm, I use advanced macros and automated animations in my own game and haven't had this issue. That would be surprising? It could be a combination of a few modules though...
Quixion
commented
3 years ago Yeah I'm wrong. I give up, nothing I disable seems to fix it. Guessing it's something outside of foundry
DFreds
commented
3 years ago Is this a brand new world or an old world?
DFreds
commented
3 years ago Feel free to respond and I can possibly help. Otherwise, this doesn't appear to be an issue with CE
Quixion
commented
3 years ago It's a 7.x world. I've been able to replicate the issue without CE installed now so it's definitely something more fundamental. I'm not sure why it's easier to trigger the issue with CE installed. I'm stepping away from it all for now, my sanity needs a recharge. Thank you for the help though!
thatlonelybugbear
commented
3 years ago The error you get @Quixion is one encountered in many situations in Foundry 0.8.x.
It is triggered by race conditions desyncing server side and client side. Deletion of many active effects at the same time is a trigger.
It is supposed to be fixed in v0.9.x of Foundry, so this means we have to live with that for the time being. When the error occurs a reload should fix it.
Similar issues https://gitlab.com/foundrynet/foundryvtt/-/issues/5312 and https://gitlab.com/foundrynet/foundryvtt/-/issues/5309
DFreds
commented
3 years ago @thatlonelybugbear is probably right (thank you).
Unfortunate, but I hope it isn't too game breaking for you. If you could, can you check if it also happens in a brand new world for you? It's also possible some weird migration happened.
Quixion
commented
3 years ago Y'all saved me so much mental anguish with this just now 😭 thank you so much for the update
Quixion
commented
3 years ago @thatlonelybugbear is probably right (thank you).
Unfortunate, but I hope it isn't too game breaking for you. If you could, can you check if it also happens in a brand new world for you? It's also possible some weird migration happened.
Confirmed to happen in a new world without any modules
DFreds
commented
3 years ago @thatlonelybugbear is probably right (thank you). Unfortunate, but I hope it isn't too game breaking for you. If you could, can you check if it also happens in a brand new world for you? It's also possible some weird migration happened.
Confirmed to happen in a new world without any modules
Very strange. My only other suggestion would to do a full reinstall of foundry, to ensure that the underlying framework is also updated. You should maybe back up your user data to be safe, but it shouldn't effect it at all.
Quixion
commented
3 years ago So I think it's something with my computer. Only way I've gotten rid of the error was to install to a different computer. Haven't moved anything over to it yet but fresh install on my desktop still threw the error. Clearly I'm cursed
DFreds
commented
3 years ago Did you do the full reinstall of foundry on the computer with issues and still had the problem?
Quixion
commented
3 years ago Yeah, but I'm giving it another go. Same computer, different destination install
Quixion
commented
3 years ago hmm, well, as long as I have no modules enabled it seems to be ok. Haven't tested any macros or anything more complicated than applying and unapplying a status marker to an actor but that works now so I'll take it until the core update and move from there. Thanks again!
When an applied condition expires or is manually deactivated, the effect remains on the actor and it displays this error
The mechanical effects of the condition are removed, but the condition and any lighting or magic effects remain until the application is reloaded.
This seems to happen with any of the conditions that apply any change to the actor. Conditions that simply display a status icon on the token don't always have this issue. I've tried deactivating the other installed modules one by one but CE seems to be the only thing that I can disable to remove the problem. I've not tried this in any other systems outside of 5e. Here's the list of my active modules.