• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

d20pfsrd Data Sets - Powered by Hero Lab....

Status
Not open for further replies.
Tomb of the Iron Medusa:
Module_Tomb of the Iron Medusa.user: <usesource source="srcTombIrM"/>

This file contains items that are not PFS legal without a chronicle sheet.

Infensus Mucro
Gown of Resistance, +4

I've built the Gown for the future PFS-Boons files.

If we could mark the Gown and the Mucro in the file as not legal for PFS, this would help.
Thanks for the report. Will try and have this in the next update.
 
Hmm I got moved to requested thread.

But I solved my problem by making an adjustment:
Code:
  <thing id="pGearAddCo" name="Gear Add Contents list" description="Add contents to gear CustDesc" compset="InPlay">
    <comment>v1.0: Risner</comment>
    <fieldval field="pUsePicks" value="1"/>
    <usesource source="PFS_Boons" parent="UserParent" name="PFS Boons"/>
    <tag group="Adjustment" tag="S2Custom" name="Custom Menu" abbrev="Custom Menu"/>
    <tag group="Helper" tag="NoIncr" name="NoIncr" abbrev="NoIncr"/>
    <eval phase="First" index="3"><![CDATA[~ If we're not enabled, get out now
doneif (field[pIsOn].value <> 1)
~ If nothing chosen, get out now
doneif (field[pChosen].ischosen <> 1)

   field[pChosen].chosen.field[CustDesc].text &= "\n\nContents:\n" & field[pChosen].chosen.gearlist["; ", TRUE]]]></eval>
    <eval phase="PreLevel" priority="11000" index="2"><![CDATA[      ~ If we're not enabled, get out now
      doneif (field[pIsOn].value = 0)

      ~ Picks on Hero
      field[pUsePicks].value = 1

      ~ Set search to daze or prone
      field[pCandExpr].text = "component.BaseEquip & thing.holder"]]></eval>
    </thing>

Shadow, can you add this to the adjustments community list?
Don't see why not. :)
 
Hi. Im getting missing sources opening Realm of the Fellnight Queen module portfolios.

Specifically on the bees and queen.
 
Hi. Im getting missing sources opening Realm of the Fellnight Queen module portfolios.

Specifically on the bees and queen.
You can right click on the error message and paste it here. It maybe something that can be fixed.

The other issue is you may be missing source if it uses a book you don't own. The CB lists the minion required packages to load. It does NOT list every book every .por uses. Which can often be more. For example the Reign of Winter AP uses stuff from Paths of Presitage and the People of the North. But those packages are not required to LOAD the CB.
 
Errors were encountered when loading the saved portfolio! A record of these errors can be found in the file "C:\Users\Lee\AppData\Local\Temp\hero_lab_load_issues.log". If you notice incorrect behaviors in your portfolio, please report it to the data file authors (you can contact them from the Help menu).

Critical information not found in data files: Source 'Realm of the Fellnight Queen'
Critical information not found in data files: Source 'Realm of the Fellnight Queen'

After selecting the module in Configure Hero and resaving the portfolio, still get the above error.
 
You can buy a Scarf of the Suggestive Dance without the sheet and HL
doesn't show an error.

Also seems to be Poison, Maiden Lily Attar?

I'll be putting the Scarf of the Suggestive Dance into the PFS Boon file.
 
You can buy a Scarf of the Suggestive Dance without the sheet and HL
doesn't show an error.
I don't really know what this means. I looked at what you did for that PFS Boon file and I assume you mean you want to look for a specific Journal. If that is the case I doubt I want to put that into the CB/CPP actually as its very CPU intensive script.

This stuff was never built with PFS play in mind actually. So why I don't mind marking things that are NOT for PFS. I am not sure about putting in CPU intensive scripts for journals that have to have very specific text. I try and keep in mind that we have people running this software on net books and iPad 2 now. Those are NOT very powerful machines and the more CPU we eat up the more battery life we are eating up also. These are things I have to keep in mind now.


Also seems to be Poison, Maiden Lily Attar?
Also what? Needs a special journal or is not PFS allowed?

I'll be putting the Scarf of the Suggestive Dance into the PFS Boon file.
I am not a big fan of duplicating Things to multiple packages actually. If the Paizo modules are becoming PFS allowed then I can see people needing access to the CPP then for game play during PFS.

Instead of looking for specific journal I think I like the idea of marking these Things as NOT PFS allowed and including an Adjustment to remove that tag. Then on the Adjustment the Boon Information could be stored instead. I think this would work out nicely as the default character sheet can even print the Adjustments that are on a character so that gives a nice note then for DM's looking at the character sheet.

Thoughts?
 
Instead of looking for specific journal I think I like the idea of marking these Things as NOT PFS allowed and including an Adjustment to remove that tag. Then on the Adjustment the Boon Information could be stored instead. I think this would work out nicely as the default character sheet can even print the Adjustments that are on a character so that gives a nice note then for DM's looking at the character sheet.

