*NEW* Singular 3.0.0.3142 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.3142 ---
General
fixed - Issue resulting in Null Reference exception when Tick()ing behaviors for a few classes
*new* - Added BehaviorFlags tracking to monitor changes to BehaviorFlags. Only works if Combat Routine is still being pulsed
change- Internal revisions to some aspects of casting logic. Should not result in any noticeable difference to user but improves re-entrancy of code
Death Knight
change- All Specs - default setting for Death Siphon % changed from 60 to 85
fixed - Blood - changed Blood Tap so treated as not invoking GCD
*new* - Blood - diagnostic output when Debug enabled
fixed - Blood - Instances: will no longer use Death Strike as first melee ability unless not at full health
fixed - Blood - Instances: several improvements to Blood priority. If you have issues with holding aggro, set Log Level to Diagnostic and post a log file.
fixed - Blood - Bone Shield will be cast during Rest if in an Instance or Battleground. Previously was casting only in Combat which forced 1 min cooldown period to occur entirely in combat
Druid
fixed - Balance - issue with failed Starsurge cast immediately following a successful one
Hunter
fixed - Beast Master - issue with Kill Command not accounting for size of hitboxes. Some casts also missed because of check for Hunter to be in range of target as well.
change- All Specs - Hunter's Mark cast between 44 and 65 yards from target in Solo and Instances since out of range for other abilities
change- All Specs - additional debug logic added to Trap behavior to detect reason for failure when Log Level >= Verbose
Mage
change- All Specs - removed Blink from Loss of Control reaction behavior.
Priest
fixed - Discipline - fixed target selection for Shadow Word: Death casts
fixed - Shadow - fixed priority of Mind Blast vs Devouring Plague to avoid wasting Shadow Orbs
fixed - Shadow - fixed so successful Mind Blast casts are not immediately followed by a failed attempt
Shaman
fixed - Elemental - fixed so successful non-instant Lava Burst casts are not immediately followed by a failed attempt.
fixed - Enhancement - suppress use of Feral Spirit on trivial mobs
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.