Pathfinder 2 - Release 18 information thread.

Trenloe would you delete whatever is giving the Witch a spellclass on creation for the next release please? I'm adding witch spellclasses from lookupdata and I get a message that the class already exists and the one that fg creates doesn't have the spell tradition applied.

Thanks

Quote:

---

Originally Posted by Zieg

Trenloe would you delete whatever is giving the Witch a spellclass on creation for the next release please? I'm adding witch spellclasses from lookupdata and I get a message that the class already exists and the one that fg creates doesn't have the spell tradition applied.

---

I'll investigate the tradition not being applied. I'm sorry, but I'm not going to remove the functionality in the standard product that's (mostly) working to cater for custom work you're doing.

Sorry I didn't express myself correctly. I meant change it so that it doesn't apply automatically if another feature is adding it, like the sorcerer and other classes.

It's like the issue I reported with the cleric but this time instead of creating 2 spellclasses it says it already exits.

Sorry again if my previous post was somewhat rude.

Quote:

---

Originally Posted by Zieg

Sorry I didn't express myself correctly. I meant change it so that it doesn't apply automatically if another feature is adding it, like the sorcerer and other classes.

It's like the issue I reported with the cleric but this time instead of creating 2 spellclasses it says it already exits.

Sorry again if my previous post was somewhat rude.

---

Ah, right - thanks for clarifying. Sorry for my misunderstanding.

The ruleset code looks for a class feature called "Witch Spellcasting" and creates the spell class based off that class feature, unless there's any automation in that class feature. If you don't want the "Witch Spellcasting" class feature to create the spell class, then put automation of [NONE] in that class feature, this will mean that it doesn't process the usual code for that entry.

Good to know.

Thanks!

Quote:

---

Originally Posted by Zieg

The one provided in the automation document

[OPTIONS choice xref=BIR Black Dragon=acid|Blue Dragon=electricity|Green Dragon=poison|Red Dragon=fire|White Dragon=cold|Brass Dragon=fire|Bronze Dragon=electricity|Copper Dragon=acid|Gold Dragon=fire|Silver Dragon=cold]

---

With today's release this should now be fixed. Thanks again for reporting the issue.

https://www.fantasygrounds.com/forum...July-27th-2021

Quote:

---

Originally Posted by Trenloe

With today's release this should now be fixed. Thanks again for reporting the issue.

https://www.fantasygrounds.com/forum...July-27th-2021

---

Yes

Thanks!

Hi again!

There seems to be some kind of issue with [OPTIONS choice item] with items whose name has some kind of special character. It doesn't recognize healer's tools, Clothing - Fine or Bolts (10) among others.

Quote:

---

Originally Posted by Zieg

Hi again!

---

Hello again! :)

Quote:

---

Originally Posted by Zieg

There seems to be some kind of issue with [OPTIONS choice item] with items whose name has some kind of special character. It doesn't recognize healer's tools, Clothing - Fine or Bolts (10) among others.

---

Works fine for me for all these three items - see below. The PC automation I used for this test was: [OPTIONS choice item Clothing - Fine|Bolts (10)|Healer's Tools]

Case doesn't matter as the comparison to find the item records is all done in lower case.

https://www.fantasygrounds.com/forum...chmentid=48446

I found the issue, I copy pasted from the official book and some characters seem to be different.