5 réponses à ce sujet

[mogromon]

im doing some changes to Frenzy, if there are no nearby enemies you start attacking your friends, so to force this
i use SetCommandable(FALSE); the question is what to do when the frenzy ends.

Obviously i must use SetCommandable(TRUE), but the doubt resides in what happens when you have another effects like confused or frightened. It's easy to chech this via GetHasEffect(effectype) and as far as my tests went if i don't use SetCommandable(TRUE) to a confused creature, it wont be commandable until the effect expires and is commandable once again. But I dont fully understand charmed and dominated effects and how they work in PC's. Reading the difficult settings, it says that this effects when used on a PC add a dazed effect but i have no clue how to force an NPC to cast a domination effect on me, so can anyone tell me what  this spells do?.

If i just use SetCommandable(TRUE) without checking effects, will this have a negative impact on the effects or do they still work as intended.

And finally, does anyone knows all the effects that use SetCommandable(FALSE) to work so i can check them before using SetCommandable(TRUE), like sleep, fear, confused.

[M. Rieder]

You can open up the scripts for fear, confused, etc... Use the toolset to search for a script and type fear or whatever the name is and generally you will be able to find it that way.

[mogromon]

i found some that way: nw_g0_.... but dont know if paralyzed or stunned have a hard coded SetCommandable(FALSE)

[The Fred]

I would suggest just applying an Insane effect. I think that would work. You might need to do something about immunity items, though, like decide whether they would bother you if they prevented the effect.

[mogromon]

Insane effect seems like a good idea. I've doing some tests just using SetCommandable(TRUE) withouth checking the current state of the target, and in general it causes some malfunctions for some seconds if the effect has a HB script or some animation glitch if you're paralyze or something like that.

[The Fred]

SetCommandable() can be a bit wonky, mostly I think because there are routines which temporarily turn it off, but forget to check if it were off in the first place, and can turn it back on again afterwards even when they shouldn't. To be honest, with the best will in the world, it's pretty much not possibly to program a 100% foolproof way of using functions like this, just because you could get multiple scripts acting more or less at once and interacting with each other in wierd ways. Also, turning commandability off could interrupt other routines and screw them over in other ways.