Hero.Epic

[ErinRigh]

I know this is an old topic, but I am wondering if anyone involved in the d20 data set has any thoughts on addressing this.

Checking back I can find issues with this going back at least 4 years!

I may be in a minority but I would really like to see Epic character support in Hero Lab. Epic characters fall in line with Open Gaming guidelines and the SRD, so why not support in Hero Lab?

But aside from that, does anyone have an idea on how I would create an adjustment (preferably a condition) that would add the Epic hero (Hero.Epic) state to a character making epic feats valid for the character.

Seriously though, can anyone tell me why epic character support is so limited within HL?

[ShadowChemosh]

Its called "time". I have very little of it and so my decisions are often based on what has the biggest impact on those using the software. The improvements to spells, spell-like abilities, and deities will affect 99% of the user base. Epic will affect maybe 25% of the user base.

Not saying I will never get to improving Epic support. But I need to stay focused on the changes that will help the most number of users.

That means Epic/Gestalt will stay as low-priority in the list. As I make other improvements I will keep them in mind and if something happens where I can add in a feature that also will help Epic/Gestalt then it will happen.

But as been seen lately I think many more people would be happier with support for say "Configurables" in the editor. That allows for "new" tabs to be added allowing for more customization by editors and the community.

[ErinRigh]

No problem SC, time is a precious commodity for all lately

[ErinRigh]

Originally Posted by ErinRigh

But aside from that, does anyone have an idea on how I would create an adjustment (preferably a condition) that would add the Epic hero (Hero.Epic) state to a character making epic feats valid for the character.

anybody got any thoughts on this?

[Nightfox]

The hardest part as I see it would be figuring out the classes affected and calculating the appropriate adjustments. Time consuming and clunky coding, but manageable I think. My own gaming groups either finish the campaigns before epic (victory or death) or have simply continued level (like Pathfinder) for levels above 20.

I don't even know where my ELHB is anymore, so can you refresh my memory on what exactly the changes for 21+ level are? As I recall BAB is replaced by just an attack bonus, and the saves are the same for all classes.

[ErinRigh]

Well I have no problems using continued advancement, which is how hero lab handles it now, but epic feats require that Hero.Epic <> 0. this state does not appear on characters who are character level 21 automatically and I am looking for a way to do it Manually.

[bodrin]

Originally Posted by ErinRigh

Well I have no problems using continued advancement, which is how hero lab handles it now, but epic feats require that Hero.Epic <> 0. this state does not appear on characters who are character level 21 automatically and I am looking for a way to do it Manually.

Can you make a special, which once bootstrapped, checks for level greater than 20 and assigns the Hero.Epic tag?

Possibly an adjustment or Epic template.

[Sendric]

Originally Posted by ErinRigh

Well I have no problems using continued advancement, which is how hero lab handles it now, but epic feats require that Hero.Epic <> 0. this state does not appear on characters who are character level 21 automatically and I am looking for a way to do it Manually.

I thought there was one already. I will look into it when I get a chance. In the meantime, you should be able to create a script that searches for total class level (should be a herofield), and if above 20, you can assign the tag:

perform hero.assign[Hero.Epic]

[ErinRigh]

Originally Posted by Sendric

I thought there was one already. I will look into it when I get a chance. In the meantime, you should be able to create a script that searches for total class level (should be a herofield), and if above 20, you can assign the tag:

perform hero.assign[Hero.Epic]

Should be able to, but I am just little in the realm of coding, so how about a bit of a walkthrough?

I'd like to create a condition that I can simply click on and set the character as Epic, any thoughts?

[Nightfox]

Originally Posted by ErinRigh

Should be able to, but I am just little in the realm of coding, so how about a bit of a walkthrough?

You are right were I was a couple years ago, and asking all the same types of questions. In a few months you'll be the one helping others.

Originally Posted by ErinRigh

I'd like to create a condition that I can simply click on and set the character as Epic, any thoughts?

If you are willing to deal with it manually a condition could work. Go to the editor and add an adjustment. Name it something easy like "Epic", check the box labeled "Is Condition?".

In the eval script you want something like:

      ~ If we're not enabled, get out now
      doneif (field[pIsOn].value = 0)

      ~ Give our hero the Epic tag
      perform hero.assign[Hero.Epic]

If you want it to automatically add the code when the hero has reached level 21 or above you would need to add an If() statement and find some place to hide it. Conditions are good places to hide these types of things because they are loaded on all characters.

Originally Posted by Illyahr

BAB stops increasing once you hit 20 HD. After that, you get a +1 Epic bonus every odd level. You also no longer get class bonuses to saves and instead get a +1 Epic bonus to saves every even level. Other than that, class abilities are gained as listed by the class.

I think you would need to break it down into individual tasks. For the BAB and saves you would need to be able to figure out what they would be at level 20 and reset then to that value. Then calculate how many levels you have above 20 and divide by 2, round up for attack bonus, round down for saves. The saves bonus could simply be added to the individual saves as normal, but for the attack bonus you would want to add it as a bonus to your hero.child[Attack] or to the [tAtk].value so it doesn't effect the number of attacks the character has from BAB. The really hard part will be figuring out what the character had at 20th.

As for progressing classes beyond 20th, I think that would have to be done as separate classes. For example a single class 30th level fighter would actually have 2 classes, Fighter 20 and Epic Fighter 10. I haven't dug deep into HL in a while, but if I remember correctly it limits the number a classes a hero can have so this may be a problem.