Lone Wolf Development Forums  

Go Back   Lone Wolf Development Forums > Hero Lab Forums > HL - Pathfinder Roleplaying Game
Register FAQ Community Today's Posts Search

Notices

Reply
 
Thread Tools Display Modes
ShadowChemosh
Senior Member
Volunteer Data File Contributor
 
Join Date: Jan 2010
Location: Chicago, IL (USA)
Posts: 10,729

Old January 27th, 2016, 08:28 AM
@Quintain can you list the "game" rules you are trying to do? One minute you make it sounds like its a PrC which Aaron tries to answer but then you put the scripts onto a feat. Maybe I am the only the only that is now confused but please list "what" game rule you are trying to implement. Is this a PrC, Archetype or just a feat?

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.
ShadowChemosh is offline   #11 Reply With Quote
ShadowChemosh
Senior Member
Volunteer Data File Contributor
 
Join Date: Jan 2010
Location: Chicago, IL (USA)
Posts: 10,729

Old January 27th, 2016, 08:59 AM
Quote:
Originally Posted by Quintain View Post
I saw on a differrent post that "linkage[varies]" is the same as hero.childfound
So this statement is not correct. Linkage[varies] is a link between an Archetype and the "base" class it is "linked" too. "hero.childfound" allows you to search for ANY Pick that is live on the character.

Above Aaron is showing you that a Class Helper has a "link" to which attribute it uses for Psionics. This is represented using "linkage[psiattr]" which links the Class Helper directly to the "attribute" score it uses. The linkage is set in the editor and can't be changed once set. But it makes it easy for the class to go to the linked attribute without having to use "tags".

Still not 100% sure what your trying to implement but it sounds like "Pulling" the "UseAttr.?" tag from the linkage[psiattr] is what you want. Then you can simply delete the "UseAttr.?" tag on fPUUnwillP feat and "push" the one you pulled from the Linkage onto the feat. This way you won't have to care which actual ability score the class works with.

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.
ShadowChemosh is offline   #12 Reply With Quote
Quintain
Senior Member
 
Join Date: Feb 2012
Posts: 546

Old January 27th, 2016, 07:29 PM
Quote:
Originally Posted by ShadowChemosh View Post
@Quintain can you list the "game" rules you are trying to do? One minute you make it sounds like its a PrC which Aaron tries to answer but then you put the scripts onto a feat. Maybe I am the only the only that is now confused but please list "what" game rule you are trying to implement. Is this a PrC, Archetype or just a feat?
Shadow,

It's just a feat. One of my own devising. Since the unwilling participant feat is based off of Wisdom, and there are classes with collectives based off Int and potentially Cha, I was making a feat that switched the attribute used and added one to the DC.

Part of what I saw as the problem was a character could potentially have more than 1 collective based off different attributes. So, I was trying to make the feat always work on the highest attribute mod automatically.

So, with multiple possible classes with multiple possible attributes and multiple collectives, I was looking for a way to have that calculation be automatic.

This proved unworkable, so I decided to fall back on letting the user choose.
Quintain is offline   #13 Reply With Quote
ShadowChemosh
Senior Member
Volunteer Data File Contributor
 
Join Date: Jan 2010
Location: Chicago, IL (USA)
Posts: 10,729

Old January 27th, 2016, 08:01 PM
Quote:
Originally Posted by Quintain View Post
This proved unworkable, so I decided to fall back on letting the user choose.
A simple chooser is most often best. Even LW tries not to figure out the 'best' score as doing all the logic checks and the foreach loops required is "allot" of overhead. Its better to just let the gamer choose. In that case look at THIS post where I give the script to change the attribute for the Unwilling Participant feat. Change the "xxx" then to "field[usrChosen1].chosen".

Update: The post I linked too would be assuming the drop down selection is the Psionic Class "helper". If you want to select based on "attribute" remove the "linkage" part leaving the first statement as "field[usrChosen1].chosen.pulltags[UseAttr.?]"

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.

Last edited by ShadowChemosh; January 27th, 2016 at 09:59 PM.
ShadowChemosh is offline   #14 Reply With Quote
Quintain
Senior Member
 
Join Date: Feb 2012
Posts: 546

Old January 28th, 2016, 07:41 AM
Yeah, I came to that conclusion myself.

Here's the final result on my code that came up with that looks like it's working -- it doesn't reference a specific class, just limits the attribute list to Intelligence, Wisdom or Charisma and does the calculations based on which one is chosen.

It works, although it could probably be shortened with the pull/pushtags options in your other post.

Code:
~ replace the Wis Modifier of Unwilling Participant with 
~ chosen key ability modifier
~if the user hasn't selected an attribute, there's nothing more we can do
  doneif (field[usrChosen1].ischosen = 0)

  var vKAb as number
  
~set our focus to the chosen attribute. This saves typing later
    perform field[usrChosen1].chosen.setfocus

if (focus.tagis[thingid.aINT] <> 0) then
  vKAb = #attrmod[aINT]
elseif (focus.tagis[thingid.aCHA] <> 0) then    
  vKAb = #attrmod[aCHA]
else
  ~ go with the default
  vKAb = #attrmod[aWIS]
endif

  #dc[fPUUnwillP] += 1 + (vKAb - #attrmod[aWIS])
Quintain is offline   #15 Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 04:10 PM.


Powered by vBulletin® - Copyright ©2000 - 2024, vBulletin Solutions, Inc.
wolflair.com copyright ©1998-2016 Lone Wolf Development, Inc. View our Privacy Policy here.