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

Die_Quelle said:
What Class+Spec are you?

Druid, Restoration

What 'context' is the bot in? (Instance, BG, Normal):

Grinding, Normal

What level are you?

54

Have you made any modifications to Singular?

No

What time (HH:MM:SS) or LogMark did your issue occur?

Logmark 2

What happened (be specific)?

I died because my Character does not use self heal, Restoration for example. Only if he is not infight.

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

Private Paste - Pastie
Click to expand...
Die_Quelle, As described in Reporting Bugs [CLICK HERE] ​ the log file will need to be attached to your post and not provided as a 3rd party link. I did look into the issue in general and believe I found the issue so a fix will appear in the next release. If you would like me to look at the specifics of the issue as you encountered it, please attach the log and I'll review it to make sure it matches what I found. Thanks for the post and good luck with your Druid, Bobby53
 
I'm having an issue with singular holy pally after the latest honorbuddy update. I will no longer heal myself in battle. Singular is fighting mobs and I just watch my health go down without healing. I only heal myself after combat.
 
iezequil said:
Hi, rogue pickpockets, but wont lockpick the chest, just use skill, but no targeting the chest, between logmarks 1 and 2.
View attachment 97061
Click to expand...
bobby53 said:
iezequil, Thanks for the post with log file. Unfortunately I am not experiencing any problems with Pick Lock. To look into this further for you I will need a log produced with some debug settings. Be sure to set the following Options before running:
Settings & Tools:
Set Log Level to Diagnostic

Class Config:
Set Debug Logging to true
Set Debug Spell.CanCast to true

​
That should include enough information in the log file for me to trouble shoot for you. Just run again and post the new log and I'll look into this again for you. Thanks for the post, Bobby53
Click to expand...
iezequil, In researching another issue, I found the problem with Pick Lock. The api for detecting a pending spell on the cursor is failing. Will be fixed in the next release of Singular. Prior to that you will want to set Use Pick Lock to false. Thanks for the post, Bobby53
 
Last edited:
bobby53 said:
iezequil, In researching another issue, I found the problem with Pick Lock. The api for detecting a pending spell on the cursor is failing. Will be fixed in the next release of Singular. Prior to that you will want to set Use Pick Lock to false. Thanks for the post, Bobby53
Click to expand...
When is the next release. I've been waiting for the lock pick error.
 
Hey Bobby, i want to make a little pull request. I have overworked the bosslist - i've added heroic szenarios, the missing world bosses in mop and fixed wrong ids for raid bosses.
Here we go:

