Easy Metamagic feat from 3.5

[Aaron]

There are tags for that, the ReduMMCost tags:

      foreach pick in hero from BaseSpell where "HasMetaMag.mmXXX"
        perform eachpick.assign[ReduMMCost.mmXXX]
        nexteach

Obviously, replace mmXXX with the unique ID of the metamagic power your feat picked.

[Mathias]

I had forgotten about those - that makes it even simpler - pull the ReduMMCost tag from the selected metamagic, and then push it to the hero, and you're done.

The description of the tags is in the v7.2 FAQ if you want more detail. They can either be used like Aaron says, adding them to the custom spells, or they can be added to the hero if every copy of that metamagic gets the discount.

[Aaron]

And I had forgotten about the hero assign thing, by our powers combined!

[ShadowChemosh]

Nice! Like I mentioned above. Many things are easier in Pathfinder.

[Jewrrick]

Originally Posted by Mathias

I had forgotten about those - that makes it even simpler - pull the ReduMMCost tag from the selected metamagic, and then push it to the hero, and you're done.

The description of the tags is in the v7.2 FAQ if you want more detail. They can either be used like Aaron says, adding them to the custom spells, or they can be added to the hero if every copy of that metamagic gets the discount.

Ok I understand what you're getting at, but I'm not sure where I need to be putting it all to make this work.

I also did a search and can't find anything about a v7.2 FAQ

[ShadowChemosh]

Originally Posted by Jewrrick

I also did a search and can't find anything about a v7.2 FAQ

Start HL and Pathfinder. Then go to "Help->Pathfinder Roleplaying Game FAQ". Then in the browser scroll down to v7.2 and click it. Then read the "Data File Authoring" section.

[ShadowChemosh]

Aaron/Mathias I think I am missing something. I read the FAQ and what you guys wrote and thought this is easy. Plus this would make a great adjustment.

So I built the following:

  <thing id="pS2MetaDec" name="Metamagic, Decrease" compset="InPlay">
    <fieldval field="pCandExpr" value="component.BaseMetamg"/>
    <fieldval field="pMinimum" value="-10"/>
    <fieldval field="pMaximum" value="-1"/>
    <usesource source="srcS2Adjus"/>
    <tag group="OthAdjCat" tag="Spell"/>
    <tag group="ProductId" tag="HLCommunit"/>
    <tag group="Helper" tag="CoreCampOK"/>
    <tag group="Adjustment" tag="S2Custom"/>
    <eval phase="First" priority="500"><![CDATA[
      ~ If we're not enabled, get out now
      doneif (field[pIsOn].value = 0)
      ~ If nothing chosen, get out now
      doneif (field[pChosen].ischosen <> 1)

      var iX as number
      var nAdjust as number
      nAdjust = field[pAdjust].value * -1
      ~ Pull the correct number of tags based on the counter
      while (iX < nAdjust)
        iX += 1
        ~ Pull the Reduce Metamagic Cost tag
        perform field[pChosen].chosen.pulltags[ReduMMCost.?]
      loop

      ~ Push tag(s) to the hero
      perform hero.pushtags[ReduMMCost.?]]]></eval>
    <eval phase="PreLevel" priority="11000" index="2"><![CDATA[
      ~ Set custom expression to "All Things on Hero"
      field[pUsePicks].value = 0]]></eval>
    </thing>

I am running at First/500. To test I had a sorcerer with a Burning adhesive spittle spell and it was listed at level 3 before turning on the adjustment. I turned on the adjustment above selecting "Burning" and nothing changed. The spell was still listed at level 3 not 2.

It was not until I removed the mmBurning Pick and re-added it that the new value too effect. Its confusing me as to why it would be required to remove the mmBurning Pick to get this to work?

[Mathias]

The bound script on pAdjust is at pre-levels/10000 ("Bound pAdjust"). I don't recommend looking up a user field's value before the bound script, or you can end up with the changes you're trying to apply being an evaluation behind.

To test if that's what's happening, try changing something else (like adding/deleting text in the character name, or turning on or off something unrelated).

ReduMMCost tags are checked in the "Set mmFinalLev Value" script at Post-Attr/10000, so you don't need a script as early as the first phase for this.

[ShadowChemosh]

Originally Posted by Mathias

The bound script on pAdjust is at pre-levels/10000 ("Bound pAdjust"). I don't recommend looking up a user field's value before the bound script, or you can end up with the changes you're trying to apply being an evaluation behind.

To test if that's what's happening, try changing something else (like adding/deleting text in the character name, or turning on or off something unrelated).

ReduMMCost tags are checked in the "Set mmFinalLev Value" script at Post-Attr/10000, so you don't need a script as early as the first phase for this.

Thanks. I guess I never really combined pAdjust with early timing before to have noticed this issue. I think the latest I went to was Pre-Level/4000.

I will test when I get home but this makes perfect sense to why it was acting so strange...

P.S. - The Psionic stuff I was doing this week all had "really" early timing and I guess it stayed in my head when I wrote this script. For those I had to have scripts running at First/50.

[ShadowChemosh]

Originally Posted by Mathias

The bound script on pAdjust is at pre-levels/10000 ("Bound pAdjust"). I don't recommend looking up a user field's value before the bound script, or you can end up with the changes you're trying to apply being an evaluation behind.

To test if that's what's happening, try changing something else (like adding/deleting text in the character name, or turning on or off something unrelated).

ReduMMCost tags are checked in the "Set mmFinalLev Value" script at Post-Attr/10000, so you don't need a script as early as the first phase for this.

So I have moved the script to Post-Level/50000. Same issue. The metamagic value does not get reduced unless I re-add the mmBurning Pick.

Even stranger once the value is reduced by 1. So in example I re-add the Burning mmBurning Pick with the adjustment on and its reduced from 3 to 2. Then I remove the adjustment totally from the character and mmBurning stays at 2. Then I tried changing a skill up and down. It still stayed at 2. I have never seen HL react this way before. Its almost like some "script" in the background is not always firing.

I know Colen did some work with causing some scripts to not always fire and I wonder if that is what is happening.

If you want try this out. Use the adjustment above and change its timing to after pre-levels/10000. Make a sorcerer and add Burning Hands. Then create a "Favorite Metamagic Spell" with "Burning" and you will have a level 3 spell. On the adjustment select "Burning" and leave the counter at -1. You will see the spell "Burning burning hands" is still a level 3 spell. Then edit the metamagic Pick and remove Burning and re-add it. Now it will show a level 2 spell.

So weird....