• 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

Pathfinder Battles

Personally, I prefer the import from portfolio and deleting the monster/character when do with it. Mostly because HeroLab starts to slow down a little when the number of monsters in it gets long enough.
 
Maybe they could improve the way it handles a larger number of heros in the portfolios so that performance isn't an issue.
 
I think its the way the scripts run, the more heroes the more data the program needs to go through on every go around. Nature of the beast.

For running combats though, importing from another portfolios works awesome, esp since you can add multiple copies of any of the monsters/heroes. Being able to apply conditions (or damage) to multiple pcs/npcs at once will be great when they do that :).
 
As a computer programmer by trade, I would disagree. The scripts should only run during the initial load to calculate all the values, then as you make changes to individual heros only a few scripts should ever have to execute to complete the recalculations. Should not burden modern CPUs. Think about ALL the scripts that run in many web pages?
 
Last edited:
As a computer programmer by trade, I would disagree. The scripts should only run during the initial load to calculate all the values, then as you make changes to individual heros only a few scripts should ever have to execute to complete the recalculations. Should not burden modern CPUs. Think about ALL the scripts that run in many webpages?

There are two factors here that you are likely overlooking. First, changes to a character have ripple effects throughout the entire character. For example, consider a Strength adjustment, whose effects cascade through numerous aspects of the character (skills, encumbrance, weapon attacks/damage, etc.). Consequently, the slightest change to a character requires that it be *fully* re-evaluated to properly reflect all the cascading effects.

Second, assorted "characters" in Pathfinder have cross-dependencies. For example, an animal companion may derive various characteristics from its master, or a familiar may confer bonuses to its master. In these situations, Hero Lab needs to fully re-evaluate all the cross-linked characters to ensure that everything is correct after a small change.

Hero Lab strives to be "smart" and only re-evaluate the characters that are impacted by a given change. However, there are many situations where Hero Lab has to play it safe and re-evaluate everything, since the alternative is incorrect calculations being shown to the user.
 
As with anything that is computationally intensive, it depends entirely on the horsepower of the computer being used. On my year-old system, I just imported a dozen assorted 10th level characters and another dozen assorted monsters of moderate CR. Everything runs very quick and efficient for me. Your mileage may vary, of course, since the horsepower of your computer will likely be different.
 
Then I believe that Hero Lab should be able to handle many heros in the same portfolio and this is really a null issue unless you have a very old system. I am sure that Hero Lab like all software has a minimum requirements spec, so if we stick to that we should all be good.
 
On my year and a half system I start noticing a 'lag' at around 30+ heroes... Who are 20th level or more.

That's when I started automatically doing the import rather than worrying about when I would hit that mark.

Plus, it's cleaner for my to have separate portfolios for each module/AP I may run my players through. That way I can just open that portfolio and adjust the CRs up and save it as a new file. But that's just me.
 
That's when I started automatically doing the import rather than worrying about when I would hit that mark.

Plus, it's cleaner for my to have separate portfolios for each module/AP I may run my players through. That way I can just open that portfolio and adjust the CRs up and save it as a new file. But that's just me.

The great thing about the folder system I am asking for is that you could still do things your way if you prefer. I am not requesting they remove a feature from HL, just add a great organizational feature.
 
while d20pro is a nice product, and would help to show a combat, i find it difficult to use and the docimentation is lacking. JUst getting a map to display is an effort and i still havent figured out how to just move peices around the board. I wish it were easier, i would use it all the time.

The documentation problem is being worked. Plus a set of tutorial videos should be out soon. We have some, but more on on the way.

Once you learn the ins and outs of d20Pro you will find that importing maps and doing combat becomes easy.

If you need some help let me know we can do a tutorial session or something.

I am running a game on July 9th for d20ProCon through the infrno.net system if you were interested in learning d20pro some more. There are also player and DM tutorials that weekend as well being offered.
 
Is anyone using d20pro?

I've been using HL for just one character while playing, and it's fine. But I know the GM for our group is also using HL, and it takes a long time to apply conditions (e.g. Dazzling Display applying Shaken), apply damage/healing (Fireball, Lightning Bolt, etc), etc. Does d20pro make these things simpler? Is it worth the money? Does it support all the content that HeroLab has?

I'm not really looking for a full VTT app -- I just want a robust and fully functional combat manager. I prefer the traditional physical "board" and miniatures.
 
Last edited:
@ Adam.Ormond

d20Pro is a full VTT app. It can be used as an aid at the table, but its best use (IMHO) is to replace the miniatures and tabletop map.

If you do not use it that way, to get the damage effects and such, the GM would have to essentially repeat each action on the d20Pro map after you play it out on your battlemat.

They do offer a trial license so you and your GM can download it and try it out. There is a bit of a learning curve, and the map creation can take time the first few times. There are community resources for Pathfinder, but it is not fully supported in the core package (or was not the last time I looked). For example, CMB and CMD require some more advanced setup to get just right.

The HL export helps with a lot of that, but there's still some work to be done for full seamless integration.
 
Back
Top