Reply to thread

Message

<blockquote data-quote="Elric" data-source="post: 4749641" data-attributes="member: 1139">I think of what I'm doing as adding a property to each solo monster to resist status effects better, and using the exact same property each time.&nbsp; As LuckyAdrastus says, your solos look very flavorful and fun to play against.&nbsp; If you could only choose one resilience solution for every solo, which one would you pick?&nbsp; Now you have a default and if you want to create a solo from scratch or further modify an existing one, you can do that as a specific exception.Even a bonus save like the one Klang has doesn’t affect the two big issues, though, which are that a solo has no special defenses against until end of next turn effects, and that it will be affected for at least a round by (save ends) effects.&nbsp; A solo is only affected for 1.25 rounds on average by a (Save ends) effect right now; even having it automatically make saving throws would only decrease this to 1.&nbsp; A bonus save would be handy against RAW Orb Wizards and AV static-save penalty stuff, but I think those abilities should be fixed with a house rule so they aren’t so overpowered, instead of trying to immunize solos from the consequences of static save penalties being so overpowered.&nbsp; I agree with you that Stunned is much stronger than Weakened against solos.&nbsp; Still, against most solos it’s not 5x as strong.&nbsp; Weakened is not that good, in any case, so not including it in a “condition specific fix” won’t lead to (until end of turn) weaken effects trivializing solo encounters.When you put it that way, I see that the first line should read “Solos make saves at the start of their turn instead of the end of their turn”, and the fact that it’s hard to even describe it correctly means that it’s probably too complicated <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile&nbsp; &nbsp; :)"&nbsp; data-smilie="1"data-shortname=":)" /></blockquote>

[QUOTE="Elric, post: 4749641, member: 1139"] I think of what I'm doing as adding a property to each solo monster to resist status effects better, and using the exact same property each time. As LuckyAdrastus says, your solos look very flavorful and fun to play against. If you could only choose one resilience solution for every solo, which one would you pick? Now you have a default and if you want to create a solo from scratch or further modify an existing one, you can do that as a specific exception. Even a bonus save like the one Klang has doesn’t affect the two big issues, though, which are that a solo has no special defenses against until end of next turn effects, and that it will be affected for at least a round by (save ends) effects. A solo is only affected for 1.25 rounds on average by a (Save ends) effect right now; even having it automatically make saving throws would only decrease this to 1. A bonus save would be handy against RAW Orb Wizards and AV static-save penalty stuff, but I think those abilities should be fixed with a house rule so they aren’t so overpowered, instead of trying to immunize solos from the consequences of static save penalties being so overpowered. I agree with you that Stunned is much stronger than Weakened against solos. Still, against most solos it’s not 5x as strong. Weakened is not that good, in any case, so not including it in a “condition specific fix” won’t lead to (until end of turn) weaken effects trivializing solo encounters. When you put it that way, I see that the first line should read “Solos make saves at the start of their turn instead of the end of their turn”, and the fact that it’s hard to even describe it correctly means that it’s probably too complicated :) [/QUOTE]

Verification