What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

HB ARCHIVES: Singular--DO NOT DELETE

Singular "confused" if target dies in between selecting and placing Light's Hammer

What Class+Spec are you?: Ret paladin
What 'context' is the bot in? (Instance, BG, Normal): Normal, grinding mobs in VoEB
What level are you?: 90
Have you made any modifications to Singular?: Yes, (Class Specific) Blessing is set to Might, Seal is set to Justice. The rest is default.
What time (HH:MM:SS) or LogMark did your issue occur? [17:45:41.833 N] (near bottom of log)
What happened (be specific)?
I play a Paladin and have the Light's Hammer ability. HB will try to use the ability when there is more than 1 mob attacking. This works great most of the time.

THE PROBLEM arises when the CURRENT mob targeted dies in between the first action of activating Light's Hammer and the second action of placing the "hammer" on the ground.

IF the mob dies in between those two actions the bot will not change targets, will not place Light's Hammer on the ground, and will just sit there until it dies or until I manually place the hammer.

For the time being I will use a different talent, but I like that this talent does AOE damage as well as healing.

If you look in the attached log you will see (near the bottom of the log) the repeated text:

"[17:45:41.833 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:43.856 N] [Singular] EnsureTarget: no valid target set -- skipping spell priority
[17:45:43.995 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:46.189 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:48.383 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:50.607 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:52.800 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:54.813 N] [Singular] EnsureTarget: no valid target set -- skipping spell priority
[17:45:54.975 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:57.180 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:59.408 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:01.634 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:03.821 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:05.898 N] [Singular] EnsureTarget: no valid target set -- skipping spell priority
[17:46:06.041 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:08.246 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:10.450 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:12.623 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:14.820 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:16.883 N] [Singular] EnsureTarget: no valid target set -- skipping spell priority
[17:46:16.968 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1! "

If you read the log you will see that immediately after this text the log says the target is dead. That's because I manually killed the last, un-targeted mob. My manual action of selecting and killing the last mob is what selected the target, of which the bot realized was dead. (hope that wasn't too confusing, all I'm trying to say is "THIS IS WHEN I STEPPED IN AND TOOK OVER")

The issue can/will be easily duplicated with any mob and in any area. It's not an issue based on the environment of the character, it's simply Singular not knowing what to do when it's attempting to place Light's Hammer, yet it's target is dead. How do I know this? Because, when HB uses Light's Hammer regularly, it will place it EXACTLY at the location (X, Y, Z) of it's current target. THIS is the issue, because if it's current target dies it does not have a location to place the hammer (nor does it have a logical reason to place it) so it will simply wait until it is out of combat to continue it's routine.

Possible solution: give singular an "if, when" command to do one of the following things:

1) ONLY use Light's Hammer when the current targeted mob's HP is above 50% AND there is more than one mob.
2) When casting Light's Hammer, place at characters current location, not the target's. (it's radius is large enough to reach any mob that is in melee range)
3) Use Light's Hammer on the OTHER mob, not the currently targeted one.

Did you attach a complete debug log? (choose one: YES or YES) Yes (attached below)


EDIT: I just realized my log isn't in diagnostic mode. I will recreate the event in diagnostic mode and submit another log. TY

EDIT: After running the bot in diagnostic mode for a while it happened again. This time it was a different mob, same situation. The only difference is that I didn't step in to do anything. I let it attack to see what would happen and HB kicked in again after the mob had brought it down to when it healed itself at 36.6%HP (the Singular setting for Flash of Light was set at 50% HP). This must have a higher priority than continuing in it's current action? Anyway, that kicked it back into gear and it was able to continue as usual.

I've attached the new log below (it's the compressed one). The action starts at this time stamp: [19:38:12.553 N] It goes to cast Lights Hammer, and then says "YourCurrentTarget: changed to: (null)" which I believe commences the start of the bug.
 

Attachments

Is it normal, that Singular does not use Horn of Winter with a DK?

?dit: Okay, I'm fiddling with the Blood.cs file. Will post results as soon as I've got them in place.
?dit2: normal mode Blood DKs have no Horn included in their Spellpriorities.

I just added
Code: 
Spell.Cast("Horn of Winter", ret => !StyxWoW.Me.HasAura("Horn of Winter")),
to the normal spell priority list. Works now. :)
 
so i am using gatherbuddy 2 and i am running in to a problem in dread wastes.
Ill dismount to mine a node and end up pulling a mob, who somehow ends up standing right on top of me. so my toon will just stand there healing him self over and over. and not attack.

