HB ARCHIVES: Singular--DO NOT DELETE

[letsgo2u]

what pve fury warrior talent spec do you recommend for 80+ leveling?

 

[bobby53]

what pve fury warrior talent spec do you recommend for 80+ leveling?

The only must have is Impending Victory because of how it rewards you -- the faster you kill the more frequently you get a 20% heal while damaging a mob with your opener.

 

[bobby53]

What Class+Spec are you?: Shaman Restoration
What 'context' is the bot in? (Instance, BG, Normal): Normal (Questing)
What level are you?: 90
Have you made any modifications to Singular?: No
What time (HH:MM:SS) or LogMark did your issue occur?: [17:23:00.718 N]
What happened (be specific)? The bot replaces Water Shield with Lightning Shield and can not decide which is the right one
Did you attach a complete debug log? (choose one: YES or YES): YES

View attachment 71890

Huinabug, Thanks for clearly written post and complete debug log file! You are using:

[17:22:14.971 N] [Singular] Installation: integrity verififed for 3.0.0.1271

That issue was resolved in version 3.0.0.1301, however you should upgrade to the latest which will include other fixes as well. The current release of Singular is available from the first post in this thread [CLICK HERE]. Thanks and good luck with your Shaman, Bobby53

 

[hockeycom14]

Blood DK Chases other player's Bloodworm

What Class+Spec are you?: Blood DK (Alliance)
What 'context' is the bot in? (Instance, BG, Normal): Normal
What level are you?: 88
Have you made any modifications to Singular?: No
What time (HH:MM:SS) or LogMark did your issue occur? 2:36:24 through 2:36:41
What happened (be specific)?

While questing in Kun-Lai summit ( a quest in a cave, I forget which) my DK began targeting the bloodworm of a horde DK and repeatedly tried to cast "outbreak" on it. He actually chased the bloodworm out of the cave. I had to stop the bot and wait til the DK left the area. A few minutes later he passed me in a different quest area and the same thing happened.
Did you attach a complete debug log? Yes

View attachment 7504 2012-12-05 17.59.zip

 

[tomten]

Hi.
Just wanna make sure, for protection warrior, does it treat ultimatum procs as an on gcd ability ?
I can see the proc lit up for ages, if heroic strike is not on cooldown from regular usage, it should be used instantly as its off the gcd
Still think rage limit is bit high for heroic strike in general, I even cap rage sometimes. Does it take into account 120 rage glyph ?

Also, any word on the aoe pulling of mobs, for grinding ?
It doesn't need to be limited to tank specs, most classes have an instant cast and a way to pull, would "just need" a priority list for pulling mobs for each class/spec.
Protection warr would be: taunt, heroic leap, charge(double time talent), heroic throw, mocking banner.
For none tank specs you could limit the number of mobs it tries to gather.

Side bonus is that it will look like less bottish behavior, long as the hitbox issue gets fixed and it can avoid hits in the back with multiple mobs.

Thanks

 

[xaq]

What Class+Spec are you?: Shadow Priest (Horde)
What 'context' is the bot in? (Instance, BG, Normal): Normal
What level are you?: 70
Have you made any modifications to Singular?: No
What time (HH:MM:SS) or LogMark did your issue occur? NA
What happened (be specific)?

First no log because there was nothing in the log of note - I can describe the behavior though.

First off, I love the fact that you added the speed buff option to use Angelic Feather - However this does appear to cause a targeting problem. What happens is the bot clicks on angelic feather buff and has the cursor up on where to place it on the ground, however if it's in a situation where it needs to combat it is unable to target a mob while that cursor is up - I tested this manually as well, while the green cursor is up you cannot tab to select nearest or click on a mob.

The end result is bot will stand there (or continue running through loads of mobs) until the cursor disappears - if you manually hit esc to clear the cursor bot moves on to battle flawlessly and continues on its way - if you disable speed buff problem of course goes away

-X

 

[skules]

