forums.cubicle7.co.uk
archive

Dunkelbrink wrote: ↑

Sat Feb 17, 2018 3:20 pm

But what happens to a poisoned character who is poisoned again? Since being poisoned does not mean "getting wounded" my reading is that nothing additional happens; the hero is already considered to be wounded (and needs to be actually Wounded to drop).

A different reading, where getting Poisoned equals getting Wounded, would also make a special rule for being poisoned unnecessary, so why have it? It would also make Poison the far deadliest called shot in the game - Pierce would be laughable in comparison, with autowound regardless of armour through every called shot.

I had always played that Poisoned equal Wounded (although I have to say it never happened in my games that someone was Posioned twice). BUT I have to say that your reading of the rules makes a lot more sense and seem more according to the intention of the authors.

I'll go with that way of treating Poisoned from now on, it seems the right way to me.

There's always room for improving!

Rich H wrote: ↑

Sat Feb 17, 2018 8:27 pm

Different posions would still apply their own effects, I'm just really talking about the Poison status and the fact that I don't agree with letting two poison attacks effectively cause two Wounds. I think Poison attacks should only count as one Wound and no more due to the nature of them not requiring Protection tests.

Okay, that is perfectly reasonable.

Ah thanks Random and everyone else. I hadn't realised that it was a Called shot effect from just reading the Spider entry on the rules book (p241-2). Haven't used spiders (or anything else using Poison) before...
I can see how this represents the rare occasion when a spiders sting would actually penetrate armour or find an unarmoured location. Must have been a band of particularly nasty Spiders the Company came across on this occasion
Cheers!

I also see that in my hasty reading during the session that I missed two(!) references mentioning Poisoning relating to Called Shots amongst the Spider rules!

So, now I have acquainted myself with the Called Shot rules - I want to confirm one last aspect.
If an Adversary attempts a Called Shot, I presume that, as well as successfully reaching the attack Target Number, it also requires a 6 on it's Success dice to hit with a Called Shot.

I see that the rules don't include the possibility of a Fumble if an Adversary attempts a Called Shot i.e. if a Gandalf is rolled. I can imagine that is extra work for the LM but it could be amusing for the Company if a troll hit a fellow troll or tripped over his own feet.

Winterwolf wrote: ↑

Sun Feb 18, 2018 6:09 am

I see that the rules don't include the possibility of a Fumble if an Adversary attempts a Called Shot i.e. if a Gandalf is rolled. I can imagine that is extra work for the LM but it could be amusing for the Company if a troll hit a fellow troll or tripped over his own feet.

I would say that you should let the adversary Fumble if he fails, since the RAW states that the rules for adversaries only change how Called Shots are triggered, not how they will be executed.

The rules for triggering a called shot work differently for creatures confronting a company of heroes.

and by fail, I meant a Gandalf rune

Dunkelbrink wrote: ↑

Sat Feb 17, 2018 3:20 pm

A different reading, where getting Poisoned equals getting Wounded, would also make a special rule for being poisoned unnecessary, so why have it?

Possibly because there might be side effects associated with poison, or even possible treatments.

Dunkelbrink wrote: ↑

Sat Feb 17, 2018 3:20 pm

It would also make Poison the far deadliest called shot in the game - Pierce would be laughable in comparison, with autowound regardless of armour through every called shot.

Yeah. It really shouldn't just bypass armor. Frankly, I think the poison rules are kinda lacking. I'd much rather see some "types" of poison with some sort of side effects. For instance the Spider venom in the Hobbit made the Dwarves sleepy, so I could see them acting as Fatigued, not Wounded.
By contrast some orc wielded envenomed weapon probably shouldn't have any effect if the weapon doesn't pierce the skin.

atgxtg wrote: ↑

Sun Feb 18, 2018 3:28 pm

Yeah. It really shouldn't just bypass armor. Frankly, I think the poison rules are kinda lacking. I'd much rather see some "types" of poison with some sort of side effects. For instance the Spider venom in the Hobbit made the Dwarves sleepy, so I could see them acting as Fatigued, not Wounded.
By contrast some orc wielded envenomed weapon probably shouldn't have any effect if the weapon doesn't pierce the skin.

If the weapon did not pierce the skin then the attack was unsuccessful in the first place because the character succeeded in his Protection test (and presumably the toxin was not a contact poison that would be absorbed through the skin. That's how nasty a clever LM might be, but let's not over-complicate matters ). RAW already takes into account the additional effects of different varieties of poison:

Different poisons may provoke different additional effects. A Poisoned character remains as such until a proper remedy is applied, or the effects of the particular poison affecting him wear off.

Even if Poisoned character is not again Wounded, the additional effects of a specific poison might very well place the affected character in a permanent coma, paralyze him, or otherwise kill him before the effects can be alleviated with a remedy or otherwise where off. The Hero is fortunate if he is only put to sleep for a day.

The character who says "I'm already poisoned, I might as well charge through the spiders!" risks getting an actual Wound. Which, since he is "considered Wounded", would be bad.

As LM, I might further rule that a character who did that might be subject to additional attacks from angry, swarming spiders, even after he is unconscious...

It seems to me that if Poisoned was meant to be a Wound, and not just like a Wound, the language would have simply said, "A Poisoned character is also Wounded."