here is part of the log

[04:40:55.503 D] Stop and dismount... Reason: Combat
[04:40:55.935 D] Changed POI to: Type: Kill, Name: Mistblade Ripper
[04:40:56.109 N] [Singular] Switching to BotPoi: Mistblade Ripper.DA01!
[04:40:57.567 D] (Singular) [CombatLog] SPELL_CAST_FAILED Mining#74517 failure: 'Interrupted'
[04:40:57.542 N] [Singular] Casting Berserking on Me @ 100.0%
[04:40:58.094 N] [Singular] Casting Moonkin Form on Me @ 100.0%
[04:40:58.893 D] [Lua.Events] Attached to event SPELLS_CHANGED with handler OnSpellsChanged
[04:40:58.893 D] PB 1.634: Pulsing Tradeskills from OnSpellsChanged
[04:40:59.858 N] [Singular] Casting Sunfire on Mistblade Ripper.DA01 @ 100.0% at 4.6 yds
[04:40:59.915 D] (Singular) Adding DoT: Sunfire
[04:41:01.708 N] [Singular] Casting Lifeblood on Me @ 92.7%
[04:41:03.201 N] [Singular] Casting Moonfire on Mistblade Ripper.DA01 @ 98.1% at 4.6 yds
[04:41:03.283 D] (Singular) Adding DoT: Moonfire
[04:41:04.092 D] PB 1.634: Updated tradeskills from OnSkillUpdateTimerCB
[04:41:05.490 N] [Singular] Casting Starsurge on Mistblade Ripper.DA01 @ 95.8% at 4.6 yds
[04:41:07.300 D] (Singular) Spell.Cast("Starsurge"): cast has ended
[04:41:10.533 N] [Singular] Casting Rejuvenation on Me @ 79.3%
[04:41:22.617 D] PB 1.634: Updated tradeskills from OnSkillUpdateTimerCB
[04:41:24.044 N] [Singular] Casting Rejuvenation on Me @ 73.8%
[04:41:32.297 N] [Singular] Casting Barkskin on Me @ 67.7%
[04:41:34.151 N] [Singular] Casting Rejuvenation on Me @ 74.4%
[04:41:45.457 N] [Singular] Casting Rejuvenation on Me @ 70.8%
[04:41:56.142 N] [Singular] Casting Rejuvenation on Me @ 76.6%
[04:42:07.216 N] [Singular] Casting Rejuvenation on Me @ 76.0%
[04:42:20.539 N] [Singular] Casting Rejuvenation on Me @ 78.4%
[04:42:31.643 N] [Singular] Casting Rejuvenation on Me @ 68.5%
[04:42:35.680 N] [Singular] Casting Barkskin on Me @ 69.8%
[04:42:42.124 N] [Singular] Casting Rejuvenation on Me @ 71.0%
[04:42:52.999 N] [Singular] Casting Rejuvenation on Me @ 75.3%
[04:43:02.271 N] [Singular] Casting Lifeblood on Me @ 65.1%
[04:43:03.088 D] PB 1.634: Updated tradeskills from OnSkillUpdateTimerCB
[04:43:03.415 N] [Singular] Casting Rejuvenation on Me @ 66.8%
[04:43:16.692 N] [Singular] Casting Rejuvenation on Me @ 60.5%
[04:43:23.324 D] PB 1.634: Updated tradeskills from OnSkillUpdateTimerCB
[04:43:30.203 N] [Singular] Casting Rejuvenation on Me @ 59.5%
[04:43:35.858 N] [Singular] Casting Barkskin on Me @ 52.5%
[04:43:40.502 N] [Singular] Casting Rejuvenation on Me @ 55.3%
[04:43:51.449 N] [Singular] Casting Rejuvenation on Me @ 59.9%
[04:43:57.956 N] [Singular] Casting Berserking on Me @ 61.0%
[04:44:02.300 N] [Singular] Casting Rejuvenation on Me @ 59.7%
[04:44:13.357 N] [Singular] Casting Rejuvenation on Me @ 63.4%
[04:44:24.437 N] [Singular] Casting Rejuvenation on Me @ 54.6%
[04:44:35.944 N] [Singular] Casting Rejuvenation on Me @ 50.1%
[04:44:38.081 N] [Singular] Casting Barkskin on Me @ 49.6%
[04:44:46.328 N] [Singular] Casting Rejuvenation on Me @ 50.8%
[04:44:56.983 N] [Singular] Casting Rejuvenation on Me @ 50.1%
[04:45:02.522 N] [Singular] Casting Lifeblood on Me @ 51.0%
[04:45:02.758 D] PB 1.634: Updated tradeskills from OnSkillUpdateTimerCB
[04:45:07.910 N] [Singular] Casting Rejuvenation on Me @ 58.3%
[04:45:21.414 N] [Singular] Casting Rejuvenation on Me @ 56.4%
[04:45:23.410 D] PB 1.634: Updated tradeskills from OnSkillUpdateTimerCB
[04:45:34.582 N] [Singular] Casting Rejuvenation on Me @ 58.5%
[04:45:38.274 N] [Singular] Casting Barkskin on Me @ 63.2%
[04:45:45.416 N] [Singular] Casting Rejuvenation on Me @ 59.5%
[04:45:55.667 N] [Singular] Casting Rejuvenation on Me @ 61.2%
[04:46:06.506 N] [Singular] Casting Rejuvenation on Me @ 59.1%
[04:46:17.542 N] [Singular] Casting Rejuvenation on Me @ 64.0%
[04:46:28.519 N] [Singular] Casting Rejuvenation on Me @ 60.4%
[04:46:38.574 N] [Singular] Casting Barkskin on Me @ 64.8%
[04:46:39.520 N] [Singular] Casting Rejuvenation on Me @ 64.8%
[04:46:50.212 N] [Singular] Casting Rejuvenation on Me @ 66.8%
[04:46:58.185 N] [Singular] Casting Berserking on Me @ 71.4%
[04:47:00.675 N] [Singular] Casting Rejuvenation on Me @ 69.5%
[04:47:03.017 N] [Singular] Casting Lifeblood on Me @ 74.3%
[04:47:03.872 D] PB 1.634: Updated tradeskills from OnSkillUpdateTimerCB
[04:47:11.676 N] [Singular] Casting Rejuvenation on Me @ 70.0%
[04:47:24.400 D] PB 1.634: Updated tradeskills from OnSkillUpdateTimerCB
[04:47:25.364 N] [Singular] Casting Rejuvenation on Me @ 64.3%
[04:47:35.743 N] [Singular] Casting Rejuvenation on Me @ 73.7%
[04:47:46.489 N] [Singular] Casting Rejuvenation on Me @ 75.9%
[04:47:57.346 N] [Singular] Casting Rejuvenation on Me @ 74.7%
[04:48:07.794 N] [Singular] Casting Rejuvenation on Me @ 74.9%
[04:48:19.264 N] [Singular] Casting Rejuvenation on Me @ 79.1%
[04:48:29.922 N] [Singular] Casting Rejuvenation on Me @ 79.2%