skules, Thanks for the post. I am not familiar with that issue, but it does not appear to be a Singular issue based upon my reading of it. A heavy CC as referred to by CodenameG in that thread is a term used to describe CC's which take a long time to process in each frame due to either calls to sleep or loops. Despite a fairly large codebase, Singular is light with regards to the processing done per frame because of its architecture. For further details on that issue, you'll want to follow up in that thread specifically. If you are getting this with Singular and not with another CC, please be sure to post as described in Post #4 in this thread so I can research for you. Be very specific about what the local computer time that the freeze ups occur since there won't be an indication in the log file already identifying that.

As for the Wild Mushroom request, please see Post #4 in this thread so I can have the details regarding this issue to fully research it for you.

Thanks for the post, Bobby53

Thanks very much for the reply

 

[Tamahawk]

Shaman Enhancement Issues

What Class+Spec are you?: Shaman Enhance
What 'context' is the bot in? (Instance, BG, Normal): Normal
What level are you?: 90
Have you made any modifications to Singular?: NO
What time (HH:MM:SS) or LogMark did your issue occur? All the time
What happened (be specific)? CC doesn't make use of either Shamanistic Rage (SR) or Hex, EVER (I always click the SR button myself when I see the need), and there are still melee movement issues
Did you attach a complete debug log? (choose one: YES or YES) YES


Hi Bobby! 1319 of Singular rocks! and my shammy manages quite well but I did want to bring up the aforementioned issues (which Stealthy has mentioned more than once but he refuses to post a log) because they are real.

I've watched my bot for countless hours and he has never made use of SR, ever, (except when I click the button) and he also has never used Hex.

Also, my shammy gets into melee and gets so damn close that the mob moves back, so my shammy moves forward, so the mob moves back, etc... You get the picture.

Are these issues intentional? Perhaps I don't "get" the best way to run a shammy but SR seems quite good in the right circumstances as does mob control with Hex. The motion is a pain because sometimes my shammy will push back a mob into another mob and aggro which is not always preferred.

Anyway, thanks for doing an awesome job! Keep up the good work!

EDIT: I was just reading my log file and I was left confused. As far as I know, I am running 1319 (which I recently d/led and unzipped after deleting the old Singular folder). However, these lines in my log left me perplexe:

[00:38:35.444 D] Singular v3 v3.0.0.1248
[00:38:35.444 D] [RoutineManager] Routine selected from command line: Singular
[00:38:35.448 N] [Singular] Starting Singular v3.0.0.1319
[00:38:35.621 N] [Singular] Installation: integrity verififed for 3.0.0.1319

Let me know. Thanks again for an AWESOME CC.

EDIT 2: My shammy has intersected the path of another player who is grinding the same mobs. Despite his mobs being tapped, my shammy targets them and runs after them and fights them. I thought there was a check to see if a mob was already tapped, and if so then just move on. I've uploaded the log file again (and deleted the original), but it's longer and bigger now. I actually stopped the bot after the problem happened twice, within a 10 or 20 seconds, which made "me" look retarded. it's at 02:33:something, at the bottom.

 

[bobby53]

What Class+Spec are you?: Blood DK (Alliance)
What 'context' is the bot in? (Instance, BG, Normal): Normal
What level are you?: 88
Have you made any modifications to Singular?: No
What time (HH:MM:SS) or LogMark did your issue occur? 2:36:24 through 2:36:41
What happened (be specific)?

While questing in Kun-Lai summit ( a quest in a cave, I forget which) my DK began targeting the bloodworm of a horde DK and repeatedly tried to cast "outbreak" on it. He actually chased the bloodworm out of the cave. I had to stop the bot and wait til the DK left the area. A few minutes later he passed me in a different quest area and the same thing happened.
Did you attach a complete debug log? Yes

View attachment 72111

hockeycom14, Thank you for the detailed post! Targeting is primarily handled by the Bot. In this case, you were running:

[01:59:38.137 N] [Singular] Your Level 88 Human Blood DeathKnight Build is
[01:59:38.138 N] [Singular] ... running the Questing bot Solo in Krasarang Wilds

so the targeting is also modified by the Questing profile. The following lines indicate the targeting was handled by the Quest Bot:

