• 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

Does anyone have...

woobyluv

Well-known member
a completed adventure input into Realm Works for Pathfinder yet? I'd be interested to see how you set up the encounters. I have had no problem making the town, region, country for The Dragon's Demand, but I'm not exactly sure how to set up the encounters to flow from one to the next.
 
I've done a couple of the pathfinder APs now. I've done it twofold - for locations with maps, I use the map for navigation so I can just click on the site the party are attending, whilst overall I can use the storyboard for navigation to provide continuity through events.
 
I'm sure there are a number of methods to approach this subject. The one that I most commonly use for transcribing adventure modules into Realmworks is to create at least one "parent topic" for a given adventure, which contains a broad overview of the adventure and also acts as an *Index* to the rest of the adventure, which I have split up into individual subtopics. To make a subtopic, I will make each encounter into its own Topic, and then set the "Containing Topic" of these individual topics to be the "parent topic" - this creates a nested structure, which allows you to easily navigate, and if you want to get really precise, you can start manually creating links within your topic structure. Usually, in my "Parent Topic" I will make a Table of Contents which includes links to all encounters, bestiary entries, notable NPCs, maps, and any other Topics pertaining to that adventure. You can be as granular about this kind of content linking as you want. There's also content tagging, etc. So really, I guess just try to find a method which agrees with your personal logic, and then develop it from there with experience. Thankfully, in Realmworks, there are plenty of ways to revisit content at a later point to implement additionally functionality as your methods change/improve. Good luck!
 
I'm sure there are a number of methods to approach this subject. The one that I most commonly use for transcribing adventure modules into Realmworks is to create at least one "parent topic" for a given adventure, which contains a broad overview of the adventure and also acts as an *Index* to the rest of the adventure, which I have split up into individual subtopics. To make a subtopic, I will make each encounter into its own Topic, and then set the "Containing Topic" of these individual topics to be the "parent topic" - this creates a nested structure, which allows you to easily navigate, and if you want to get really precise, you can start manually creating links within your topic structure. Usually, in my "Parent Topic" I will make a Table of Contents which includes links to all encounters, bestiary entries, notable NPCs, maps, and any other Topics pertaining to that adventure. You can be as granular about this kind of content linking as you want. There's also content tagging, etc. So really, I guess just try to find a method which agrees with your personal logic, and then develop it from there with experience. Thankfully, in Realmworks, there are plenty of ways to revisit content at a later point to implement additionally functionality as your methods change/improve. Good luck!

Do you use an "Incident" topic as your parent topic? Or "Scene"?
 
Back
Top