Skip to content
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

Open
rorp24 opened this issue Jan 9, 2025 · 5 comments
Open

Migration to 6.0.0 have change tokens custom assets #294

rorp24 opened this issue Jan 9, 2025 · 5 comments
Assignees

Comments

@rorp24
Copy link

rorp24 commented Jan 9, 2025

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

@moo-man
Copy link
Owner

moo-man commented Jan 9, 2025

This doesn't make any sense, migration does not change images.

By default token do you mean mystery man?

Repository owner deleted a comment from Redkiller93 Jan 9, 2025
Repository owner deleted a comment from Redkiller93 Jan 9, 2025
@moo-man
Copy link
Owner

moo-man commented Jan 9, 2025

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.

@moo-man moo-man closed this as completed Jan 9, 2025
@rorp24
Copy link
Author

rorp24 commented Jan 11, 2025

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 custom/token/image to wng-core/token/image).

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)

@rorp24
Copy link
Author

rorp24 commented Jan 11, 2025

can you reopen the issue, please ?

@moo-man moo-man reopened this Jan 11, 2025
@moo-man
Copy link
Owner

moo-man commented Jan 11, 2025

Bizarre, well the only way I can really try investigate here is if you send me your world prior to migration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants