What's new
  • 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

Hey, ive been using several paid routines but recently have been taking a closer look at singular. I how ever really like to choose when i am using cooldowns outside the normal rotation (such as recklessness/bladestorm) but also stormbolt, I really just want singular to do the basic rotation for fury (warrior) and i'm more than willing to fiddle with the file if i could just learn how haha (hope thats allowed o.O) how can i make it so it will only use the main dps abilities such as wild strike, raging blow, blood thirst, execute when applicable, keep hamstring on target (for the occasional bg).

so any info on how to remove cooldowns from the routine or if someone could help me out, would be amazing, i love all of the communties work and hope to one day be able to contribute :)
 
doesnt attack players when they attack you. please fix this. it looks so super bottish when your being attacked and you ignore the player and just continue trying to pull a mob while being hit in the back.

and yes, its set to obviously ^^
 
Happy new year!

Here's another log. Singular still doesn't work right on my Mistweaver Monk in Battlegrounds,
It only tries to walk to somewhere, but doesn't heal himself while being attacked.
 

Attachments

When questing, the shaman (have tested with other class like Warlock or Shadow priest and it seems fine) has to escort this skeleton to another mob, but when it gets that mob the totem disappears, the bot then casts a totem spell which then kills the skeleton, I believe that this is a very rare occuracnce and only occurs with this quest.. basically it's an infinite loop because the bot keeps casting totem when he gets the skeleton.

I hope the end result is that the bot just doesn't cast totems when doing this quest, thank you.

WoWHead Quest Link: Killing Two Scourge With One Skeleton - Quest - World of Warcraft

EDIT1:

What Class+Spec are you?: Enhancement Shaman
What 'context' is the bot in? (Instance, BG, Normal): Questing
What level are you?: 85
Have you made any modifications to Singular?: No
What time (HH:MM:SS) or LogMark did your issue occur? Near the end of the log file
What happened (be specific)? Recalls totems which kills the escort skeleton required to kill another mob, infinite loop of getting the skeleton which kills the totem and then the bot casts totem which kills the skeleton.
Did you attach a complete debug log? (choose one: YES or YES) Log Level - Normal.
 

Attachments

Singular for Mage needs heavy fixing. It won't use Ice Barrier, it wants to sometimes cast FFB over FB. The pet glitches out and sometimes won't even attack.
 
Hello.
* Pull more target option; "Hostile" / "All", does that include enemy players ?
If so, would be nice if it avoided players.
Can't tell from log but ran ~12 hour grind yesterday and had several counts where it looks like i initiate enemy combat but not sure.
Thanks for the detailed description and log file!

No, Singular will never invoke Pull More functionality to attack an Enemy Player. Additionally, if attacked by an Enemy Player, Singular will temporarily disable Pull More use until completing the current combat ( Rest, Out of Combat, etc.)

* "Die by the sword", "Enraged regeneration" and "Recklessness" is not being used in normal context at all, only in pvp context.
Huge log, no logmarks (was sleeping) but just to give you a reference to go on.
View attachment 159313
Only code editing are number values to things like aoecount and unfriendlyunits, no actual "change".
This log file is actually generated entirely from Normal Context. Battlegrounds Context (aka PVP) only occurs within Battlegrounds or Arena. It is interesting to note that there was only one call to these spells in the log while fighting an NPC (*Enraged Regeneration while fighting Iron Arbalester.1DE3). All other casts were made only when fighting an enemy player in World PVP. I'll need to look into this further as it is not related to specific criteria enforcing that, so a side-effect appears to be occurring. This will require further research, -Bobby53
 
[15:03:31.171 N] [Singular] Your Level 100 Night Elf Balance Druid Build is
[15:03:31.171 N] [Singular] ... running the Gatherbuddy2 bot in Spires of Arak
[15:03:31.171 N] [Singular] ... Zone: Draenor using my SOLO Behaviors
[15:03:31.379 N] [Singular] Pull More: not active, Singular disables for Balance Druid until learning 'Sunfire'

Is this a bug? Even when setting Pull More to 'Always' instead of Auto it still won't pull more. Maybe to do with the spell being replaced with Moonfire in Lunar Phase?
 
No, Singular will never invoke Pull More functionality to attack an Enemy Player. Additionally, if attacked by an Enemy Player, Singular will temporarily disable Pull More use until completing the current combat ( Rest, Out of Combat, etc.)

Pull more would be my starting point for finding out why singular won't react to enemy players attacking you. I'm thinking if the disable of pull more for reaching mobs could affect enemy players attacking you ?
I've seen it from time to time but been lazy digging out a log for it. Will get one soon but its a pretty nasty bug :(


This log file is actually generated entirely from Normal Context. Battlegrounds Context (aka PVP) only occurs within Battlegrounds or Arena. It is interesting to note that there was only one call to these spells in the log while fighting an NPC (*Enraged Regeneration while fighting Iron Arbalester.1DE3). All other casts were made only when fighting an enemy player in World PVP. I'll need to look into this further as it is not related to specific criteria enforcing that, so a side-effect appears to be occurring. This will require further research, -Bobby53

Ohh, i assumed pvp context was pulled upon entering pvp combat. I should stop assuming so much :p
Yeh, it should definitely have more uses and i've seen the bot literally die while having all cooldowns available, ties in to the blacklisting issue i've mentioned earlier. Where singular won't see its getting attacked.
 
Is this a bug? Even when setting Pull More to 'Always' instead of Auto it still won't pull more. Maybe to do with the spell being replaced with Moonfire in Lunar Phase?

Full log would be nice but im pretty sure you're not using the latest version of HB ?
You're using old singular version aswell ye ?
 
Last edited:
Full log would be nice but im pretty sure you're not using the latest version of HB ?
You're using old singular version aswell ye ?

[16:37:01.053 N] Honorbuddy v2.5.12479.763 started.
[16:37:12.585 N] [Singular] Starting Singular v4.0.0.4107
 
Hello, I was wondering is there any way to use option "Always Prowl" (Feral Druid) only when my character is outside of instances/bgs etc. and disable it when he enters a dungeon?
 
Log attached for Singular Pull More error.
View attachment 161989

Thanks, see how easy it was when you posted log ?
I can see the error but i can't tell you why its happening lol. Bobby will get back to you ;)

@Bobby. Spellmanager is showing the override entry for sunfire over moonfire but it never happens when initializing, only on starting.
Either way, sunfire is learned at lvl 82 (according to wowhead) while moonfire is learned at lvl 10. Think it makes more sense to use moonfire as the check for boomkin ?
 
Hello, I was wondering is there any way to use option "Always Prowl" (Feral Druid) only when my character is outside of instances/bgs etc. and disable it when he enters a dungeon?

Why do you want this ?
If you disable it... then when he enters dungeon how do you expect him to pull mobs ??
 
Edit. Merging 2 posts as they are pretty much about the same issue. You can archive https://www.thebuddyforum.com/honor...riven-cc-plain-version-3-a-8.html#post1772241

Don't think the targeting issue is exclusive to warrior :p





The bot gets into some weird loop where it just stands still and rapid targetting 2 blacklisted mobs, deblackisting them etc.
Eventually just dies from standing still.

No logmark sorry but last minute or two details the issue. "The installation modified" is just me tweaking a few numbers, no actual code change.

View attachment 159077



Here is a smaller log detailing the issue from around line 9290. (no logmark, sorry)
Its blacklisting Mob 2E03 (currently hitting me) and then trying to take the target next to it (not in combat) but realizing its getting attacked but its not lifting the blacklist.
So it goes into an endless loop where its trying to select a new target but it cant cause (im guessing here) Aggroed mob has higher priority than a new target and thus this endless loop is created until toon dies.

View attachment 159472

EDIT: These issues are still active in v.4101

Edit3. Log where singular decides to initiate combat after it died with an enemy hunter. Line 47416
Earlier in the log (no log mark, sry) you will also find the issue of the bot being attacked by enemy players but walking away from them.
View attachment 161707
Thanks Tomten. Looked into these issues.

- Changes in next release for blacklisting mob issue. Not certain its a fix as I was not able to duplicate, but based upon subsequent feedback with new code should be able to identify if issue persists.

