Rogue lvl90 - MoP Dailys Start at: [16:25:09.220 N] Toon stays behind a NPC, ready to kill but performs all the time Code: [16:25:57.356 N] [Singular-DEBUG] .... [Pull] h=100.0%, e=100.0%, moving=False, stealth=True, aoe=1, recup=0, slic=0, rawc=0, combo=0, aoe=1, Sra'thik Hivelord.8F1C, 100.0%, dies -1, 2.0 yds, behind=True, loss=True, rvlstrk=0, rupture=0 [16:25:57.549 N] [Singular-DEBUG] CanCastHack[Pick Pocket]: spell specific CanCast failed [16:25:57.549 N] [Singular-DEBUG] CanCastHack[Ambush]: spell specific CanCast failed [16:25:57.550 N] [Singular-DEBUG] CanCastHack[Cheap Shot]: spell specific CanCast failed [16:25:58.067 N] [Singular-DEBUG] CanCastHack[Pick Pocket]: spell specific CanCast failed [16:25:58.067 N] [Singular-DEBUG] CanCastHack[Ambush]: spell specific CanCast failed [16:25:58.068 N] [Singular-DEBUG] CanCastHack[Cheap Shot]: spell specific CanCast failed doesnt stop. have to put pull by hand.
tumbum, Not sure on that one. That message indicates WOW is saying the spell cannot be cast. When you mentioned pulling by hand, did you move the character or simply have to press the key for Ambush or Cheap Shot?
Why would you wait several months to report an issue that nobody else has reported? Since you are familiar this issue it should be easy for you to duplicate, so please visit the Reporting Bugs [CLICK HERE] page and follow those steps and I'll gladly look into whatever issue you are encountering. Be sure to enable Debug Logging and Debug Logging Spell.CanCast settings in Class Config before pressing Start so the detail needed to drill down in detail on your problem with Thrash is present. Thanks for the post and good luck with your Druid, Bobby53
You have to set the DEBUG on TRUE in the Singular Settings! Very Important for Bobby to get more informations if there is an issue. So better set all your Toon Settings 3x "Debug" True.
My Shaman keeps targetting a mob. Running to that place and then starting to fight. Meaning it will take significant damage before starting to fight. Can't Singular just stop walking and fight when it initiates fights?
I'll need more than that, because my Shaman doesn't. Of course, there are 4 different specs of Shaman (Lowbie counts as one) each with up to 3 context specific spell priorities, each with potentially an additional AoE specific spell priority, which could have been run under any of a number of BotBases with a seemingly limitless variety of profiles, and with varying components active. The likelihood that your Shaman was doing the same thing the same way with the same abilities as mine is unlikely. That's part of the reason log files are so critical. As for the movement, whichever component initiates the movement needs to also stop the movement, otherwise other component won't know when its done moving. There are exceptions to this, but for me to look into the specifics of a case you observed and look for opportunies to improve, I'll need a complete debug log file as described in Reporting Bugs [CLICK HERE]. Be sure to do the following before pressing Start- Click Settings button - Set Log Level to Diagnostic - Click Save button - Click Class Config button (and leave window open) - Click Start button # leave running until the issue occurs - Immediately click LogMark button Each LogMark press will create a unique entry in the log file you can reference to describe specifically when the behavior you saw occurred. If you encounter additional problem it is easy to click the button again and mention in your post "Condition A happened at Log Mark #1, Condition B at LogMark #2, etc." Post as described in the post I linked and I'll look into this for you. -Bobby53
Sorry didn't attach a log since I described what I thought was a general behavior. This is what it looks like 1. Target mob 2. Move to that target location 3. Aggro mob (could it be because of casting an instant? or just being close enough?) 4. Mob starts running towards you 5. Character runs through mob to set waypoint taking damage until you get to that point. 6. Start combat rotation. View attachment 5768 2013-05-01 09.46 - Copy.txt At first I didn't understand the logmark remark so I wrote a comment in the file. But I now found the plugin you are referring to. http://www.thebuddyforum.com/honorb...g-file-while-using-wow-client.html#post727596 Wouldn't this be a nice addition to the "regular" HB core. So that you can just click a button and describe the problem?
Bobby, I have no idea what is going on here but seems that I will run through several mobs, not attack trying to interact for a quest. Just stand there and let mobs kill me and never attack until after I manually open item, then I turned and attacked? I died 4 or 5 times before I hit logmark. I then opened item and hit logmark again. lvl 65 windwalker monk. Fresh clean install. Ty in advance.
Ruinit, Thank you for the complete debug log file! You are getting an exception due to HonorBuddy having a problem checking whether a WoWGameObject nearby is an herb: Code: [00:05:29.816 D] [B]Activity: Moving towards Shienor Talonite[/B] [00:06:02.237 D] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.AccessViolationException: Could not read bytes from 000001B8 [299]! at Styx.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative) at Styx.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative) at Styx.WoWInternals.WoWObjects.WoWGameObject.GetCachedInfo(GameObjectCacheEntry& inf) at Styx.WoWInternals.WoWObjects.WoWGameObject.GetDataSlot(UInt32 dataSlot, Int32& value) at Styx.WoWInternals.WoWObjects.WoWGameObject.GetDataSlot(GameObjectDataSlot dataSlot, Int32& value) at Styx.WoWInternals.WoWObjects.WoWGameObject.() at Styx.WoWInternals.WoWObjects.WoWGameObject.get_LockType() at Styx.WoWInternals.WoWObjects.WoWGameObject.get_IsHerb() at Bots.Grind.LevelBot.LevelbotIncludeLootsFilter(List`1 incomingObjects, HashSet`1 outgoingObjects) --- End of inner exception stack trace --- at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner) at System.RuntimeMethodHandle.InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeType typeOwner) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) at System.Delegate.DynamicInvokeImpl(Object[] args) at System.Delegate.DynamicInvoke(Object[] args) at Styx.CommonBot.Targeting.(Delegate , Object[] ) --> System.AccessViolationException: Could not read bytes from 000001B8 [299]! at Styx.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative) at Styx.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative) at Styx.WoWInternals.WoWObjects.WoWGameObject.GetCachedInfo(GameObjectCacheEntry& inf) at Styx.WoWInternals.WoWObjects.WoWGameObject.GetDataSlot(UInt32 dataSlot, Int32& value) at Styx.WoWInternals.WoWObjects.WoWGameObject.GetDataSlot(GameObjectDataSlot dataSlot, Int32& value) at Styx.WoWInternals.WoWObjects.WoWGameObject.() at Styx.WoWInternals.WoWObjects.WoWGameObject.get_LockType() at Styx.WoWInternals.WoWObjects.WoWGameObject.get_IsHerb() at Bots.Grind.LevelBot.LevelbotIncludeLootsFilter(List`1 incomingObjects, HashSet`1 outgoingObjects) So Questing Bot initiated movement towards the named mob in bold above, then encountered an exception in Targeting trying to check if a WoWGameObject was an Herb or not. That is something occuring within HonorBuddy and driven by something within the Questing profile. Not sure what happened except something relative to that quest caused the Questing Bot to not call Singular, as it's not called from the point you start moving towards to the named mob to the point the toon dies. It appears that after you manually opened the WoWGameObject, the code that was having the issue was no longer invoked so things began to function as expected. This isn't a combat routine issue. You'll want to post in the HonorBuddy Support Issues as this appears to be a HonorBuddy, Questing BotBase, or Profile issue. You can just link back to this post for reference. Thanks again for your post and good luck with your Monk, Bobby53
23051602, Thanks for the complete debug log! There really isn't general behavior in Singular. Everything that occurs factors in behavior specific to your class, spec, talents, glyphs, botbase, and a lot of different combat scenario conditions. I can clearly see the issue occurring in the log based upon the debug logging being turned on, but I don't seem to be able to duplicate the behavior and don't see how the code associated with Pull and Combat for your Elemental failed in that circumstance. If I don't find the issue, I'll add additional logic tracking statements to explicitly trace what is occurring and ask you to run with that for awhile so we can get to the bottom of it. Thanks for your post and good luck with your Shaman, Bobby53 Note: forwarded the request regarding LogMark and there should be a Log Mark button or similar added in an upcoming release. Thanks for the suggestion! Edit: Found the problem. Fixed in next release. Thank you for the report!
Yeah ty as always Bobby! I figured out it was HB and posted in forum already. Nat is working on it Keep up the good work!
Singular Users: The revisions to movement (and specifically stopping) in the .2341 build are promising, but currently there are circumstances it will run through to the next hotspot rather than stopping. This will be fixed in the next release. If your character does not seem to be stopping promptly where it did before, and possibly runs through mobs it should have stopped short of to fight, this is a known issue. If this is causing significant issues, you can downgrade to the prior release (still available on the download post in Singular.) Thanks for your patience and look for a release soon, Bobby53
Bobby - I have the classes that you currently have as and [P] - would happily lend them out for bug fixes.
Just noting that the walking while having pulled three mobs problem exist in the downgraded version too.
this is so true there is a quest in durator you need to kill 12 birds its just keep standing in one spot waiting for the birds to respawn i mostly do that quest self i hope u can fix that movement
