- Registered User
Member for 14 years, 8 months, and 15 days
Last active Fri, Oct, 4 2013 14:29:42
- 0 Followers
- 8 Total Posts
- 0 Thanks
Jan 31, 2008It's probably somethign silly, but I can't find the answer. In my cast bars, the name of what's being cast only appears when it's either interrupted or finishes casting. Not so useful when debating whether to interrupt my enemy or not depending on what they're casting, heh. Any ideas?Posted in: Unit Frames
Oct 22, 2007Posted in: General AddOns
me tooQuote from Cal »
[2007/10/22 20:45:33-2285-x2]: SpellReminder-0.9\SpellReminder.lua:621: attempt to compare string with number ---
[2007/10/22 20:46:19-2285-x1]: SpellReminder-0.9\SpellReminder.lua:621: attempt to compare string with number SpellReminder-0.9\SpellReminder.lua:412: in function `func' Dewdrop-2.0-48630 (DewdropLib):721: in function <...erface\AddOns\DewdropLib\Dewdrop-2.0\Dewdrop-2.0.lua:660> ---
Oct 11, 2007From what I understand, this mod is awesome. But it only tracks when CC effects are about to time out if I had it targeted when the effect was cast, eh? I was wondering, and maybe this is out of the scope of the project, but what if it synced with everyone else in the group that was using the mod as well? That way when my mages sheep and my warlocks banish, even though I don't have them targeted when it's done, when I finish with the mob I'm tanking, I could see what's about to break first. Also, even on things like sap and whatnot, it'd be the correct time because the mod would be able to tell if the rogue has imp sap or not. Now, I haven't had a chance to try out the mod in a group setting yet, so maybe it does all this already. But if it doesn't, that'd be something you could work on implementing.Posted in: General AddOns
Sep 17, 2007Posted in: General AddOnsQuote from Quagmire »
I cannot reproduce this. I did discover a bug with reenabling nQuestLog from the FuBar menu, though the bug doesn't appear to break anything...I'll fix it when I get a chance, but it's not hurting anything. Please try deleting nQuestLog.lua and nQuestLog.lua.bak from your "World of Warcraft\WTF\Account\<your account>\SavedVariables" folder, and see if that fixes the problem. If not, please explain the exact steps you are taking in detail so I can try to reproduce the problem and do further troubleshooting. Thanks!
Ya, I donno what I did to screw it up so badly, but when I deleted the luas, it was all cool again. Fixed.
Sep 14, 2007As of the latest update, I get this everytime I try to open nquestlog.Posted in: General AddOns
[2007/09/14 15:00:31-20-x1]: nQuestLog-1.0\moduleLoading.lua:88: attempt to index field 'db' (a nil value)
nQuestLog-1.0\moduleLoading.lua:78: in function `IsModuleEnabled'
nQuestLog-1.0\moduleLoading.lua:106: in function `GetColor'
nQuestLog-1.0\core.lua:311: in function `RefreshBackdrop'
nQuestLog-1.0\core.lua:317: in function `RefreshTracker'
nQuestLog-1.0\core.lua:129: in function `ToggleVisible'
nQuestLog-1.0\events.lua:102: in function `OnClick'
<string>:"NQUESTLOG_TOGGLE":1: in function <[string "NQUESTLOG_TOGGLE"]:1>
- To post a comment, please login or register a new account.