-
Notifications
You must be signed in to change notification settings - Fork 19
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
Migration to 6.0.0 have change tokens custom assets #294
Comments
This doesn't make any sense, migration does not change images. By default token do you mean mystery man? |
I assume this "custom directory" existed in the module or system folder, which is heavily warned against for this specific reason, as it will be deleted if the system or module updates. Feel free to re-open if this is not the case. |
No, the directory is not in module. It's on a top directory, on the same spot of system or modules. what happen is that most token that were from the core and which I changed their images got reverted back to their old image path (from The fact that it was on foundry default token was another issue that I didn't spotted, which is that wng-core broke on update, which just uninstalled the module without reinstalling the new version (which I fixed by reinstalling it back) |
can you reopen the issue, please ? |
Bizarre, well the only way I can really try investigate here is if you send me your world prior to migration |
Describe the bug
After I switched to 6.0.1, creatures which I changed token by importing them as actor and updated their token changed to no token at all, and the path was changed to wng-core instead of my custom directory
To Reproduce
in 5.X.X, import a token from compendium, then change their image. upgrade to 6.0.0 or 6.0.1, and watch them have default foundry token.
Version Numbers
Foundry: latest
wrath-and-glory: latest
The text was updated successfully, but these errors were encountered: