WowAce

I have the ability to communicate with Gagorian outside of games or forums.  After all, I did help him get his WoW account reactivated. :)

In any event, he's been on (for me) a lot sooner than March 6th.  We discussed some weird wow mechanics and how to implement a few things we needed to get done.  Nonetheless, my last communication with him (after March 6th) indicated there was no change in the status of the Ion addon integration as he hadn't heard anything from the author.

Though, keep in mind that Ion support is lower on the list of priorities.  Higher on the list is to make sure all classes function correctly.  (Which is not relevant to custom UI integration since the addon works with the supported ones or with none.)  This will hit the widest number of people than stalling a project to wait for the addon author to respond.  This is why I ask for feedback on the untested classes/specs - as it affects the widest number of people at once.  

Monks are next on the list, but they're in a waiting pattern until information about established classes is provided.  This class requires a brand new module which could completely break or fail to function - whereas most of the other classes are modifications without a rewrite.

So, I must reiterate, if people want the addon out of alpha state, more testing is needed.  See the website for more details.

Right now, the only class that isn't implemented at all is monk.  Other classes may be inaccurate (mostly only a few specs like Discipline due to last minute 5.2 changes) but otherwise mostly functional.

See the current status on the known issues page.  Follow the mod feedback link to test and see how to report bugs/issues.

Update 4/01/2013:  I still need testing for the listed classes.

1.) Paladins (all specs)

2.) Enhancement shaman

3.) Assassination Rogues

4.) Resto druids

5.) Balance druids

6.) Warriors (all specs)

7.) Shadow priests (aqCelestyna@wowace has helped some on this)

8.) DKs (all specs)

9.) Hunters (all specs)

Please follow the known issues and mod feedback links on the wowace site.  So far, I haven't had anyone willing to provide this feedback at all (despite indications that folks were interested).  Less feedback means a much longer period of time to get this into a beta/release state.  

I'm not sure why you would get that kind of error.  The relevant code is:

local chance = 0.2 + (UnitHealth("target") ~= 0 and ((UnitHealth("target") / UnitHealthMax("target")) <= 0.35) or 0)

In essence, the chance to proc earth living weapon is based on target's health.  What you're saying is that the addon is sending a LUA error on this (which doesn't make sense).  Chance is equal to 20% plus (target's health percentage, if under 35% -- otherwise 0).  The only conceivable change I could make is to add an `if UnitisFriend("target","player")` check.  I don't believe that will solve the error in question, however.

That said, I added the probably unnecessary check in r1933.

Update on 03/27/2013:

A few classes that are implemented may need additional testing (as indicated in the Known Issues page) but otherwise may be ready.  Those not listed are not started.

If a class is listed as needing testing, what I would need is this:  You must have knowledge of how theorycraft for your class (at minimum, spec) works.  If a value doesn't match in game to the tooltips, you'll not only need to provide what's on the mod feedback link, but also why the ability displayed doesn't match.

Headhuntress (on Curse/Wowace) was able to do this privately quite well on a couple holy paladin abilities without me asking for it.  As such, that got several key updates in for holy paladins.

If you do not know theorycraft for your class (modifiers, talents, buffs, etc), please hold off on feedback as yet because I will spend more time trying to explain it to you than being able to update the mod.  If I can't use your feedback, at least understand that if something appears wrong and you don't know why, it will likely be fixed at some point.

If a class is listed as needing testing with the above requirements, please follow the mod feedback guidelines on the wowace page (a link to that plus the known issues) is located on the website.  At this time, I'm specifically looking for feedback only on the following specs/classes:

(If not listed, I am not looking for feedback on that spec/class combination)

1.) Paladins (all specs)

2.) Enhancement shaman

3.) Assassination Rogues

4.) Resto druids

5.) Balance druids

6.) Warriors (all specs)

7.) Shadow priests (aqCelestyna@wowace has helped some on this)

8.) DKs (all specs)

9.) Hunters (all specs)

The list ends there.  That should be more than enough to help me get the currently untested classes verified and/or working.

Please send me a PM on this site and I'll tell you what I need to get from you to test.

I'm not getting the message you list (in frost spec or fire spec either).  I'll remove the line if it's in there (pretty sure I removed it at some point, but it may have been in Gagorian's backup copy).

Edit to add:  This is updated in r1818.

Gagorian is assisting me with updating a few of the harder, but less heavy, elements of the addon.  He updated the mana regen calculations as well as fixed a few minor bugs in the addon. 

Please note the "Known Issues" link on WoWAce before touching the addon.  Several classes aren't yet even remotely touched.

To answer the most commonly asked question: "Why isn't my class/my spec ready yet?"  Answer:  As is always the case with this addon, the classes/specs that the authors have available to test are the ones that get done first.  This will never change.  As an example, the addon originally was designed for warlocks because Gagorian originally made it for them.  No other class had functionality until added.  Each expansion gets updated in the order of the highest available class/spec to test for the authors.

To answer the most common followup question: "Why can't you update my class/my spec and I'll test it for you?"  Answer:  Because this is a lot slower to do updates for than to have one the author can make a test and immediately verify the results.  It sounds simple for you to do it this way, but in reality it slows things down a lot and may make things worse.

We are not yet ready for prime time testing.  So, if you test an alpha build and it doesn't work for you, please understand that we know this to be the case or it wouldn't be alpha!  When we release this as either a Beta or Release build, it will be stable for just about everyone at that point.  Thank you for your understanding.

Edit to remove details since changed.