- Attacking enemy player. In the case of the enemy hunter example provided, the attack was done due to carrying out the botbases instructions:
Code:
[B][22:45:44.372 D] Changed POI to: Type: Kill, Name: Lvl 99 Horde Hunter
[/B][22:45:44.752 N] [Singular] Switching to BotPoi: Enemy.Hunter.74A4!

- Dropping mobs while in Combat. This isn't a decision a Combat Routine can make other than by blacklisting a mob. Unless Singular has blacklisted the mob in question (which would be indicated in the log) leaving is due to the botbase determining it is time to leave and not continuing to invoked the Combat Routine to kill the mob. In the cast of LOGMARK #2 referenced, Singular was unable to reach the mob in question within 20 seconds (maximum time Singular allows for moving into melee range of a Pull target) so the mob was Blacklisted for Pull. This doesn't blacklist the mob for Combat (if it was aggroed Singular will fight it) but it will prevent the mob from being a Pull target and so we won't try to enter combat with it if we aren't already in combat by some other means. This is by design and appears to be working as expected.

Thanks for the specifics on these,
-Bobby53
 
Not sure if this is a known bug or not, but basically unless the questing profile calls for Singular to be disabled (for movement or other purposes) my warrior will constantly switch between Battle and Defensive stances.

It begins almost instantly, and the logs seem to show much more than just the stances being activated in them.

View attachment 8144 2015-01-03 18.45.txt
View attachment 7580 2015-01-03 18.14.txt
View attachment 9124 2015-01-03 18.14.txt
View attachment 6396 2015-01-03 18.06.txt

I hope these logs will give some help. I was trying out different things with disabling some plugins to see if that resolved the problem, and it did not.

Let me know if you need any extra information from me, I will be glad to provide what I can figure out.
 
Thanks Tomten. Looked into these issues.

- Changes in next release for blacklisting mob issue. Not certain its a fix as I was not able to duplicate, but based upon subsequent feedback with new code should be able to identify if issue persists.

Thanks, will report back after testing new release :)
- Attacking enemy player. In the case of the enemy hunter example provided, the attack was done due to carrying out the botbases instructions:
Hmm, that is really strange, why would questingbot attack enemy players..
I'll open ticket with hb. Thanks for the info :)
- Dropping mobs while in Combat. This isn't a decision a Combat Routine can make other than by blacklisting a mob. Unless Singular has blacklisted the mob in question (which would be indicated in the log) leaving is due to the botbase determining it is time to leave and not continuing to invoked the Combat Routine to kill the mob. In the cast of LOGMARK #2 referenced, Singular was unable to reach the mob in question within 20 seconds (maximum time Singular allows for moving into melee range of a Pull target) so the mob was Blacklisted for Pull. This doesn't blacklist the mob for Combat (if it was aggroed Singular will fight it) but it will prevent the mob from being a Pull target and so we won't try to enter combat with it if we aren't already in combat by some other means. This is by design and appears to be working as expected.

The issue is that singular is attacking and having aggro on all of them and at low hp they start fleeing.
I'm pretty certain the mobs don't flee for 20 seconds but something is wrong.
It can't be by design to have fleeing mobs be ignored, cuz they all flee. Me being arms is just lucky to have an aoe ability being my single target filler so a good chunk of them die before getting out of range.
Could grindbot be the one to blame ?
Sorry i cant offer more to go on this time but something is wrong, i know it :(
 
Last edited:
Request

I would like to make a request if such an addition wouldn't take too much of your time.

Hunters with the beastmastery talent are capable of taming the silithid pet family. This pet family offers a buff called qiraji Fortitude which is not automatic applied when the pet is summoned, as are other pet's buffs, for reason unknown to me.

Now I was wondering if it was possible to make the CC apply this buff when possible :), but truth be told is that it really wouldn't be of high priority for me.

Qiraji Fortitude[TABLE="width: 100%"]
[TR]
[TD]Increases Stamina by 10%.
Increases spell power by 10%.[/TD]
[/TR]
[/TABLE]
 
Back
Top