Code: 
                // Mogu'shan Vaults
                60047, // Amethyst Guardian
                60051, // Cobalt Guardian
                60043, // Jade Guardian
                59915, // Jasper Guardian
                60009, // Feng the Accursed <Keeper of Champion Spirits>
                60143, // Gara'jal the Spiritbinder
                60708, // Meng the Demented <Mad King>
                60701, // Zian of the Endless Shadow
                60709, // Qiang the Merciless
                60710, // Subetai the Swift
                60410, // Elegon
                60400, // Jan-xi <Emperor's Open Hand>
                60399, // Qin-xi

            
                // Heart of Fear
                62980, // Imperial Vizier Zor'lok <Voice of the Empress>
                62543, // Blade Lord Ta'yak
                62164, // Garalon
                62397, // Wind Lord Mel'jarak
                62511, // Amber-Shaper Un'sok
                62837, // Grand Empress Shek'zeer
            
                // Terrace of Endless Spring
                60583, // Protector Kaolan
                60586, // Elder Asani
                60585, // Elder Regail
                62442, // Tsulong
                62983, // Lei Shi
                60999, // Sha of Fear

                //World Bosses
                60491, // Sha of Anger
                62346, // Galleon
                69099, // Nalak
                69161, // Oondasta

                // Throne of Thunder (5.2)
                69465, // Jin'rokh the Breaker
                68476, // Horridon
                69131, // Council of Elders
                69132, // Council of Elders
                69134, // Council of Elders
                69078, // Council of Elders
                67977, // Tortos
                70212, // Megaera
                70235, // Megaera
                70247, // Megaera
                69712, // Ji-Kun
                68036, // Durumu the Forgotten
                69017, // Primordius
                69427, // Dark Animus
                68078, // Iron Qon
                68905, // Twin Consorts
                68904, // Twin Consorts
                68397, // Lei Shen
                69473, // Ra-den

                //Szenarios

                //A Brewing Storm
                58739, // Borokhula the Destroyer
                71259, // Huntmaster S'thoc
                59632, // Champion Sithiss

                //Battle on the High Seas 
                67391, // Lieutenant Drak'on
                71330, // Lieutenant Fizzboil
                70963, // Lieutenant Fizzel
                71328, // Lieutenant Fuseblast
                71326, // Lieutenant Parker
                70762, // Lieutenant Sparklighter
                70893, // Lieutenant Blasthammer
                71329, // Lieutenant Boltblaster
                67426, // Admiral Hagman
                71327, // Admiral Hodgson

                //Blood in the Snow
                70468, // Bonechiller Barafu
                70474, // Farastu
                70544, // Hekima the Wise
                70787, // Skullcrusher Gundu

                //Crypt of Forgotten Kings
                61707, // Abomination of Anger
                61814, // Jin Ironfist
                67081, // Forgotten King
                71492, // Maragor 

                //Dark Heart of Pandaria
                71123, // Echo of Y'Shaarj
                70822, // Earthborn Hatred

                //The Secrets of Ragefire
                70683, // Dark Shaman Xorenth
                71030 // Overseer Elaglo
 
Heyho bobby

First Thank you for the amazing work on the healer Parts of Singular. I play 90% Healers in WOW and now I can simple use Singular with all of them. No need to search for other CRs.

I found just a little Issue:
The Disciple Priest switch Target also if this is disabled in Singular (I disabled it on the first Tab - Point Targeting)
He always says: "switch to highest health mob ..."
I also find the Function which triggers this: File Disciple.cs - Line 722

The Problem is, every time I myself or also my Botbase chooses a Target with low health, Singular switches to another one. But sometimes you need to choose a special Target. Also this is a Problem if the Botbase says: "Always attack the Target of your Leader" and Singular says: "Switch to Target with highest health". So this end up in switching between two Targets.
I will upload a Logfile of this behavior later in the afternoon.
I used Singular Version 3.0.0.2619

It would be great to disable also the Targeting for Atonement if Targeting is disabled global in Singular.
If you can't change this, please also let me know, so I had to change my Botbase or my local Singular special for the Disc Priest.

EDIT:
What Class+Spec are you?: Disc Priest
What 'context' is the bot in? (Instance, BG, Normal): Instance
What level are you?: 80
Have you made any modifications to Singular?: No
What time (HH:MM:SS) or LogMark did your issue occur? Will be added with the Logfile
What happened (be specific)? CR switch Target also if disabled in Singular (for Disc Priest Atonement)
Did you attach a complete debug log? (choose one: YES or YES) I will upload the Logfile later ;)



Thank you very much
 
Last edited:
bobby53 said:
See Bobby53's Standard Request for More Information [CLICK HERE]
Click to expand...


