
![]() ![]() ![]() ![]() ![]() ![]() |

Lets begin
I implore the leadership of organized play to either delete or update dealing with afflictions in guide 9.1 and here is why:
On page 16. you do step 8
"If the character gained an ongoing condition like a curse or disease during the scenario, the player should note that here as well. See Dealing with Afflictions below for more information on noting conditions gained and cleared during a scenario or after its conclusion."
Fine that leads us to Dealing with Afflictions
"At the end of a scenario, a PC might have been afflicted
with any number of possible afflictions, such as blindness,
a curse, deafness, a disease, or a poison..."
Yes a pathfinder can be afflicted by many conditions
"It is important that conditions be written legibly
so the player and subsequent GMs can understand them."
Okey meaning that afflictions, such as blindness,
a curse, deafness, a disease, or a poison might transfer from senario to senario.
"Note: Any affliction that would result in an unplayable
character must be resolved at the table once the game
ends as explained in Chapter 4 of this document. If the
character cannot resolve an affliction that would render
her unplayable, mark the character as dead."
okey so the next part must tell us what an unplayable character is
Page 19. CONDITIONS, DEATH, AND EXPENDABLES
"Conditions: Unless noted otherwise, all conditions
gained during an adventure, including death, must be
resolved before the end of the session. A condition in this
context includes an affliction, a negative effect, or an effect
that is intended to mechanically affect your character in
a negative way. If such a condition isn’t resolved by the
end of play, the character should be reported as dead and
becomes unplayable."
So if you get a condition that is not: "However, a few conditions need not be resolved by the end of play, including permanent
negative levels, ability drain that does not reduce an
ability score to 0, becoming a fallen member of a class
that requires an atonement spell to regain class features
or spellcasting abilities, and conditions that impose no
mechanical effect."
then you are dead/unplayable so why shall i note: curse or disease during the scenario, the player should note that here as well. You become unplayable.
Leadership could just cut the whole affliction out and state that if you do not resolve all conditions except these few (page 19) then the character shall be reported dead/unplayable.
i would hope they lifted to strict rule so disease or blinded/deafend could go from senario to senario.

![]() ![]() ![]() ![]() ![]() |
1 person marked this as FAQ candidate. |
The opposite of what he said. The Guide should list specifically what conditions must be fixed by the end of the adventure. Otherwise, whenever a character gets a boon, they are automatically killed at the end of the adventure! If an adventure does something unlisted that is required to be fixed, then the adventure should say so.
Currently, the list of conditions which don't have to be fixed by the end of the adventure includes the word "including", which is not at all compatible with "everything must be fixed unless otherwise stated". Apparently at least one of the Guide's authors thinks that the GM is supposed to decide what counts as unplayable if a condition is not mentioned in the Guide, but that does not match with "everything must be fixed".
Players have been complaining about this for years.

![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |

I don't understand the complaint. The rule seems simple enough to me? You have to fix any ongoing affliction, except a very small list:
- permanent negative levels
- ability drain that does not reduce an ability score to 0
- becoming a fallen member of a class that requires an atonement spell to regain class features or spellcasting abilities
- conditions that impose no mechanical effect.
Each of these has a clear mechanical effect that the next GM can work with, and also a clear CRB remedy that does not require special knowledge from the next GM.
They're all also non-fatal, but require expensive spells to fix. Seems reasonable not too kill a PC who can't afford to fix it immediately.
The big aim of the rule is not to saddle the next GM with making rulings on a condition from a different scenario, that he might not have access to.
Suppose you get a curse in a scenario, which has a certain DC to remove. And you don't remove it or find out the DC. Next session you show up and there's a friendly PC cleric that wants to case Remove Curse for you, but the GM doesn't have the previous scenario so he can't look up the DC.

![]() ![]() ![]() ![]() ![]() ![]() |

Clarified?
Conditions: Unless noted
otherwisebelow, all conditions gained during an adventure, including death, must be resolved before the end of the session. A condition in this context includes an affliction, a negative effect, or an effect that is intended to mechanically affect your character in a negative way. If such a condition isn’t resolved by the end of play, the character should be reported as dead and becomes unplayable."
However, a fewThe following conditions need not be resolved by the end of play:, includingpermanent negative levels, ability drain that does not reduce an ability score to 0, becoming a fallen member of a class that requires an atonement spell to regain class features or spellcasting abilities, and conditions that impose no mechanical effect. Permanent negative levels, ability drain, and nonmechanical conditions being carried over to the next session should be recorded on the Chronicle sheet and the player must inform the GM of all negative effects before the next adventure begins.
The point of the "Dealing with Afflictions" section on Page 16 is to account for the costs of removing them. Whether it was cleared by spending Fame or gold or if another player was able to clear it for free. You reference Page 19 to make sure that you don't have any conditions left that would make your character unplayable.

![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |

Kevin, almost. Your "Unless noted below" is a bit too strongly worded. I know of at least one scenario that can leave you with a nasty curse but which doesn't render the character "dead unplayable", because it includes a full description of the curse on the chronicle sheet.
Apart from that, your text is better.