after this point i intervened and help it.
 
Is a rogue supposed to utilize cloak and dagger? Because at the moment it's still moving to stand behind them before using ambush.
 
possible to get this interrupting with all classes more random, and not interrupt all casts? if someone using an WoW Addon and posting all the interrupts from one toon its very bad.
 
I was wondering if you could make singular detect Tyrael? Currently, if you have the movement setting set to auto, it wont allow you to control your own movement. You have to instead use lazyraider, if you dont want to keep changing back and forth from none to auto.

thanks! singular is awesome. always works. :D

EDIT: to be clear, im asking about a way to leave singulars movement set to 'auto' while being able to use tyrael as your bot base. instead of having to use lazyraider OR having to set auto to 'none'. I know its not a huge deal, but would be cool if that gots fixed :D

EDIT2: this is being fixed in the next release. thanks bobby. :D
 
After HB update 721, I get this...

"[07:02:22.180 D] (Singular) 0.0 days since Windows was restarted
[07:02:22.189 D] (Singular) 33 FPS currently in WOW
[07:02:22.205 D] (Singular) 58 ms of Latency in WOW
[07:02:22.207 D] (Singular) 01/17/2014 08:02:22 local system time
[07:02:22.179 N] [Singular] Starting Singular v3.0.0.3195
[07:02:22.502 D] (Singular) === following 9 files with issues ===
[07:02:22.505 D] (Singular) deleted: 53943 ClassSpecific\Druid\Resto.cs
[07:02:22.507 D] (Singular) deleted: 15533 ClassSpecific\Warrior\Protection.cs
[07:02:22.509 D] (Singular) deleted: 29450 Helpers\Common.cs
[07:02:22.511 D] (Singular) deleted: 27866 Helpers\Movement.cs
[07:02:22.513 D] (Singular) deleted: 97555 Helpers\Spell.cs
[07:02:22.515 D] (Singular) deleted: 32919 SingularRoutine.Behaviors.cs
[07:02:22.518 D] (Singular) deleted: 14787 SingularRoutine.Context.cs
[07:02:22.520 D] (Singular) deleted: 20830 Utilities\EventHandlers.cs
[07:02:22.521 D] (Singular) deleted: 7408 Utilities\Logger.cs
[07:02:22.523 D] (Singular)
[07:02:22.526 D] (Singular) (Singular) FixGlobalCooldownInitialize: using Singular GCD
[07:02:22.758 D] (Singular) (Singular) Attached combat log
[07:02:22.502 N] [Singular] Installation: modified by user - forum support may not available "

