shemetz's page

3 weeks have passed. I repeat my request! (for the next errata, of course)

I think the nonlethal trait is a counterpart to the death trait and has a similar issue. A lot of creatures have immunity to nonlethal attacks, often right next to immunity to death effects (e.g. Homunculus). The rules explicitly say immunity to nonlethal attacks is an exception, and a creature with this immunity is completely immune to them, rather than just dying instead of being knocked out. This is - at least in my opinion - a weird thing, a mechanic that's hard to rationalize in the context of the narrative, especially since it only applies to nonlethal attacks and not nonlethal spells.
But the existence of that weird rule (a homunculus is completely immune to punches) lends a lot of credibility to the weird interpretation of the death trait (a homunculus is completely immune to Phantasmal Killer).

Resurrecting this thread!

With Pathfinder 2e Remastered approaching, this question has still not been answered in the rules text in any form of errata, and the rules are only going to get more confusing because spells no longer have the verbal trait.

Instead, the rule will read something like:

Casting a spell requires the caster to make gestures and utter incantations, so being unable to speak prevents spellcasting for most casters.

This is pretty much just rephrasing what the verbal component was already doing, except now it's less decisive ("most" casters, probably with permanently deaf/mute casters being the exception).

The Deafened condition still only refers to "an action with the auditory trait", which does not apply.

The Social Splash Damage rules still say "A deaf character (...) have enough practice to supply verbal components for casting spells (...) but if they perform an action they’re not accustomed to that involves auditory elements, they must succeed at a DC 5 flat check or the action is lost. ", and refers to *permanently* deaf characters, strongly implying that temporarily deafened characters *do* need to make such a check.

Paizo, please update the Deafened condition in the Remaster or in an errata document

The FoundryVTT team has apparently gotten semi-official confirmation from Michael Sayre that Bless and Bane are indeed auras!

Now we just need the errata to actually happen, hopefully with the Remaster release adding the trait to many spells.

For more discussion of this probable rules mistake, and a list of other spells that suffer from it, see:
Are the Bless and Bane spells intended to be auras?

Bumping this thread again - it would be nice if we got some response like "Errata flagged" from one of the devs, to know that this is being seen. I assume (based on an old blog post) that there is no better way to bring needed errata to the developers' attention except by opening forum threads about it, so let me know if I'm wrong.

This issue is a bit more pressing than expected because the Foundry VTT system implementation of PF2E has added Aura automation, which forced them to rely on the RAW interpretation of these spells. This means that, for example, when a cleric casts Bless and moves forward, the spell effect stays behind and the cleric loses the benefit of the spell (due to exiting its radius), mechanically removing the +1 bonus from its stats in the VTT sheet. Ruling the bless spell as an aura is now harder than it is in tabletop games, because it requires working around this RAW interpretation with special modules or by remembering to move it each round (unlike other similar spells).

All of that is to say, in short: Paizo, please note that errata is actually important even in cases like these where most players naturally assume an interpretation and don't think about it again.

Eerie Flicker:

Your body flickers momentarily into the Ethereal Plane. You become concealed for 1 round, and the flat check for concealment applies to the Strike that would have hit you. If the flat check fails, the Strike misses you.

The bolded text should probably be errata'd into "the Strike has no effect", to be consistent with how the concealed condition works.

For those who are interested, I compiled a list of all spells I've found with this issue in a reddit post,
"A lot of spells and abilities need to get the Aura trait for their emanations"

Overall, in addition to 10 existing spells with the Aura trait, I have found at least 23 spells that are lacking the Aura trait but really seem like they need it, with about 10 others that could go either way, and only 6 spells that definitely seem like they shouldn't be Auras.

Here's a list of spells that may require errata, as they have an emanation with a long duration yet don't have the Aura trait, and seem kind of intended to move with the user (some of them explicitly say so, some of them include rules about how the effect can move, some encourage you to move, etc):

- Antimagic Field
- Aura of the Unremarkable
- Bane
- Bless
- Circle of Protection
- Cloak of Shadow
- Control Sand
- Detect Scrying
- Entrancing Eyes
- Focusing Hum
- Foul Miasma
- Glimpse the Truth
- Invisibility Sphere
- Pass Without Trace (heighten 4)
- Poltergeist's Fury
- Prying Survey
- Reaper's Lantern
- Show the Way
- Song of Marching
- Spirit Sense

And some feats, of course...
- Curse Maelstrom Dedication
- Marshal Dedication
- Overwatch Dedication
- Resounding Cascade
- Slip into Shadow
- (I stopped researching here)

Not sure if this is the right place to report it, but it seems a typo has snuck its way into the final print? "Reversing Charge" is referred to as "Snapback Charge" in that sneak-peek video.

So this is kind of a big one then that should probably be asked. The PDF to Foundry module worked off of purchased PDF's. Can we anticipate some support to those of us who have used this route to help create our games? And being as the Beginner's Box is very common in the Humble Bundles, will there be future support for that?

Users who bought the PDF will get a discount for getting the module, and users who purchase the module will get the PDF alongside it for free!

There is an FAQ about this announcement on the Foundry website (should be more prominent in the announcement).