Senior Member
Join Date: May 2013
Posts: 240
|
@Gragan Maaaaybe. I'll have to go back and look at how I did it.
@lacker I have no idea if it works on iPad -- I haven't got one to test it. Anybody? @Fuzzy I'll see if I can fix that this evening when I get home. |
#11 |
Senior Member
Join Date: Nov 2013
Location: Andover, Ma
Posts: 632
|
I realize this is a bit off-topic from the currently, discussed issue. But, I'm currently running a Mythic game and while I understand that the rules were never set up to work with mythic versions of the feats. There are some issues regarding how it the no feat tax rules interacts with the mythic versions of the feats.
Especially those that require you to select a weapon such as Mythic improved critical. Which actually seem to produce errors because you cannot select weapons properly. |
#12 |
Junior Member
Join Date: Nov 2013
Posts: 6
|
So for those who may use an iPad and want to use the No Feat Tax system... it DOES work with the iPad.
My error was in not selecting the WiS software to download to my iPad (under licenses, update software). Since my character was created on my laptop using No Feat Tax it was readily accepted on my iPad once the software was loaded. Happy camper now 😊! |
#13 |
Senior Member
Join Date: May 2013
Posts: 240
|
I sat down tonight to start looking at some revisions to these. Here's my to-do list.
[ ] Give Unarmed Combatant to Monks, Unchained Monks, and Brawlers [ ] Make Weapon Focus require BAB at +1 [ ] Investigate the possibility of turning on and off individual feats [X] Make Weapon Focus work for animal companions [ ] Figure out Mythic Improved Critical issues, which are super weird I also thought I would go looking for archetypes and other abilities that might need to be modified. For example, a Ranger with the two-handed combat style can still select Power Attack as a bonus feat even though it's already been supplied by WiS. Similarly, a Feral Child Druid is supposed to Improved Unarmed Strike, which should be converted to Unarmed Combatant. I made it through every option listed for the core classes on d20pfsrd. That includes: Barbarian rage powers, Cleric domains and subdomains, Ranger combat styles, Rogue talents, Sorcerer bloodlines, Wizard schools, and all archetypes for all core classes. At that point my list was 82 items long, and I know for a fact I missed several because I overlooked Deadly Aim and Improved Steal early in the process. ... yeah, I think I'm going to fix those when somebody complains about them. I don't really want to go through and rewrite a major chunk of the entire Pathfinder system. So I'll work on this shorter list, probably tomorrow night. I already added Helper.AnimCompOK to Weapon Focus, so it works for animal companions now. (Note: I haven't pushed out an update yet, I'll do that once the above checklist is done.) |
#14 |
Senior Member
Join Date: May 2013
Posts: 240
|
[X] Give Unarmed Combatant to Monks, Unchained Monks, and Brawlers
[X] Make Weapon Focus require BAB at +1 [ ] Investigate the possibility of turning on and off individual feats [X] Make Weapon Focus work for animal companions [ ] Figure out Mythic Improved Critical issues, which are super weird [ ] Grant Weapon Focus (Flails) to Kapenia Dancer magus archetype Some progress. I got Unarmed Combatant onto monks, unchained monks, and brawlers with no particular difficulty. Weapon Focus now complains if you take it without having a BAB of +1 or higher. I started looking into the Mythic Improved Critical issue, and staggered out feeling rather dizzy a couple hours later. That sucker is complicated. To clear my head, I thought I'd go work on granting Weapon Focus (Flails) as a bonus feat to Kapenia Dancers, who ordinarily get Weapon Focus (Bladed Scarf). The logical approach was to use a Mechanic that checked for the appropriate archetype and bootstrapped the feat on if so, then gave it skippreq. The original Weapon Focus uses the tag Target.? to auto-assign a value to a bootstrapped feat. For example, tagging the feat with Target.wBite gives you Weapon Focus (Bite). My own Weapon Focus doesn't share much code with the original, so I set out to replicate that feature. And it works! Mostly. I created a new tag GTarget, and tagged the bootstrapped feat with GTarget.Flails. Okay so far. After banging my head at it for a while, I even got it to correctly pick up the targeted weapon group from GTarget.?. It correctly applies the +1 bonus and tags the hero as having Weapon Focus with all weapons in the Flail group. Mechanically, everything is working fine. Buuut ... the UI doesn't work so well. My sample Kapenia Dancer winds up with Weapon Focus (-No Selection-) and a validation error saying to choose an option for Weapon Focus, even though she's getting the bonus applied correctly. I've gone over and over the code for the original Weapon Focus, and I'm stumped. How do I inform the drop-down selector that it should be set to Flails? And, preferably, not allowed to change? |
#15 |
Senior Member
Join Date: Oct 2011
Posts: 6,793
|
Why do you need to create the new GTarget tag group? I'd simply use a script to find the copy of weapon focus bootstrapped by Kapenia Dancer, then at an early timing switch the Target tag it has.
|
#16 |
Senior Member
Join Date: May 2013
Posts: 240
|
Well, correct me if I'm wrong, but doesn't the Target tag only allow for specific weapons? Under the World is Square rules, Weapon Focus applies to weapon groups. I need to be able to say something like "Target.Flails" or "Target.BladesHeavy", but the compiler complained about non-existent tags when I tried that.
I tried extending the Target tag by adding the groups as options in my .1st file, but then the compiler complained about a duplicate id "Target", which is perfectly reasonable. So I shrugged and made it "GTarget" for "Group Target". |
#17 |
Senior Member
Join Date: Oct 2011
Posts: 6,793
|
So basically they all get the benefit of the following feat from ARG:
Martial Versatility You further broaden your study of weapons to encompass multiple similar weapons. Prerequisites: Fighter level 4th, human. Benefit: Choose one combat feat you know that applies to a specific weapon (e.g., Weapon Focus). You can use that feat with any weapon within the same weapon group. I'd say copy that and see how it modifies whatever feat it selects. Then your mechanic can do the same modification, but for every copy of weapon focus on the hero. |
#18 |
Senior Member
Join Date: May 2013
Posts: 240
|
That part is already working. I have a fully coded weapon focus that allows you to select a weapon group instead of a specific weapon. I've used a *Preclude rule to suppress the standard weapon focus when the World is Square rules are active.
The preclude rule, however, poses a problem in cases where an archetype grants weapon focus as a bonus feat. For example, the Kapenia Dancer archetype of the Magus class gives you Weapon Focus (bladed scarf) at level 1. Because the standard weapon focus has been precluded, characters with that archetype do not receive the bonus feat they are entitled to. In order to correct that, I'm using a Mechanic that checks for the appropriate archetype tags and bootstraps the modified weapon focus feat instead. For example, a Kapenia Dancer would get Weapon Focus (Flails) instead of (bladed scarf) because a bladed scarf is in the flails weapon group. That's where it breaks down. I can bootstrap my feat to the archetype just fine, but so far I haven't been able to pre-select flails. It always bootstraps the base feat with no group selected, when I need it to grant it with one specific group already set. The original weapon focus solves this by tagging the feat with Target.Whatever when it is bootstrapped, and then its eval script uses that instead of usrChosen1 to determine the selection. I'm trying to do the same. My code is at home, I'll post it after work. On a final note, this missive is probably the longest thing I've ever typed on my phone. Not a fan of tapping away on a teeny screen for long compositions! |
#19 |
Senior Member
Join Date: Oct 2011
Posts: 6,793
|
Alright, so if I understand correctly, you have all the mechanics working how you want, you just need to force a selection. You tried adding a new tag group which shared Target's group ID, but that ran into duplication errors. Target is a dynamic tag group though, so you are free to make new ones at will with whatever Tag IDs you want. As long as it is defined on something in a common file, the tag should be usable.
Try this. Create an ability which isn't added anywhere, purely to store the new Target tags you'll define. Then define them on this ability, making sure to set the name attribute when defining. Code:
<thing id="abTagDf" name="Tag Definition Helper" description="Just something to define some tags we want to use elsewhere." compset="Ability"> <tag group="Target" tag="wGrpFlail" name="Flail Weapon Group" abbrev="Group (Flail)"/> </thing> |
#20 |
|
|