I havent done any changes to Singular.
 
Slite62 said:
After HB update 721, I get this...

[07:02:22.502 N] [Singular] Installation: modified by user - forum support may not available "

I havent done any changes to Singular.
Click to expand...
Slite62, Thanks for the post. A change was made to the version of Singular distributed with HonorBuddy. A new version will be available shortly (a new release announcement will be posted here) that resolves this and other bugs. Thanks again for the post and good luck with your toon, Bobby53
 
*new* Singular v3.0.0.3231 available for download!

Change History for this release appears below. Complete Change History as always is included in the .ZIP

See the Reporting Bugs [CLICK HERE] post for details on how to request assistance, post about a problem, or ask questions about the behavior of your botting session with Singular.

Still receiving too many bug/question posts regarding behavior users watched that don't contain a complete log file and point of reference to when a single event happened. So, no multi-color bright lights this time. Just a simple request to provide the detail.

Don't forget to use the LOGMARK! button. It is located on the Class Config window and will place a mark in the log file making it easy for you to indicate when something happened that you have a question about or problem with. This button provides the same behavior as the LOGMARK plugin. Having a problem while running Singular that you want to report? Click the LOGMARK button immediately when you notice. A line will be added to the log file at that time and now you have a very accurate way to let me know when the problem occurred.

Ok, now that's out of the way:

- Download the latest version of Singular.ZIP from Post #1 in this thread

- .ZIP in Singular thread will always be the current version

- HonorBuddy will contain an older version until a new release of HB posts

Any post must include a debug log file (a file created with Debug Logging set to true.) To do this, click Class Config and set the Debug Logging option to 'true' then run until you create the issue again. The resulting log file will contain more info than a standard log file which will be essential in understanding the decisions being made by Singular which you weren't expecting.

As always, the prior version is still available for download. If you encounter a problem due to the new release of Singular you can always downgrade as needed.

--- Release 3.0.0.3231 ---

General

fixed - exception when checking instance difficulty fixed

fixed - no longer attempts to summon pets/demons when a cinematic is playing

change- Heal Targeting now uses the HonorBuddy HealTargeting instance to allow bots and components to overload weighting, etc.

fixed - Debug output from Singular was not fully disabled when Disable Debug Output setting was checked

change- cached guids in unit lookup portion of Combat Log event handler


Druid

*new* - Resto - added diagnostic output behavior to monitor buffs, etc.

fixed - Resto - bug in DruidHealSettings class initialization and availability


Hunter

change- All Specs - Feign Death will now report when its been cancelled by something other than Singular


Paladin

fixed - All Specs - bug with keeping Eternal Flame up

fixed - Holy - at times not self-healing


Rogue

fixed - All Specs - support for Combat Readiness and


Shaman

fixed - Resto - Instance behaviors had redundant Interrupt and Purge logic when Telluric Currents glyph is equipped
Click to expand...

Worth mentioning one more time due to the large number of posts without log files that are received, but you must attach a complete debug log with any post. Please see the link at the top of this post for details.
 
User0828 said:
I was wondering if you could make singular detect Tyrael? Currently, if you have the movement setting set to auto, it wont allow you to control your own movement. You have to instead use lazyraider, if you dont want to keep changing back and forth from none to auto.

thanks! singular is awesome. always works. :D
Click to expand...
User0828, Thanks for the post. Updated to recognize in next release, Bobby53
 
