-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
[BREAKING CHANGES] Many bug fixing and some not retrocompatibility changes #82
Conversation
…ys for the stupid flagscope foundry core code...
…uses for the input uses...
I'll check this during the week, thanks for the help 🤗 |
@AGCeyx not really on forge, if you have a local instance you just pull the branch into the
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to be working good, at least the codeside is okay looking for me, i'll test more on Thursday evening and make a release then
In this PR I rewrote quite a bit of stuff...test it as much as you can...it seems to me that it all works....
The foundry core not accept anymore flags with a scope not equals to the module id...
So anyway now we must migrate all the old scoped flags
magicitems
to the new scoped flagmagic-items-2
as standard (this is why I didn't understand the error at first in all my modules i always used the standard of using module id as the scope of the flags)I created a dangerous (but tested) function in the module api to be launched manually and after making a safety backup...
game.modules.get("magic-items-2").api.fixFlagsScopeDataOnAllActors()
A brief re-epilogue of this PR
maicitems
tomagic-items-2
game.modules.get("magic-items-2").api.fixFlagsScopeDataOnAllActors
for fix all actor in the world