• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Foundry loose integration

One other thing that might be useful is if the import included information on which topics contain and are contained by others. My realm is extensively organized in that manner for physical geography, and I while I know Foundry doesn't (and probably never will) support that style of organization, having the info there makes it a lot easier to adapt.
 
One other thing that might be useful is if the import included information on which topics contain and are contained by others. My realm is extensively organized in that manner for physical geography, and I while I know Foundry doesn't (and probably never will) support that style of organization, having the info there makes it a lot easier to adapt.

Each journal entry created from a topic will have a "Governed Content" section near the end, this contains the list of child topics from Realm Works.

Unfortunately, at the moment there is no link from a child topic back to its governing topic.
 
Each journal entry created from a topic will have a "Governed Content" section near the end, this contains the list of child topics from Realm Works.

Unfortunately, at the moment there is no link from a child topic back to its governing topic.

Ah yes, and so it does. I must have forgotten that it's there in one direction, just not the other.
 
Ah yes, and so it does. I must have forgotten that it's there in one direction, just not the other.

0.3.19 now creates a link to the parent, and puts it at the top of the Journal Entry. You can set the prefix for the link in the module settings.

Also...
Add module configuration setting to set the preferred Actor type when generating Actors from statblocks.

When decoding PF1 Actors, check for presence of "challengerating" element to choose 'npc' Actor type instead of 'character'.

Better fix for HP calculation of PF1 Actors for Actors with multiple types of hit dice.

Create link at start of each Journal Entry to the parent topic. The label for this link is a configurable parameter.
 
0.3.20 adds some more linking...

The "Governed Content" will now contain the full hierarchy of descendents rather than only the direct children.

Provide link from Scene Notes journal entry back to the Scene - although clicking on the link will not do anything, since the default behaviour for a @Scene link in Foundry VTT seems to be to open the scene notes associated with that scene (and not switching you to that scene).
 
Cool thanks!

(There's a mod that lets the scenes links in the journal take you back to them, so that part is covered.)

Full hierarchy might not be ideal for all worlds. For instance, one of my top level topics is "The Multiverse" which includes all geographical areas nested underneath it, so if I'm understanding the feature correctly, it will have thousands of governed content links. Maybe it could be a toggleable option?
 
Cool thanks!

(There's a mod that lets the scenes links in the journal take you back to them, so that part is covered.)

Full hierarchy might not be ideal for all worlds. For instance, one of my top level topics is "The Multiverse" which includes all geographical areas nested underneath it, so if I'm understanding the feature correctly, it will have thousands of governed content links. Maybe it could be a toggleable option?

I was considering how to get the content hierarchy to be collapsible, but it appears that raw HTML doesn't allow it and you have to mess around with CSS and possibly JS as well.

The way that the module creates the hierarchy of governed content does lend itself to allowing a maximum depth to be specified - this would allow a top-level journal entry to perhaps be limited to showing 3 levels of descendents rather than the full tree (and setting it to 1 would disable showing anything other than direct children).
 
Cool thanks!

(There's a mod that lets the scenes links in the journal take you back to them, so that part is covered.)

Full hierarchy might not be ideal for all worlds. For instance, one of my top level topics is "The Multiverse" which includes all geographical areas nested underneath it, so if I'm understanding the feature correctly, it will have thousands of governed content links. Maybe it could be a toggleable option?

0.3.21 adds a configuration parameter in the module settings panel so that you can specify the maximum depth of the governed content added to journal entries.
 
0.3.22 allows you to specify that image/asset files can be located in your S3 storage (if you've configured it for your foundry server).
 
0.4.1 fixes a bug introduced in 0.4.0 which meant that the module would fail to initialise if you did not have the D&D 5E game system installed on your Foundry installation.
 
0.5.0 will now set the disposition of the default token of NPC actors to match the allegiance found in the HL portfolio file.

It also adds support for Savage Worlds HL portfolio files. It will import into the FVTT Savage Worlds game system, and will use the compendiums in the "Savage Worlds Core Ruleset" premium module if installed.

It has not been tested with the HL "Adventure Edition" premium content since I don't own the "Savage Worlds Upgrade to Adventure Edition".
 
Is RealmWorks necessary? Or can exports be done from Hero Lab?

I've held off buying RealmWorks because when Hero Lab announced they were doing layoffs, they indicated they were no longer supporting RealmWorks.

This seems like a big time saver....but does it require buying a no longer supported piece of software, just to get an export to work?
 
Hi Aril. I don't know the answer to your question, but wanted to point out that while support has been scant it's not non-existent. A few months ago they fixed an import-export bug, and a bug that kept RW from integrating the 64 bit version of HeroLab.

What they actually said was specifically that they ARE still supporting RW, but that it is no longer in development.
 
Hi Aril. I don't know the answer to your question, but wanted to point out that while support has been scant it's not non-existent. A few months ago they fixed an import-export bug, and a bug that kept RW from integrating the 64 bit version of HeroLab.

What they actually said was specifically that they ARE still supporting RW, but that it is no longer in development.

Gotcha. How much does it have in the way of features? I hate the idea of paying monthly for software, but when they made that announcement re: RealmWorks, I changed from planning to buy that, to subscribing to WorldAnvil instead, and though WorldAnvil is neat, it's a progressive model where all kinds of features are kept back from you unless you pay even more.
 
I think the only feature that was initially intended that didn't get implemented is the calendar.

I use it all the time - it is by far the best, most flexible world building/campaign management tool I've seen (and I've been playing a LONG time :)).

You buy the software once and can install it on as many machines as you wish and don't HAVE to pay any monthly fees just to use the program.

BUT, to sync your realms between machines (and to allow your players to sync to their machines if they've chosen to buy RW themselves) you do have to pay a small monthly server maintenance fee (well worth it, in my mind).
 
Is RealmWorks necessary? Or can exports be done from Hero Lab?

I've held off buying RealmWorks because when Hero Lab announced they were doing layoffs, they indicated they were no longer supporting RealmWorks.

This seems like a big time saver....but does it require buying a no longer supported piece of software, just to get an export to work?

Hi Aril, the module will load a .por file directly and create an Actor for each sheet in the .por portfolio file. If it is PF1, D&D 5E or Savage Worlds then it will also try to populate as much of the Actor fields as possible; otherwise it will simply store the statblock in the Description/Biography field of the Actor(s).
 
0.5.1 fixes a bug.

Snippets are now placed immediately after the section header when the section has sub-sections. (Previously they were put AFTER all sub-sections, and so appeared to be part of the last sub-section.)
 
Back
Top