I<3botting said:
What Class+Spec are you?: Ret paladin
What 'context' is the bot in? (Instance, BG, Normal): Normal, grinding mobs in VoEB
What level are you?: 90
Have you made any modifications to Singular?: Yes, (Class Specific) Blessing is set to Might, Seal is set to Justice. The rest is default.
What time (HH:MM:SS) or LogMark did your issue occur? [17:45:41.833 N] (near bottom of log)
What happened (be specific)?
I play a Paladin and have the Light's Hammer ability. HB will try to use the ability when there is more than 1 mob attacking. This works great most of the time.

THE PROBLEM arises when the CURRENT mob targeted dies in between the first action of activating Light's Hammer and the second action of placing the "hammer" on the ground.

IF the mob dies in between those two actions the bot will not change targets, will not place Light's Hammer on the ground, and will just sit there until it dies or until I manually place the hammer.

For the time being I will use a different talent, but I like that this talent does AOE damage as well as healing.

If you look in the attached log you will see (near the bottom of the log) the repeated text:

"[17:45:41.833 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:43.856 N] [Singular] EnsureTarget: no valid target set -- skipping spell priority
[17:45:43.995 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:46.189 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:48.383 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:50.607 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:52.800 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:54.813 N] [Singular] EnsureTarget: no valid target set -- skipping spell priority
[17:45:54.975 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:57.180 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:45:59.408 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:01.634 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:03.821 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:05.898 N] [Singular] EnsureTarget: no valid target set -- skipping spell priority
[17:46:06.041 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:08.246 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:10.450 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:12.623 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:14.820 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1!
[17:46:16.883 N] [Singular] EnsureTarget: no valid target set -- skipping spell priority
[17:46:16.968 N] [Singular] Switching to BotPoi: (MOB NAME HERE).5EF1! "

If you read the log you will see that immediately after this text the log says the target is dead. That's because I manually killed the last, un-targeted mob. My manual action of selecting and killing the last mob is what selected the target, of which the bot realized was dead. (hope that wasn't too confusing, all I'm trying to say is "THIS IS WHEN I STEPPED IN AND TOOK OVER")

The issue can/will be easily duplicated with any mob and in any area. It's not an issue based on the environment of the character, it's simply Singular not knowing what to do when it's attempting to place Light's Hammer, yet it's target is dead. How do I know this? Because, when HB uses Light's Hammer regularly, it will place it EXACTLY at the location (X, Y, Z) of it's current target. THIS is the issue, because if it's current target dies it does not have a location to place the hammer (nor does it have a logical reason to place it) so it will simply wait until it is out of combat to continue it's routine.

Possible solution: give singular an "if, when" command to do one of the following things:

1) ONLY use Light's Hammer when the current targeted mob's HP is above 50% AND there is more than one mob.
2) When casting Light's Hammer, place at characters current location, not the target's. (it's radius is large enough to reach any mob that is in melee range)
3) Use Light's Hammer on the OTHER mob, not the currently targeted one.

Did you attach a complete debug log? (choose one: YES or YES) Yes (attached below)


EDIT: I just realized my log isn't in diagnostic mode. I will recreate the event in diagnostic mode and submit another log. TY

EDIT: After running the bot in diagnostic mode for a while it happened again. This time it was a different mob, same situation. The only difference is that I didn't step in to do anything. I let it attack to see what would happen and HB kicked in again after the mob had brought it down to when it healed itself at 36.6%HP (the Singular setting for Flash of Light was set at 50% HP). This must have a higher priority than continuing in it's current action? Anyway, that kicked it back into gear and it was able to continue as usual.

I've attached the new log below (it's the compressed one). The action starts at this time stamp: [19:38:12.553 N] It goes to cast Lights Hammer, and then says "YourCurrentTarget: changed to: (null)" which I believe commences the start of the bug.
Click to expand...



Why isn't this issue getting any attention? This happens not only with Paladin but also any class spell where bot needs to target a mob select the spell and select a poi. For example Hunter's throw trap spell is affected by the same issue. Bot selects a target then clicks throw trap but if target dies before he could throw a trap bot gets stuck with green circle activated and doesn't select any other mobs.

Again same thing happens with mage's flamestrike if target dies before bot selects the poi, it gets stuck with green circle activated. This has been going on for months as far as I remember since May 2013. I have PM'ed this issue to a developer but still havent been fixed. Either remove those spells from the rotation cause they cause bot the get stuck or fix it.
 
