Exporting NPC placement, map markers etc.

[Valhingen]

I am not sure if this is simply not supported or if I'm doing something wrong.

What I did was, I started a new "campaign" (to write a module, used by my main campaign). So I added a map, drew walls, created story entries which I placed as pins on the map. Afterwards I created encounter for those story pins and in all I placed the enemies on the same map.

Next I export this with everything checked and imported it into my main Campaign file.

Now my problem is that all seemed fine, except neither the story pins nor the NPCs within encounters are placed. Is that intentional or how would I achieve this?

Thank you!

PS: I don't think it matters since I vaguly remembered having this issue long ago in 5E but currently I'm using Shadowdark.

[Valhingen]

Correction - I dont know what I did different but placement of NPCs DID export correctly. Just not the map/story pins ?

[Laerun]

Correction - I dont know what I did different but placement of NPCs DID export correctly. Just not the map/story pins ?

Did you drag and use your own module assets or did you use links and assets from any official modules? I don't remember if this matters, but anything official cannot be exported without making a copy of the data you are linking from.

[Valhingen]

No, I made my own module, typed up some story entries like "this is the boss room" and want those as pins on the map. For me those pins were not exported. The text was, just not the actual pin locations.

[Laerun]

No, I made my own module, typed up some story entries like "this is the boss room" and want those as pins on the map. For me those pins were not exported. The text was, just not the actual pin locations.

What about the map image itself? Also, Are you loading and building your module and loading it in the same campaign session? That can cause issues too, as sometimes I was in the wrong campaign, unlikely, but it happens. Also, exporting multiple variations of the same module data in your modules folder can be problematic because Fantasy Grounds will only show the oldest data.

[Zacchaeus]

Everything that you create in a campaign should get exported. Even if the pins were to something in a different module (and not something you had created) it should get exported since you created it. You might need to zip up your campaign and post it here so that we can take a closer look at what is happening.

[Griogre]

Also double check you don't Map pins turned off on your map.

[Valhingen]

I did some more testing and its even more odd, apparently, somehow linked to my campaign (?) So, I did...

1. exported my "session" campaign again (the module where I made the map and placed the pins), gave it a new name and icon to make sure I pick the right one
2. activated it in my main campaign (deactivating the old attempts), clicked on it under modules, then images, then the map and...no pins
3. created a brand new, empty shadowdarkcampaign and then the same from point 2; activated it, click on modules, then images, then the map and...boom, pins!

I dont get it... :(
(yes, pins are on in both tries)

[Griogre]

Hmm, in your Main campaign if you open the module activation window and right click on the exported module is there a "Revert Changes" at 11 o'clock? It sounds like there is an override in your main campaign.

Otherwise your main campaign's XML main have some sort of persistent record data - which sometimes happens from extensions.

[Valhingen]

o-m-g

Revert changes fixed it. Thank you so much :) I didnt even know that feature!

[Griogre]

:) Basically if you change the data in an exported or purchased module, the playing campaign you changed it in - keeps those changes.

Updates to the changed exported module doesn't effect the changes since it is assumed you made the changes for a reason. The revert changes at the module level lets you use the module as it was exported and throws out any changes. You can also revert changes at the individual record level, ie maps, images, npcs etc.

Since you re-exported everything it was fine to revert the whole module back to the baseline export, but you may not always want to revert the whole module.