2.4.2_beta_6-16-g0272da7-nolib
Details
-
FilenameDecursive-2.4.2_beta_6-16-g0272da7-nolib.zip
-
Uploaded by
-
UploadedAug 6, 2009
-
Size363.05 KB
-
Downloads68
-
MD5d595cd70ad7460360445b9dc7ef6df8a
Supported WoW Retail Versions
- 3.2.0
Changelog
Archarodim:
- - Added new Shaman spell "Cure Toxins"
- - Probably fixed the long standing issue of this beta phase (innacurate group/raid unit roster in race conditions). The fix may have side effects, it requires TESTING! (debug reports will still be generated though to confirm the fix)
- Removed the random sorting option that has become completely useless and stupid.
- changing the focused unit from a friendly one to another friendly one with a debuff did not trigger a debuff rescan of the 'focus' unit.
- Fix self report function and beta warning (last commit broke them completely)
- Forgot some message() calls.
- Added a message when a LUA error is not from Decursive since Decursive hook appears in the debug stack whenever a LUA error occures.
- TOC bump for WoW 3.2
- - Decursive error reporter now able to report LUA errors happening while loading Decursive
- code cleanup
- - Decursive no longer uses the message() global Blizzard function to display error messages (corrupt install or debug report availbility). Blizzard broke message() in WoW 3.2 :/
- - More data in debug reports about UnitGUID() strange behavior after group updates :/
- - Added a dev version warning at start for people who complains about the error reports ;-)
- - fixes a LUA error that occures in rare race conditions (Dcr_LiveList.lua:426 attempt to index field '?' (a nil value))
- - small optimisation in the group scanning functions.
- - Added more data to the sanity check report.
- - fixes "Sanity check failed in LiveList:GetDebuff() no MUF for unit"
- - MUF status were no longer updated after the last debuff was removed (bug introduced in beta6)
- - Added the latency to the debug reporter.
- - Sanity check update (more data) and tweaks
- - Show MUFs only when their position is set correctly to avoid MUFs overlapping at maximum in race condition (entering combat while players are joining/leaving the raid).
This won't prevent overlapping from happening since the player may enter in combat at any moment while the MUFs are being reordered. (this is rare though)
- changed "Refresh speed" option value max limit from 20 to 82.
- - Added a sanity check to confirm an hypothesis about why COMBAT_LOG_EVENT_UNFILTERED() fails sometimes.
- - Fixes the virtual test affliction creation that was broken since the last commit.