Hi, EmersonBigTips, and welcome aboard. This article should answer your question: HelpDesk: Updating Singular between Honorbuddy drops cheers, chinajade
Tumbum, Have mentioned this in past posts, but Singular does not take an action like setting the CurrentTarget or the BotPOI without output of a log message. In this case, it would be one of the following two messages: [Singular] Switching to ganker: ..... [Singular] Pull More wants to aggro ..... These do not appear in your log so it is not Singular going out of its way to choose Lucky as a target. The key messages in your log are: The 'YourCurrentTarget' message is an informational message output by Singular notifying you that "something" changed the target. It does not indicate that the target change was done by Singular, only that it recognized somebody changed it. That message is output even if the user interferes with bot operation and manually changes the target. The <<< PULL >>> message indicates that Singular's Pull Behavior was called. As you know from past posts, a Combat Routine doesn't decide when to pull. The BotBase decides this and then tells the Combat Routine to perform that action by calling its Pull Behavior. This message indicates that the BotBase told Singular to Pull Lucky. So which component is responsible? You and the profile author will most likely need to work that out from the other components involved. I can only say it wasn't Singular at this point. Profile is responsible - if it is setting the opposing faction as a valid kill target Plugin is responsible - if it set Lucky as the current valid target or specifically as the BotPoi HBCore is responsible - if none of the above were the cause As for the plugins, I can see you had the following plugins active which based on my prior usage were not responsible: Anti Drown, Refreshment Detection, Tidy Bags 3.6 Reloaded. That still leaves CavaPlugin, LogMeOut!, or MIR2. I don't use those so you will either want to review or check with the respective authors if they do any of the following actions: - include enemy players in the TargetList - set the Current Target (at any time) - set the Current BotPoi (at any time) Any of those three actions could lead to what occurred for you. The log seems to indicate that it Lucky was either just the last target included in the target list -or- it was specifically targeted. Also, this could occur if the targeting were done manually. I don't need to know as there is nothing left on this for me to research, but if you manually clicked on the enemy player to inspect their gear, to target for an emote like /wave, etc. it is possible that initiated this sequence causing them to be included in the target list and then selected as a pull target. That really depends upon whether any of the other components are blindly including "Me.CurrentTarget" in the IncludeTargets filter. Just to reiterate, Singular does not decide when to Pull or choose the Pull target and there is nothing in the log indicating that Singular targeted Lucky. Singular appears to be the only component involved at that point in your log which identifies itself and its role in attacking that player (by writing log statements regarding its actions and decisions that begin with the texts [Singular]). I can confirm that you can rule out Singular as the cause on this one, but unfortunately won't be able to be of further assistance. Hope the additional detail is of use in running this one down, -Bobby53
frost mage does evocation with invocation talent twice in a row pre-pull. i log marked 3 times when he did it. View attachment 3868 2014-09-05 08.48.txt edit: look at log mark's 2, 3 and 4.
Bobby53 - I just had the chance to test pull more feature, and I want to compliment you on your work. It's absolutely amazing, and you really have pulled Singular to the next level!! Thank you
yes, i just changed that talent, it seems its not waiting long enough for the evocation spell to end in order to check to see if the buff is active, it recasts before the previous cast is over
I don't know if it's a bug, but my shield wall and spell reflect are not triggering in BG's (I have set it to 35) but no option for spell reflect, but mass spell reflect works just fine :S
Frost mage ends up spamming ice lance till the mob is dead after pet freeze without any procs up. It also never uses aoe.
There is a Problem with the Rogue CC since the last 2-3 Releases. Sometimes after: Code: Clearing POI - Reason POI is dead from combat the Bot need between 20-40 Seconds befor the Bot continues: View attachment 10316 2014-09-07 13.48.txt Code: [13:26:59.173 D] Clearing POI - Reason POI is dead from combat [13:27:26.623 D] Garbage collected 1 nav tiles Code: [13:22:12.435 D] Clearing POI - Reason POI is dead from combat [13:22:45.638 D] Garbage collected 1 nav tiles Code: [13:21:04.275 D] Clearing POI - Reason POI is dead from combat [13:21:44.825 D] Garbage collected 1 nav tiles Code: [13:19:16.208 D] Clearing POI - Reason POI is dead from combat [13:19:35.840 N] (Singular) YourCurrentTarget: changed to: Slingtail Stickypaw.544D h=0.0%, maxh=158079, d=2.1 yds, box=1.7, boss=N, trivial=N, player=N, attackable=Y, neutral=N, hostile=Y, entry=55110, faction=2559, loss=Y, facing=Y, blacklist=N, combat=N, flying=N, abovgrnd=N, tagme=Y, tagother=N, tapall=N This only happend at the Rogue CC, all other CCs works fine.
I love it how bad singular is for boomies.... When a mob is targeted it will shift into kitty form, run to range, shift out of kitty form for a second to non shifted, shift into boomkin form then moonfire and wast time while the mob runs towards you.... rotation should be Starsurge (if up), Starfall (both surge and fall will hit at the same time), Moonfire, Starfire then work on getting into a eclipse if needed. Takes forever and then some to kill a mob thats 10 ish levels below me because the rotation sucks. View attachment 6728 2014-09-07 09.00.txt
Hello, I just have a quick issue, the bot is perfect most of the time in SOO, however, when it comes to the Paragon fight, and whenever Korven goes into amber, as a hunter it hugs the amber and almost looks like it is trying to melee the amber down. Anyone else have this issue?
Edsaxe, My apologies. I had read and responded to your earlier post, but I must have missed an error or clicking Post because I don't see it in the thread. It appears that a behavior was omitted in some prior refactoring done awhile ago. Look for it in the next release. -Bobby53
User0828, Thanks for the well delineated log file. Fixed in the next release. There may be multiple casts of it (hopefully not) but will now state its intention as to why it cast in the log so we can review settings and logic in a manner specific to the context you are using it in. Anyway, look for the new release shortly, Bobby53
Dramoru, Welcome to HonorBuddy! When posting regarding an issue or question with Singular, be sure to follow the steps in Reporting Singular Bugs (click here). That way I'll have all the details needed to answer your question with respect to your configuration and circumstances. Thanks for the post and good luck with your Warrior, Bobby53
Truulte, It should cast Ice Lance without procs up in very limited circumstances (mob about die, toon is moving and must cast instant, etc.) I am not certain in your case however as I have not seen that behavior before. I'll attempt to recreate and at a minimum add some additional logging to determine why it is being spam cast in that case (since it appears it should not.) Thanks for the post, -Bobby53
siuyuz, Thanks for the post. I will take a further look at this, but have been unable to duplicate it. Not sure if this is an unexpected behavior associated with a non-english client or not. -Bobby53