[02:24:02.894 D] Activity: Setting Bloodworm at 22 yards as your target
[02:24:03.256 D] Changed POI to:Type: Kill, Name: Bloodworm

The architecture dictates that the Combat Routine attack what the Bot tells it to. That's the only way questing can work. In the next release, I have modified the portions of Singular that target or select adds during combat to avoid items created or summoned by another player. However it won't fix the initial targeting which was the case in your report. I'll forward this along, but you may want to post in HonorBuddy Support Issues as well.

Thanks for the post and good luck with your DK, Bobby53

 

[bobby53]

Hi.
Just wanna make sure, for protection warrior, does it treat ultimatum procs as an on gcd ability ?
I can see the proc lit up for ages, if heroic strike is not on cooldown from regular usage, it should be used instantly as its off the gcd
Still think rage limit is bit high for heroic strike in general, I even cap rage sometimes. Does it take into account 120 rage glyph ?

Also, any word on the aoe pulling of mobs, for grinding ?
It doesn't need to be limited to tank specs, most classes have an instant cast and a way to pull, would "just need" a priority list for pulling mobs for each class/spec.
Protection warr would be: taunt, heroic leap, charge(double time talent), heroic throw, mocking banner.
For none tank specs you could limit the number of mobs it tries to gather.

Side bonus is that it will look like less bottish behavior, long as the hitbox issue gets fixed and it can avoid hits in the back with multiple mobs.

Thanks

tomten, Ultimatum is a passive ability that procs an aura. There is no GCD associated with it or the Heroic Strike/Cleave that would be cast in response to it. I am happy to look into an issue with this if you take the following steps:
- Click Class Config, Class Specific tab, and set Debug Logging to True
- Run for a bit in whatever bot/environment you want until the Ultimatum issue you described occurs
- Follow the steps in Post #4 of this thread on submitting an issue with debug log file
The log file has status information monitoring the state of Ultimatum procs. Based on its contents I should be able to diagnose why you are getting different results than I am.

In what circumstance is the Rage threshhold a little high? Tanking or Grinding/Soloing? Please share your results in the form of a log file created as described above so I can track the rage levels in your session and see if either an adjustment is needed or a configuration value allowing users to set the rage dump level (not my preference.) As for a hitbox issue, perhaps I overlooked something or am simply not making the connection in this reference with the description in another post, but I'm not aware of a prior report on this and not enough details are provided here to research. If there is something occurring you would like me to look into, be sure to visit Post #4 and follow those steps.

Thanks for the post and good luck with your Warrior, Bobby53

 

[bobby53]

What Class+Spec are you?: Shadow Priest (Horde)
What 'context' is the bot in? (Instance, BG, Normal): Normal
What level are you?: 70
Have you made any modifications to Singular?: No
What time (HH:MM:SS) or LogMark did your issue occur? NA
What happened (be specific)?

First no log because there was nothing in the log of note - I can describe the behavior though.

First off, I love the fact that you added the speed buff option to use Angelic Feather - However this does appear to cause a targeting problem. What happens is the bot clicks on angelic feather buff and has the cursor up on where to place it on the ground, however if it's in a situation where it needs to combat it is unable to target a mob while that cursor is up - I tested this manually as well, while the green cursor is up you cannot tab to select nearest or click on a mob.

The end result is bot will stand there (or continue running through loads of mobs) until the cursor disappears - if you manually hit esc to clear the cursor bot moves on to battle flawlessly and continues on its way - if you disable speed buff problem of course goes away

-X

xaq, The Angelic Feather issue only occurs on certain machines and isn't a widespread issue. It has been resolved and a fix present in the next release which will be available to you soon. Have to tell you, I enjoy watching my priests level more than just about any other character (... almost.) Please be sure to always provide a log file. It provides version and configuration detail that applies to any issue research I do so is always relevant even if there doesn't appear initially to indicate anything regarding the primary problem you are reporting. It also prevents the delay introduced by my requesting one and you having to make a second post. Thanks again for taking the time to report this and good luck with your Priest, -Bobby53

 

