23051602, See Bobby53's Standard Request for More Info [CLICK HERE]. Thanks for the post, but a log is created each time you run and is easy to attach. As mentioned in the posts, it is always required for any issue you would like me to research and is your way of indicating that the issue you wrote about is important to you. In this case, it would have detail on the use of kiting/avoidance and offer insight into where you mention a change in settings having no effect. Be sure to set Debug Logging to true and run for a bit, set a LogMark at a point where the kiting didn't work as expected and I'll definitely look into that. As for duplicating the issue, I attempt to in virtually all cases, however without the log I have no idea whether my efforts are even close to duplicating what occurred for you. For example, missing from this but present in a log file are the version of HonorBuddy, the version of Singular, the botbase in use, profile if any, your specialization, talents chosen, glyphs equipped, settings selected, etc. etc. etc. all of which have a bearing on decisions being made by Singular. Simply too many variables that can impact the decisions made by Singular to look into issues that don't provide a log. Thanks for the post and good luck with your Mage,Bobby53
Yo. Logic request: If it tries to mount, a mount, that requires a certain skill to ride, for example tailoring, cloud serpent riding skill, it would be awesome if bot could blacklist said mount instead of going into a loop where it tries to mount, cant, walks, tries to mount, walks and acts all out retarded (as per usual when i bother to post something) Thanks. View attachment 1388 2013-07-10 15.49.txt Edit: Looking at the logs somone probably just missed to implement cloud serpent riding skill as a prereq for serpent mounts. Code: [13:58:11.407 D] [Mount] Flying Carpet is known, but we don't have the skill to use it! [13:58:11.410 D] [Mount] Frosty Flying Carpet is known, but we don't have the skill to use it! [13:58:11.417 D] [Mount] Magnificent Flying Carpet is known, but we don't have the skill to use it! Cloud Serpent Riding - Spell - World of Warcraft Edit2. Ye, highly doubtful if its singular issue, some brilliant code logic for mounts i must say... On a fresh install, without doing any settings, it decided to configure a cloud serpent as mount setting. Whats even more brilliant is the fact they also made those settings override any other logic, thus creating the loop.
Yes, that's an HonorBuddy issue. The only mount management that Singular does is it will cast Ghost Wolf or Travel Form if the appropriate setting is true, the distance to travel is less than the configured Mount Distances, or the character cannot summon a mount (indoors, insufficient riding skill, etc.)
Hello Bobby, sorry that i jump in here. I have a question regarding the MountManager - maybe you can help me. I've looked into the code and have seen that you do stuff with the event fired when mounting is called (dont know the proper spelling). What i wonder is: My testing has shown, that this event will only be fired if the Distance to walk is higher then the Mountdistance. This would lead to the fact, that your MountManager does not use Travel Form. Am i wrong?
Actually saw another post in the archive that the frost mage does initial pull and after that nothing. Will search for log when I get back
handnavi, You are correct. The code you are referencing is an artifact from a copy paste of code written a good while back when MountManager was called without checking the distance (there was no Mount Distance setting in Settings at that point.) The only things that code does presently is preventing toon from mounting early in battlegrounds (to avoid the mount/buff/mount/buff/mount/buff/... behavior which used to occur) and stops movement if HB is going to mount. This latter addition was due to behavior that was in HB where it would try mounting too quickly after requesting to stop moving resulting in a failed mount cast, walking forward a few steps, another failed mount cast, walk a few more steps, and so on. The behavior which carries out the Mount Manager stuff I referenced is handled as last part of class specific Rest behaviors and is the same concept just invoked by a different HB mechanism to get around the Mount Distance issue you cited. -Bobby53 btw... No apology needed, jump in anytime. Greatly appreciate your contributions and am happy to offer any value I can. -Bobby53
Phelon, Thanks for the post. A lot to respond to, so will break it out for ease of reference... Stuck messages come from HonorBuddy, not Singular. Would be happy to look at a specific occurrence and see if it was something that was directly or indirectly due to Singular movement, but would need some context as in timestamp/logmark you are referring to. Every occurrence of Singular not attacking that I have encountered is due to the BotBase/Quest Behavior/Plugin not calling Singular. Set Debug Logging to true and you'll receive messages when significant time has elapsed without someone calling any Singular behaviors (including Rest.) If you get that message, it is an issue with the caller. If you don't, you should be getting invalid target messages of some sort. I haven't seen this. I checked the first several logs and they contain a lot of redundant compilation errors from another Combat Routine. This typically indicates a need to close everything, delete the HB\CompiledAssemblies folder, then restart your system. It appears that the HB loader gets borked at times after repeated errors or sometimes after source updates. Log files are great and I thank you very much not forcing me to ask for them. It appears you had encountered a lot of errors that jeopordized the state of HonorBuddy and resulted in some unexpected behavior. I am happy to look at even those, but need a time/logmark to focus on the point that something did or did not happen. Healers movement is specific to the class, so would need details on the specific occurrences you observed. A logmark or timestamp is a great indication that grounds your observations with what appears in the log. Additionally, Resto Druid, Holy Paladin, and Mistweaver Monk have not been rewritten yet so will function for the most part as they always have. Resto Druid is being rewritten and should be out in one of the next two releases. I appreciate the logs and will go through them again to check for Singular exceptions and other identifiable issues. I did see a number of HonorBuddy Targeting exceptions occurring during weighting which can result in an empty targetlist that will cause a stand still and do nothing behavior that appears as though the Combat Routine is not attacking. Thanks for the post, Bobby53
Toon doesnt dismount to kill Yellow Mobs. Just run behind them but doesnt fight Start at: 15:41:17.624 N]
View attachment 7824 2013-07-12 22.13.txt Hello, Singular is cauing some lag spikes to the game. Very often the game just freezes for a second. That is often enough to die. I have tested it on diferent toons and different botbases. It is always the same - spikes.
tumbum, Thank you for the Debug log! The Pull Behavior isn't being called, so basically Singular isn't being told to attack. If it were, you would see a log entry similar to this one earlier in your log: Code: [15:38:53.510 N] [Singular-DEBUG] <<< PULL >>> CurrentTarget now: Silkwing Larva.FC1E h=100.0%, maxh=8834, d=10.9 yds, box=1.9, player=N, hostile=N, faction=7, loss=Y, facing=Y, IsBotPoi=Kill, TargetIndex=1 My assumption is that the targetlist remained empty for some reason: Code: [15:41:14.156 N] [Singular] Bot TargetList is empty, no targets available That was an issue in HonorBuddy recently that was being fixed, but am not sure specifically which version it was/will be addressed in. -Bobby53
Stoyo, Thanks for the log file. However there isn't much I can do with it as there is no indication in the post or within the log file exactly when you observed that behavior. The easiest way to indicate when something occurs is to leave the Class Config settings window open and click the LogMark button when it happens. Thanks for the post and good luck with your toon, Bobby53
Firstly, let me express my thanks for this wonderful routine. I've never had a problem with Singular. I've recently began leveling up a rogue and noticed an issue with pick pocket. Sometimes, it will inch towards a mob, even when it is static. However, if it uses Sap first, it will move normally to the mob, pick pocket, then attack as it should. It's nothing important, but the result looks much less bottish. Thanks again for a fantastic cc.
Latest singular or perhaps even previous i cannot remember is working weird with rogue that blinds other people/npcs If it is in combat after blinding an npc or player it will just stand still and wait until the blind effect has ran out from the npc/player and wait for em to attack it before it starts to attack again or it will wait to get out of combat.
When using singular on an elemental shaman using quest bot and kick's leveling profiles the routine will constantly try to run to melee range of the target and stand behind the target, when the target turns around it tries to run behind again, cancelling any spell casting, and making the simplest mobs take very long to kill, the problem is mostly shown in the log starting at [04:15:41.898 N] View attachment 4404 2013-07-14 21.01.txt
not an issue, just an advice: i just noticed that mistweaver monks, while leveling (im17 right now) make damage with jab and blackout kick (the rotation is correct) while in serpent stance; if they did in tiger stance questing as a mistweaver would be much faster because it builds double the chi, doesn't spend mana on it and moves 10% faster (i think you should code so that he switches to serpent stance only to heal himself or party members)
Bobby -- If you already addressed my issue, my apologies for not seeing you address it. I'm still having issues with Singular and my DK. Anytime I load my DK in WoW and try to load HB and Singular, HB crashes. This only happens when I try to use Singular with my DK. I can use PureRotation and TuanHA's DK routine without any issues, but when Singular is chosen HB crashes. Here's the link to my issue, which is still occuring, so I can't run my DK with HB and Singular. Same issue, same log output, same error message. This is basically just a 'bump' on my post. I just tried again tonight after HB updated, but I'm not sure if Singular had an update to go with it. Link: Zeldrak's original post regarding DK problem
Jimgnarkill, Thanks for the log file! Unfortunately I cannot tell exactly what was occurring since the log was produced with the Debug Logging setting as false. Set to true if you encounter issue as this provide a great deal of diagnostic info needed to look into issues like the one you submitted. The one thing I did notice is: It appears that the questing profile has set the Pull Distance to 0 yds. Quest Profiles do this when they want a character to be move through an area without attacking any hostile mobs in the area. A little bit later, the InteractWith quest behavior sees a hostile mob within the aggro range and elects to kill it. However since the Pull Distance is still 0 yds, it moves to it even though at 19 yds it is within attack distance of all ranged classes. This is a quest profile or quest behavior issue and outside the control of the combat routine (in this case Singular.) A lot of work is currently being done on the questing system, so this is likely one of the things being looked at. For more details, you may want to post in the Questing Profile Authors thread or the HonorBuddy Support thread and link back to my response so it isn't thought to be a combat routine problem (which on the surface it may.) Thanks for the post and good luck with your questing, Bobby53
nwsh, Thanks for the post. A few quick points: 1. If you want to Quest fast as a Level 17 Monk, you should be rolling as a Windwalker. Specializations allow you to select a toon that is better at some things than others. A Mistweaver doesn't do as much damage, and group healing with a Windwalker won't keep you in a group long. Simply put, evaluating how fast a Mistweaver Monk quests should always result in the response "Why are you questing as a Mistweaver?" 2. The stance choice is gear dependent. A Mistweaver should be collecting and equipping +Intellect gear. As such, the best stance selection for DPS as a Mistweaver is Stance of the Wise Serpent since you receive attack power equal to 200% of your spell power plus a 50% haste bump. If for some reason you are running in gear that has no +Intellect (which you shouldn't if you are a Mistweaver) then Stance of the Fierce Tiger would be better since you would at least get the increased Chi generation and 10% movement buff. The current implementation for Mistweaver questing came from a bug report (user saying it was an issue that we were using Tiger stance) and after a lot of testing found that for 99% of the cases he was correct. My recommendations are to switch to Windwalker if you are concerned about questing speed, -or- equip as much +Intellect gear as possible if you are committed to questing as Mistweaver (which is valid if you are trying to use the Mixed bot for dungeons as well.) Thanks for the post and good luck with your Monk. If you have any further questions or suggestions based on your observations, even if it isn't a bug report please be sure to include a log file. -Bobby53
zeldrak, My apologies for not responding to this one sooner. As for the "Send Error Report" button, those are likely useful for the HonorBuddy Dev Team but I don't receive those. I don't see an exception indicated in the log file and in trying to duplicate I am able to load my Unholy DK with a variety of Bots without error. Please create a new HB installation that does not contain any plugins other than the default ones shipped with HB and try again. If you get the error, please check the "Ignore and try to continue" option on the error dialog and see if we can force it to add an exception or some form of error the log. Thanks for your post, Bobby53
I can do that, Bobby, but I'm not given the option to "Ignore and try to continue". Give me a bit and I'll try with a completely fresh install with nothing but the shipped HB files.
