|
In reviewing the Errata changes, I noticed that the spell Breath of Life was not updated.
In Errata version 1.2 the Dying condition includes the statement: 'You lose the dying condition upon returning to 1 or more Hit Points.'.
The text under Breath of Life (Page 208 of the Rulebook) states: 'The target regains 4d8 plus your spellcasting ability modifier Hit Points, reduces its dying condition to dying 3, and gets a +2 conditional bonus to its next recovery save.'
Since the Playtest no longer keeps track of negative hit points, the Breath of Life spell should bring the character above 0 Hit Points. According to the Errata, the character should lose the dying condition. The Breath of Life spell should remove the text: "reduces its dying condition to dying 3".
Speaking of Breath of Life, does Massive Damage (page 296) count as a death effect, or can BoL save you from it? I think it should be the former.
The general rules for the Scent ability (rulebook page 302) do not include a default range, yet almost nothing in the rulebook that grants scent specifies a range.
While many (most?) creatures in the Bestiary with scent specify a range of 30', some leave it unspecified: mastodon, goblin dog, hell hound, any kind of horse, hydra, hyaenodon, hyena, jabberwock, manticore, owlbear, rat swarm, sandpoint devil, serpentfolk (and degenerate), shoggoth, viper, ball python, giant anaconda, giant viper, warg, winter wolf, wererat rogue, werewolf fighter, wolf, and yeti.
Some rituals (such as Planar Binding or Geas) allow targets of the ritual to make will saves to resist the effects. However, there's no listed way to calculate this DC.
| 1 person marked this as a favorite. |
Demon Armor (page 386) has horns that function as weapons with the deadly trait, but no damage die is listed for the trait.
Stone fist Elixir has the Polymorph tag.
According to tag descriptions, it should be changed to Morph tag.
Polymorph usually indicates complete change while slight alterations (changing your hands to be harder) are Morphs.
Balance wise, it means that an alchemist can't atm use stonefist elixir +any mutagen (notably bestial) simultaneously, which is one more nail in the the class' coffin (only goblins are allowed more than d4 unarmed damage until level 8...)
There's another issue with the Stone Fist Elixir. It doesn't remove the non lethal trait from your fist attacks. As such, an Alchemist is left without any means to do lethal unarmed damage (barring Feral Mutagen at 8th level)
| 1 person marked this as a favorite. |
There's another issue with the Stone Fist Elixir. It doesn't remove the non lethal trait from your fist attacks. As such, an Alchemist is left without any means to do lethal unarmed damage (barring Feral Mutagen at 8th level)
This Feral Mutagen doesn't seem to be in the list of Alchemical items. An oversight, no doubt. Perhaps it's meant to refer to Bestial Mutagen.
The description for darkvision states that the creature sees in black and white even in any light.
So does this mean that the creature is colour blind?
I saw your thread asking this and answered before seeing this collated thread. Basically, Creatures with Darkvision do not see in black in white across all Light levels, Darkvision does not mention reducing their sight in Bright Light to greyscale. The difficulty is determining Dim Light, since the entry in the Senses section conflicts with the Ancestry descriptions ...
Hm, I kind of like idea Darkvision = Colorblind, although perhaps in normal light it would be like typical real Human colorblind-ness, i.e. LESS colors not none... On the basis that Darkvision is replacing one color photoreceptor with "Infrared" receptor or whatever.
Relatedly, in regards "disabilities"/senses,
IMHO Sign Language should be treated more as just another language (that shares written form with normal language). The rules should not need to suggest GMs grant characters Free Feats just for growing up around deaf/signing people, it's not egregious to spend your Language slot on Sign... And the Feat itself is over-powered as the "standard" since it automatically gives you Sign for ALL languages, which isn't inherent to "talking sign with deaf family". We don't need pan-dimensional universal communication between deaf people/beings (or if that is intention, it's simpler to make Sign Language single universal language, and grant Deaf/Mute characters independent fluency in written/Lip-Reading form of 'host' culture language). Having Feat exist to automatically know Sign version of all Languages you know is fine, but IMHO the 'standard' shouldn't rely on that, but rather just use Language 'slot' system.
Since raising INT to 14 at later levels will be very common given Stat Boost system, I wonder if there should be explicit distinct rules to cover that, i.e. if your present location would be more relavent than your background/race language access? I also think the basic "Common" list should be pared down, making things like Ancestry/Region/Class more relatively important. Undercommon, Draconic, Elven just don't seem like universal Inner Sea languages, although right region (e.g. near Kyonin for Elven), or Class/Dedication/Race/Religion can reasonably treat them as such... And Class/Race/Region/Religion/Feat language access thus becomes more important.
I also see specific problem with Ethnic language for Nidalese (Shadowtongue), the only Common access for it is via Nidalese Ethnicity. That is reasonable to exist (allowing ethnic Nidalese who grew up in Cheliax to still know ethnic tongue), but it should ALSO be available via Region (Nidal) for any Varisian, Chelish etc who grew up in Nidal (the former being key aspect of Nidal demographics AFAIK). This issue seems to exist because of 1-sided organization of listing major languages and then the multiple regions they exist in, as opposed to inverse approach of listing regions and the languages they contain - Which raises question, will Absalom background have access to all Humanoid (and not) tongues?
Ethnic Taldane could also have Common access to Ancient Azlanti to represent Azlanti supremacist cult tendency, also making up for otherwise lack of bonus ethnic language for them? And likewise for ethnic Osirioni / Ancient Osirioni, or perhaps associated to the Ancient Osironi cult Religions? (the Osirioni ethnic description is vague to point of meaningless, it doesn't even imply relationship to NotEgypt)
Agree regarding sign language being a language in the same sense that Taldane or Shoanti or Varisian is a language. Also agree, in theory, that different regions would develop different versions of sign language, but I wonder if it would be more practical, for game purposes, to ignore that and just have one universal sign language which is the same everywhere. Plus perhaps some specialty sign languages for specific groups, like thieves or soldiers.
In general I think players should specify in their PC's backstory where they grew up, and to what they were exposed in growing up. This would inform what languages and other things to which the PC might have access. For example, we (or "the game") treat Taldane as a common language all across the Inner Sea reason for two reasons: in the background/history of the region, it is a common language, and for game purposes we need such a language or the game gets bogged down because the players can't talk to each other. But the game assumes that if you "know" a language, you are perfectly fluent in it, and that's not always the case. A Varisian who grows up in a caravan moving around that region may be able to make himself understood in Taldane, but he's not going to be as fluent in it as a native speaker. The game ignores that, and that's fine, but it's still true (or would be, if Golarion really existed). OTOH, the Varisian is going to be more fluent in Varisian, and probably Shoanti, than somebody from Oppara.
As for access to Ancient Azlanti, how would that work? Azlant died more than 10,000 years ago, and the only native speaker to survive for any length of time, so far as we know, was Aroden, and it's been a while since he's been around. Even when he was around, why would he speak the language if no one else understood it? Maybe he might teach it to a few, but I doubt it would be commonly known. And as usage faded, so would knowledge, over the years.
Certain languages might be taught, as Latin and Greek were taught long after the collapse of the Roman Empire. That can be accounted for in the PC's back story. But it seems to me there should be a reason in that backstory why the PC knows that language, not just that the player wants his PC to know it.
Absalom will be an interesting case. Not addressed (so far) in PF2, and AFAIK has no "native" language of its own. Come to think on it, that seems odd. The greatest city in the world, been around for 5,000 years or so, and never developed its own language. That's not just odd, it's damn near unbelievable. Unless of course Absalom's "own language" is Taldane.
BTW, I do think shift from Polyglot->"Mwangi language" is good, more analagous to Taldane, both spoken by varying tribes/nationalities which are still related/mutually intelligible. "Polyglot" just felt like it weakened Mwangi identity and left it diffuse, like if Taldane was just only called "Common".
I also wonder if there is value in separately indicating regions' Native language(s) and non-Native languages that nonetheless have easier Common access for that Region. I know Taldane is default "Common", but it still seems reasonable to specify the regions where it is actually Native (i.e. Taldor, Cheliax, Andoren, etc) and naturally Common access... both to smoothly function if anybody plays with game assumption where Taldane is NOT Common, and potentially relevant for other mechanics which hinge on Region:NativeLanguage correlation... as well as indicating any territories where Taldane/Common may be less useful within Taldane/Common assumption game.
For Mwangi, it seems reasonable that it would have non-Native status but Common access in neighboring Nex, Geb, Mana Wastes (an angle that opens more narrative routes vs. past treatment), and that same status is perhaps more appropriate for Sodden Lands where it isn't actually native AFAIK (?).
There's another issue with the Stone Fist Elixir. It doesn't remove the non lethal trait from your fist attacks. As such, an Alchemist is left without any means to do lethal unarmed damage (barring Feral Mutagen at 8th level)This Feral Mutagen doesn't seem to be in the list of Alchemical items. An oversight, no doubt. Perhaps it's meant to refer to Bestial Mutagen.
Feral Mutagen is an Alchemist Feat that affects Bestial Mutagen, that was clarified in the update document.
| 1 person marked this as a favorite. |
So I was looking at some spells. One i loved to cast in older editions of DND.
Continual Flame. It can be heightened. But there is no benefit of it being heightened since it is any object touched with no size restriction. Except it costs more gold to cast the spell heightened. I guess if you want to blow your gold and higher spell level slots.
Is there something I am missing on this spell for it be be heightened or was there something they forgot to add in or changed before the book was printed?
My guess is that it's for dealing magical darkness of higher and higher levels, since Magical light only shines in magical darkness of a lower level than itself.
I just downloaded the pdf a few days ago, so I'd assume my version includes any errata, but idk.
It doesn't, because updating the PDF every two weeks would be insane, and any expectations that they do, don't account for the massive amount of work involved in layout and editing. Not to mention any places where the page numbers change would be rife for confusion.
On your specific points, I'm not sure I see the need for errata for many of them (most of the rest have already been errata'd). Most of the justifications that you're making involve a lot of bending over backwards to misread the rules, like arguing that all unarmed attacks are fists, when the actual text specifies that other abilities grant access to "special, more powerful unarmed attacks" which indicate they don't follow the preceding statement.
Use the statistics for a fist even if you’re kicking, kneeing, or attacking with another part of your body.
- pg 178In other words, treat all unarmed attacks as fists, even if it's actually a knee, etc instead of a fist.
Saying that certain features can make unarmed attacks more powerful is not quite the same as saying they can change any aspect of them, including removing traits.
Well in that case, all unarmed attacks do 1d4 damage, because they're all treated as a fist, which does 1d4 damage. I don't think this is a reasonable read, and I would find it hard to believe if someone at my gaming group came to me with this reading of it, claiming to be sincere.