(some) Token paths broken in the Core update

[celestian]

So there has been a lot of discussion on this topic in discord but I've not seen anything about it anywhere else so...

Some modules have token paths such as tokens/campaign/filename.png@SomeModule and they no longer work. To make them work I had to go in and bulk replace tokens/campaign/ with tokens/ so the end path was tokens/filename.png@SomeModule.

An actual example: <token type="token">tokens/campaign/Gargoyle.png@AD&amp;D 2E Monstrous Manual</token>



Is there a reason for this change? Will there be some sorta update to make it continue to work as before or will all the content devs need to update their modules?

[Moon Wizard]

I'm not aware of any changes that would affect this. I checked the internal client export code; and it hasn't been changed since first week of September. And, the ExportManager code in CoreRPG doesn't do anything with built in token fields (other than PC portrait tokens).

Those paths should still work as long as the token images are actually stored at tokens/campaign/filename.png in the module.

Some questions to investigate further:
* How were those modules generated? (external tool vs. built-in export)
* When were they initially generated?
* When were they last updated?

Thanks,
JPG

[celestian]

I'm not aware of any changes that would affect this. I checked the internal client export code; and it hasn't been changed since first week of September. And, the ExportManager code in CoreRPG doesn't do anything with built in token fields (other than PC portrait tokens).

Those paths should still work as long as the token images are actually stored at tokens/campaign/filename.png in the module.

Some questions to investigate further:
* How were those modules generated? (external tool vs. built-in export)
* When were they initially generated?
* When were they last updated?

Thanks,
JPG

This got me checking, the newly exported AD&D 2e MM no longer places tokens as tokens/campaign/* but tokens/*. So it's not an issue of the path in the other modules but with the MM pathing changing compared to previous export. I didn't move the tokens from tokens/campaign to tokens/ in the Campaign either.

I'm guessing I can make the tokens/campaign directory and move them and bulkd change the path references in the campaign db.xml to tokens/campaign/ and it'll work like before.

Right now a sample path for a token in the MM campaign im exporting for an NPC is <token type="token">campaign/tokens/Aarakocra.png</token>

Keep in mind I've not touched the tokens since I created this.

[celestian]

Further testing, if I make a tokens/campaign directory and move the token there, put it on the npc and export.... the path for the exported npc's token changes from tokens/campaign/* (from the Campaign's db.xml) to tokens/* . The tokens/campaign/ folder is not included in the exported .mod, only tokens/ where ALL the token images are placed.

[Moon Wizard]

As far as the direct client export code, it has always saved to "tokens/filename.png", as far as I can tell from the code SVN logs up to a couple years back on FGU.
Perhaps the MM XML was generated by another method originally?

Regards,
JPG

[celestian]

As far as the direct client export code, it has always saved to "tokens/filename.png", as far as I can tell from the code SVN logs up to a couple years back on FGU.
Perhaps the MM XML was generated by another method originally?

Regards,
JPG

I used Author to export it to inject the ref-manual on export. I copy/pasted in the export code from CoreRPG and the code I added was for a reference only. Perhaps the export code I used from CoreRPG did this when I created it. Now, Author doesn't need to do that with Builder.

I don't understand why the path for tokens is changed in the new one. I could fix this by making tokens/campaign/* in the Campaign and moving the tokens on the npcs to that and exporting it but the export process removes any paths deeper than tokens/*.

[Moon Wizard]

As far as I know, the standard export in FGU never placed the tokens there. Perhaps it was a FGC export difference?

JPG

[celestian]

As far as I know, the standard export in FGU never placed the tokens there. Perhaps it was a FGC export difference?

JPG

It could have been. For now im going through my past products and updating so the new paths work.

[AlterZwerg]

This is an issue for various NPCs in almost every D&D Classics Module. I just updated MC3, MC11 and RQ1

[Moon Wizard]

I've just pushed hot fixes for all the 2E modules affected by the 2E Monstrous Manual changes.

Regards,
JPG