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

Dunno if anyone has already reported this, and if so, im sorry, but singular is not using survival instincts (druid), in any spec, form or level, tested in most botbases.
 
bobby53 said:
tumbum, You currently have your Pull Distance set to 1. Here is the config info at HB startup:
Code: 
[18:39:07.117 D] PullDistance: 1
Singular will output a warning when the Bot is started as well:
Code: 
[18:42:33.595 N] [Singular] Your Level 90 Tauren Elemental Shaman Build is
[18:42:33.595 N] [Singular] ... running the Questing bot in Shrine of Two Moons  
[18:42:33.595 N] [Singular] ... Zone: Pandaria using my SOLO Behaviors
[18:42:33.660 N] [B][Singular] your Pull Distance is 1 yds which is low for any class!!! [/B]
If you get that message at startup, you'll want to Stop the bot, click Settings and change it to between 30 and 40 for an Elemental Shaman. Some of Kick's questing profiles temporarily set it to 1 yard to avoid getting into combat. If a profile aborts or doesn't include the code to restore the original value, you'll end up with 1 set as your choice for Pull Distance.

I rechecked the log you submitted previously for your Elemental Shaman doing dailies. The Pull Distance there was set to 20, so I don't believe the Pull Distance was the only issue you encountered. Changing Pull Distance to the values I mentioned will give you better results in other circumstances, but it seems there is another circumstance affecting you as well. No other data needed at this time. Will look specifically at the quest from your earlier log and follow up tomorrow. Thanks for the post and the detailed submissions, Bobby53
Click to expand...

Ok here my last Log to this. Happens right now again, Pull Distance is 10 at the moment. Start at [22:01:29.006 N]
Its really different, sometimes it works after a while, sometimes it need to let the Toon die before the Fighting runs normal again.
 

Attachments

