LibMobHealth-4.0-r60975
Details
-
FilenameLibMobHealth-4.0-r60975.zip
-
Uploaded by
-
UploadedFeb 11, 2008
-
Size6.79 KB
-
Downloads40
-
MD5183bb6241d4a97e13a8c85c4e4974d63
Supported WoW Retail Versions
- 2.3.3
Changelog
------------------------------------------------------------------------
r60975 | ckknight | 2008-02-11 14:06:49 -0500 (Mon, 11 Feb 2008) | 1 line
Changed paths:
M /trunk/LibMobHealth-4.0/LibMobHealth-4.0.lua
LibMobHealth-4.0 - tweaking for efficiency
------------------------------------------------------------------------
r60974 | ckknight | 2008-02-11 14:05:37 -0500 (Mon, 11 Feb 2008) | 1 line
Changed paths:
M /trunk/LibMobHealth-4.0/LibMobHealth-4.0.lua
LibMobHealth-4.0 - when saving data, go through and if you have more than 1000 points of data, remove any old data if possible.
------------------------------------------------------------------------
r60952 | ckknight | 2008-02-11 11:31:53 -0500 (Mon, 11 Feb 2008) | 1 line
Changed paths:
M /trunk/LibMobHealth-4.0/LibMobHealth-4.0.lua
LibMobHealth-4.0 - be able to convert data from MobHealth3 for bosses with level -1
------------------------------------------------------------------------
r60896 | ckknight | 2008-02-10 22:39:16 -0500 (Sun, 10 Feb 2008) | 1 line
Changed paths:
M /trunk/LibMobHealth-4.0/LibMobHealth-4.0.lua
LibMobHealth-4.0 - check for _G.MobHealth3DB on PLAYER_LOGIN, and if found, gleam data from it.
------------------------------------------------------------------------
r60892 | ckknight | 2008-02-10 22:09:29 -0500 (Sun, 10 Feb 2008) | 3 lines
Changed paths:
A /trunk/LibMobHealth-4.0
A /trunk/LibMobHealth-4.0/LibMobHealth-4.0.lua
A /trunk/LibMobHealth-4.0/LibMobHealth-4.0.toc
A /trunk/LibMobHealth-4.0/LibStub
A /trunk/LibMobHealth-4.0/LibStub/LibStub.lua
A /trunk/LibMobHealth-4.0/lib.xml
LibMobHealth-4.0 - initial commit
Works similarly to MobHealth3, with a few differences, (a) more efficient (b) slightly different API (c) checks focus as well as target for data (d) less options for the user (which hopefully won't be a problem)
Currently, if run as a non-embed, it will save data in a saved variable. Not sure if it will stay this way, would like comments on it.
------------------------------------------------------------------------