Feat to add a favored enemy and extra

[Darthane]

Basically, I am trying to make a feat that adds Favored Enemy (humans) at +1 or if they have Favored Enemy (humans) already, give them a +1 untyped bonus to it.

I have tried almost everything I could think of or find (I am a newbie at this, but not new to programming) and nothings seems to work.

Firstly I can't seem to work out how to edit the feHumhuman value and second I am unsure how to check if something is missing with conditionals.

Is there a documented list of syntax for either language (from what I understand, each are different languages)?

The text of the feat (the rules) is as follows: You gain humans as a favored enemy, as per a ranger, with a +1 bonus. If you have a favored enemy that overlaps, this +1 stacks.

 

[Darthane]

Just a bump to this, if anyone can help it would be greatly appreciated. I am completely new to this and am dismayed and lost at the almost complete lack of documentation (even FORTH was easier to find guides for than this).

 

[ShadowChemosh]

Just a bump to this, if anyone can help it would be greatly appreciated. I am completely new to this and am dismayed and lost at the almost complete lack of documentation (even FORTH was easier to find guides for than this).

I would recommend reading the Glossary of Terms for the Editor. Then check out FAQ#2 for all the places to learn about the editor including YouTube videos.

 

[ShadowChemosh]

Basically, I am trying to make a feat that adds Favored Enemy (humans) at +1 or if they have Favored Enemy (humans) already, give them a +1 untyped bonus to it.

Be easier for you to make this "two" feats instead of one. Make one have a pre-req of needing to already having Favored Enemy (Humans). The 2nd one would require that you "Don't' have Favored Enemy Humans.

Then you could do this script to "increase" FE bonus.
Post-Levels/10000

      ~ If we're disabled, do nothing
      doneif (tagis[Helper.FtDisable] <> 0)
      
       ~ Increase Favored Enemy by 1 
      #value[feHumHuman] += 1

The other feat if I would simply have it added as "text" instead of trying to actually add the "Pick" itself. This is because Favored Enemy picks are designed to be added to a specific class. Be better off to simply have the 2nd feat list all the details of the FE ability instead.

 

[Darthane]

Hrmm, okay, will certainly look through those again and watch the videos again. What I mean when I say "make a feat" is that the book is already published and I am trying to make the HeroLab file to accompany it because the guy who normally does that for us is no longer able to.

Looking at how the pathfinder files themselves handle Favored Enemy, I might just add this in as #situational to the relevant fields and be done with it.

Thanks for the help and I will certainly investigate those guides in detail. It is just discouraging, as a programmer, to find no 'definition' of the language from the originators of it :/

 

[ShadowChemosh]

Hrmm, okay, will certainly look through those again and watch the videos again. What I mean when I say "make a feat" is that the book is already published and I am trying to make the HeroLab file to accompany it because the guy who normally does that for us is no longer able to.

Book and programming don't always match up perfectly. Even LW breaks feats up into multiple sometimes to make things easier. One "rules" sentence can make a hundred hours of scripting.

Thanks for the help and I will certainly investigate those guides in detail. It is just discouraging, as a programmer, to find no 'definition' of the language from the originators of it :/

I guess I am confused how help pages, wikis, and videos means "no definition" of the language is present. If you check out that FAQ you can go read the Authoring wiki if you wish.

But yes this is not Oracle meaning you are not going to find Java Docs.

 

[Darthane]

I guess I am confused how help pages, wikis, and videos means "no definition" of the language is present. If you check out that FAQ you can go read the Authoring wiki if you wish.

But yes this is not Oracle meaning you are not going to find Java Docs.

I guess I was hoping for a syntax of all program-flow features. While I didn't expect all the variables and data from the Pathfinder system to be fully documented, I hoped it would be easier to learn this than how it is right now.

The only issue I am having now is that I need to add these situational reminders to the knowledge skills (all of them) and am unsure if there is a way I can just say 'all' or if I am going to have to do an if statement for each one to make sure it is visible?

EDIT: Hey, I found a definition, I am at least not flying blind structurally. That wiki, imho, needs to be one of the first things pointed to for programmers, not at the bottom of a list >.>

 

[ShadowChemosh]

EDIT: Hey, I found a definition, I am at least not flying blind structurally. That wiki, imho, needs to be one of the first things pointed to for programmers, not at the bottom of a list >.>

Most people I help on here are NOT programmers. Heck I know one is a retired fire-fighter. That wiki would have given him a heart attack.

For all knowledge skills you will want to do a Foreach loop to loop through all the active Knowledge Picks on a character.

 

[Aaron]

You might want to look at some of the new tutorials and resources I'm designing for 5e. Although the fields and tags will be different, most of the concepts I am covering are universal to HL.

foreaches, for example, will be covered in the Tag expression section I will be putting out next release.