azidtrip, Thanks for taking the time to post and my apologies for the issue. The BotPoi is the way the Questing botbase and Quest Behaviors communicate what the most important target is. If the current target is changed programmatically or manually without the BotPoi being updated, it will re-target the BotPoi. For me to look into this issue, I really you to follow the steps described in Reporting Bugs [click here] when posting. That way you will be running with Log Level set to Diagnostic and will have set a LOGMARK at the point the behavior begins. With that info I can research the debug log activity in that area and forward info as needed to the HB Devs. Thanks for the post and good luck with with your Rogue, Bobby53
I don't exactly have any bugs for this as im not entierly sure this is a bug.. however i was using singular for awhile now as it out performed tuahna and the other DPS CC's for a ret pally that where out there normally it was doing 350-400K single target stable DPS.. i have not changed anything in singular settings nor changed from tyrael but recently it is not casting certain spells my dps has dropped down to a mere 210K stable the AOE rotation is buggy i raid 25man HM SOO and this cc was fantastic but it seems to have just stopped working like it's not casting spells fast enough when they are on CD f View attachment 118279
thanks for the explanation, bobby53. Maybe there is no error at all? All I know is it is def trying to charge too soon, as I always watch my bot while it is leveling and I frequently get the out of range message. I will re-attach the same log file, hope this time it works. View attachment 3052 2014-01-21 20.23.zip EDIT: confirmed attachment is working this time.
User0828, Thanks -- issue with attachment extracting was a format compatibility issue on my end. The log was created with: For me to research an issue the LogLevel would need to be set to Diagnostic. Additionally, it is always a good idea to add a LOGMARK at the time you notice the issue so I am looking at the portion of the log which corresponds to what you saw. For steps on posting that detail, see Reporting Bugs [CLICK HERE]. As for my previous explanation, I wasn't saying there wasn't an error -- just elaborating on that it wasn't due to the symptom it appeared to be. While spells should be expected to fail (as they do at times when you play manually) it does sound like there is an issue because it shouldn't be happening frequently. Frequently is a subjective term but if you are getting a failed charge on 1 out of every 5 attempts or it is failing when charging a stationery target, it is a bug. That said, I would need the diagnostic info to look into it. Review the post I linked above and run with Log Level = Diagnostic for awhile. If you encounter the issue set a LOGMARK and then post the log and I'll research that and see what can be done. Thanks for the follow up and good luck with your Warrior, -Bobby53
Eunoia, Sorry to hear that. I am happy to look into this for you, but will need you to follow the steps in Reporting Bugs [click here] as there simply isn't enough information provided for me to research this for you. Note: it will instruct you to set Log Level = Diagnostic. Be aware that: 1. This setting will reduce your performance. 2. Reducing your performance is okay, because it is temporary. 3. It causes diagnostic info to be output that is required for me to research this 4. Run an LFR to generate an example file then after posting reset LogLevel to Normal 5. After posting your results from LFR, you can reset LogLevel to Normal for typical raiding performance Thanks for the post and good luck with your Paladin, -Bobby53
What Class+Spec are you?: Discipline Priest What 'context' is the bot in? (Instance, BG, Normal): normal, questing What level are you?: 64 Have you made any modifications to Singular?: no What time (HH:MM:SS) or LogMark did your issue occur? What happened (be specific)? Not using shield during battle, using shield only as speed boost. Did you attach a complete debug log? (choose one: YES or YES) yes Hi there, new member to the Honorbuddy community and I am really liking this CC for my questing bot, I am currently leveling up a disc priest using Kick's profiles and Cava's profiles. One thing that I noticed though is that the bot is not using shield in combat when I am discipline spec. Its fine for short fights where the initial shield lasts long enough (usually it is cast while running around to get a speed buff) but in protracted battles I notice it is not using it. I dug around and see that you have a setting for shadow priests to use a shield below a certain percentage... why not just make that a general setting for all priest spec?
Hey, i don't seem to find an option to enable vanish for my rogue, + it doesn't use it at all as far as i can tell, does singular supports it?
thanks for keeping up with me, bobby. I will do some more leveling with my warrior tonight, and change my log to diagnostic as well as use LOGMARK as soon as I see a failed charge. Is it better that I run with my log set to diagnostic? Does that cause lag? Will other developers of profiles or whatnot be ok with reading a log that is in diagnostic form? Or should I only use it when im having singular issues. thanks EDIT: Ok, here you go. I let him do 3 kills, i believe. Each time, he attempted to charge too soon, and I think 2 of the 3 times, he wasnt able to use charge at all before he reached the mob just by running there. I hit logmark after he started combat each time. View attachment 8268 2014-01-26 19.59.txt EDIT2: It almost looks as if he actually IS in range to charge. I see the bot 'click' the charge icon on my action bar, but then it says he is out of range, and doesnt do the charge...weird. EDIT3: hey bobby, if u dont wanna mess around with my issues if u dont want. i know u must be a busy guy. its not that big of a issues, cus he does charge properly maybe 60% of the time.
Bobby is there a setting somewhere to turn off auto revive? Some people afk in raid and keep trying to revive them. I must be overlooking it but damned if I can find it.
Can we give Singular an option for a Druid to pull with a Entangle Root/Fairy Swarm combination please? This is the way I do it when I am controlling the toon - and is the normal way for a Druid to pull a one-on-one encounter as far as I know - and I would like the bot to be able to pull in that fashion as well if possible.
Anyone else with Problems in LFR with RaidBot when try to kill the "Amber" at the Boss "Paragons of the Klaxxi" ? All my Toons dont fight when i switch to the Amber, same with the Ingi at Garrosh. Have to do some more Toons. Nexttime i add here a Log.
Bobby on Disc priest I set mass dispell to 5 but anything but 0 even when not in combat it is trying to cast mass dispell? Can provide a log but all log saysis. [16:59:46.470 N] (Singular) .... [REST] h=82.8%/m=94.3%, combat=N, evang=0, archa=0, spiritsh=0, borrtim=4667, inner=none, target=lead.DeathKnight.A3A2 th=50.0%/50.0%, @ 0.0 yds, combat=N, tloss=True, pw:s=0, renew=0, spiritsh=0 [16:59:46.580 N] [Singular] Casting Mass Dispel on Me @ 82.8%
Hi, Omorashi, This is not a problem with Singular, but the questing profile. Please submit your log that captures the vehicle issue to the appropriate thread for the Questing profile. cheers, chinajade
Wonder why this wasn't fixed yet, but when I have Visions of Insanity active, Singular just hangs and tries to use Alchemist's Flask. If Crystal of Insanity is available you should use this instead. [Singular] Using Alchemist's Flask [Singular] Using Alchemist's Flask [Singular] Using Alchemist's Flask [Singular] Using Alchemist's Flask [Singular] Using Alchemist's Flask [Singular] Using Alchemist's Flask [Singular] Using Alchemist's Flask [Singular] Using Alchemist's Flask [Singular] Using Alchemist's Flask
China any way to stop singular from trying to move behind targets in LFR? waste so much dps trying to do this and runs around the feet of many bosses not doing anything. Thanks
Can anyone help me with my problem please? I am using this profile on my frost mage and for some reason it will evocate 3 or 4 or 5 times in a row and in some random places get stuck in an evocate loop.
