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

zorked said:
Hey there,
Especially when using solo Dungeon profiles or solo levelling as BloodDK (yeah, some people do that :D ) the bot does not buff Horn of Winter.

It's easily fixed by adding
Code: 
Spell.Buff("Horn of Winter", ret => !StyxWoW.Me.HasAura("Horn of Winter")),
somewhere in the #region CombatBuffs part of the Blood.cs file in the Death Knight folder.

Would love to see it implemented in the next HB update since I have to manually adjust it everytime I update HB.

Thank you. :)
Click to expand...
zorked, Sorry, but Horn of Winter is buffed in both the PreCombatBuffs and the PullBuffs behaviors. If it is not being cast it is due to a bug in the logic of the component driving combat failing to call these behaviors. This is typically the botbase, but in some cases could be a plugin, quest behavior, or profile. Without a log file there is no way to advise however. Please see the Reporting Bugs post in this thread (#4) and follow those steps when posting an issue. -Bobby53
 
Cyphoner said:
I am having some trouble with my healer staying too far behind so when the tank pulls a boss and the door shuts, my healer is left outside.

Max Heal Target Range: 50
Stay near tank: True
Stay near Tank Range: 5

Dungeonbuddy follow is set to: 1

With these settings, shouldn't the healer pretty much grouphug the tank at all times?
Click to expand...
Cyphoner, Please follow the steps in the Reporting Bugs post (#4) in this thread.

As for this topic, I can only speak to the Singular settings that were mentioned (bolded above.) In general, DungeonBuddy would handle movement while not in combat, and Singular while in combat. I say general because DungeonBuddy will move to get out of ground effects, implement scenario specific movement strategy, etc.

- Max Heal Target Range indicates the maximum range at which you will "see" a group member. Given the above, if they are 51 yards away, they will not appear in the Heal Target list regardless of their Health %. This will not cause you to stay within 50 yards, it just means you won't move towards anyone that is more than 50 yards away.

- Stay Near Tank indicates you should try to stay near the tank while In Combat. It has no effect when out of combat

- Stay Near Tank Range is the maximum range distance you want to be from the tank during combat. Presently it uses the maximum of the range specified or the value 10. This is because it uses range buffered approach for movement to avoid the staccato type of jerky movement sometimes seen by components moving a fixed distance away from an object/unit. In this case however it is interfering with your intentions to stay close so I'll revise this portion of the logic.

It is important to note that your healer could still move away from the tank to get within range of a heal target that is 50 yards away (10 yds further than most heal spells) because of your settings. If you don't want to move towards another raid member to heal them and only stay near the tank, set your Max Heal Target Range to 40.

Note: this change will only impact the distance from the tank during Combat, not while out of combat. When standing and waiting for the Tank to Pull and the Tank runs towards the mob, it is DungeonBuddy controlling the follow distance until the point you are in combat. Once the tank actually engages and you are in combat Singular will act upon the settings described above and move within the appropriate distance described.

-Bobby53
 
have there been any other reports of questing in BC, hellfire peninsula, where the bot will try and fight unflagged opposite faction players? Resulting in the bot simply following them, constantly trying to attack?

This will easily result in player reports. Resulting in bans. I caught my 61 WW monk doing this 4 different times last night. Will post diagnostic level log tonight when it starts to do it again. Pretty big issue I have never noticed after botting 1-90 on 9 other toons.
 
User0828 said:
have there been any other reports of questing in BC, hellfire peninsula, where the bot will try and fight unflagged opposite faction players? Resulting in the bot simply following them, constantly trying to attack?

This will easily result in player reports. Resulting in bans. I caught my 61 WW monk doing this 4 different times last night. Will post diagnostic level log tonight when it starts to do it again. Pretty big issue I have never noticed after botting 1-90 on 9 other toons.
Click to expand...
User0828, No other reports and no log files. Please be sure to follow the steps in Reporting Bugs (post #4 in this thread) so the log file contains the information necessary to research. In other words, be certain that Log Level is set to Diagnostic before Questing and if you observe the behavior you set a LOGMARK immediately. I won't be able to look into it without that level of detail. Thanks and good luck with your question, -Bobby53
 
Just caught my bot doing it. I hit logmark, then a couple seconds later, stopped the bot. Log level: diagnostic.

View attachment 122019

My bot saw a unflagged opposite faction player just doing the same quest as me, then began to follow him. I hit logmark, then stopped the bot.

EDIT: It is doing it really badly now. Had to stop quest bot completely, as im questing in a cave area, it constantly is locking on to unflagged horde players and following them everywhere. Luckily, I caught it shortly after it started doing this. Hope I didn't get ban. Using latest singular. Currently, this bug makes singular+questing *unusable*. Sorry :( Switched to TuanHAMonkPublicRelease. Using "Full AFK" defaults.
 
User0828 said:
Just caught my bot doing it. I hit logmark, then a couple seconds later, stopped the bot. Log level: diagnostic.

View attachment 122019

My bot saw a unflagged opposite faction player just doing the same quest as me, then began to follow him. I hit logmark, then stopped the bot.

EDIT: It is doing it really badly now. Had to stop quest bot completely, as im questing in a cave area, it constantly is locking on to unflagged horde players and following them everywhere. Luckily, I caught it shortly after it started doing this. Hope I didn't get ban. Using latest singular. Currently, this bug makes singular+questing *unusable*. Sorry :( Switched to TuanHAMonkPublicRelease. Using "Full AFK" defaults.
Click to expand...
Issue appears to be due to some component setting the enemy Death Knights Risen Ally as the current target:
Code: 
[01:07:33.150 N] (Singular) YourCurrentTarget: changed to: Marsh Lurker.4607 h=0.0%, maxh=6192, d=5.7 yds, box=4.1, trivial=False, player=N, attackable=Y, neutral=N, hostile=Y, entry=18136, faction=1706, loss=Y, facing=Y, blacklist=N, combat=N, flying=N, abovgrnd=N, IsBotPoi=Loot[01:07:33.181 N] Looting Marsh Lurker Guid:0xF13046D800504607
[01:07:33.181 V] Blacklisting F13046D800504607 for 00:15:00 [Type: Loot] - Reason : Looting done!
[01:07:33.181 V] Blacklisting F13046D800504607 for 00:00:02 [Type: Loot] - Reason: Done looting!
[01:07:33.182 D] ItemId: 0, IsCurrency: 0, IsCoinage: 1, Byte6: 0, Byte7: 0, TextureId: 0, Quantity: 580, Int10: 0, Int14: 0, Status: 5
[01:07:33.183 D] [Lua.Events] Detached from event LOOT_OPENED with handler 
[01:07:33.183 D] Clearing POI - Reason Finished looting
[01:07:33.760 D] Changed POI to: Type: Hotspot, Loc: <-1229.383, 5817.541, 2.606127>
[01:07:33.792 D] Activity: Moving to hotspot
[01:07:33.792 N] Moving to Type: Hotspot, Loc: <-1229.383, 5817.541, 2.606127>
[01:07:33.827 D] Changed POI to: Type: Kill, Name: Marsh Lurker
[01:07:33.855 N] (Singular) YourCurrentTarget: changed to: Risen Ally.4B18 h=100.0%, maxh=4799, d=80.8 yds, box=1.0, trivial=False, player=N, attackable=Y, neutral=N, [B]hostile=Y[/B], entry=26125, faction=2, loss=N, facing=N, blacklist=N, combat=N, flying=N, abovgrnd=N, TargetIndex=1
[01:07:33.856 D] Clearing POI - Reason POI is dead from Combat
The botbase then calls Singular's Pull Behavior and tells it to kill it. Singular detects that it is a player pet, so switches to the parent which in this case is a player.

I'll add detection of non-flagged player pet owners to close off that hole. Thanks for providing the diagnostic log for it, -Bobby53
 
bobby53 said:
Issue appears to be due to some component setting the enemy Death Knights Risen Ally as the current target:
Code: 
[01:07:33.150 N] (Singular) YourCurrentTarget: changed to: Marsh Lurker.4607 h=0.0%, maxh=6192, d=5.7 yds, box=4.1, trivial=False, player=N, attackable=Y, neutral=N, hostile=Y, entry=18136, faction=1706, loss=Y, facing=Y, blacklist=N, combat=N, flying=N, abovgrnd=N, IsBotPoi=Loot[01:07:33.181 N] Looting Marsh Lurker Guid:0xF13046D800504607
[01:07:33.181 V] Blacklisting F13046D800504607 for 00:15:00 [Type: Loot] - Reason : Looting done!
[01:07:33.181 V] Blacklisting F13046D800504607 for 00:00:02 [Type: Loot] - Reason: Done looting!
[01:07:33.182 D] ItemId: 0, IsCurrency: 0, IsCoinage: 1, Byte6: 0, Byte7: 0, TextureId: 0, Quantity: 580, Int10: 0, Int14: 0, Status: 5
[01:07:33.183 D] [Lua.Events] Detached from event LOOT_OPENED with handler 
[01:07:33.183 D] Clearing POI - Reason Finished looting
[01:07:33.760 D] Changed POI to: Type: Hotspot, Loc: <-1229.383, 5817.541, 2.606127>
[01:07:33.792 D] Activity: Moving to hotspot
[01:07:33.792 N] Moving to Type: Hotspot, Loc: <-1229.383, 5817.541, 2.606127>
[01:07:33.827 D] Changed POI to: Type: Kill, Name: Marsh Lurker
[01:07:33.855 N] (Singular) YourCurrentTarget: changed to: Risen Ally.4B18 h=100.0%, maxh=4799, d=80.8 yds, box=1.0, trivial=False, player=N, attackable=Y, neutral=N, [B]hostile=Y[/B], entry=26125, faction=2, loss=N, facing=N, blacklist=N, combat=N, flying=N, abovgrnd=N, TargetIndex=1
[01:07:33.856 D] Clearing POI - Reason POI is dead from Combat
The botbase then calls Singular's Pull Behavior and tells it to kill it. Singular detects that it is a player pet, so switches to the parent which in this case is a player.

I'll add detection of non-flagged player pet owners to close off that hole. Thanks for providing the diagnostic log for it, -Bobby53
Click to expand...

Thanks bobby. You think it may be the case for *any* classes instant summon pet? Such as a hunters "dire beast" spell, or the warlocks talent "grimoire of service" or druid talent "force of nature" . etc etc

Perhaps something worth looking into? Or maybe something that will have to wait for another specific log report. Either way, thanks for the help. Will be waiting on next release of singular. :)
 
The bug I posted appears to be indeed some kind of bot issue, and not a CR issue. The exact same issue happens with TuanHAMonkPublicRelease CR.

Caught bot following a horde frost mage elemental in shattrath city. New HB bug? Perhaps you should tell the HB dev team?
 
Bobby,

I can always count on you for a straight up answer so here's a question, Is there and issue within HB causing cr's to not self heal and otherwise not gauge people being in need of heals? I watch my toon get to very low levels and just stand there until someone else heals me. I notice this mostly in raid nor Dungeonbuddy, even using lazyraider.
 
Ruinit said:
Bobby,

I can always count on you for a straight up answer so here's a question, Is there and issue within HB causing cr's to not self heal and otherwise not gauge people being in need of heals? I watch my toon get to very low levels and just stand there until someone else heals me. I notice this mostly in raid nor Dungeonbuddy, even using lazyraider.
Click to expand...
Ruinit, Thanks for the post. As for a general issue, I am not aware of one. A couple quick points:

- Singular (and many raiding aware combat routines) will in general not self-heal during Combat while in a Raid. Their focus is DPS and being in a raid means trusting if a heal is needed that the healer will take care of it, as casting weak self-heals instead of attack abilities will lower DPS ***

- Singular will self-heal out of combat in its Rest behavior

- Some botbases do not call the Rest behavior, which means no Non-Combat behaviors will be run (self-healing, eating, drinking, rezzing, etc.) The main one I know of is RaidBot. LazyRaider will skip also if you check the act-like RaidBot setting.

Happy to look at a specific occurrence, just be sure to follow the steps in Reporting Bugs posts so the log contains everything needed to research for you. -Bobby53
 
bobby53 said:
Ruinit, Thanks for the post. As for a general issue, I am not aware of one. A couple quick points:

- Singular (and many raiding aware combat routines) will in general not self-heal during Combat while in a Raid. Their focus is DPS and being in a raid means trusting if a heal is needed that the healer will take care of it, as casting weak self-heals instead of attack abilities will lower DPS ***

- Singular will self-heal out of combat in its Rest behavior

- Some botbases do not call the Rest behavior, which means no Non-Combat behaviors will be run (self-healing, eating, drinking, rezzing, etc.) The main one I know of is RaidBot. LazyRaider will skip also if you check the act-like RaidBot setting.

Happy to look at a specific occurrence, just be sure to follow the steps in Reporting Bugs posts so the log contains everything needed to research for you. -Bobby53
Click to expand...

Thank you Bobby as always :) I am not talking about dps class I guess I should have mentioned I am talking healer class. I am running things such as dungeonbuddy as heals and it tends to heal others but not myself if that makes sense?
 
Hey bobby, leveling a warrior now and there seems to be some issue with the bot targeting enemy faction players.

Code: 
[Singular] invalid attack unit Enemy.Warlock.4041:Pet.32C6 has a Player as Parent
[Singular] Current target owned by a player.  Switching to Enemy.Warlock.4041! 
[Singular] Casting Battle Shout on Enemy.Warlock.4041 @ 100.0% at 37.8 yds
[Singular] invalid attack unit Enemy.Warlock.4041:Pet.32C6 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.Warlock.4041!
[Singular] invalid attack unit Enemy.Warlock.4041:Pet.32C6 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.Warlock.4041!
[Singular] invalid attack unit Enemy.Warlock.4041:Pet.32C6 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.Warlock.4041!
[Singular] Casting Shield Slam on Enemy.Warlock.4041 @ 100.0% at 5.0 yds 
Moving to Type: QuestTurnIn
[Singular] invalid attack unit Enemy.Warlock.4041:Pet.32C6 has a Player as Parent
[Singular] Current target owned by a player.  Switching to Enemy.Warlock.4041! 
[Singular] invalid attack unit Enemy.Warlock.4041:Pet.32C6 has a Player as Parent
[Singular] Current target owned by a player.  Switching to Enemy.Warlock.4041! 
[Singular] invalid attack unit Enemy.Warlock.4041:Pet.32C6 has a Player as Parent
[Singular] Current target owned by a player.  Switching to Enemy.Warlock.4041! 
[Singular] invalid attack unit Enemy.Warlock.4041:Pet.32C6 has a Player as Parent
[Singular] Current target owned by a player.  Switching to Enemy.Warlock.4041! 
[Singular] invalid attack unit Enemy.Warlock.4041:Pet.32C6 has a Player as Parent
[Singular] Current target owned by a player.  Switching to Enemy.Warlock.4041! 
Honorbuddy: Paused
[Singular] invalid attack unit Enemy.Warlock.4041:Pet.32C6 has a Player as Parent
[Singular] Current target owned by a player.  Switching to Enemy.Warlock.4041!

It looks very bad when it switches between the player and the pet so rapidly and follows the other player around. It seems to have been doing this since I started leveling this warrior.

It also seems to only be happening when the player has a pet.

Code: 
Moving to Type: QuestTurnIn
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301! 
[Singular] Casting Shield Slam on Enemy.DeathKnight.3301 @ 100.0% at 2.2 yds
Moving to Type: QuestTurnIn
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301!
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301!
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301!
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301!
[Singular] Casting Shield Slam on Enemy.DeathKnight.3301 @ 100.0% at 4.6 yds 
Moving to Type: QuestTurnIn
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301! 
[Singular] Casting Shield Slam on Enemy.DeathKnight.3301 @ 100.0% at 2.0 yds
Moving to Type: QuestTurnIn
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301!
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301!
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301!
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301!
[Singular] Casting Shield Slam on Enemy.DeathKnight.3301 @ 100.0% at 4.7 yds 
Moving to Type: QuestTurnIn
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301! 
[Singular] Casting Shield Slam on Enemy.DeathKnight.3301 @ 100.0% at 2.2 yds
Moving to Type: QuestTurnIn
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent 
[Singular] Current target invalid. Switching to TargetList mob Enemy.DeathKnight.3301:Pet.3322!
Moving to Type: QuestTurnIn
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301!
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301!
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301!
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301!
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301!
[Singular] invalid attack unit Enemy.DeathKnight.3301:Pet.3322 has a Player as Parent 
[Singular] Current target owned by a player.  Switching to Enemy.DeathKnight.3301!
 
I'm running into this so much that I've had to (at least temporarily) switch to other CCs. It's suspicious enough when your guy ends up stalking them around trying to kill them till you notice, but it's even worse when it flags you for PVP.
 
Evocation

Further to the post i made earlier regarding Singular casting Evocation 3 times and might sometimes get stuck in an evocation loop. i tried to logmark my file.
 

Attachments

confession said:
I'm running into this so much that I've had to (at least temporarily) switch to other CCs. It's suspicious enough when your guy ends up stalking them around trying to kill them till you notice, but it's even worse when it flags you for PVP.
Click to expand...
confession, Thanks for taking the time to post. For any issue you would like me to research you'll want to follow the steps in Reporting Bugs [click here]. -Bobby53
 
You must log in or register to reply here.
Back
Top