Shattered Kingdoms

Also, how is failing your will save against intimidate any worse than failing your will check against charm person/sleep or fort check vs petrification/fod?

At least you can still abandon ship while intimidated.

This just strikes me as whining about something that is mildly useful and that the lighties don't have access to.

Intimidate is totally not just "mildly useful."

You don't deserve a buff because there may be a bug.

I'm sorry you feel that people are trying to nerf you, or it's whining. I just don't have that kind of motivation.

Honestly, I really don't think you can tell me it's not a bug/broken thing that the members of your group don't face the same restrictions you do in order to trigger/be protected by a skill.

Though, it may not be. It depends on what Dulrik really thinks on it - this is just here to bring it to his attention and let whatever decision be made on it.

This is going to render intimidate completely useless, since then everybody in the other group can just target the same person as whoever succeeded.

Nevermind that you don't have to pass intimidate to autoassist.

Uhg NO.

The group should gain the initial benifit, once the group is engaged it should drop for them, it should drop when the hellion engages and not persist for several rounds after the hellion has fled.

I'm not sure where you guys get that "after the group has already initiated a fight" equates to "none of the other members of the party should be protected against initiation by intimidate."

It looks like a complete red herring when you make that the argument, and then argue against that. No one is saying they shouldn't be protected against initiation by the hellion's intimidate. The argument here is that once all the initiation is done, the fighting is started, and things are under way - intimidation still protects people that are actively in combat with an enemy group. And the person that successfully "broke through" intimidate has already started combat, meaning the entire group can auto assist - meaning the thing WickedWitch argued against is already in place, now. It only prevents spell-casting, not melee.

I didn't read that last post, but are you arguing with yourself, jerin?

No. It was me re-stating my initial post, since there were posts that made it clear I wasn't clear enough in my initial post about what I felt the bug was. Let me edit it so it's more clear.

This sounds like something that may have broken when i made the change that everyone in a party is considered fighting even if you arent in melee. Not sure because its hard to follow the argument. If two parties are already fighting each other, i dont think intimidation should be coming into play.

The specific instance of it happening is as follows:

Player A recites a scroll at Player B with two spells. Player C is the hellion.

The first casting passes Player C's intimidate check but the spell fails, so Player B, who was targeted, engages the party in combat.
The second casting fails the intimidate check. Arguably, there shouldn't be an intimidate check here to begin with, as the targeted player, Player B, is in combat already.

There is another recital of another scroll later, but even though Player B has been in combat for one or two rounds, Player A still cannot recite at Player B -- or, really, any other member of the group, even though a few of those group members are currently fighting.

My suggestion is as follows:

If Player B (in the enemy party, with Player C) is NOT engaged, Player C's intimidate protection should extend to him. However, if Player B is engaged with Player A's party, then Player A and anyone else in Player A's party should be able to hit or target him.