My singular is not working he is just auto shooting anyone know why please help. Tried fresh install and older version of singular and nothing. Attached a bunch of logs
Was able to see my poor drood being attacked by evil rogue while im just running and getting new targets. Start investigating around line 17600. View attachment 7252 2015-01-05 04.40 - Copy.txt The target switch to rogue only happens after i manually target him and cast a spell. I stopped bot as he wouldnt stop moving/attacking the npc mob. This one should be easy to reproduce as well, seen it happen a lot and singular always notices if you cast spell manually on enemy target. It makes it very easy to spot bots while leveling.
I want my character to farm instances normally (without prowl) but when he goes out to refresh it, he should use prowl so nobody can gank him
Singular or paid CR not working There was a guy that has the exact same problem as me. I'm the fool to actually go and fresh install Windows 7 because I've seen this problem about a yr ago, it fixed it that time. A couple months ago I was running Dx11, same thing happened, went to Dx9 and everything was ok up until yesterday (randomly). The authors also had (cokx toizi) released an update yesterday....not sure if that had anything to do with it. " " This guy had the exact same problem, although in this case Warrior. I've done all the same things he was instructed to (typing console message etc),I thought I'd save my self the trouble of the authors sending me here and post a log ahead of time. I've tried singular, doesnt work with enyo etc Fury Unleashed premium actually does work fine Glad suite does not work with enyo etc I did a fresh install of windows 7 today, tried everything, lmk wtf is going on please. First attachment - using singular Second - using glad suite
Hi. Thanks for such a great CR. I was modifying the CR a bit and noticed there appears to be a bug in the TalentManager.cs file in the IsSelected method. Here is the method (there is a 5 where I believe there should be a 6). When calling this method, it always appears that the last talent in the tree is not selected. public static bool IsSelected(int index) { // return Talents.FirstOrDefault(t => t.Index == index).Selected; int tier = (index-1) / 3; if (tier.Between(0, 5)) return TalentId[tier] == index; return false; }
Hi there I was told to report this here: I read that when you put mobs in the "avoid mobs" part, your character will ignore them and only attack them when they attack you. However, with the questing bot base, the character lets those mobs kill you slowly and doesn't attack back. He just continues to the next hot spot and skips looting as well. Is this normal behaviour? I initiate Cursed Harbinger while there is an Onyx ravager attacking me (which is blacklisted). I never attack the mob back and I either die or the mob loses aggro. The log doesn't seem to show this though. http://pastebin.com/raw.php?i=QietdzrF Full log 4136 2015-01-05 15.16.txt Switching Combat Routines fixed the issue.
Unfortunately, blacklisting mobs has always been an issue and a reason to die when botting unattended. It's an easy give away that you are a bot. Any human player would turn around and kill the mob. I notice this almost every day. Last night I was chased around by a mob and the char did not bother with it at all. It just pulled others, killed them, tried to loot while being banged on the head. In general; this is an issue that has been around since 2010 or even earlier. Sometimes HB just does not realize you're in combat. I do not know why, how, or what to do about it because the logs do not show this at all. It's a problem nonetheless. Two days ago it tried to pull a mob LOS, so blacklisted it for a while. Then it ran forward TOWARDS that mob, but because it is blacklisted, the mob started banging in my head and I cheerfully ran on and on.... awful. Blacklisting because a mob is EVADING is fine ofcourse, but because of LOS or just not noticing you are in combat is a real issue sometimes.
*new* Singular v4.0.0.4167 available for download! Download from Post #1 of this thread. Contains a fix for melee toon heal/buffing which has been a long standing issue preventing adequate use of offensive / defensive cooldowns for Melee characters. Numerous other fixes as well (see change history.) Change Log v4.0.0.4167 Code: --- Release 4.0.0.4167 --- General fixed - Melee Toons - opportunities for defensive cool-downs and buffs implemented in Heal or CombatBuff behaviours were being missed (for example, Arms warriors were not seeing Die by the Sword cast as promptly / often as it should) *new* - Capability Flags - support for disabling functionality/abilities based upon capability flags enhanced, including ability for Questing to disable Pull More for specific encounters requiring that fixed - Auto-Attack - now enabled for all characters if the Questing profile disallows Special Attacks. Requires melee range fixed - Refreshment - will now correctly wait for combined food/drink items which yield a Refreshment buff instead of 'Food' or 'Drink' fixed - Cast on Ground abilities - issues affecting Priest and other classes corrected fixed - Talents and Spec recognition - fixed issue which was causing some odd log output and at times not correctly indicating type of character change- Lag in World PVP - reduced the amount of Combat Log information processed which should resolve this for most users Druid *new* - Balance - support for Glyph of the Flapping Owl when falling Hunter *new* - All Specs - added support for Freezing Trap when mob is more than 15 yds away and Pet dies Mage change- All Specs - revised priority of crowd control / snare effects used prior to Blink. Will allow Blink to proceed only if mob slowed to at least 50% Monk *new* - Windwalker - added setting and support for Tigereye Brew Priest fixed - Holy - Flash Heal: was incorrectly referencing the Disc Flash Heal settings so changes made to settings appeared to have no effect. Rogue fixed - Assassination - exception occurring when in Combat and no Current Target Shaman change - Elemental - AOE: changed to cast Chain Lightning to buff Improved Chain Lightning at highest priority when learned Warlock change - Destruction - revision to priority to only cast Conflagarate if >= 2 charges Warrior fixed - All Specs - check range to target before casting Whirlwind since spell info does not include a maximum distance fixed - All Specs - check range to target before casting Dragon Roar since spell info does not include a maximum distance *new* - Glyph of Victorious Throw now recognized *new* - Glyph of Death from Above now recognized *new* - All Specs - support for Spell Reflect change- Arms/Fury - Heroic Leap: now more intelligent and will allow jumping further (to edge of ranged mobs hitbox rather than their location.)
Soeski, If there is an issue I'll need the detail logs for a specific case. Simply using the term Blacklisting is a bit too vague and misleading, since there is a tremendous difference in functionallity when a mob is blacklisted for Pull versus Combat versus Loot versus Node as well as numerous other details for the encounter. For example, a Rogue with Pick Pocket enabled will blacklist the mob with a type of Node (name artificat from harvesting implementations.) This has no impact upon any subsequnet Pull or Combat with that mob. Likewise blacklisting a mob for Pull because the toon does not find a navigatable path to the Pull Target within a reasonable time is an absolutely requirement regardless of whether it is evading. Blacklist for Pull does not prevent subsequently engaging in combat if you end up body pulling or chain aggroing the mob, it simply means that HonorBuddy will no longer include it as a Pull target. So way too many details needed to understand a specific case where it appears something was incorrectly blacklisted to simply discuss in general. For example, the description of ignoring a mob that is banging you on the head could have in fact been ignored because the BotBase or Profile disabled the Combat Routine while trying to move to do a turn-in, vendor run, etc. I would gladly look into the specifics of any case you upload a log file for and identify a specific occurrence. Thanks again and good luck with your Singular toon, Bobby53
ectocooler, Thanks for the post and logs. In subsequent posts if you could add a LOGMARK at the point an issue occurs I can focus on that occurrence and research the root cause and any remedies needed. I researched the first occurrence I found in the 8144...txt log provided and the issue appears to be due to the Questing botbase completing an objective for the quest Horses for Duskhaven - Quest - World of Warcraft where the character was in a vehicle. It is the BotBases responsibility (in this case via control offered by the Questing profile) to either not call the Combat Routine or to disable it. In this case, the issue is due to that step not being specified in the profile and is not a Singular issue. I saw other occurrences of the stance spam in the 7580 file however that did not seem related to this root cause. This appears to be specific to Protection Warriors specifically due to the logic for that spec detecting that a shield is not equipped and switching to Battle Stance. Thanks for the post w/ logs and good luck with your Warrior, Bobby53
It is already supported in recognizing it as a Group Buff, but having the Hunter cast it was not implemented. Look for it in the next release. There will be a setting for Hunter Pet Buffs or something similar which will default to false, so you will have to enable it to test. -Bobby53
paperc07, Was fresh install to a new folder? Be sure you are not installing over any remnants (including settings.) The only logs which indicated an error seemed to imply a possible issue in being unable to determine if Z position, so potentially an issue with the meshes. Be sure those are deleted (they aren't stored in your HB folder unless you reconfigured that way.) Thanks for the post and good luck with your toons, Bobby53
Xom, The description sounds like you have some corruption in one of your Settings files. Create an empty folder and install a fresh copy of HB to that destination (rather than installing on top of or upgrading an existing installation) and it should work. Give that a roll and let me know your results, -Bobby53
Support I am having problems with Claws of Shirvallah on Me @ 94.1% it will not cast or the bot is casting the wrong spell labeled Claws of Shirvallah View attachment 328 2015-01-07 08.50.txt
airwolf1, Thanks for the post with log file. A couple clarifications: - 'Avoid Mobs' - these are profile commands which instruct the Questing botbase to avoid those mobs, not the Combat Routine. The Combat Routine is basically a slave and does what it is told, so if it is told to attack a mob it is supposed to carry that action out. You'll want to post regarding any Avoid Mob issues in the HonorBuddy Support or the questing profile authors thread - Onyx Ravager is blacklisted - any blacklist that occurs will be recorded in the log file. Here is a filter of all the blacklist actions taken in this session, the type of the blacklist they were added to (there are multiple ones for different purposes), and the reason the mob was blacklisted: Code: [14:59:24.418 V] Blacklisting 1C396894E051B9C000001A00002AA637 for 00:15:00 [Type: Loot] - Reason: Looting done![14:59:47.912 V] Blacklisting 1C396894E051D38000001A00002AA6C9 for 00:15:00 [Type: Loot] - Reason: Looting done! [14:59:47.912 V] Blacklisting 1C396894E051D6C000001A00002AA6C9 for 00:00:02 [Type: Loot] - Reason: AoE looted! [15:00:07.263 V] Blacklisting 1C396894E051D6C000001A00002AA6AB for 00:15:00 [Type: Loot] - Reason: Looting done! [15:00:24.132 V] Blacklisting 1C396894E051D58000001A00002AA669 for 00:15:00 [Type: Loot] - Reason: Looting done! [15:00:50.516 V] Blacklisting 1C396894E0569EC000001A00002AA6CA for 00:15:00 [Type: Loot] - Reason: Looting done! [15:01:09.073 V] Blacklisting 1C396894E051D58000001A00002AA722 for 00:15:00 [Type: Loot] - Reason: Looting done! [15:01:09.073 V] Blacklisting 1C396894E051D38000001A00002AA6B7 for 00:00:02 [Type: Loot] - Reason: AoE looted! [15:01:28.359 V] Blacklisting 1C396894E051D90000001A00002AA2A5 for 00:15:00 [Type: Loot] - Reason: Looting done! [15:01:41.441 V] Blacklisting 1C396894E051D90000001A00002AA415 for 00:15:00 [Type: Loot] - Reason: Looting done! [15:02:15.868 V] Blacklisting 1C396894E051D70000001A00002AA74D for 00:15:00 [Type: Loot] - Reason: Looting done! [15:03:28.210 V] Blacklisting 1C396894E053BD8000001A00002AA7B4 for 00:15:00 [Type: Loot] - Reason: Looting done! [15:03:28.210 V] Blacklisting 1C396894E053BE0000001A00002AA506 for 00:00:02 [Type: Loot] - Reason: AoE looted! [15:03:51.287 V] Blacklisting 1C396894E053BE0000001A00002AA472 for 00:15:00 [Type: Loot] - Reason: Looting done! [15:03:51.287 V] Blacklisting 1C396894E053BD8000001A00002AA7CE for 00:00:02 [Type: Loot] - Reason: AoE looted! [15:04:13.427 V] Blacklisting 1C396894E053BE0000001A00002AA7BB for 00:15:00 [Type: Loot] - Reason: Looting done! [15:04:23.786 V] Blacklisting 1C396894E053BE0000001A00002AA799 for 00:15:00 [Type: Loot] - Reason: Looting done! [15:04:43.485 V] Blacklisting 1C396894E053BE0000001A00002AA60D for 00:15:00 [Type: Loot] - Reason: Looting done! [15:04:43.485 V] Blacklisting 1C396894E053BE0000001A0000AAA60D for 00:00:02 [Type: Loot] - Reason: AoE looted! [15:04:57.959 V] Blacklisting 1C396894E053BD8000001A00002AA817 for 00:15:00 [Type: Loot] - Reason: Looting done! [15:05:30.004 V] Blacklisting 1C396894E053BD8000001A00002AA592 for 00:15:00 [Type: Loot] - Reason: Looting done! [15:05:30.004 V] Blacklisting 1C396894E053BE0000001A00002AA592 for 00:00:02 [Type: Loot] - Reason: AoE looted! [15:05:30.004 V] Blacklisting 1C396894E053BD8000001A00002AA592 for 00:15:00 [Type: Loot] - Reason: Looting done! [15:05:30.004 V] Blacklisting 1C396894E053BE0000001A00002AA592 for 00:00:02 [Type: Loot] - Reason: AoE looted! All actions above were initiated by the Questing BotBase (in other words nothing in this session was blacklisted by Singular). Very important to note, there are multiple types of blacklists. In this case, all in this session were blacklistType: Loot, which means HonorBuddy will not attempt to loot that mob again -- this has no impact or bearing upon combat with a mob, even if that type of blacklist set before or during combat. Based on what is present in the log file the symptoms you observed were due to something else. I will look into this further running a Balance Druid near same level and same settings and see what I encounter, but if you bump into this again upload the log and I'll be happy to look at it. Thanks for the post and log file and good luck with your Singular toon, -Bobby53
Fd2me, Thanks for the post. Support for T7 talents in Singular is still being added, and Claws is not implemented yet. Look for it in an upcoming release, -Bobby53
Thank you for your extensive answer. I've investigated the issue more and I'm confident that the issue indeed doesn't lie with Singular. Good luck!
