I know that the LSJ PrC "Temptress" is not ready, but the cells to calculate the BAB and Saves have a Value Error problem from the related Custom PrC cells.
Err, that's on the DataClasses tab.
Grin. Good thing that I made sure I consulted the Bestiary as well when doing some of the LSJ races. :)I did notice the aasimar and tiefling are nearly identical, except for the favored classes. I'm assuming the renaming with an LSJ tags works okay? That's how I've handled things like duplicate Domain names as well. I was wondering on the feats--it looks like some are now duplicates of the Bestiary feats. Should I tag those as LSJ-specific or remove them in favor of the core feats?
Don't worry about the favored classes any more. Those rules were a missed holdover from BETA and favored classes are exactly as mentioned in the PFRPG Core Rulebook.
Go ahead and label the tags LSJ-specific. It makes things a lot easier. We haven't looked at the Bestiary feats yet. I'll let you know which one takes precedence for any duplications.
First, I've got a workaround for now on the duplicate names in the Feat lookups. I've changed certain ones--Acrobatic, Dodge, and Run specifically--to all-caps since that will force the formula to see them properly. Not the greatest solution, but it works for now...
A few more errors I have found:
Error on the front page tab under the SENSES section (the Perception modifier). Here is the corrected formula: =VLOOKUP("Perception",Table_Skills_Known,24,0)
I know that the LSJ PrC "Temptress" is not ready, but the cells to calculate the BAB and Saves have a Value Error problem rom the related Custom PrC cells. Under the Class Abilities tab, the Godly Gift ability should be >3 (not >4).
That's all for now. :)
Nice catch on the Perception...all fixed!
Don't worry about the favored classes any more. Those rules were a missed holdover from BETA and favored classes are exactly as mentioned in the PFRPG Core Rulebook.
Go ahead and label the tags LSJ-specific. It makes things a lot easier. We haven't looked at the Bestiary feats yet. I'll let you know which one takes precedence for any duplications.
I'll switch all the favored classes to Any One then. Do you want me to remove the aasimar and tiefling from the LSJ section since they are now core?
Do you want me to remove the aasimar and tiefling from the LSJ section since they are now core?
Sure, I have no problem with them being moved to Core.
Also I noticed on the Front Page tab under the Saving Throw boxes ... for some reason there is a "1" listed in each of the Race Boxes for all three saves. This is with Human being selected for the PC's race.
Sure, I have no problem with them being moved to Core.
Do you want me to remove the aasimar and tiefling from the LSJ section since they are now core?
Done...
Also I noticed on the Front Page tab under the Saving Throw boxes ... for some reason there is a "1" listed in each of the Race Boxes for all three saves. This is with Human being selected for the PC's race.
This is similar to the Perception issue you noted earlier and was also pointed out above--specifically the VLOOKUP was looking two rows too early. Fixed for the next version...
Okay folks, this is my last big push before declaring this "Version 0.7" and sending it over to the Pathfinder Database as the latest official version. I've fixed all the errors noted to date, and also done some work to help usability, including cell-by-cell instructions on the Character Options main section, "red flags" on all the selectable/changeable cells on the Front and Back tabs, and the addition of a What Is This tab to give folks the basic idea and discuss customization. I'd definitely like feedback on this particular change. I'll be finalizing the Shaman over the weekend and getting it in place, but barring catastrophic issues that prevent testing I won't release another version before hitting v.0.7 (incorporating the Shaman change and any bugs noted up to next Monday). So, test away and let me know what you find!
Thanks, as always...
The character sheet is great and almost exactly what I was looking for, but is there a way to increase the size of the Racial Abilities box? The last few lines of info about my Dwarven Cleric of Torag is missing!
The character sheet is great and almost exactly what I was looking for, but is there a way to increase the size of the Racial Abilities box? The last few lines of info about my Dwarven Cleric of Torag is missing!
Yeah, the dwarf has a huge racial block...I meant to lock that sheet but allow formating of locked cells, so a user could enlarge/reduce font size as needed. I'll have that in for the final release. For this version, all you have to do is unlock the sheet and you can change the font size as needed.
Okay folks, this is my last big push before declaring this "Version 0.7" and sending it over to the Pathfinder Database as the latest official version. I've fixed all the errors noted to date, and also done some work to help usability, including cell-by-cell instructions on the Character Options main section, "red flags" on all the selectable/changeable cells on the Front and Back tabs, and the addition of a What Is This tab to give folks the basic idea and discuss customization. I'd definitely like feedback on this particular change. I'll be finalizing the Shaman over the weekend and getting it in place, but barring catastrophic issues that prevent testing I won't release another version before hitting v.0.7 (incorporating the Shaman change and any bugs noted up to next Monday). So, test away and let me know what you find!
Thanks, as always...
Hmm. For some reason the feats no longer appear on the Abilities & Feats tab.
Ah monkey-nuggets...messed up one of the fields by adding descriptive text. Incremental update to fix...
Not sure if its just me or the sheet, but if you take Eldritch knight, it gives you an extra spell progression at level 1.
Not sure if its just me or the sheet, but if you take Eldritch knight, it gives you an extra spell progression at level 1.
Good catch--I had the VLOOKUP correct in the ability description but not in the actual caster level increase calculation. Fixed.
I am unsure if the Skill Focus feat grants you an additional +3 (to +6) when you have 10 ranks in that specific skill...
I am unsure if the Skill Focus feat grants you an additional +3 (to +6) when you have 10 ranks in that specific skill...
Hmm, that one was acting funny, but I finally figured out the VLOOKUP was pointing two cells too early. Fixed.
All, please note I'm looking to finalize v.0.7 to upload to the Pathfinder DB tonight. Please post any findings before that time and I'll work to get any required fixes in place. I am particularly interested in hearing fr my Mac, Linux, and OpenOffice folks to ensure everything is looking good on these various platforms. Thanks!
|
Question on the pull down for armor:
Progression of many armors are:
Pluses to armor (which I found)
Type of ammor (leather, studded, chain, plate, etc) (which I found)
Material of armor (normal, mithral, dragon scales, wood :) ) (which I cannot find).
Bonuses (Masterworked, +1, +2, +3, etc) (which I found)
Example:
Chain shirt (base cost)
Mithral Chain Shirt (1100 gp)
+1 Mithral Chain Shirt (2250 gp)
Thanks
Robyn
Aha, found it in very tiny type underneath the other line (wow small type)
Error found:
Curved Elven blade allows access to the Weapon Finesse Feat for using Dex for bonus to hit (just like Rapier and light weapons), special feature of the CEB
Dagger set for melee does not access Weapon Finesse Feat (same as above), but set it for ranged and the sheet does give access to dex bonus to hit
Ah, you hid it on the BAB line, as a switch to change the bab mod based on a selectible stat (very sneaky).
|
|
All, please note I'm looking to finalize v.0.7 to upload to the Pathfinder DB tonight. Please post any findings before that time and I'll work to get any required fixes in place. I am particularly interested in hearing fr my Mac, Linux, and OpenOffice folks to ensure everything is looking good on these various platforms. Thanks!
Erian,
Looks very good on my Macintosh running Office 2008.
Typical message on startup about the incompatibility of inherent 2003 macros.
But prints nicely on my HP Color laserjet.
Thanks
Robyn
Three very minor fixes, all on armor and shields.
Cell Back!CR16
Change the initial the formula from:
=IF(OR(CM19="Mithral",CM19="Darkwood"),VLOOKUP(BP13,Table_Armor,10,0)/2,VLO OKUP(BP13,Table_Armor,10,0))
to
=VLOOKUP(BP13,Table_Armor,10,0)/IF(AND(Front!B8="Small",OR(CM19="Mithral",C M19="Darkwood")),4,IF(OR(Front!B8="Small",CM19="Mithral",CM19="Darkwood"),2 ,1))
This moves the IF statement to just changing the divisor, and tests for the combination of Small and Darkwood/Mithral
Cell Back!CR25
change the initial formula to:
=VLOOKUP(BP22,Table_Armor,10,0)/IF(AND(Front!B8="Small",OR(CM19="Mithral",C M19="Darkwood")),4,IF(OR(Front!B8="Small",CM19="Mithral",CM19="Darkwood"),2 ,1))
Does the same thing as above.
Cell Back!BX29
Change the formula to:
=IF(VLOOKUP(BP22,Table_Armor,5,0)="-","-",VLOOKUP(BP22,Table_Armor,5,0)+IF( CM28="Mithril",2,0))
This gets rid of a #VALUE error for max DEX for shields when the data pulled from the table is non-numeric. You may need to make sure that the long-hyphen is copied correctly between the quotation symbols to ensure a match.
I know of a non-VBA method of getting dynamic dropdowns to work; this could be used to greatly reduce the sorting clutter on selecting weapons from the drop downs, and from pulling feats from limited feat lists.
Two more armor fixes:
In cell Back!BV16, add the following to the end of the formula:
IF(Lvl_Ftr<3,0,ROUNDUP(0.25*(Lvl_Ftr-2),0))
In cell Back!CB18, you'll be inserting the same element inside the last parenthesis, so that Armor Training won't give an Armor Check penalty of greater than 0.
After determining Armor_Cat, once the armor category has been modified for Mithril, movement speeds should also be modified as follows:
IF(Lvl_Ftr>7,"Light",IF(AND(Armor_Cat<>"Heavy",Lvl_Ftr>3),"Ligh t",Armor_Cat))
This gets the other (major) benefit of Armor Training in for fighters. I'd suggest an exact place for that to go in, but I think you're going to have to define another named variable in this - and that's beyond the scope of changes I'll make in someone else's sheet sans permission.
Class Abilities!E86
Replace the word peantly with penalty in the description of Armor Training.
I'd suggest an exact place for that to go in, but I think you're going to have to define another named variable in this - and that's beyond the scope of changes I'll make in someone else's sheet sans permission.
Great suggestions one and all from what I can tell. I'll incorporate these before releasing v.0.7.
As for reserving comments/other changes without permission, please feel free! I by no means claim to be an Excel expert and what skills I have come from copying/studying better solutions than whatever I've cobbled together in the past. So long as it doesn't "break" the sheet for compatibility with Mac/Linux, OpenOffice, and older versions of Excel I'm all for it...
Thanks!
EDIT: To state that more specifically, I wouldn't care if you recommended changes for every cell in the spreadsheet if it'll make this a better tool!
Character Options, cell C63 and C64 are not showing the cumulative tallies for extra Swift Foot and Damage Resistance rage powers.
Again, great job on everything.
Will you be adding the soon to be out new base classes for Pathfinder? The playtest will start with Cavalier and Oracle.
I'm not sure if Paizo will allow it (i.e. they have to be released as Open Game Content) but if so I'm definitely interested in doing so and think it might help the playtest. I'll check with them--perhaps if I clearly mark them as BETA or some such that would work.
Found the source of a #NAME error.
Feats!H15
Formula should be:
="Swift Action, weapons deal +"&1+FLOOR(MAX(CL_Sorcerer,CL_Wizard,CL_Bard)/5,1)&" dmg and are considered magic vs. DR"
rather than
="Swift Action, weapons deal +"&1+FLOOR(CL/5,1)&" dmg and are considered magic vs. DR"
It's complaining that CL is not a valid name to be divided by 5.
Is there another variable name that already shows the maximum of a character's Arcane sorcerer levels?
I've added two conditional formats to cell Back!CN16. They need to be entered in the following order:
=AND($BF$16="Heavy",Lvl_Ftr>6,$CN$16="Yes")
=AND($BF$16="Medium",Lvl_Ftr>2,$CN$16="Yes")
Both of these turn the cell light green; this is a visual reminder that if you're a fighter of a high enough level, you don't get a speed reduction for wearing heavy armor. This solves the problem I mentioned earlier about inserting a named variable to handle this. You already have a 'no speed reduction' override, this just reminds players they can use it when it's appropriate.
The feat drop downs for the fighter bonus feats in Character Options have
Weapon Focus
Weapon Specialization
(And the Greater versions of these)
rather than the
Weapon Focus []
Weapon Specialization []
where you can enter the weapon type in them in the square brackets, like the general feat drop downs do on that page. I'm not sure how you got the square bracket trick to work, or I'd try and fix this - but it means that they break when pulled off of the Feat_Summary page when selected as Fighter Bonus Feats.
Cell Feats!H165
You have the formula for two handed weapons as:
+"&(2+(FLOOR(BAB/4,1)*2)*1.5)&" w/ 2-handed weapon
it should be
+"&(2+(FLOOR(BAB/4,1)*2))*1.5&" w/ 2-handed weapon
Which multiplies the entire bonus by 1.5, rather than the BAB part of it and adding two to the result.
I'm making a character with 2 levels of Sorc and the rest in fighter, and on the Sorcerer Abilities Summary, it's showing the 3rd level Bloodline Power.
When I select any of the Bloodlines after Lycanthropic, it shows the entire list of Bloodline powers, rather than whatever's appropriate to the Lvl_Sor variable.
I'm making a character with 2 levels of Sorc and the rest in fighter, and on the Sorcerer Abilities Summary, it's showing the 3rd level Bloodline Power.
When I select any of the Bloodlines after Lycanthropic, it shows the entire list of Bloodline powers, rather than whatever's appropriate to the Lvl_Sor variable.
I haven't completed the automation for most of the 3rd-party sorcerer bloodlines. In the interim, they display the full OGC text for each entry.
The rest of your suggestions are great, just what I need to really refine the sheet. I'm glad I didn't updload it as v.0.7 to the Pathfinder DB as yet. I'll give it to the end of the week before I post anything. That'll also give me some more time to work out the 3rd party automation...
I am loving this sheet. I created a character with a version a couple back and it is the best sheet I have ever used.
Thanks--this sheet gets better with every release thanks to the folks on this thread!
Rage Powers:
Swift Foot 1 does not unlock Swift Foot 2; without Swift Foot 2, Swift Foot 3 never unlocks.
Increased Damage Reduction 1 does not unlock Increased Damage Reduction 2, and without Increased Damage Reduction 2, Increased Damage Reduction 3 never unlocks.
Cell Back!CR16 should have the following formula:
=VLOOKUP(BP13,Table_Armor,10,0)/IF(AND(Size="Large",OR(CM19<>"Mithral ",CM19<>"Darkwood")),0.5,IF(AND(Size="Large",OR(CM19="Mithral",CM19=" Darkwood")),1,IF(AND(Size="Small",OR(CM19="Mithral",CM19="Darkwood")),4,IF( OR(Size="Small",CM19="Mithral",CM19="Darkwood"),2,1))))
Once entered, you'll be able to cut and paste it into Back!CR25, where it will look like this:
=VLOOKUP(BP22,Table_Armor,10,0)/IF(AND(Size="Large",OR(CM28<>"Mithral ",CM28<>"Darkwood")),0.5,IF(AND(Size="Large",OR(CM28="Mithral",CM28=" Darkwood")),1,IF(AND(Size="Small",OR(CM28="Mithral",CM28="Darkwood")),4,IF( OR(Size="Small",CM28="Mithral",CM28="Darkwood"),2,1))))
If you're cutting and pasting from here, make sure you tell it to use the local forms of the variables to avoid Excel trying to be helpful on linking things.
This change accommodates races with sizes of Small, Medium and Large.
I know of a non-VBA method of getting dynamic dropdowns to work; this could be used to greatly reduce the sorting clutter on selecting weapons from the drop downs, and from pulling feats from limited feat lists.
Meant to note this earlier...I'm definitely interested in this!
Okay, final cut (hopefully) before I post v.0.7 to the Pathfinder DB:
Oh, and as it looks like the APG classes are going to be OGC during playtest, I will indeed incorporate them into a future version. They will be clearly marked as BETA.
Thanks!
Wanted to let you know that it looks like the GP Variance calculation is off. It looks to be subtracting Total GP Value from 1000 and ignoring what is entered in Starting Gold.
Wanted to let you know that it looks like the GP Variance calculation is off. It looks to be subtracting Total GP Value from 1000 and ignoring what is entered in Starting Gold.
Assuming that's for a 2nd level character, this is actually correct. The Starting Gold field simply allows you to designate the value for 1st level characters. After that, the calculations use the Gold Per Level chart from PRPG.
Okay, I've sent v.0.7 up to the Pathfinder DB as the new BETA baseline. Biggest change from the last test version is that I expanded the Table_Size to incorporate all sizes from Fine to Colossal. This way I can just use a VLOOKUP to calculate weight for armor and weapons as neeeded. So, all sizes are now supported. It also properly halves the Armor bonus for sizes smaller than Small (never noticed that before!).
The feat dervish dance. I was wondering, does it apply both dex mod to hit and damage or just to hit. It factors in just to hit, but states it does both hit and damage.
The feat dervish dance. I was wondering, does it apply both dex mod to hit and damage or just to hit. It factors in just to hit, but states it does both hit and damage.
As I read the feat, it applies to both attack and damage rolls
if it applies to both (as read) it does not account for the damage...only the to hit in the program. :)
if it applies to both (as read) it does not account for the damage...only the to hit in the program. :)
I haven't actually automated this feat at all--if for some reason the attack rolls are being modified that's pretty weird...
Not sure if any of the campaign traits are meant to be automated, but just in case I wanted to let you know that the Westcrown Firebrand is not applying +1 to Initiative
Not sure if any of the campaign traits are meant to be automated, but just in case I wanted to let you know that the Westcrown Firebrand is not applying +1 to Initiative
Nope, no trait automation as yet either. Hoping to have that in v.0.8 as it shouldn't be too difficult for most of them.
Are calculations on the spells tab planned for a future release? stuff like save DC's, spells known, etc.
Looking good!
Are calculations on the spells tab planned for a future release? stuff like save DC's, spells known, etc.
Looking good!
Yes, I've been thinking on the best way to handle this. Obviously a character might have more than one caster class, so I'll either need multiple sheets or some means of parsing out the information for each class on a single sheet. What do y'all think as far as one vs. multiple Spell sheets?
Yes, I've been thinking on the best way to handle this. Obviously a character might have more than one caster class, so I'll either need multiple sheets or some means of parsing out the information for each class on a single sheet. What do y'all think as far as one vs. multiple Spell sheets?
Multiple sheets seems the quick and dirty fix since you only need 3, one for each casting attribute. Not sure how this would affect multi-attribute casters like the Mystic Theurge though. But going this route lets you have something up and running in the interim, giving you more time to decide how best to combine things into one sheet.
Downloaded the latest version; I'll be poking at it a few more times.
Do you have an estimate on when you want to push out the next version, so I can focus my efforts on a deadline?
The stunt for 'dynamic' dropdowns is this:
A dropdown can use a named range.
You can build the name of a named range through use of the CONCATENATE function.
So...
Let's assume cell A2 is named RangerFeats
Let's assume that the range B2:B10 is being used to create a drop down list. We call a named range that's just B2 "RangerFeats1". We name the range B2:B3 "WizardFeats2" and so on until we get to RangerFeats9, which covers B2:B10.
We have a user entry area where the user specifies how many RangerFeats they have, and this gets concatenated and placed into cell A2. (For example, for a Ranger between levels 2 and 6, it would be "RangerFeats6" since there are 6 feats available to select. For a Ranger between levels 7 and 11, it would be RangerFeats10 because the full list of 10 possible bonus feats are available.)
Now, any drop down that we want to pull RangerFeats from should have, as its source, =INDIRECT(RangerFeats)
Warning: Overuse of this trick WILL impair performance on your sheet, so use it sparingly. I'd recommend using it, first and foremost, to limit the ranges of weapons that can be equipped to things the class knows, but that's up to you.
Let me know by PM if that doesn't make sense; give me your email address and I'll send a quick mockup to you.
Also, look seriously into converting your VLOOKUPS into INDEX and MATCH workups. They're computationally less intensive and MUCH MUCH easier to maintain once you've learned them.
Downloaded the latest version; I'll be poking at it a few more times.
Do you have an estimate on when you want to push out the next version, so I can focus my efforts on a deadline?
I'm shooting for about two weeks from now. The next version will contain the OGC for the Oracle and Cavalier so I can help support the playtest. Paizo has asked the d20PFSRD folks to hold off for two weeks so they can get a good feel for who's downloading the playtest PDF before having the OGC out in public. So, I'll roughly follow the play test release schedule + 2 weeks for the next several releases.
The stunt for 'dynamic' dropdowns is this:
<<Good Stuff>>
Also, look seriously into converting your VLOOKUPS into INDEX and MATCH workups. They're computationally less intensive and MUCH MUCH easier to maintain once you've learned them.
Thanks! I'm not familiar with INDEX/MATCH functions at all, but I pick stuff up fairly quickly in Excel once I know where to start. The dynamic range bit is interesting--I'll think on the best places to use it connsidering the possible performance hits.