Created two scheduling engines for the timer: One based on the Animation system, and one based on the classic OnUpdate methods, with the animation system used by default. If you're experiencing crashes when using OmniCC, try switching to the OnUpdate engine.

To switch to the OnUpdate engine, use

Code:

/omnicc setengine classic

To switch back to the Animation engine, use

Code:

/omnicc setengine animation

GitHub:

OmniCC development has moved from GogleCode to GitHub. The intention is to make it easier for people to fork/contribute to OmniCC development (and also for me to learn about git). Writing code for me typically gets your request implemented faster than asking me to write it myself :P

Submitting bugs & feature requests:

In order of preference, here's where you should submit bug reports and feature requests:

Created two scheduling engines for the timer: One based on the Animation system, and one based on the classic OnUpdate methods, with the animation system used by default. If you're experiencing crashes when using OmniCC, try switching to the OnUpdate engine.

I'm going to test if the same bug appears with the new update, posting later today

Tested it just now and I haven't been able to reproduce the error. But just in case it reappears - I had configured Weak Auras to show cooldown timers on my spells, but realized it was a bit overdoing it, so I decided to remove the cooldown timers and after that the error starting spamming me. OmniCC was controlling the timers on the icons btw..

The 50d bug should be "resolved", though I've not tested it for confirmation. Instead of estimating a cooldown, which may be inaccurate, I've opted to simply not display text for that situation.

The fixes I implemented should also hopefully resolve the cooldown effect not showing up thing.

I'm hoping at this point I've squashed enough bugs to think about doing a full release. Other than finishing up the new guide, the only thing I think I may want to do is implement an upgrade script from 3 to 4.