Tales of Maj'Eyal

Tales of Maj'Eyal

Timed Rest
10 Comments
General Chaøs™ 8 Jan, 2016 @ 12:44pm 
Should be put into the game by default, thanks
Teh Bun 19 Apr, 2015 @ 1:32am 
Extremely useful and a must-have for all owners of ToME.
Skaffi 4 Nov, 2014 @ 9:11pm 
ThatWhichIsMe, even if your addons weren't kosher, you certainly are as kosher as an addon dev can ever hope to be! Your efforts, both in developing all of your addons in the first place, as well as fixing up this minor issue, is really, very much appreciated! Especially since I'm running a lot of Chronomancers lately.

My next character will be named after you, in your honour. I hope you don't die easily.
ThatWhichIsMe  [author] 4 Nov, 2014 @ 7:21pm 
@Skafsgaard: The bug affected all my addons that install a keybinding (turns out the way I was installing them wasn't really kosher...). This latest release should fix the problem.
Skaffi 27 Oct, 2014 @ 5:19pm 
Oi, mate!

No, thank you for looking into it! It's very much appreciated.
And, as I mentioned, it affects both your Timed Rest addon and your Note To Self addon for sure, but it might possibly also be a bug that happens with your other addons. If you find the bug that causes it, then maybe check to see if it's also an issue with your other addons.

Again, thanks!
ThatWhichIsMe  [author] 23 Oct, 2014 @ 6:00pm 
@Skafsgaard: Hmm, now that you mention it, I think I had that happen to me once in (I think) 1.2.3. And it may indeed have been the one that I accidentally fired off Precognition on. I'll need to investigate this further. Thanks.
Skaffi 20 Oct, 2014 @ 7:12pm 
A correction: it seems that going back to the main menu, and the loading the character again, is enough to fix the issue, rather than having to restart the game. Also, it very much happens whenever Precognition has run its course. Maybe it's the only thing that triggers it, and I just didn't realize?
Skaffi 20 Oct, 2014 @ 6:47pm 
Anyway, I hope you'll take a look at this, since your two addons are of immense help to me. It would certainly be very, very much appreciated - it's hard to go back to vanilla, after having gotten used to your addons! Also, if there's any further info I can give you, to help you out, do not hesitate to let me know!

Cheers, and thanks!

P.S.: Sorry for the broken up comments - I seemed to easily exceed the max character count of one thousand.
Skaffi 20 Oct, 2014 @ 6:47pm 
Basically, what happens is that load up the game, play for a while, and both of your addons are working just swell initially. Then after a while of playing, usually between 30 and 60 minutes, my hotkeys for the addon functions won't work. And if I go into the keybinds to see if they've become unbound, or some such, they've actually disappeared from the list of possible functions to bind - in short, it's as if the addons aren't active at all! This continues on, until I shut down and restart the game, at which point the addons are working just great again, and I get another 30-60 minutes of use out of them, before needing another restart. I haven't been able to pinpoint any particular in-game type of event or situation which makes this occur, however, though it does seem to happen more frequently, but not limited to, when I've cast Precognition to split the timeline, and when the effect wears off and I'm returned to my original timeline, the addons will often have ceased to work.
Skaffi 20 Oct, 2014 @ 6:47pm 
Hey mate!
I've used your addon for quite a while now, and it's definitely the single biggest improvement on the game that I get from any of my addons - all of which are utility ones like this - since Archmages are one of my favourite classes, and timed resting is just invaluable in managing one's Disruption Shield. So, I can't tell you how much I appreciate the effort you went through to make this.

That being said, I've sadly started experiencing a bug with both this, and your other very handy note-to-self addon. I'm not an expert, so the issue could of course be with my computer, but since the bug, IIRC, first started to appear when the 1.2.4 update hit, I figure there's a big chance there might be some sort of incompatibility with your addon and the new version. I don't recall exactly, though, and the bug might have appeared a few times before as well, though if it did, it was nothing compared to the frequency of it now.