christiantroy said:
Why isn't this issue getting any attention? This happens not only with Paladin but also any class spell where bot needs to target a mob select the spell and select a poi. For example Hunter's throw trap spell is affected by the same issue. Bot selects a target then clicks throw trap but if target dies before he could throw a trap bot gets stuck with green circle activated and doesn't select any other mobs.

Again same thing happens with mage's flamestrike if target dies before bot selects the poi, it gets stuck with green circle activated. This has been going on for months as far as I remember since May 2013. I have PM'ed this issue to a developer but still havent been fixed. Either remove those spells from the rotation cause they cause bot the get stuck or fix it.
Click to expand...
@christiantroy, See the Reporting Bugs [CLICK HERE] post for steps on providing the details needed to research an issue. Piggy backing on another users post with only "happens to me too" doesn't provide any additional detail and doesn't affect the priority of items being worked on. What does? A thorough bug posting similar to i<3botting's which provides details on the circumstances when you encounter an issue. Happy to look into any problems you encounter, just be sure to follow the bug reporting steps and I'll research for you. -Bobby53
 
hi there,

thanks for the great routine although i'm having some issues on my priest. it will never cast renew no matter what settings i apply. is there a fix for this problem?

again thanks for the routine keep up the good work!
 
wooooodyy said:
hi there,

thanks for the great routine although i'm having some issues on my priest. it will never cast renew no matter what settings i apply. is there a fix for this problem?

again thanks for the routine keep up the good work!
Click to expand...
woooooodyy, Thanks for the post and Welcome to HonorBuddy! When you encounter a problem or a behavior you observed that you have a question about, please follow the steps in the Reporting Bugs [click here] post. That will provide the detail needed on your configuration and combat circumstances to hopefully understand what is occurring and provide assistance. Thanks again and good luck with your Priest, Bobby53
 
*new* Singular v3.0.0.3253 available for download!

Change History for this release appears below. Complete Change History as always is included in the .ZIP

See the Reporting Bugs [CLICK HERE] post for details on how to request assistance, post about a problem, or ask questions about the behavior of your botting session with Singular.

Still receiving too many bug/question posts regarding behavior users watched that don't contain a complete log file and point of reference to when a single event happened. So, no multi-color bright lights this time. Just a simple request to provide the detail.

Don't forget to use the LOGMARK! button. It is located on the Class Config window and will place a mark in the log file making it easy for you to indicate when something happened that you have a question about or problem with. This button provides the same behavior as the LOGMARK plugin. Having a problem while running Singular that you want to report? Click the LOGMARK button immediately when you notice. A line will be added to the log file at that time and now you have a very accurate way to let me know when the problem occurred.

Ok, now that's out of the way:

- Download the latest version of Singular.ZIP from Post #1 in this thread

- .ZIP in Singular thread will always be the current version

- HonorBuddy will contain an older version until a new release of HB posts

Any post must include a debug log file (a file created with Debug Logging set to true.) To do this, click Class Config and set the Debug Logging option to 'true' then run until you create the issue again. The resulting log file will contain more info than a standard log file which will be essential in understanding the decisions being made by Singular which you weren't expecting.

As always, the prior version is still available for download. If you encounter a problem due to the new release of Singular you can always downgrade as needed.

--- Release 3.0.0.3253 ---

General

change- added Tyrael to list of manual movement bots automatically detected

change- Singular no longer suppresses summoning Pet during cinematic (see next change)

fixed - Singular now suppresses summoning Pet and all other Pulse() logic if Combat BehaviorFlag has been disabled

*new* - added settings to General -> Group Healing to control whether and when Healers can DPS. This applies to general DPS and not attack spells which have a specific healing/mana benefit (Atonement, Telluric Currents, etc.)

change- Ground spell casts which took position from a specific target unit location will now correctly handle if that target dies between the spell cast and the point where click on the ground is performed


Death Knight

fixed - All Specs - no longer casts back to back Blood Boil/Pestilence to spread diseases (second cast was occurring too fast before results of prior one had become available.)

fixed - Frost - was previously not taking advantage of Death Runes in all cases


Druid

*new* - Resto - will now cast Moonfire/Wrath based upon the General -> Healer DPS ... settings


Priest

*new* - Disc - will now cast SD:D/SW:P/Penance/Holy Fire/Smite based upon the General -> Healer DPS ... settings

*new* - Holy - will now cast HW:C/SD:D/SW:P/Holy Fire/Smite based upon the General -> Healer DPS ... settings


