The latest rev at this point now saves timers through reloads and relogs (restarting your machine will dump all the timers, because the function that the timers are based on returns seconds since you booted up). I broke a couple things in the process though, like being able to click on bars or do a clearall. I'll work on it more tonight but people will probably want to stick with r40871 for the time being.
I just added clearall (/inc clearall or /incubator clearall) as an option to kill all running timers. Shift click was a decent way to kill any running timers if they were all displaying but there wasn't a way to kill timers if they didn't have a bar up for one reason or another (already displaying too many bars, hasn't hit your display threshold yet, etc).
Yes, that's intentional - I don't want to blow away timers for someone because the raid group got shuffled temporarily or something of that nature. Currently the only real solution is to shift + left click on all the bars you see to destroy them.
Looks like r34282 is pretty stable again, but I was able to determine that the R&J handler isn't working properly -- it doesn't kill all the timers midfight like before, but it doesn't kill all the timers after they die, either.
Incubator got moved from SurfaceLib to SharedMediaLib last night - I'd recommend sticking with r34141 until the last few things get ironed out - there isn't any new functionality with the newer revs, just cleaner on the backend (should be a lower memory footprint due to using less libs, too).
If you're willing to live on the edge I just checked in r34282 from work, hopefully that fixes that particular surface error, but I can't say for sure until I get home ;)
Aflat -- give r34140 or newer a try (34141 has that toc update) and let me know how it goes.
Also there's currently a bug where if a "solo" mob dies while you're dead then the timer will be extremely wrong (I had an underbog colossus come up as a 10 day respawn last night, for example). Should have a bugfix for that one sometime today.
Added a preliminary R&J handler to hopefully take care of that (r33872). I can't verify it myself as to if it works or not unless we happen to get R&J this week, so if anyone finds that it works (or doesn't work) let me know!
OOC Checking is a lot more robust now, and doesn't just depend on the player going out of combat. This means that if you die during a pull you'll still get a timer starting correctly when everyone else kills it, so long as you don't release. If everyone dies it should figure out that it's a wipe and just discard that combat information.
"Solo" mobs should also properly start timers when pulled with other mobs (i.e. if you get a spectral servant on accident with a spectral guest AOE pull).
Gregory: see page 2 of the thread for why that is ;)
So for some reason as of tuesday PLAYER_REGEN_ENABLED is firing when the player dies in addition to when you go out of combat, which is leading to some screwy times showing up. Should have a fix later today but just a heads up on it.