the shadow fix works great ! thank you so much bobby i upload you a zip text there so alot for errors, its spamm my log over 20 mb i use Tyarel bot base updated today*
should to use framelock in singular while honorbuddy's framelock are enable? There are framelock in dungeonbuddy,honorbuddy and singular. so...to have the best possible speed of overall software what framelock's should be enable?
If you have HonorBuddy's Use Framelock setting enabled, none of the settings in other components matter because they will already be running in HonorBuddys application wide framelock. -Bobby53
Clearcut, Thanks for the post. Unfortunately I don't add options without a detailed explanation of the circumstance as to why it would be needed. Please advise when you don't want a Monk to use Roll. Please also expect me to spend as much time researching it and considering for addition as you invest into your post. -Bobby53
Okay Bobby, ill try and explain why i would like the option to disable it. Using dungeonbuddy everything works perfect for me except that sometimes the roll will shoot past a mob running towards you. In certain instances this can cause you to accidently pull more than intended and it sometimes get used too close to edges (Gnomeragan for example, just as you enter i have witness it roll too far and fall off the ledge, also in Deadmines, where the bridge area is, it has rolled into the water accidently)
Clearcut, Thanks for the clarification. Adding an option to allow disabling in next release. -Bobby53
*new* Singular 3.0.0.3173 available for download! Change History for this release appears below. Complete Change History as always is included in the .ZIP See the Reporting Bugs [CLICK HERE] post for details on how to request assistance, post about a problem, or ask questions about the behavior of your botting session with Singular. Still receiving too many bug/question posts regarding behavior users watched that don't contain a complete log file and point of reference to when a single event happened. So, no multi-color bright lights this time. Just a simple request to provide the detail. Don't forget to use the LOGMARK! button. It is located on the Class Config window and will place a mark in the log file making it easy for you to indicate when something happened that you have a question about or problem with. This button provides the same behavior as the LOGMARK plugin. Having a problem while running Singular that you want to report? Click the LOGMARK button immediately when you notice. A line will be added to the log file at that time and now you have a very accurate way to let me know when the problem occurred. Ok, now that's out of the way: - Download the latest version of Singular.ZIP from Post #1 in this thread - .ZIP in Singular thread will always be the current version - HonorBuddy will contain an older version until a new release of HB posts Any post must include a debug log file (a file created with Debug Logging set to true.) To do this, click Class Config and set the Debug Logging option to 'true' then run until you create the issue again. The resulting log file will contain more info than a standard log file which will be essential in understanding the decisions being made by Singular which you weren't expecting. As always, the prior version is still available for download. If you encounter a problem due to the new release of Singular you can always downgrade as needed. --- Release 3.0.0.3173 --- General fixed - infrequent bug where Combat behavior would still run if no current target established. fixed - Pending Spell on Cursor detection Monk *new* - All Specs - support for Class Specific setting Disable Roll (defaults to false) Priest change- Discipline - will Pull with Smite if no aggro yet. Should slightly reduce damage taken and rate of kill from point of combat fixed - Shadow - null reference exceptions occurring during Solo combat in some cases Rogue fixed - All Specs - Pick Lock bug (issue due to Pending Spell on Cursor issue mentioned above) change- Assassination - if not Dual Wielding daggers will emit message regarding user error then cast Sinister Strike Warlock change- Affliction - slight reordering of dot logic for efficiency Worth mentioning one more time due to the large number of posts without log files that are received, but you must attach a complete debug log with any post. Please see the link at the top of this post for details.
bobby, excuse me, where can I look the priority spell rotation for warrior, I mean noxxic elitejerks and icyveins , each web has a lot of rotations so how I know which of these its using my warrior? I Have default noxxic, but want too know the exact rotation of each 3, maybe for PvP it found better another priority . Thanks
I am running WW Monk, and it seems that whenever it uses flying serpent kick, it likes to go to the mob its going to attack and then back to where it started, very rarely does it actually reuse the skill and land at the mob
Stron, Welcome to HonorBuddy! Thanks for taking the time to post and provide logs, but the post doesn't describe an error. Please read the Reporting Bugs [CLICK HERE] post which will walk you through how to author a post regarding a question / bug you are encountering and I will gladly research for you. Thanks for the post and good luck with your Warrior, Bobby53
You would need to be able to read and understand C#. It is contained within the Singular source files for Warriors. -Bobby53
dlowis, Thanks for taking the time to post. Please read the Reporting Bugs [CLICK HERE] post which will walk you through how to author a post regarding a question / bug you are encountering and I will gladly research for you. Thanks for the post and good luck with your Monk, Bobby53
Having an issue where my rogue will have problems deciding what target to attack (?) It keeps running back and forth between what seems to be either two mobs, or one mob and a hotspot. It happens when mounted and when not mounted. This looks EXTREMELY bottish and needs to be fixed asap. This has been happening since lvl 1 through to my current level 53. Little preview for ya. Code: [03:57:48.769 N] (Singular) MoveToLoss: moving to LoSS of Moonbrook Thug.267F @ 24.1 yds [03:57:48.812 N] (Singular) MoveToLoss: moving to LoSS of Moonbrook Thug.267F @ 24.2 yds [03:57:48.856 N] (Singular) MoveToLoss: moving to LoSS of Moonbrook Thug.267F @ 24.3 yds [03:57:49.220 N] (Singular) MoveToLoss: moving to LoSS of Moonbrook Thug.267F @ 23.5 yds [03:57:49.265 N] (Singular) MoveToLoss: moving to LoSS of Moonbrook Thug.267F @ 23.4 yds [03:57:49.310 N] (Singular) MoveToLoss: moving to LoSS of Moonbrook Thug.267F @ 23.5 yds [03:57:49.353 N] (Singular) MoveToLoss: moving to LoSS of Moonbrook Thug.267F @ 23.8 yds [03:57:49.399 N] (Singular) MoveToLoss: moving to LoSS of Moonbrook Thug.267F @ 24.0 yds [03:57:49.443 N] (Singular) MoveToLoss: moving to LoSS of Moonbrook Thug.267F @ 24.2 yds [03:57:49.489 N] (Singular) MoveToLoss: moving to LoSS of Moonbrook Thug.267F @ 24.3 yds [03:57:49.857 N] (Singular) MoveToLoss: moving to LoSS of Moonbrook Thug.267F @ 23.5 yds [03:57:49.903 N] (Singular) MoveToLoss: moving to LoSS of Moonbrook Thug.267F @ 23.3 yds [03:57:49.948 N] (Singular) MoveToLoss: moving to LoSS of Moonbrook Thug.267F @ 23.5 yds [03:57:49.994 N] (Singular) MoveToLoss: moving to LoSS of Moonbrook Thug.267F @ 23.8 yds [03:57:50.040 N] (Singular) MoveToLoss: moving to LoSS of Moonbrook Thug.267F @ 24.0 yds The issue occurs several places, but is easily found at the end of this log.
Thanks for taking the time to post and providing a log file. Although the behavior described may have been occurring while this message was emitted, unfortunately that message does not serve as a good indication of the issue. The message "(Singular) MoveToLoss: moving to LoSS of ..." will be spammed when debugging output is enabled and any Singular character (not just rogues) is moving towards its target to get into Line of Spell Sight on them. If back and forth movement occurred within the 1.8 seconds represented above, the issue is due to another component performing movement functions at a point it should not and failing to log them -or- the HonorBuddy navigator generating two completely different paths to the same spot in subsequent calls. If it was Singular I would expect to see the target of the MoveToLoSS change in that span, but it remained consistent. Please read the Reporting Bugs [CLICK HERE] post which describes the information needed in a post for me to research the issue further. Thanks for the post and good luck with your Rogue, Bobby53
Hello Bobby, looks like got the same with my Rogue right now. Log start: [09:08:01.601 D] Changed POI to: Type: Kill, Name: Dalaran Worker till the End of the Logfile. Toon stuck in open Field, ok its a HB Issue, but all the attempts to get to the Mob to kill.
Log starts at: [13:13:44.776 D] Goal: Picking Up Quest - To Forsaken Forward Command : QuestID - 27290 : To - Lady Sylvanas Windrunner : ID - 44365 Toon Pickup a Quest and is on a Flightmount/Vehicle? Dont know something for the Quest. But Singular trys always to summon the Hunter Pet.