Log:
Code: 
Initialization complete.
Starting the bot!
Currently Using BotBase : Questing
Changing current profile to SkyShards Motes/WindWool Cloth/Guo-Lai Cache and Key's Rev .09b (***Phased***)
[Singular] Your Level 90 Human Holy Paladin Build is 
[Singular] ... running the Questing bot in Vale of Eternal Blossoms 
[Singular] ... Zone: Pandaria using my SOLO Behaviors 
[Singular] Context changed, re-creating behaviors
[Singular] GCD check fix spell set to: Righteous Fury 
Remoting server started
[Singular] Casting Hammer of Justice on Stone Guardian.81CF @ 100.0% at 13.0 yds
[Singular] Casting Judgment on Stone Guardian.81CF @ 100.0% at 5.0 yds 
[Singular] Casting Holy Shock on Stone Guardian.81CF @ 93.1% at 5.0 yds
[Singular] Casting Crusader Strike on Stone Guardian.81CF @ 76.6% at 5.0 yds 
[Singular] Casting Denounce on Stone Guardian.81CF @ 73.7% at 5.0 yds
[Singular] Casting Judgment on Stone Guardian.81CF @ 73.0% at 5.0 yds 
[Singular] Casting Holy Shock on Stone Guardian.81CF @ 59.8% at 5.0 yds
[Singular] Casting Crusader Strike on Stone Guardian.81CF @ 43.6% at 5.0 yds 
[Singular] Casting Denounce on Stone Guardian.81CF @ 41.0% at 5.0 yds
[Singular] Casting Judgment on Stone Guardian.81CF @ 40.3% at 5.0 yds 
[Singular] Casting Holy Shock on Stone Guardian.81CF @ 27.0% at 5.0 yds
[Singular] Casting Hammer of Wrath on Stone Guardian.81CF @ 10.8% at 5.0 yds 
[Singular] Casting Crusader Strike on Stone Guardian.F5E4 @ 100.0% at 2.7 yds
[Singular] Casting Judgment on Stone Guardian.F5E4 @ 97.7% at 2.7 yds 
[Singular] Casting Holy Shock on Stone Guardian.F5E4 @ 94.5% at 2.7 yds
[Singular] Casting Crusader Strike on Stone Guardian.F5E4 @ 84.1% at 2.7 yds 
[Singular] Casting Denounce on Stone Guardian.F5E4 @ 81.8% at 2.7 yds
[Singular] Casting Judgment on Stone Guardian.F5E4 @ 78.5% at 2.7 yds 
[Singular] Casting Holy Shock on Stone Guardian.F5E4 @ 67.8% at 2.7 yds
[Singular] Casting Crusader Strike on Stone Guardian.F5E4 @ 48.8% at 2.7 yds 
[Singular] Casting Hammer of Justice on Stone Guardian.F5E4 @ 48.8% at 2.7 yds
[Singular] Casting Judgment on Stone Guardian.F5E4 @ 44.8% at 3.0 yds 
[Singular] Casting Holy Shock on Stone Guardian.F5E4 @ 35.1% at 3.0 yds
[Singular] Casting Hammer of Wrath on Stone Guardian.F5E4 @ 15.4% at 3.0 yds 
[Singular] Casting Judgment on Stone Guardian.F5E4 @ 5.1% at 3.0 yds
[Singular] Current target invalid. Switching to aggroed mob Stone Guardian.8ABE! 
[Singular] Casting Judgment on Stone Guardian.8ABE @ 100.0% at 5.3 yds
[Singular] Casting Holy Shock on Stone Guardian.8ABE @ 92.7% at 5.3 yds 
[Singular] Casting Crusader Strike on Stone Guardian.8ABE @ 76.5% at 5.3 yds
I died!

This is a typical fight of Singular. It will attack mobs, and just not heal itself at all. It completely ignores the HP until after the fight is over(if it wins) when it will heal itself. The "logmark" is this entire log, since it went straight into battle. It happens with every fight, sadly. I didn't notice it happening before, perhaps just because I was in easier fights.

EDIT:

What Class+Spec are you?: Holy Pally
What 'context' is the bot in? (Instance, BG, Normal): Normal (Questing mode to grind)
What level are you?: 90
Have you made any modifications to Singular?: No
What time (HH:MM:SS) or LogMark did your issue occur? - It's a very short log.
What happened (be specific)? The bot will not heal itself during combat.
Did you attach a complete debug log? (choose one: YES or YES) I think so. :|
 
