Moving Target 03 Overhaul: Troubleshooting

[pootthedestroyer]

I'm attempting to create a new Moving Target 03 perk with functionality split between combat and noncombat, or, alternatively, between "weapon drawn" and "weapon not drawn."

 

There appear to be Function calls for both conditions: IsInCombat and IsWeaponDrawn, respectively.

 

Unfortunately, both functions, when applied as a Perk Condition, appear to break functionality.

 

Specifically: I'm attempting to cordon off MT03's vanilla effect (50% AP Cost for Sprinting) to only trigger out-of-combat (or with weapons sheathed.) Attempting to apply either function - whether by using Not Equal To / 1.000000 or Equal To / 0.000000 - as a Perk Condition causes the benefit to never trigger, ever.

 

I've also attempted two different variations (on both functions) for the Subject to be the player. The first is the default Subject call. The second is Reference, where Reference Object = player [000014].

 

All four possible combinations have produced the exact same in-game result: the benefit not triggering under any circumstances.

 

The in-combat/weapon-drawn functionality I have plotted out (and have already added into the MovingTarget ability-spell) obviously relies upon the opposite check for one of these Functions. That means that unless and until I can figure out what's going wrong with them, I cannot do any testing on the more complex branch of the perk.

 

For future reference, the more complex branch involves a Slow Time effect while Sprinting, a movement speed buff while Sprinting, a Sprinting AP cost multiplier (2x base cost, which would equal 4x new out-of-combat cost) and a prohibition on wearing Power Armor to access it. The final condition I've already used successfully elsewhere. I suspect that once the functions for the combat condition is sorted, I'll have to test the magic effect calls and likely create custom spells to avoid classification conflicts (e.g. constant effect versus fire-and-forget. I had to do this to make a persistent Chameleon effect while sneaking for my revamped Sneak 05 to work properly.)

 

Any advice or insight would be much appreciated.

Edited December 1, 2015 by pootthedestroyer

[DominusSicarum]

Well, you can make it work, actually.

 

http://s17.postimg.org/p8miioz73/Is_In_Combat.jpg

Here's your basic setup (this makes sprint ap drain zero when not in combat). Note: all fields are important.

[ShinraStrife]

Well, you can make it work, actually.

 

 

Here's your basic setup (this makes sprint ap drain zero when not in combat). Note: all fields are important.

 

Dominus beat me to it XD

[pootthedestroyer]

I'll double check all of the unknown/ambiguous fields when I switch partitions later tonight, but what I'm attempting to relay is that this setup is what I tried (among three others,) and when using a nonzero value for the Float, it was not producing any result. Did you guys actually check the functionality with a nonzero number in-game? I did, with the vanilla value of 0.500000. I directly witnessed it fail to apply in-game, while most assuredly out of combat.

[DominusSicarum]

Yeah, I tried 0.1 and 0.2 as well. They work. Gonna try 0.5.

 

You are both activated your plugin and have the perk, right?

 

EDIT: yeah, 0.5 works like a charm.

Edited December 2, 2015 by DominusSicarum

[pootthedestroyer]

Differences noted: Parameter #3 in mine was set to -1, due to that being the convention for virtually every perk condition I've added thus far. I've never had that break functionality before.

 

I'm going to try adjusting that value everywhere and see if it fixes my other problems. That would be one hell of a catch in terms of a situational issue.

[pootthedestroyer]

Confirmed. Adjusting Parameter #3 from -1 to 0 resolved the issue with the out-of-combat functionality. Now moving on to testing in-combat modifications.

 

Thank you so much for the help, though I wish I understood what I actually just *did.*