Bug fixes released yesterday Wednesday evening (Eastern Daylight Time, UTC-0400) 6 August 2014.

So I did manage to leave a few bugs in.

And totally forgot about the DisplayNames function being broken in v1.2.3 which caused a lose of saved settings (saved variables in the API parlance), which re-caused a lose of saved settings after upgrading to v1.3.3, which happened on Monday.

Double Doh.

Luckily my Internet access was down after I came home from work, so I didn't know about any of this until very late this evening.

Just released the Rainbow Reticle updated for v1.3.3 (Armour Dyes), based on yesterday's 1.0.1 beta release.

Appears to work, based on my limited (~0.5 hour) testing.

Yesterday I discovered that Garkin has been maintaining his own version of Rainbow Reticle since the 0.9b patch which fixed it for the v1.2.3 (Veteran Crypt of Hearts). -- I guess I failed to explain / state that I had planned on continuing maintaining RR even after using his fixed version.

The code changes are similar, with his tending to simplify / or shorten where I tend to wrap bits into functions. I might incorporate something similar to his change on the "queue timer" as it uses integer values (milliseconds rather than decimals of a second) and is quite short, tidy, and straight forward.

While waiting for the NA server to update (I don't have an EU install, multiple ~60GB installations for typically a single configuration file!), I updated the ESOUI page for Rainbow Reticle (updated) and entered some feature requests, as I did manage to incorrectly remember one of them, so I thought I had implemented it.

Thankfully upgrading to LibAddonMenu-2.0 makes most of the proposed changes easier to implement. That is of course assuming that the update live version of 1.3.3(?) is similar to the version on the PTS (v1.3.2) test server, with no radical new breakage.

I've published version 1.0.1 as a beta release of Rainbow Reticle, in hopes to a) make sure I didn't do anything too stupid, and as preparation for the pending Elder Scrolls Online update to version 1.3.x, which I believe is Monday 4 August 2014.

As I'm starting to get the hang of Lua code I think, it should be hopefully easier to implement some new features in the near future (after the ESO update).

I was thinking of checking with Garkin and Mitz about adding a MIT or X11 license, just so the code has a license. The rationale for X11 / MIT is merely the license is short and easy to read, and with a scripting language like Lua, there are no binary executables or byte-code (e.g. .jar) only options to distribute anyhow making LGPL or Apache 2.0 license irrelevant and a long read for a small add-on.