Last edited:
What Class+Spec are you?: Frost Death Knight, but I doubt that matters here.
What 'context' is the bot in? (Instance, BG, Normal): Questing right now, but I doubt that matters here as well.
What level are you?: 90
Have you made any modifications to Singular?: Yes, I've added Tyrael to the list of no movement botbases.
What time (HH:MM:SS) or LogMark did your issue occur? -
What happened (be specific)? Bot uses Asphyxiate (interrupt) on mobs that are not in combat and therefore pulling them. Could you add a check if mob is being in combat or my character having any threat against it?
Did you attach a complete debug log? (choose one: YES or YES) Sorry, did not.
 
What Class+Spec are you?: Pre-Spec Mage
What 'context' is the bot in? (Instance, BG, Normal): Normal Questing
What level are you?: 1-5. However I have seen the issue as high as 13 for me.
Have you made any modifications to Singular?: No
What time (HH:MM:SS) or LogMark did your issue occur? I have 2 specific issues I could quickly gather from this quick 1-5 mage, explained below.
What happened (be specific)?

Issue #1 (Logmark 1): This is the major issue, where the bot will pull something and then quickly after pull something else, then proceed to kite them both. This usually lead to the bots death, kiting the mobs by backpeddling till the mage is killed. When the mage rezzes the issue is corrected and it goes on its merry way.

Issue #2 (Logmark 2 & 3): In this case the mage will pull something, and then sometime during the fight make an instant jerk-like rotation towards another target before refacing the current enemy. I believe this occurred 1-2 more times in this log, but I missed the button and left it be. Minor but still relatively annoying.

Did you attach a complete debug log? It's in Diagnostic log mode with just Debug enabled for Singular.

I have noticed some other issues, like it can combine the issues with different spells and this can result in a pileup. Ex: Frost Nova, backpedal into a group of mobs and then proceed to fight or reverse kite them. I'm testing some profiles extensively for someone, and have noticed some other things in about half of the other classes. Nothing major, but it would seem like this one issue with the Mage just gives me aneurysms. The one thing I see very common however is singular deeming lots of targets invalid. Sometimes it simply stops attacking, or the message has no effect on the bots combat.
Click to expand...
 

Attachments

Hello,

I have performance issues with HB (i7 920, HB uses on average 6% of CPU, its a lot when you compare it to past), therefore I have question about frame lock... Does Singular use framelock? Context: Instance solo, 85 prot paladin, questorder bot base. If so, is it possible to turn it off? I need test if this is causing problems, I had exactly same problem with dungeonbuddy, but after disabling framelock (db settings) hb cpu usage droped by half.
 
handnavi said:
Hey Bobby, i want to make a little pull request. I have overworked the bosslist - i've added heroic szenarios, the missing world bosses in mop and fixed wrong ids for raid bosses.
Here we go:
... cut for space ...
Click to expand...
handnavi, Thanks for the post sharing your work! Singular switched awhile ago from a static list to dynamically building as it changes contexts / zones. This makes it self-maintaining (mostly) and keeps the list smaller since only the bosses from the current zone are loaded at any given time. If there was a problem recognizing a boss let me know (they are written out to the log file.) If that is occurring its most likely due to not detecting a zone/context change and a log would be a tremendous help. Thanks for the post and sharing your work, Bobby53
 
katzerle said:
Heyho bobby

First Thank you for the amazing work on the healer Parts of Singular. I play 90% Healers in WOW and now I can simple use Singular with all of them. No need to search for other CRs.

I found just a little Issue:
The Disciple Priest switch Target also if this is disabled in Singular (I disabled it on the first Tab - Point Targeting)
He always says: "switch to highest health mob ..."
I also find the Function which triggers this: File Disciple.cs - Line 722

