Release v3.2.2 is live

[dulux-oz]

That was fast! Seriously, I went to sleep, thinking there was no way this would be resolved in time and woke up to the issue patched and my post answered directly!? You are magnificent bastards, seriously.

Welcome to the wonderful world that is FG, SmiteWorks and this Community

[Mortar]

Welcome to the wonderful world that is FG, SmiteWorks and this Community

That and I don't JPG us actually human cause he doesn't seem to sleep

[vodokar]

That was fast! Seriously, I went to sleep, thinking there was no way this would be resolved in time and woke up to the issue patched and my post answered directly!? You are magnificent bastards, seriously.

Welcome to Fantasy Grounds. The Bestest place on the internet.

[Moon Wizard]

Pushed Savage Worlds hot fix for weapon type information missing from weapon records.

Regards,
JPG

[Dwayne Squires]

Damned recommended I repost this question to the 3.2.2 thread. I hope this is where he meant. I just completed my first Dungeon Module export and ran into this issue.

1st) Maps and images. All my maps Titles/links pulled over in the Maps and Images list but two of my maps did not come across correctly. I think I know what is wrong so just looking to see if I am correct or doing something wrong. So two images that did not export correctly are really just drawings I created on a blank map field. I.E. you hit new image but do not link it to a .jpg or .png file you get a grey screen. I hand drew too crude pictures and then saved them (or thought I did as they worked perfectly in the original campaign I built them in). However, when I exported and then move to my actual campaign and open the module. The Title/links show up on the list but when I open them they are blank. The actual drawings did not come across. I know I can fix this by creating the drawings in paint and saving them as an actual file but is there something else I am missing? It appears the drawings you make in FG do not actually save.

[Nickademus]

He was actually referring to the bug thread here.

[CoreRPG+] Added quick navigation buttons to the bottom of story records. All navigation buttons are relative to module of the story record. Use "(Index)" or "(Content)" to denote the name of the top-level story entry.

What effect does naming a story entry (Content) have? The parenthesis causes it to be at or near the top of an alphabetical list, but does FG do anything special for a 'top-level story entry'?

[Dwayne Squires]

Thanks, Nickademus.

[damned]

He was actually referring to the bug thread here.

[CoreRPG+] Added quick navigation buttons to the bottom of story records. All navigation buttons are relative to module of the story record. Use "(Index)" or "(Content)" to denote the name of the top-level story entry.

What effect does naming a story entry (Content) have? The parenthesis causes it to be at or near the top of an alphabetical list, but does FG do anything special for a 'top-level story entry'?

The new NAV buttons at bottom of page - the UP arrow - takes you to (Contents)

[Nickademus]

Oh. So there was no Up arrow since the patch notes said to name it "(Content)", which apparently doesn't register.

Thanks. That's really nifty. It would be more helpful if clicking on a story link in a story entry opened the entry in the same window (similar to how the arrows now do) instead of opening a new window. Then the arrows and an index could be used to navigate the entire story tree in a single window.

[Zacchaeus]

Hmm, not sure about that. You often need a number of Story entries open so if they all opened in the same window that would cause navigation problems I feel.