Community Effort: Feats

[MagicSN]

Hmmm, seems to be easier than I thought with the editor after all...

Still would prefer a .dat files release so one can get the complete overview of things in the implementation.

[Elindor]

I'm probably not going to be contributing to feats too much for the rest of the week - my priority is (hopefully understandably) covering the non-SRD material being used in the D&D game I'm running. I think I'm doing quite well - in addition to all of the feats, I've got one subrace and three sub classes (with all features) in a usable state (not as polished as I'd like, but I take what I can get), and a fallback strategy for Variant Human if I can't work out how to add a feat that the user can choose. So my immediate plan will be to deal with the two remaining subclasses and add in the spells I need (even if they're just placeholders at this time).

There is, however, some interesting design space in the feats, so I'll probably swing back into it in short order. But for now, sleep beckons - I've got work in the morning *yawn*

[Tesh]

Not sure if this is correct thread to ask this question, but if you are not a programmer or the knowledge do all the editing that you guys are doing, is there is there away to add them or just need to wait for updates?

[daplunk]

This information is enough for a non programmer to add this information in. You are just copying the steps and code provided into the matching fields in the editor.

The green ones are complete and functional. Orange is partially complete. Red is still work in progress.

I will post a tutorial with images in a bit as an example.

[ShadowChemosh]

Originally Posted by daplunk

This information is enough for a non programmer to add this information in. You are just copying the steps and code provided into the matching fields in the editor.

The green ones are complete and functional. Orange is partially complete. Red is still work in progress.

I will post a tutorial with images in a bit as an example.

Why go through all that instead of just making actual .user files that can be shared? As has been mentioned the community can add the missing pieces of the SRD.

If all the separate people adding stuff started to work together it would go so much faster. Right now its like 20 people each doing there own thing.

[daplunk]

Its probably the way to go. I'm assuming however changes will need to be made.

Feat Names changed
Feat Descriptions removed

I'm assuming community files can only contain the mechanism.

Can anyone confirm?

[ShadowChemosh]

Originally Posted by daplunk

I'm assuming community files can only contain the mechanism.

Can anyone confirm?

Yep it has been CONFIRMED.

Basically you can most likely get away with the same "Name" of a Thing but you only want to list the Mechanics of the ability. So lets say "Dodge" feat (Sorry I don't know 5e) from 3.5. Call it "Dodge" but list a very simple text of +1 AC bonus.

Then take a look at my NOTE here about consistent file names and pick a two digit unique ID and how to set that.

Next stage of this is to compile the .user files into working version called Package or .hl file. This can be setup on the community servers with a working Update URL. Meaning that people will be able to download and install this community Pack really easily. In addition HL will tell gamers when a new version is out and will even prompt gamers to download and install.

This means you reach a MUCH larger audience.

[daplunk]

Thanks Shadow.

Not sure I'm the right person to be taking the lead on this. The only reason i have availability is because i'm home with a 2 week old /zzzzzzz

[daplunk]

NOTES - Pathfinder Scripting:

Two Weapon Defense

~ If we're disabled, do nothing
doneif (tagis[Helper.FtDisable] <> 0)

~ Check to see if we have something equipped in each hand
doneif (hero.tagis[Hero.EquipMain] + hero.tagis[Hero.EquipOff] < 2)

~ Check to see that we have at least two weapons equipped, or a double
~ weapon
if (hero.tagcount[Hero.EquipWep] < 2) then
doneif (hero.tagcount[Hero.EquipDbl] = 0)
endif

~ Check to see if our Unarmed Strike is selected in either main or off
~ hands
doneif (hero.child[wUnarmed].tagis[Hero.MainHand] + hero.child[wUnarmed].tagis[Hero.OffHand] > 0)

~ Otherwise, add a +1 Shield bonus to our AC
#applybonus[tACShield, hero.child[ArmorClass], field[abValue].value]

~ If we're in output mode, don't do anything
doneif (state.isoutput <> 0)

#appenddesc[pstTotDef,"{b}Addition from Two-weapon Defense{/b}: When wielding a double weapon or two weapons (not including natural weapons or unarmed strikes), you gain a " & signed(field[abValue].value) & " shield bonus to your AC.{br}{br}When you are fighting defensively or using the total defense action, this shield bonus increases to " & signed(field[abValue2].value) & "."]
#appenddesc[pstFtDefen,"{b}Addition from Two-weapon Defense{/b}: When wielding a double weapon or two weapons (not including natural weapons or unarmed strikes), you gain a " & signed(field[abValue].value) & " shield bonus to your AC.{br}{br}When you are fighting defensively or using the total defense action, this shield bonus increases to " & signed(field[abValue2].value) & "."]

~ if we're fighting defensively or total defense, the shield bonus increases to +2
if (#hascondition[pstFtDefen] + #hascondition[pstTotDef] <> 0) then
#applybonus[tACShield, hero.child[ArmorClass], field[abValue2].value]
endif

Aldori Dueling Mastery

~ If we're disabled, do nothing
doneif (tagis[Helper.FtDisable] <> 0)

~ If we have a shield, do nothing, we are done.
doneif (hero.tagis[Hero.EquipShld] <> 0)

~ If we have something in our off hand, is it an Aldori Dueling sword wielded 2 handed? If so set our bonus to 1, if not, done.
var shield as number
if (hero.tagis[Hero.EquipOff] <> 0) then
foreach pick in hero from BaseWep where "IsWeapon.wDuelSwo"
if (eachpick.field[gIsEquip].value + eachpick.field[wIs2nd].value = 2) then
shield = 1
endif
nexteach

doneif (shield = 0)

~ If we don't have something in our off hand, is an Aldori Dueling sword equipped in 1 hand? If so set our bonus to 2, if not, done.
elseif (hero.tagis[Hero.EquipOff] = 0) then
foreach pick in hero from BaseWep where "IsWeapon.wDuelSwo"
if (eachpick.field[gIsEquip].value = 1) then
shield = 2
endif
nexteach
doneif (shield = 0)
endif

~ Add the shield bonus to our Value field, and then add that as a shield bonus to AC. Doesn't stack with other shield bonuses (like the spell)
field[abValue].value += shield
#applybonus[tACShield, hero.child[ArmorClass], field[abValue].value]

~ If we're disabled, do nothing
doneif (tagis[Helper.FtDisable] <> 0)

~ Assign the piercing weapon tag so dueling swords work with Duelist abilities.
foreach pick in hero from BaseWep where "IsWeapon.wDuelSwo"
perform eachpick.assign[wType.P]
nexteach

~ Do we have a dueling sword equipped in either hand? If so +2 Init.
foreach pick in hero from BaseWep where "IsWeapon.wDuelSwo"
if (eachpick.field[gIsEquip].value + eachpick.field[wIs2nd].value <> 0) then
hero.child[Initiative].field[Bonus].value += 2
endif
nexteach

Armor Proficiency (Heavy)

Type: Expr-reqs
Message: Armor Proficiency (Light) required.
tagis[Hero.ProfLight] <> 0
tagis[Hero.ProfMedium] <> 0

[Starchildren3317]

Originally Posted by daplunk

NOTES - Pathfinder Scripting:

So, you're the man, just saying.