The Problem is, every time I myself or also my Botbase chooses a Target with low health, Singular switches to another one. But sometimes you need to choose a special Target. Also this is a Problem if the Botbase says: "Always attack the Target of your Leader" and Singular says: "Switch to Target with highest health". So this end up in switching between two Targets.
I will upload a Logfile of this behavior later in the afternoon.
I used Singular Version 3.0.0.2619

It would be great to disable also the Targeting for Atonement if Targeting is disabled global in Singular.
If you can't change this, please also let me know, so I had to change my Botbase or my local Singular special for the Disc Priest.

EDIT:
What Class+Spec are you?: Disc Priest
What 'context' is the bot in? (Instance, BG, Normal): Instance
What level are you?: 80
Have you made any modifications to Singular?: No
What time (HH:MM:SS) or LogMark did your issue occur? Will be added with the Logfile
What happened (be specific)? CR switch Target also if disabled in Singular (for Disc Priest Atonement)
Did you attach a complete debug log? (choose one: YES or YES) I will upload the Logfile later ;)



Thank you very much
Click to expand...
katzerle, Thanks for the post! A check for the the disable targeting setting is missing from Atonement support. Thanks for making me aware of it. Look for a fix in the next release. Thanks for the post and good luck with your Priest, Bobby53
 
shamash said:
Log:
Code: 
Initialization complete.
Starting the bot!
Currently Using BotBase : Questing
Changing current profile to SkyShards Motes/WindWool Cloth/Guo-Lai Cache and Key's Rev .09b (***Phased***)
...
I died!

This is a typical fight of Singular. It will attack mobs, and just not heal itself at all. It completely ignores the HP until after the fight is over(if it wins) when it will heal itself. The "logmark" is this entire log, since it went straight into battle. It happens with every fight, sadly. I didn't notice it happening before, perhaps just because I was in easier fights.

EDIT:

What Class+Spec are you?: Holy Pally
What 'context' is the bot in? (Instance, BG, Normal): Normal (Questing mode to grind)
What level are you?: 90
Have you made any modifications to Singular?: No
What time (HH:MM:SS) or LogMark did your issue occur? - It's a very short log.
What happened (be specific)? The bot will not heal itself during combat.
Did you attach a complete debug log? (choose one: YES or YES) I think so. :|
Click to expand...
shamash, Thanks for describing the issue in more detail. The post includes a copy/paste of the log window, but I need the complete debug log from your Logs folder attached. Please see the Reporting Bugs [CLICK HERE] ​for steps on attaching a log file with your post. You will also need to set Debug Logging to true and Debug Spell.CanCast to true in your Class Config. Thanks for the post and I'll look for a follow up, Bobby53
 
Wuzzery said:
What Class+Spec are you?: Frost Death Knight, but I doubt that matters here.
What 'context' is the bot in? (Instance, BG, Normal): Questing right now, but I doubt that matters here as well.
What level are you?: 90
Have you made any modifications to Singular?: Yes, I've added Tyrael to the list of no movement botbases.
What time (HH:MM:SS) or LogMark did your issue occur? -
What happened (be specific)? Bot uses Asphyxiate (interrupt) on mobs that are not in combat and therefore pulling them. Could you add a check if mob is being in combat or my character having any threat against it?
Did you attach a complete debug log? (choose one: YES or YES) Sorry, did not.
Click to expand...
wuzz, Tyrael isn't supported for use with Singular as it does not call the CombatBuff behavior. For example, you will notice that your DK when using Singular with Tyrael is not casting a number of cooldowns include AMS, AMZ, IBF, Lichborne, Raise Ally, Army of the Dead, Raise Dead, Empower Rune Weapon, etc. This doesn't impact the interrupt behavior however which was casting on non-combat mobs. Fix in next release. If you have any further issues, be sure to attach a complete log file created with Debug Logging and Debug Spell.CanCast. Thanks and good luck with your DK, Bobby53
 