[bobby53]

What Class+Spec are you?: Shaman Enhance
What 'context' is the bot in? (Instance, BG, Normal): Normal
What level are you?: 90
Have you made any modifications to Singular?: NO
What time (HH:MM:SS) or LogMark did your issue occur? All the time
What happened (be specific)? CC doesn't make use of either Shamanistic Rage (SR) or Hex, EVER (I always click the SR button myself when I see the need), and there are still melee movement issues
Did you attach a complete debug log? (choose one: YES or YES) YES
...

Tamahawk, Thank you for taking the time to make such a detailed an accurate post! I'll try to respond to each of your questions/issues individually to make sure they are covered:

Shamanistic Rage - a miss on my part..... will be in the next release

Too close to melee - That was definitely a problem prior to Singular .1314 and fixed in .1319. You mentioned replacing the log file so am not sure if you updated in the intervening time or now since you are running .1319. This should be fixed, but please double check this behavior and if still occurring upload a log file along with telling me the exact local computer time you observed it to the second (HH:MM:SS)

Attacking mobs tagged by another player - there is logic for that (present for a long time.) I'll need to look into this one further.

Hex - support already present for Elemental in Normal context. that was tested so will roll into an upcoming release for other specs/contexts.

The behaviors you referenced were not by design. SR was simply missed during a heavy development phase and not adequately reported as missing prior to your post. The melee distance issue was a bug introduced in the process of adding some improvements/fixes.

Thanks for the post and good luck with your Shaman, Bobby53

 

[Tamahawk]

Shaman Enhancement Issues cntd...

Tamahawk, Thank you for taking the time to make such a detailed an accurate post! I'll try to respond to each of your questions/issues individually to make sure they are covered:

Shamanistic Rage - a big miss on my part..... it will be in the next release

Too close to melee - That was definitely a problem prior to Singular .1314 and fixed in .1319. You mentioned replacing the log file so am not sure if you updated in the intervening time or now since you are running .1319. This should be fixed, but please double check this behavior and if still occurring upload a log file along with telling me the exact local computer time you observed it to the second (HH:MM:SS)

Attacking mobs tagged by another player - there is logic for that (present for a long time.) I'll need to look into this one further.

And no, the behaviors you referenced were not by design. SR was simply a miss and the melee distance issue was some breakage I introduced fixing some other movement issues (where a melee would stop just out of melee range but think he was in it.) Note that unlike other abilities, SR will be cast based upon dropping to a certain Health% or Mana%. This covers both of its situational uses (damage reduction and mana efficiency.)

Thanks for the post and good luck with your Shaman, Bobby53

Hello and thanks for the prompt response! You're doing an awesome job here on Singular.

I don't mean to be rude, but you didn't address HEX, which I also brought up in my earlier post.

Also, if you look at my original post (and the attached log), you'll see that this behavior (the motion thingy) is happening under 1319; 1319 as seen in my log and in the few lines included in my original message quoted from the log.

In other words, I'm running 1319 AND I'm still have those motion issues. I've been running 1319 since you released it; it's not something I updated today.

Thanks again for your time.

 

[bobby53]

Hello and thanks for the prompt response! You're doing an awesome job here on Singular.

I don't mean to be rude, but you didn't address HEX, which I also brought up in my earlier post.

Also, if you look at my original post (and the attached log), you'll see that this behavior (the motion thingy) is happening under 1319; 1319 as seen in my log and in the few lines included in my original message quoted from the log.

In other words, I'm running 1319 AND I'm still have those motion issues. I've been running 1319 since you released it; it's not something I updated today.

Thanks again for your time.

Tamahawk, HEX was covered. The edit to my prior post saved 6 minutes PRIOR to your reply so am guessing you may have already been composing your post. I had also mentioned you were running .1319 BUT because of the multiple edits to the issue post wasn't sure whether the comment applied to .1319 or whatever version you were running when the post was initially made. I'll look into it specifically with an Enhancement Shaman, but I'm not seeing it on other melee classes. Anyway, if you are still seeing the movement problem then its obviously something different than was fixed in .1319 so may need additional detail from you if I can't recreate (debug log produced with the settings and specific time reference described earlier.) The different version number references you mentioned as confusing definitely are... fixed in next release. Thanks for the follow up, Bobby53

 

