Xorn
January 25th, 2014, 12:24
When I make an adventure module, I create my campaign, populate it with all my story/images/npcs/items/notes, then export it. No problem. The tokens I use might come from various sources: My general tokens (in my root FG folder), my campaign specific tokens (in the adventure campaign folder), and from other modules.
Something broke in this process with FG3. I made a sample campaign so that this can be easily duplicated. The campaign is named "test token export".
The first NPC is named Module Token, and it's a token from the Monster Manual I made before FG3.
The second NPC is named Host Token, and it's a token from FG2\tokens\host\custom
The third NPC is named Shared Token, and it's a token from FG2\tokens\shared\characters
The fourth NPC is named Campaign token, and it's a token from FG2\campaign\test token export\tokens\host
When I export the module (as "test.mod"), the first three NPCs retain their tokens. The 2nd and 3rd ones are actually in the module file. The fourth one did not copy into the module file, and the reference for it is wrong.
In the module file, NPC1 (module) token is "tokens/ambush drake.png@4E Essentials MM
NPC2 (host) is "tokens/host/Custom/bugbear.png@test"
NPC3 (shared) is "tokens/shared/Characters/lorkeon.png@test"
NPC4 (campaign) is "campaign/tokens/Host/basilisk.png"
Obviously, that reference is invalid. The token was located in FG2\campaign\test token export\tokens\host. What I don't get is why the token wasn't just exported into the module. Does this mean I have to fill my FG2\tokens folder with every single token I might want to ever use? Kind of defeats the point of using modules, if I'm going to have a swollen token folder.
EDIT: The workaround for now is if you have campaign specific tokens, load them into FG2\tokens\host\<folder name>. Use the tokens from there and they will export correctly, and then you can go back and delete the folder once you've done your export. Note that if you ever want to MODIFY that campaign and re-export the module, the tokens will need to be put back or it won't export correctly.
Hopefully a fix isn't too long in coming for this.
Something broke in this process with FG3. I made a sample campaign so that this can be easily duplicated. The campaign is named "test token export".
The first NPC is named Module Token, and it's a token from the Monster Manual I made before FG3.
The second NPC is named Host Token, and it's a token from FG2\tokens\host\custom
The third NPC is named Shared Token, and it's a token from FG2\tokens\shared\characters
The fourth NPC is named Campaign token, and it's a token from FG2\campaign\test token export\tokens\host
When I export the module (as "test.mod"), the first three NPCs retain their tokens. The 2nd and 3rd ones are actually in the module file. The fourth one did not copy into the module file, and the reference for it is wrong.
In the module file, NPC1 (module) token is "tokens/ambush drake.png@4E Essentials MM
NPC2 (host) is "tokens/host/Custom/bugbear.png@test"
NPC3 (shared) is "tokens/shared/Characters/lorkeon.png@test"
NPC4 (campaign) is "campaign/tokens/Host/basilisk.png"
Obviously, that reference is invalid. The token was located in FG2\campaign\test token export\tokens\host. What I don't get is why the token wasn't just exported into the module. Does this mean I have to fill my FG2\tokens folder with every single token I might want to ever use? Kind of defeats the point of using modules, if I'm going to have a swollen token folder.
EDIT: The workaround for now is if you have campaign specific tokens, load them into FG2\tokens\host\<folder name>. Use the tokens from there and they will export correctly, and then you can go back and delete the folder once you've done your export. Note that if you ever want to MODIFY that campaign and re-export the module, the tokens will need to be put back or it won't export correctly.
Hopefully a fix isn't too long in coming for this.