House Rules?

kfeltenberger · January 3rd, 2011, 05:58 AM

One of the things that's always annoyed me about d20 and was carried over to Pathfinder was the maximum Dex bonus based on armor type. Short of recreating every type of armor, is there a way to disable this? I prefer the Dex bonus to be there regardless of armor worn as the various feats offset (or enable) penalties.

Thanks!

risner · January 3rd, 2011, 06:39 AM

Make an adjustment that adds the positive difference between current Dex and Max Dex.

Mathias · January 3rd, 2011, 08:08 AM

You could use a foreach to search through all armor on the character, setting the max dex of that armor to 999. You'd put this on a Mechanic. The max dex is stored in the arMaxDex field, and it looks like Pre-Levels/1000 should be a good phase and priority for this.

kfeltenberger · January 3rd, 2011, 09:06 AM

Quote:

Originally Posted by Mathias

You could use a foreach to search through all armor on the character, setting the max dex of that armor to 999. You'd put this on a Mechanic. The max dex is stored in the arMaxDex field, and it looks like Pre-Levels/1000 should be a good phase and priority for this.

I'm sure one of the programmers in the office understands this, but it's a bit over my ability.

How difficult would this be to implement?

Thanks!

Mathias · January 3rd, 2011, 09:35 AM

In the editor, create a new file - the name doesn't matter, but leave it in the default folder with the default extension. Go to the Mechanics tab, and create a new mechanic. Give it an appropriate name and an Id.

At the top right, press the Eval Scripts button, and create a new script.

At the top of that, set the Phase to Pre-Levels and the Priority to 1000.

Copy the following text into the script:

Code:

 
foreach pick in hero from hero in BaseArmor
  eachpick.field[arMaxDex].value += 999
  nexteach

Exit the script window. Now, in the center-bottom section, find the last option - sources. Create a new source within the house rules section for this house rule.

Save your creation, exit the editor, and press ctrl-r to quick-reload the files.

Now in the configure hero menu, find and enable the source you created for this. Try adding some armor - it should have a max dex of "-" (none).

kfeltenberger · January 3rd, 2011, 03:33 PM

Excellent! Thank you Mathias, this should do the trick!

Kurt

kfeltenberger · April 24th, 2011, 01:33 PM

Real life got in the way of trying this for a while and when I did I ran into an issue. I followed the directions above and when I tried to the "Test Now" button, received an error message:

Hero Lab was forced to stop compilation after the following errors were detected:

Syntax error in 'eval' script for Thing 'KEF001'(Eval script '#1') on line 1
-> Non-existent component 'hero' referenced by script

I've attached a copy of the file to this post. Any pointers on where I messed up?

Thanks!

Kurt

Kendall-DM · April 24th, 2011, 04:32 PM

Quote:

Originally Posted by kfeltenberger

Real life got in the way of trying this for a while and when I did I ran into an issue. I followed the directions above and when I tried to the "Test Now" button, received an error message:

Hero Lab was forced to stop compilation after the following errors were detected:

Syntax error in 'eval' script for Thing 'KEF001'(Eval script '#1') on line 1
-> Non-existent component 'hero' referenced by script

I've attached a copy of the file to this post. Any pointers on where I messed up?

Thanks!

Kurt

I think it's just a coding issue, a few too many hero references in that code. I believe the following code is the correct implementation.

Code:

foreach pick in hero from BaseArmor
  eachpick.field[arMaxDex].value += 999
  nexteach

kfeltenberger · April 24th, 2011, 04:40 PM

Quote:

Originally Posted by Kendall-DM

I think it's just a coding issue, a few too many hero references in that code. I believe the following code is the correct implementation.

Code:

foreach pick in hero from BaseArmor
  eachpick.field[arMaxDex].value += 999
  nexteach

Hmm...that gives me a "Invalid syntax within 'foreach' statement"

Thanks!

ShadowChemosh · April 24th, 2011, 06:19 PM

Attached is a working version based on the .zip file you uploaded. I also fixed the "Source" you had it attached to so that it does not turn on if just any house rule is selected.

So when you add this .user file a new source under "House Rules" will show that says "No armor max dex".

Now when buying armor it will still show a Max dex, but as soon as it is added to your character the max dex will be removed....

kfeltenberger Junior Member Join Date: Jun 2010 Posts: 22 January 3rd, 2011, 05:58 AM	One of the things that's always annoyed me about d20 and was carried over to Pathfinder was the maximum Dex bonus based on armor type. Short of recreating every type of armor, is there a way to disable this? I prefer the Dex bonus to be there regardless of armor worn as the various feats offset (or enable) penalties. Thanks!
#1

risner Senior Member Volunteer Data File Contributor Join Date: Jun 2010 Posts: 623 January 3rd, 2011, 06:39 AM	Make an adjustment that adds the positive difference between current Dex and Max Dex.
#2

Mathias Senior Member Lone Wolf Staff Join Date: May 2005 Posts: 13,213 January 3rd, 2011, 08:08 AM	You could use a foreach to search through all armor on the character, setting the max dex of that armor to 999. You'd put this on a Mechanic. The max dex is stored in the arMaxDex field, and it looks like Pre-Levels/1000 should be a good phase and priority for this.
#3