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

Update README on the full effects of using the --json option #45

Open
Alarich opened this issue May 1, 2020 · 0 comments
Open

Update README on the full effects of using the --json option #45

Alarich opened this issue May 1, 2020 · 0 comments

Comments

@Alarich
Copy link

Alarich commented May 1, 2020

From a reply about potential CORS issues when converting a campaign:

one way to avoid this problem with CORS, is to extract the campaign.json file from the exported zip, and convert that using the "use json" option in the converter.. then all the images will be downloaded by the R20Converter app, so CORS becomes irrelevant and all images (as long as they exist) would be downloaded and converted. It just means the conversion will take even more time as it will redownload everything.

The README could be improved with this information.
I've also tested this option and found that, indeed, the files that R20Exporter could not obtain were present and properly downloaded. Even if it does take more time it could be a good fallback option to try for those who used a lot of external assets in their R20 campaigns.

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

1 participant