IsInCombat (Conditions Window) : V

» Wed Jun 20, 2012 5:24 am

What's the integer value for when you use IsInCombat in the conditions window? It normally defaults to 0, but you can change it. Nothing similar to it in the papyrus version.

» Tue Jun 19, 2012 8:44 pm

I'm not sure what you mean, IsInCombat is 0(false) when the actor is not in combat or 1(true) when the actor is in combat.

» Wed Jun 20, 2012 2:45 am

there is an extra integer choice/option when you use it as a condition.

the condition looks something like this when its in use:

IsInCombat > Integer choice box > Operator box > Value

This confused me also, so I used GetCombatState instead (0 = not in combat, 1 = in combat, 2 = searching)

» Wed Jun 20, 2012 2:49 am

there is an extra integer choice/option when you use it as a condition.

the condition looks something like this when its in use:

IsInCombat > Integer choice box > Operator box > Value

This confused me also, so I used GetCombatState instead (0 = not in combat, 1 = in combat, 2 = searching)

Glad I'm not the only one confused. I left it at 0 and it seems to work, not 100% sure. The NPC I ran it on appeared skittish - as if not sure which AI to run. So I added the condition but it still seemed skittish.

Might try GetCombatState instead to be sure. Thanks!

» Wed Jun 20, 2012 8:08 am

You can either use IsInCombat == 1 for someone who is in combat, or IsInCombat == 0 for someone who is not in combat. You can also make things complicated like IsInCombat !=1 or !=0. >0 or < 1 etc.

» Wed Jun 20, 2012 12:30 am

You can either use IsInCombat == 1 for someone who is in combat, or IsInCombat == 0 for someone who is not in combat. You can also make things complicated like IsInCombat !=1 or !=0. >0 or < 1 etc.

What I meant was the other number in the "Select Function Parameters" box. My fault for not being clear. I didn't mean the Comparison and Value fields. When you add IsInCombat to a conditions window yourself, you'll see what I am talking about.

» Tue Jun 19, 2012 10:38 pm

I suppose the first parameter is the combat situation (0 out of combat, 1 in combat, 2 searching) and the second one 1 is in the state described, 0 is not. It's only an assumption though.

» Wed Jun 20, 2012 6:25 am

I suppose the first parameter is the combat situation (0 out of combat, 1 in combat, 2 searching) and the second one 1 is in the state described, 0 is not. It's only an assumption though.

So should I be setting it to 1 if I want to check it the player is in combat (since I'm running it on the player reference).

» Wed Jun 20, 2012 2:55 am

So should I be setting it to 1 if I want to check it the player is in combat (since I'm running it on the player reference).

Only if my assumption is correct.

» Wed Jun 20, 2012 5:13 am

Just tested it, and it doesn't seem to matter what you put for the first parameter ("Select Function Parameter"), the game seems to ignore it. The only thing that matters is the value you compare it to.

» Wed Jun 20, 2012 8:34 am

Just tested it, and it doesn't seem to matter what you put for the first parameter ("Select Function Parameter"), the game seems to ignore it. The only thing that matters is the value you compare it to.

Thanks. That was how it worked in Oblivion too. It must be there to confuse us