CombatCounter() revisited

[WizWom]

I had a block to stop combat only actions...

IF
CombatCounter(0)
!Detect([0.0.0.0.WXJON_TARGET])
!Detect([ENEMY])
THEN
RESPONSE #100
END

 

So, imagine my surprise when I would get combat prep spell casting occasionally in the following situations:

 

1) After talking to an NPC

2) After failing a Hide in Shadows

 

So, generally, I think using it as anything but a "combat might have just ended" check is dangerous.

[Avenger]

If i understood you correctly, you say that combatcounter is not 0 after those listed events?

[devSin]

Dialogue can hiccup the combat counter. Using the invalid block to stop the rest of the script from running is what's truly dangerous, though.

[WizWom]

I'm a bit confused - why is that dangerous? As I see it, it saves a lot of CPU.

[Miloch]

I think he's saying you should throw a NoAction() in there. Though why exactly it's dangerous not to have it, other than it being an invalid block, I forget.

[igi]

Noted.