Removing an attack I do not wish in my routine ?

Try #3: View attachment Darkness_KineticCombat.cs

Whirlwind is no longer used at all for Shadow/KineticCombat:
* It takes 2secs to cast, so not good as an interrupt
* It only lasts 8secs for a Shadow, so not good as crowd-control

cheers,
chinajade

 

I see what might be happening. I did notice WingIt was casting on other targets without changing current target. I am currently fighting linked mobs which are spread out and ranged. This could be causing WingIt to run around to get in range to use these CC abilities and so forth. It would indeed account for the seemingly unnecessary running around. When the mobs are spread out and ranged mobs it is more than just an annoyance it is the difference to killing the entire pack in 10 seconds to 20 seconds. I like that wingit thinks of this but for my geared character just farming it just slows me down allot. I have even refined the default combat even more in the last hour and now my character has gone from being a baddass to just slicing up my enemies like they didn't exist.

Unfortunately I do not know how you can change WingIt to accommodate both styles of play

 

Can a combat routine create grey errors ?

 

You've found a bug in WingIt, which has been repaired in changeset #709. We previously were not doing LoS checks for targets selected for Interrupt or CrowdControl. Thanks!

Also, I botched the edit/compile in #3. Here's try #4: View attachment Darkness_KineticCombat.cs

Unless we get a GUI in place for WingIt that lets you select this, you probably won't. Choice in CCs is good. Ideas cross-pollinate, and hopefully the best will rise to the surface. Even if WingIt doesn't quite fit your needs, we'll still strive to make it better.

Please let us know of any further findings. Should I fold in the changes to WingIt/Shadow/Kinetic as an improvement or not?


cheers,
chinajade

 

GreyMagic errors happen because BW is not fully 'connected' to the SWtOR client. The problem is caused by bad interaction between BWcore and the SWtOR client. This might be a problem due to the operating system, or race conditions caused by multiple cores or the multi-threaded nature of the SWtOR client.

Any use of the BW API can cause a GreyMagic error to happen. The entity that triggers the error is not at fault--the problem is down low in BWcore and the SWtOR client.

And yes, since combat routines make use of the BW API, they can aggravate GreyMagic errors. When it happens, the fault is neither your's, nor the combat routine's.


cheers,
chinajade

 

Since removing skills in the default combat I have noticed a marked improvement before my character starts to slow down in its decision making, that is why I asked.

I will try the new revision after the servers come back up.