[Tamahawk]

Shaman Enhancement Issues cntd...

Tamahawk, Hex was covered. I edited and saved my post. Looks like final version posted six minutes before your response, so you must have already been composing it at that point. I had also mentioned you were running .1319 but because of the multiple updates to the post wasn't sure whether the comment applied to .1319 or a prior version. The different version number references you mentioned as confusing definitely are... fixed in next release. Anyway, if you are still seeing the movement problem then its obviously something different is occurring. I'll look into it specifically with an Enhancement Shaman, but I'm not seeing it on other melee classes. Thanks for the follow up, Bobby53

Thanks Bobby. Sorry for the crossover in our postings. I guess I was stalking the forums and jumped in when I saw your first response. Thanks for adressing these issues. I look forward to seeing them in the next release.

Keep up the great work!

 

[tomten]

tomten, Ultimatum is a passive ability that procs an aura. There is no GCD associated with it or the Heroic Strike/Cleave that would be cast in response to it. I am happy to look into an issue with this if you take the following steps:
- Click Class Config, Class Specific tab, and set Debug Logging to True
- Run for a bit in whatever bot/environment you want until the Ultimatum issue you described occurs
- Follow the steps in Post #4 of this thread on submitting an issue with debug log file
The log file has status information monitoring the state of Ultimatum procs. Based on its contents I should be able to diagnose why you are getting different results than I am.

In what circumstance is the Rage threshhold a little high? Tanking or Grinding/Soloing? Please share your results in the form of a log file created as described above so I can track the rage levels in your session and see if either an adjustment is needed or a configuration value allowing users to set the rage dump level (not my preference.) As for a hitbox issue, perhaps I overlooked something or am simply not making the connection in this reference with the description in another post, but I'm not aware of a prior report on this and not enough details are provided here to research. If there is something occurring you would like me to look into, be sure to visit Post #4 and follow those steps.

Thanks for the post and good luck with your Warrior, Bobby53

I will bot some later today and provide a full proper log.

English not my native language so probably just got lost a bit.
Yes, i know it procs an aura/buff, but the buff enables one free heroic strike, heroic strike is off the gcd...it does not use heroic strike instantly when the buff procs.
i.e, bot doesn't recognize it just got a rage free heroic strike is AND that heroic strike is off the gcd.
Just wanted to know if this was intended behavior or not.

But ill be good user and provide a log later today

 

[bobby53]

I will bot some later today and provide a full proper log.

English not my native language so probably just got lost a bit.
Yes, i know it procs an aura/buff, but the buff enables one free heroic strike, heroic strike is off the gcd...it does not use heroic strike instantly when the buff procs.
i.e, bot doesn't recognize it just got a rage free heroic strike is AND that heroic strike is off the gcd.
Just wanted to know if this was intended behavior or not.

But ill be good user and provide a log later today

tomten, The Prot Warrior information I have seen indicates Ultimatum procs should be dealt with at a low priority. While Singular currently implements this priority, it seems wrong to have an ability that costs nothing and incurs no GCD so low in the priority. I'll move the Heroic Strike/Cleave on Ultimatum proc higher in the priority for the next release. -Bobby53

 

[El Fluppe]

facing problems with my aflli warlock.

it is casting the voidwalker very often even it is already existing and has full life.
is anybody also having this problem?

 

[laria]

AW: Singular - A community driven All-In-One CC - It Just Plain Works - (Version 3)

You tried the archive on the front page woth the most recent Version?

 

[ripglider]

Is there a way to make my SV Hunter stop running from mobs while grinding? I'm running a Golden Lotus grind profile and anytime he pulls a mob my pet isn't already tanking he runs from them. This ends in him running off walls/cliffs or just not attacking since he's running until my pet dies. Singular is still the best CC for this profile that I've found. Would a different spec work better? Thanks