Liferose said:
What Class+Spec are you?: Pre-Spec Mage
What 'context' is the bot in? (Instance, BG, Normal): Normal Questing
What level are you?: 1-5. However I have seen the issue as high as 13 for me.
Have you made any modifications to Singular?: No
What time (HH:MM:SS) or LogMark did your issue occur? I have 2 specific issues I could quickly gather from this quick 1-5 mage, explained below.
What happened (be specific)?

Issue #1 (Logmark 1): This is the major issue, where the bot will pull something and then quickly after pull something else, then proceed to kite them both. This usually lead to the bots death, kiting the mobs by backpeddling till the mage is killed. When the mage rezzes the issue is corrected and it goes on its merry way.
Click to expand...
Liferose, Thanks for the post. In looking at Logmark #1 it doesn't appear to correspond to the issue you described. No kiting occurred and the only target switches initiated by Singular were due to your current target being dead and during Pull you aggroed another target so it stopped and fought that target which was already attacking. Based upon what appears there it is working as designed. The log was not created with the Debug Logging enabled so please set that option to true and if you encounter this issue again repost.

Liferose said:
Issue #2 (Logmark 2 & 3): In this case the mage will pull something, and then sometime during the fight make an instant jerk-like rotation towards another target before refacing the current enemy. I believe this occurred 1-2 more times in this log, but I missed the button and left it be. Minor but still relatively annoying.

Did you attach a complete debug log? It's in Diagnostic log mode with just Debug enabled for Singular.
Click to expand...
For some reason the Questing Bot decided to change the BotPoi during the fight. Targeting is the responsibility of the BotBase, and in this case it set the BotPoi (Point of Interest) to one Mana Wyrm, instructed the Combat Routine to Pull the mob, then changed the BotPoi to a different mob causing the Combat Routine to switch. The fix for this needs to occur in the botbase rather than the combat routine. I'll pass it along to the HB team, Bobby53
 
bobby53 said:
Liferose, Thanks for the post. In looking at Logmark #1 it doesn't appear to correspond to the issue you described. No kiting occurred and the only target switches initiated by Singular were due to your current target being dead and during Pull you aggroed another target so it stopped and fought that target which was already attacking. Based upon what appears there it is working as designed. The log was not created with the Debug Logging enabled so please set that option to true and if you encounter this issue again repost.
Click to expand...

Thank you for the time to look at this. However I'm deathly sure I turned on the singular debugging. Just made another level 1 mage and let the bot run for a few seconds before shutting it off. It's not recognizing that I have this set to true. This is a clean release.

[Decently Sized Image Warning]

The logmark #1 issue is interesting though if that's how the routine is reporting it, because chronologically this is what happened.
1. Bot pulls a Mana Wyrm, Kills it just fine with.
2. Bot pulls a Mana Wyrm, Casts Frostfire bolt maybe a couple times.
3. Turns and pulls another Mana Wyrm, Casts a Frostfire bolt.
4. Mana Wyrms reach the mage, and the mage proceeds to run away (as if it had cast Frost Nova for example but not nearly as far).
5. Worms attack, and She backs up again.
6. Worms attack, and She backs up again. (Studdering till it dies, one of them dies because it gets a cast off somehow, or someone else kills one)
 
Just an Request for an maybe Improvement

At the moment the Singular Kiting for Hunter works, run away, stop, turn around, shoot, if the Mob is not far enough, turn around again run away and so on.
Before MoP there was a Hunter PVP CC from someone i forgot his Name and the CC Name. But this Hunter CC had a really nice Kiting ability, running away and spinning back to shoot while running
was a really great Hunter look a like ability in this CR.
Will look in my Archives maybe i find it and give you more informations.
Maybe someone other know this one too and give you more informations.

But would like to ask you if its possible you send a bit to look at this CR and maybe change your kiting code for Hunters?

*edit* - here it is - http://www.thebuddyforum.com/archives/49534-zehunter-pvp-customclass-jump-n-shot.html
 
Last edited:
You must log in or register to reply here.
Back
Top