Junior Member
Join Date: Feb 2013
Posts: 18
|
I used the *Preclude tab to hide the core shield when my source is selected. So when the source is selected, my shield versions show up and the core doesn't.
I have attached the .user file if you want to look at it. |
#11 |
Senior Member
Join Date: Oct 2011
Posts: 6,793
|
You sure you don't want to do it with a mechanic and a foreach? That's extend to all current and future shields, so you wouldn't have to constantly update the precludes or replacements...
Only downside would be the bonus displayed when initially buying the shield wouldn't include your bonus. |
#12 |
Junior Member
Join Date: Feb 2013
Posts: 18
|
I'd love too...but I have been reading through the scripting rules and am really unclear how to go about it.
The mechanic would probably work better especially as I was planning on using a lot of pre-generated characters (I hav just started a Kingmaker campaign) and I would have to fix up anyone with any time of shield. Last edited by Matt Harris; March 7th, 2013 at 02:26 PM. |
#13 |
Senior Member
Join Date: Oct 2011
Posts: 6,793
|
Alright, so here is what I recommend. Delete your precludes, and the new shield versions, then update the eval script on your mechanic to run at Pre-Levels 500 and look like this:
Code:
~ Stop if we are not currently using the house rules. doneif (hero.tagis[source.MJH_HRules] = 0) ~Cycle through all armor type things which are Shields or Tower Shields. foreach pick in hero from BaseArmor where "ArmorClass.Shield | ArmorClass.Tower" ~ Now check to see which shield class this shield is, and apply an appropriate bonus. ~ Light shields get a +1 bonus. if (eachpick.tagis[ShldClass.Light] <> 0) then eachpick.field[arAC].value += 1 endif ~ Heavy and Tower shields get a +2 bonus. if (eachpick.tagis[ShldClass.Heavy] + eachpick.tagis[ShldClass.Tower] <> 0) then eachpick.field[arAC].value += 2 endif nexteach |
#14 |
Senior Member
Join Date: Oct 2011
Posts: 6,793
|
I tested this and it seems to be working. You didn't mention any changes to Bucklers, so I left them alone.
|
#15 |
Senior Member
Volunteer Data File Contributor
Join Date: Jan 2010
Location: Chicago, IL (USA)
Posts: 10,729
|
Quote:
Only thing I see that is an issue. If you like Aaron's way better that is cool too. My players find it confusing when they buy something with "X" values and it shows up on the character with "Y" values. Why I was leading you down this path instead. Hero Lab Resources: Pathfinder - d20pfsrd and Pathfinder Pack Setup 3.5 D&D (d20) - Community Server Setup 5E D&D - Community Server Setup Hero Lab Help - Hero Lab FAQ, Editor Tutorials and Videos, Editor & Scripting Resources. Created by the community for the community - Realm Works kickstarter backer (Alpha Wolf) and Beta tester.- d20 HL package volunteer editor. |
|
#16 |
Junior Member
Join Date: Feb 2013
Posts: 18
|
Excellent! That will save so much work.
Thank you ever so much. ShadowChemosh - thanks for your help as well. I am sure I will find a use for the stuff I learned from you, too. |
#17 |
|
|