Djinni/Efreeti problems

[Demivrgvs]

We've already talked about their wrongly assigned scripts but i've found another problem which may be related to the changes you've made to wtasight.bcs.

If i use a Djinni/Efreeti manually they became hostile as soon as i make them cast anything on themselves (like invisibility, shadow door, etc.). However i can have them cast spell on my party and party can buff them without problems. I'm sure it's related to this script, i've already disabled the generic ones because of the gas form change "incompatibility" but i'm not sure why it happens...

 

Can it be related to this?

 

IF

!Global("inafight","LOCALS",1)

OR(7)

AttackedBy([GOODCUTOFF.0.0.0.0.SUMMONED],DEFAULT)

AttackedBy([PC],DEFAULT)

AttackedBy([FAMILIAR],DEFAULT)

AttackedBy([ALLY],DEFAULT)

AttackedBy([CONTROLLED],DEFAULT)

AttackedBy([CHARMED],DEFAULT)

SpellCastOnMe([GOODCUTOFF.0.0.0.0.SUMMONED],0)

THEN

RESPONSE #100

Enemy()

SetGlobal("inafight","LOCALS",1)

SetGlobalTimer("stayontarget","LOCALS",TWO_ROUNDS)

SetGlobalTimer("seedefences","LOCALS",ONE_ROUND)

Continue()

END

[Demivrgvs]

By the way i've solved the problem, SpellCastOnMe([GOODCUTOFF.0.0.0.0.SUMMONED],0) causes summonend creatures to turn hostile if you manually use them to cast spells on themselves (and/or if another summoned creatures cast a spell on them probably).

 

Therefore it's only a matter of removing that line and changing OR(7) in OR(6) and everything will be fine!

 

IF

!Global("inafight","LOCALS",1)

OR(6)

AttackedBy([GOODCUTOFF.0.0.0.0.SUMMONED],DEFAULT)

AttackedBy([PC],DEFAULT)

AttackedBy([FAMILIAR],DEFAULT)

AttackedBy([ALLY],DEFAULT)

AttackedBy([CONTROLLED],DEFAULT)

AttackedBy([CHARMED],DEFAULT)

THEN

RESPONSE #100

Enemy()

SetGlobal("inafight","LOCALS",1)

SetGlobalTimer("stayontarget","LOCALS",TWO_ROUNDS)

SetGlobalTimer("seedefences","LOCALS",ONE_ROUND)

Continue()

END

[DavidW]

Thanks, will implement.

[Demivrgvs]

Wtasight.bcs still has this inconvenient in SCS II v4.

[DavidW]

Wtasight.bcs still has this inconvenient in SCS II v4.

 

Oops.

 

Okay, will certainly fix in v5!