Thoughts?

In my opinion, there's no need for an adjustment. The rules say this item isn't allowed for PFS characters. You have specific GM permission, because you have a signed chronicle sheet, allowing you to break that rule. I think Hero Lab should still show that as an error, so that anyone who looks at your character sheet knows to check for a chronicle sheet that allows you to break that rule.
 
In my opinion, there's no need for an adjustment. The rules say this item isn't allowed for PFS characters. You have specific GM permission, because you have a signed chronicle sheet, allowing you to break that rule. I think Hero Lab should still show that as an error, so that anyone who looks at your character sheet knows to check for a chronicle sheet that allows you to break that rule.
I do agree this is a valid point and understand that this is LW's stance on the subject. I also see the people complaining that they don't want the warning messages in HL because what they have is valid. As I do nothing with PFS at all I really have no stake in either side other than I can understand them.
 
understand that this is LW's stance
... see the people complaining that they don't want the warning messages

LW's stance doesn't work for PFS players, mostly because PFS players (like me) won't accept it. Also Paizo stresses their VC's to do audits and if your character posts an error in HL then it makes those audits take longer of the game time and everyone at the table gets more frustrated as it takes longer.

I don't really know what this means.

Sorry, I mean that:
Scarf of the Suggestive Dance
Poison, Maiden Lily Attar

They are both not PFS legal, but the Scarf is legal with the Chronicle sheet.

I am not sure about putting in CPU intensive scripts for journals that have to have very specific text

Hmm, maybe plan B:
Put all the entries in the community file as not PFS legal, and provide two options:
1) Use my Adjustment to mask the error
2) Add a new adjustment that searches chronicle sheets and enables anything present on the sheet they have the chronicle. I'd want my players using this and I'd use it for myself for more checks-and-balances.
 
ShadowChemosh,

If they don't like seeing the Validation messages they can do Control-K and scroll down the side bar to Output Options and check off "Hide Validation Messages" to remove them from their sheets. I don't recommend this for a Pathfinder Society game, but for a home campaign where the GM has given permission to do this, its an option. Personally, I like to see the validation errors on sheets and require the portfolio be sent to me so I can validate the character personally before allowing it into my campaigns. I just wish I had this software back in 3.5 when I ran RPGA events. It would have made my life alot easier back in those days.
 
LW's stance doesn't work for PFS players, mostly because PFS players (like me) won't accept it. Also Paizo stresses their VC's to do audits and if your character posts an error in HL then it makes those audits take longer of the game time and everyone at the table gets more frustrated as it takes longer.

The intent is to aid this sort of audit - we're flagging these as things a GM who audits a sheet should double check, because without a signed chronicle, they're not allowed to do that. The player of a character who has one of these errors should be able to quickly open up the printed chronicles and show the GM that he is allowed to break this rule by selecting a particular item or because he's got a non-standard race.
 
You should always have your "Comp" sheets with your character sheet and expect the "Judge" running your PFS events to audit them anyway. I don't see how having the Validation error on the sheet makes it take any longer personally. The Validation Report shows exactly what causes the error message. As Mathias said, your judge should be able to use the validation message to go straight to the error and know what it is. Now if they have to audit your comp sheets I can see that taking time, it used to take time to get some of the living Forgotten Realms and Greyhawk comp sheets validated at events I ran, but that was just part of the process of dealing with Living Campaign rules.
 
The intent is to aid this sort of audit

Chalk it up to a difference in opinion. Some people (like me) really don't like it telling me I'm invalid. It literally makes me check the validity tab every day or more often. Just to make sure I'm good and the thing it is screaming to me is valid or simply because it doesn't know I'm ok. So while it may work for some, it is simply put *not acceptable in any way at any time* for me.
 
Well we have the validation report for obvious reasons. You may not agree with it, but it helps keep players honest and simplifies my job validating characters in my personal campaigns. My first experiences with hero lab were for a much larger group of 35 players in a white wolf campaign, and I had to validate every sheet that came through. It was easier to have them all in hero lab and just check the validation report for it than to deal with verifying every single sheet by hand.
 
Well we have the validation report for obvious reasons.

We are kinda talking about different things.

I'm talking about the big red ! in the top left and the fact that players don't like that to be present when there character is legal.

You are talking about looking at the validation report to catch errors.

Vastly different things.

I will not accept a big red ! on a character that is legal. I'm not alone.
 
Got a couple of duplicate record errors after the 7.17 update that look like they might be due to conflicts with community user files, but I don't know in which files the user versions are located:

Duplicate records are lErudaki (from AP051) and fOverwhelm (from SGG Book of Runic Might II).
 
Status
Not open for further replies.
Back
Top