1.8.7-nolib
Details
-
FilenameArchy-1.8.7-nolib.zip
-
Uploaded by
-
UploadedNov 13, 2011
-
Size184.59 KB
-
Downloads554
-
MD527dfc01fb041639769b1389c2ed27731
Supported WoW Retail Versions
- 4.2.0
Changelog
tag 1.8.7
378ab4c4529c069645fc1a9de6252518d6b6ed85
James D. Callahan III <darkenelf@gmail.com>
2011-11-13 02:03:50 -0600
--------------------
James D. Callahan III:
- More cleanups, because this code is dirty.
- Fixed the path for the toast icon since Blizzard can't agree with itself on how to spell Archaeology.
- Code cleanup - fixed global (and wrong) variable use for minimap blobs.
- Removed three un-used textures.
- Added "Toast" as a sink option, and made it the default (there wasn't one, previously, so LibSink made the decision).
- Replaced the solving-confirmation StaticPopupDialog with a LibDialog-1.0 dialog.
- Removed a dead (and undefined) function.
- Removed ARTIFACT_NAME_TO_RACE_ID_MAP; while it was a decent idea, it completely broke solving artifacts with keystones. Added forced-loading of Blizzard_ArchaeologyUI (if it isn't already loaded) before pre-hooking SolveArtifact().
- Removed GraphicalUI.lua ad GraphicalUI.xml - they were never loaded.
- Renamed artifact.fragAdjust to artifact.keystone_adjustment
- Renamed artifact.fragTotal to artifact.fragments_required
- Fixed some goofy event registrations.
- Combined two if statements into a single statement.
- Removed useless function call to GetArtifactProgress().
- Removed a debug print.
- Cleanups and clarification (stonesAdded --> keystones_added)
- Since BAG_UPDATE is now bucketed, there's no need to schedule a 1/2 second timer for RefreshRacesDisplay().
- Bucket BAG_UPDATE; stop listening for ARTIFACT_COMPLETE and get rid of the silly bag update sentries associated with it.
- A bit of cleanup.
- Call RefreshRacesDisplay() at the very end of CurrencyUpdated() instead of doing so at the end of every race iteration.
- I don't know why we were checking for "usesStones" twice, but now we're not.
- Bucket ARTIFACT_HISTORY_READY so RefreshRacesDisplay() isn't needlessly called multiple times.
- Don't worry about un-registering events in OnDisable() - it's automatic.