Kelrugem's extensions

Quote:

---

Originally Posted by dllewell

I have added Hero Points to the Extra Actions extension. It absolutely doesn't replace this extension or the Advanced Character sheet but can be used as a stop gap option until a fix is in place for this issue.

You can find the extension information here -
Thread
Forge Page

---

thanks a lot! :) It is also useful for those of us who play 3.5e and want to use hero points of some sort; so, I am looking forward using it :) (because Zarestia's sheet only adds that for PF1, while it lacks that feature in 3.5e)

Quote:

---

Originally Posted by rmilmine

I had this happen in the past week.

If you put the following effect on a character.

Orange Prism Ioun Stone; NIFTAG: Channel; CL: 1d4-1

And you put in the tag "Channel" in your channel power it fails.

While trying to figure out why it was failing I clicked the cast button and got the following in chat:
[CAST] Channel Healing-30' (35' With Ring +1 To Select) + Tier Healing From Mantle [TAGS: channel]
The "channel" within "[TAGS: channel]" is lower case, even though it is uppercase in the spell.
So I tried changing the effect to have the tag being lower case and it now worked.
Something is making the tag within the spell lower case before it is compared to the tags within the IFTAG or NIFTAG effect.

---

I just uploaded a quick fix to that:

The (N)IFTAG code (the tag stuff) is now case-insensitive in any regard :)

Thanks again for the report, rmilmine :)

Sorry Wrong Bug Report Forum.

Hello Everyone!

Any word on whether or not Kelrugem's extensions are compatible with the new 1/20/2026 update? I'm going to try to get in there later tonight and set up the test Channel but I may not be able to before they push it live. Hoping someone already tested it.

Thanks as always!
Rob

Quote:

---

Originally Posted by RobboNJ69

Hello Everyone!

Any word on whether or not Kelrugem's extensions are compatible with the new 1/20/2026 update? I'm going to try to get in there later tonight and set up the test Channel but I may not be able to before they push it live. Hoping someone already tested it.

Thanks as always!
Rob

---

My golden rule is to NEVER update as soon as the update comes out, but always wait a couple weeks... if there are issues, they will naturally be reported, so once there' s no more apparent issues about extensions, I finally do update.

Quote:

---

Originally Posted by Asgurgolas

My golden rule is to NEVER update as soon as the update comes out, but always wait a couple weeks... if there are issues, they will naturally be reported, so once there' s no more apparent issues about extensions, I finally do update.

---

Hello Asgurgolas,

I agree, and I do the same. I was just wondering if anyone has tested it using the Test channel, which would give an 'early notice'. There have been previous posts where a developer has tested their extension and knew there would be no conflict. Of course, the opposite has been true as well.

Thanks for the reply!
Rob

Oh, is the new big update already out there?

I didn't test my extensions (I forgot when I played with the new features :D), but naively I would say it should work because it sounds like that only code in base FGU got changed not 3.5e/PF1 itself (I think, we will see :D)

Hello Kelrugem! As you said; 'we will see'. Thanks for all the time and effort you put into maintaining your extensions!
Rob

It seems that this extension is blocking the hit and damage animations on the map. I wasn't seeing the animations when this was loaded, I removed this one extension and the animations started to work. Aside from that excellent work on your extensions!

Quote:

---

Originally Posted by Deslock100

It seems that this extension is blocking the hit and damage animations on the map. I wasn't seeing the animations when this was loaded, I removed this one extension and the animations started to work. Aside from that excellent work on your extensions!

---

Thanks for the report and words :)

I was not yet able to look at the new ruleset code, but so there is apparently an incompatibility which I have to fix in the coming days :)