Can you tell me what talents you are using please.... Execute is also not the main dps priority.
Thank zer0kewl, i found a bug and fixed it.Ok so here is my log. Using paid warrior cr. Bg buddy this time. I see in the log it keeps saying "trying to cast execute" but I never see any dmg from execute in the battle log.
View attachment 150410
Ok Alcoal or Tuanha I have a log for you, after many hours trying to pinpoint this problem, its down to DK CR, the dk CR does not work in raids or pre-mades 5 mans are fine, heroics work but run little slow and little buggy, Singular works in raids but it is horrible pls fix this problem or whatever is wrong with this CR. In this log i was in a 5 man then got ported to LFR then it didnt do no actions, even on boss...
but switching in Singular works,Switching locations is a HB bug, not the CR issue.
We will have to wait for HB to fix it in next release.
but switching in Singular works,
Quote From:CodenameG "it looks to be your combat routine, try it with singular and see if the issue persists."
Thank for the log.Ok Alcoal or Tuanha I have a log for you, after many hours trying to pinpoint this problem, its down to DK CR, the dk CR does not work in raids or pre-mades 5 mans are fine, heroics work but run little slow and little buggy, Singular works in raids but it is horrible pls fix this problem or whatever is wrong with this CR. In this log i was in a 5 man then got ported to LFR then it didnt do no actions, even on boss...
Thank for the log.
It look like worked really fine in the 1st part of log.
Then something strange happen:
[23:58:50.412 D] System.Exception: Invalid access to memory location, at addr: F794F734, Size: 20
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
at Styx.WoWInternals.LuaTString..ctor(IntPtr address)
at Styx.WoWInternals.LuaValue.get_String()
at Styx.WoWInternals.LuaEvents.()
at Styx.Pulsator.Pulse(PulseFlags flags)
at Styx.CommonBot.TreeRoot.()
at Styx.CommonBot.TreeRoot.()
at Styx.CommonBot.TreeRoot.()
Is my log ok, would you need a better one, (I can never know if its good =P) and this was right on a boss pull no trash..I'm not sure what going on, my be my CR bug (I don't think this part is from my CR anyway), maybe HB... so I need more time to inspect that issue![]()
Is my log ok, would you need a better one, (I can never know if its good =P) and thankyou for your help[/QUOTE]I'm not sure what going on, my be my CR bug (I don't think this part is from my CR anyway), maybe HB... so I need more time to inspect that issue![]()
Double time
Enrage regeneration
sudden death
shockwave
mass spell reflection
bladestorm
I've been using Execute manually and its amazing. The cr refuses to use it and because of that you miss the oportunity to get a kill, giving them more uptime to dps back.
Hi guys.
Is it possible to add a check if soothing mist is already casting? The player model is acting odd if MW casts SM, brings the target above threshhold and starts casting a new one if the target is brought below that threshhold again. Sometimes it casts SM on CD instead of keep it channeling making it very suspicous.
Great work btw.
my contributionThank zer0kewl, i found a bug and fixed it.
The reason is Execute have 2 spellID Execute = 5308, Execute Arms = 163201. It try to cast Normal Execute 5308 in Arms spec.
Anyway, I've make an improved logic on Execute:
1. Fix that bug of course
2. Will Execute on highest priority when:
- You are in Battleground
- You are in Arena
- Your target is player
- Sudden Death buff expiring soon
- Death Sentence buff expiring soon
Please update and let me know.
And it always FASTER to fix bug with LOG man, I got no idea about your all previous post about "it just not casting Execute" without any LOG to tell what wrong xD
The reason Soothing Mist casts over its self is so it always stays active until it doesn't need to be channeled anymore... any other player could be refreshing it just like the routine isIt actually works a lot better that way.
Thank zer0kewl, i found a bug and fixed it.
The reason is Execute have 2 spellID Execute = 5308, Execute Arms = 163201. It try to cast Normal Execute 5308 in Arms spec.
Anyway, I've make an improved logic on Execute:
1. Fix that bug of course
2. Will Execute on highest priority when:
- You are in Battleground
- You are in Arena
- Your target is player
- Sudden Death buff expiring soon
- Death Sentence buff expiring soon
Please update and let me know.
And it always FASTER to fix bug with LOG man, I got no idea about your all previous post about "it just not casting Execute" without any LOG to tell what wrong xD
Thank zer0kewl, i found a bug and fixed it.
The reason is Execute have 2 spellID Execute = 5308, Execute Arms = 163201. It try to cast Normal Execute 5308 in Arms spec.
Anyway, I've make an improved logic on Execute:
1. Fix that bug of course
2. Will Execute on highest priority when:
- You are in Battleground
- You are in Arena
- Your target is player
- Sudden Death buff expiring soon
- Death Sentence buff expiring soon
Please update and let me know.
And it always FASTER to fix bug with LOG man, I got no idea about your all previous post about "it just not casting Execute" without any LOG to tell what wrong xD