Last edited:
tumbum said:
Ok here my last Log to this. Happens right now again, Pull Distance is 10 at the moment. Start at [22:01:29.006 N]
Its really different, sometimes it works after a while, sometimes it need to let the Toon die before the Fighting runs normal again.
Click to expand...
tumbum, Thanks for the post. The problem you encountered is due to the following:
Code: 
[COLOR=#0000ff]... Questing Bot selects Tamed Bladetalon as BotPOI ...[/COLOR]
[22:01:29.807 D] Changed POI to:Type: Kill, Name: Tamed Bladetalon

[COLOR=#0000ff]... Questing Bot attempts to move to BotPOI ....[/COLOR]
[22:01:29.958 D] Activity: Moving towards Tamed Bladetalon

[COLOR=#0000ff]... HB perceives an issue in attempting to move for 5 seconds but not being able to, so target is blacklisted ....[/COLOR]
[22:01:34.551 N] Tried to move to Tamed Bladetalon for 45 seconds, blacklisting!

[COLOR=#0000ff]... Questing changes BotPOI to nearby mob and kills it in 16 seconds ...[/COLOR]
[22:01:34.679 D] Changed POI to:Type: Kill, Name: Zandalari Beastlord
[COLOR=#808080][I]... cut for space ...[/I][/COLOR]
[22:01:50.099 D] Cleared POI - Reason POI is dead from Combat

[COLOR=#0000ff]... only other mob in area still blacklisted until 22:02:18, so following message spams a bit ....[/COLOR]
[22:01:51.274 N] [Singular] Current target invalid.  No other targets available 
[COLOR=#0000ff]
... then at 22:02:18 the mob is no longer blacklisted so is seen as a target ...[/COLOR]
[22:02:18.222 N] [Singular] Casting Capacitor Totem on Tamed Bladetalon.D9A9 @ 34.7% at 3.2 yds

So it appears there are at least 2 issues occurring here:

1. HonorBuddy or Questing Bot being unable to move to the target. Not sure if this is due to being unable to generate a path (it wasn't present in your log, but that was the message I received in my session I referenced above) or something else entirely. Since that zone is relatively new, there may be mesh issues still to work out but I can't say for certain. This needs to be looked at including the appropriate duration ( in this case 45 seconds ) for blacklisting mobs that cannot be moved to by HB Core Devs.

2. For some reason, after this the Combat Behavior is not called again by the Questing bot. The totems are being cast initially by the CombatBuffs behaviior (also noticed a Shamanistic Rage and other casts from here.) Once your health falls below 40% it begins spamming Healing Surge as part of the Heal Behavior. The problem is, Healing Surge doesn't appear to be able to keep up with the incoming damage you are receiving (2nd or 3rd mob agro possibly?), so you eventually die without casting an attack other than Capacitor Totem and Searing Totem.

Basically, the scenario represented by the log file has you blacklisting a hostile mob, then fighting another mob while being attacked by one or more mobs atleast one of which it has blacklisted and won't attack. You are put in a vulnerable position and unable to recover.

I'll pass this along to the HB Core Devs as there isn't much I can do. Basically, the mob shouldn't be added to the Combat blacklist but instead should be part of a Targeting Blacklist. That way HonorBuddy can choose not to actively target the mob, but if you end up in combat with it the Combat Routine isn't encumbered trying to defend itself.

Thanks for the follow up with the log file requested. -Bobby53
 
Last edited:
Bobby thanks for fantastic CC!

I have one request.... is possible add support on "touch of death" spell on monk tank?
thanks,
Max
 
now there is another big problem and it does nothing u fixed the other thing now is this here

[Singular] STUNNED! (loss of control)
[Singular] Casting Hand of Freedom on Me @ 100.0%
[Singular] STUNNED! (loss of control)
[Singular] STUNNED! (loss of control)
[Singular] Casting Hand of Freedom on Me @ 100.0%
[Singular] STUNNED! (loss of control)
[Singular] STUNNED! (loss of control)
[Singular] STUNNED! (loss of control)
[Singular] Casting Hand of Freedom on Me @ 100.0%
[Singular] STUNNED! (loss of control)
[Singular] STUNNED! (loss of control)
[Singular] STUNNED! (loss of control)
[Singular] Casting Hand of Freedom on Me @ 100.0%
[Singular] STUNNED! (loss of control)
[Singular] STUNNED! (loss of control)
[Singular] STUNNED! (loss of control)
[Singular] Casting Hand of Freedom on Me @ 100.0%
[Singular] STUNNED! (loss of control)
[Singular] STUNNED! (loss of control)
[Singular] STUNNED! (loss of control)
[Singular] Casting Hand of Freedom on Me @ 100.0%
[Singular] STUNNED! (loss of control)
[Singular] STUNNED! (loss of control)
[Singular] STUNNED! (loss of control)
[Singular] Casting Hand of Freedom on Me @ 100.0%
[Singular] STUNNED! (loss of control)
[Singular] STUNNED! (loss of control)


and it just keep standing stil and logs out.

also this happens

[Singular] Current Kill POI dead. Clearing POI Spinescale Basilisk!
[Singular] Current target invalid. No other targets available


and also again

[Singular] Current target invalid. No other targets available
[Singular] Current target invalid. No other targets available
[Singular] Current target invalid. No other targets available
[Singular] Current target invalid. No other targets available
[Singular] Current target invalid. No other targets available
[Singular] Current target invalid. No other targets available
[Singular] Current target invalid. No other targets available
[Singular] Current target invalid. No other targets available
[Singular] Current target invalid. No other targets available
[Singular] Current target invalid. No other targets available
[Singular] Current target invalid. No other targets available
[Singular] Current target invalid. No other targets available
[Singular] Current target invalid. No other targets available
[Singular] Current target invalid. No other targets available
[Singular] Current target invalid. No other targets available

and it stil does nothing.
 
Last edited:
i wil upload a log i have difference folders i use 5 bot accounts so i need to see witch log it is.
 
Balance Druid Requests

My Proposals/Requests after looking at the balance druid behavior:



  • Cenarion Ward Setting, -> Below x % Health. -> At this moment it pops it off cd/at full health causing just overheals.
  • Rejuvenation Setting, -> The current one does not trigger at set value ( 90 ) -> It will rejuv @ 30 % hp though ( probably hardcoded )
  • Typhoon Setting -> Boolean to turn it off/on, most of the time it pulls aggro on more mobs causing the druid to die.
  • Multidotting -> It does not multidot targets while questing really inefficient for a multi dotting class.


Log:
No log attached, yes NO log.

Why: Those are not errors, or have been reported earlier on by me and other players. If u want a more detailed description I can post / link to my livestream.
 
Could you make it so there's not auto vanish because I use this for PvP as it's the best. Maybe make it so you can turn it on and off.
 
here a log bobby it keeps happning

whole the time it spams invalid target and does nothing its stil there and some other thins pls watch the log it keeps happning over and over.

and more other things

[06:19:23.703 N] [Singular] Current target invalid. No other targets available
[06:19:23.802 N] [Singular] Current target invalid. No other targets available
[06:19:23.902 N] [Singular] Current target invalid. No other targets available
[06:19:24.003 N] [Singular] Current target invalid. No other targets available
[06:19:24.101 N] [Singular] Current target invalid. No other targets available
[06:19:24.198 N] [Singular] Current target invalid. No other targets available
[06:19:24.291 N] [Singular] Current target invalid. No other targets available
[06:19:24.386 N] [Singular] Current target invalid. No other targets available

alot of issues with questing
 

Attachments

In version 2150 there's a bug in ClassSpecific\Hunter\Common.cs on line 611 in CreateMisdirectionBehavior that causes Misdirection to not be cast on pet in normal context.
Code: 
Spell.Cast("Misdirection", ctx => (WoWUnit) ctx, req => Me.GotAlivePet && Pet.Distance < 100),
Should be
Code: 
Spell.Cast("Misdirection", ctx => Pet, req => Me.GotAlivePet && Pet.Distance < 100)
Cheers :)
 
Last edited:
WileE91 said:
There's a bug in ClassSpecific\Hunter\Common.cs on line 611 in CreateMisdirectionBehavior that causes Misdirection to not be cast on pet in normal context.
Code: 
Spell.Cast("Misdirection", ctx => (WoWUnit) ctx, req => Me.GotAlivePet && Pet.Distance < 100),
Should be
Code: 
Spell.Cast("Misdirection", ctx => Pet, req => Me.GotAlivePet && Pet.Distance < 100)
Cheers :)
Click to expand...

this doesend happned to my hunter only it happns to my other pallys to on my other accounts and it just keep standing there til i stop the bot and start it again witch shouldnt happns normally
 
bobby53 said:
dna9418, Thank you for the attached log file. Unfortunately I'll need more information to be able to research this for you. Specifically, I need a point of reference where you observed it doing nothing. This can be a LOGMARK you add (see LogMark plugin in my sig), the local system time on your computer when you see it occur, or possibly the name of a uniquely named mob (a boss for example) that the problem happened during. The Reporting Bugs [CLICK HERE] post describes this and provides a template you can copy and paste. Without a point of reference and no obvious errors, I don't really know what part of the log file to focus on. That is especially true in cases where the problem is the absence of something. Thanks again for your post and I'll keep an eye out for your follow up, Bobby53
Click to expand...
It's random times never happens in the same place...
 
Mario27 said:
here a log bobby it keeps happning

whole the time it spams invalid target and does nothing its stil there and some other thins pls watch the log it keeps happning over and over.

and more other things

[06:19:23.703 N] [Singular] Current target invalid. No other targets available
[06:19:23.802 N] [Singular] Current target invalid. No other targets available
[06:19:23.902 N] [Singular] Current target invalid. No other targets available
[06:19:24.003 N] [Singular] Current target invalid. No other targets available
[06:19:24.101 N] [Singular] Current target invalid. No other targets available
[06:19:24.198 N] [Singular] Current target invalid. No other targets available
[06:19:24.291 N] [Singular] Current target invalid. No other targets available
[06:19:24.386 N] [Singular] Current target invalid. No other targets available

alot of issues with questing
Click to expand...
Revised in next release. That message indicates that the BotBase isn't providing a target to Singular. However, it doesn't need to be spammed to that extent. Thanks for the log, Bobby53
 
WileE91 said:
In version 2150 there's a bug in ClassSpecific\Hunter\Common.cs on line 611 in CreateMisdirectionBehavior that causes Misdirection to not be cast on pet in normal context.
Code: 
Spell.Cast("Misdirection", ctx => (WoWUnit) ctx, req => Me.GotAlivePet && Pet.Distance < 100),
Should be
Code: 
Spell.Cast("Misdirection", ctx => Pet, req => Me.GotAlivePet && Pet.Distance < 100)
Cheers :)
Click to expand...
WileE91, Thanks for the catch. In next release, -Bobby53
 
dna9418 said:
View attachment 87316Having problem with rogue during questing with attacking mobs.It sometimes attacks and at other time it just stands there doing nothing i say 40% of the time.I checked to see if it was a plugin but i don't think it is.is this just a bug or do i need to fix something in settings?
Click to expand...
bobby53 said:
dna9418, Thank you for the attached log file. Unfortunately I'll need more information to be able to research this for you. Specifically, I need a point of reference where you observed it doing nothing. This can be a LOGMARK you add (see LogMark plugin in my sig), the local system time on your computer when you see it occur, or possibly the name of a uniquely named mob (a boss for example) that the problem happened during. The Reporting Bugs [CLICK HERE] post describes this and provides a template you can copy and paste. Without a point of reference and no obvious errors, I don't really know what part of the log file to focus on. That is especially true in cases where the problem is the absence of something. Thanks again for your post and I'll keep an eye out for your follow up, Bobby53
Click to expand...
dna9418 said:
It's random times never happens in the same place...
Click to expand...
dna9418, I think you may have misunderstood. You are reporting an error that you see happening. If you see it happen, immediately write down the local system time on your computer, OR even better press the key combination to add a LOGMARK to your log file and just note which one it was ( #1, #2, etc.) So I'm not asking you to do any analysis or troubleshooting, All that is needed is for you to include in your post: what you saw, *exactly* when you saw it, and attach a log file from that session. That is typically more than enough for me to assist users and hopefully will be in this case as well. Thanks for the post and good luck with your Rogue, Bobby53
 
bobby53 said:
Revised in next release. That message indicates that the BotBase isn't providing a target to Singular. However, it doesn't need to be spammed to that extent. Thanks for the log, Bobby53
Click to expand...


awsome what about the los control it does that the same it keeps spamming it and then afther awhile it logs out because it does nothing
 
Mario27 said:
awsome what about the los control it does that the same it keeps spamming it and then afther awhile it logs out because it does nothing
Click to expand...
It outputs it once a frame while you are stunned. Nothing to fix on that. -Bobby53
 
You must log in or register to reply here.
Back
Top