Shaman

*new* - Resto - will now cast Elemental Blast/Flame Shock/Lava Burst/Earth Shock/Chain Lightning/Lightning Bolt based upon the General -> Healer DPS ... settings
Click to expand...

Worth mentioning one more time due to the large number of posts without log files that are received, but you must attach a complete debug log with any post. Please see the link at the top of this post for details.
 
Warrior has a small issue while leveling that i noticed.

[01:25:57.158 D] (Singular) [CombatLog] SPELL_CAST_FAILED Charge#100 failure: 'Out of range'
[01:25:56.977 N] [Singular] Casting Charge on Okril'lon Infantry.4732 @ 100.0% at 26.4 yds
[01:25:58.885 N] [Singular] Casting Charge on Okril'lon Infantry.4732 @ 100.0% at 16.8 yds

Basically, he tries to charge too early, but he is out of range, as you can see. Then, as he is still running to the mob, sometimes he will reach the mob before he has a chance to cast charge again. Hence making me not receive the +35 rage that charge grants. Hence slowing down warrior leveling. Charge is a 5-25 yard range.

View attachment 3052 2014-01-21 20.23.zip

EDIT: It would be awesome if when you fix this, you could drop the update right away? My warrior is currently level 59 and questing. But when I start grinding at 85-90, you can understand how this bug will become an even bigger annoyance. Thanks!
 
User0828 said:
Warrior has a small issue while leveling that i noticed.

[01:25:57.158 D] (Singular) [CombatLog] SPELL_CAST_FAILED Charge#100 failure: 'Out of range'
[01:25:56.977 N] [Singular] Casting Charge on Okril'lon Infantry.4732 @ 100.0% at 26.4 yds
[01:25:58.885 N] [Singular] Casting Charge on Okril'lon Infantry.4732 @ 100.0% at 16.8 yds

Basically, he tries to charge too early, but he is out of range, as you can see. Then, as he is still running to the mob, sometimes he will reach the mob before he has a chance to cast charge again. Hence making me not receive the +35 rage that charge grants. Hence slowing down warrior leveling. Charge is a 5-25 yard range.

View attachment 118161

EDIT: It would be awesome if when you fix this, you could drop the update right away? My warrior is currently level 59 and questing. But when I start grinding at 85-90, you can understand how this bug will become an even bigger annoyance. Thanks!
Click to expand...
User0828, Thank you for the post and the log file. Distance and spell range don't work quite that way. The distance shown in the Singular log for the Charge cast statement is the physical distance from the center point of your hitbox to the center point of the targets. When evaluating if a target is in range spells which have an explicit target (like Charge) use the distance from the edge of your characters hitbox to the edge of the targets hitbox. Since the hitbox size of targets vary, so does the physical distance from which you can cast a spell. That is how varying sizes of targets are accounted for and allows you to Charge an extremely large mob (like a boss) without having to be within 25 yards of their center point. A Charge cast from 26.4 yds should almost always work due simply to your characters hitbox size. For example, on a Training Dummy my unglyphed Orc can charge from 28.25 yards due to a max range of 25, my hitbox of 1.5, and the targets hitbox of 1.75. Hopefully that explains the spell ranges a little better.

One other consideration is that the distances are not exact. With both characters moving the actual distance will change slightly between the point where Singular checks to see if you are in range, casting the spell, and then writing to the log file that the cast was made. Typically the change in distance isn't enough to worry about, but since it is based entirely upon the speed of both units and this being a boundary condition it could come into play.

The attached .ZIP containing the log won't open for me. Could you re-ZIP and attach as it will contain some diagnostic values needed to investigate further for you.

Thanks for the post and good luck with your Warrior, -Bobby53
 
tumbum said:
If Mana Bottle is in the Bags, Rogue try to use it

[08:23:37.210 D] (Singular) [WoWRedError] You can't use that item
[08:23:37.143 N] Used Minor Mana Potion!
Click to expand...

*edit* ok not only Rogues, my DK is getting this msg too.
Click to expand...
Tumbum, It is not Singular using the Minor Mana potion. All Singular actions and resulting messages begin with the prefix "[Singular]". Looks like you have a Drink Potions plugin active so possibly it, but only thing I can say conclusively is that action wasn't taken by Singular. Thanks for the post and good luck with your Rogue, Bobby53
 
You must log in or register to reply here.
Back
Top