Also another thing I noticed tonight. I couldn't figure out why the hell my candybars wouldn't start. Turns out I had maximum time in minutes set to the default of 60. So no candybars started because they were all over 2 hours. Change it to 0 or 2 hours and they will all show. I also have now changed the default to 0 to spare some confusion. Thought it was broken and it wasn't:P
Got the following error in Sunwell with r73617 on enUS:
[2008/05/12 17:51:03-2991-x1]: FuBarPlugin-2.0-63898:360: Tablet-2.0: Bad argument #2 to `IsRegistered' (table or string expected, got nil)
Incubator-2.00\Core.lua:892: in function <Interface\AddOns\Incubator\Core.lua:891>
<in C code>: in function `pcall'
AceAddon-2.0-57245 (Ace2):24: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:23>
AceAddon-2.0-57245 (Ace2):998: in function `ManualEnable'
AceAddon-2.0-57245 (Ace2):495: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:488>
AceAddon-2.0-57245 (Ace2):617: in function `InitializeAddon'
AceAddon-2.0-57245 (Ace2):484: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:461>
<in C code>: ?
AceEvent-2.0-66043 (Ace2):298: in function `TriggerEvent'
AceEvent-2.0-66043 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>
<in C code>: ?
<in C code>: in function `LoadAddOn'
AddonLoader-1.0\Conditions.lua:30: in function `Trigger'
AddonLoader-1.0\Conditions.lua:189: in function `RAID_ROSTER_UPDATE'
AddonLoader-1.0\Conditions.lua:193: in function `v'
AddonLoader-1.0\AddonLoader.lua:207: in function <Interface\AddOns\AddonLoader\AddonLoader.lua:173>
<in C code>: in function `pcall'
AceAddon-2.0-57245 (Ace2):24: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:23>
AceAddon-2.0-57245 (Ace2):998: in function `ManualEnable'
AceAddon-2.0-57245 (Ace2):926: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:919>
<in C code>: ?
AceEvent-2.0-66043 (Ace2):260: in function `TriggerEvent'
AceEvent-2.0-66043 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>
---
Edit: Also, I lost my Sunwell timers on a /reloadui. It may be related to this error, as I got the above error again and Incubator's FuBar icon didn't show at first.
Yes to repeat there is a bug where if you reloadui and you have timers running you will lose those timers. All you have to do is disable mod before you reloadui until I figure out what the problem is. Basically I save the timers everytime a timer is added or removed and when the mod is disabled in this format:
Timer[name] = {
[1] = 7049, --time left
[2] = true, --needs warning
[3] = true, --candybar need started
[4] = 25320 --UID}
So does disable mod not get called when you reloadui? Other weird thing is I never directly set the saved variable timers = to the local timers so I can't figure out why if the mod is enabled when you reloadui it overwrites the correct saved values with the currently running ones. Anyone has any enlightenment for me feel free:P
I haven't paid attention that closely (as a healer I'm watching health bars more than mob names) but I'm pretty sure that many of the same mobs appear in both Kalecgos' trash and Brutallus' trash. Without counting packs (and somehow detecting failed attempts / wipes) I'm not sure there'd be any way to tell which boss should reset which trash timers.
I know for sure that all of the Shadowsword guys are in the Twins' trash too.
I'll pay more attention to trash mob names next week. (We're back up to M'uru this week, hopefully will get him down!)
Out of curiosity, though, why would you skip Kalecgos? He's easy...
Out of curiosity, though, why would you skip Kalecgos? He's easy...
Ugh, we're stuck on him again even after killing him once or twice. Don't give me flashbacks to when I was a kid and told people I didn't know how to ride a bicycle.
New version fixes all candybar resuming problems. You can reloadui whenever the hell you want now:D As far as I can tell the candybars are working perfectly now so tell me if you discover otherwise.
If so I will change it I don't know sunwell plateau yet:(
No....
Each Shadowsword mob is the trash after Brutalus/Felmyst on the way to The Twins.
The Unyielding Dead are the adds that spawn in the Felmyst fight, these should be ignored.
The "Blazing Infernal" I *think* is some other language's version of the Volatile Fiend (trash on the way to the Twins), because I've never these that mob and I'm at the Twins weekly. These should be ignored as they are spawned constantly during the gauntlet event on the way to The Twins.
The "Felguard Slayer" is another one that I think is from a non-english client. I am guessing that these are the Shadowsword Deathbringers and those are also the trash on the way to the Twins, and should also be ignored because they are also spawned durign the gauntlet event.
REQUEST: In the Fubar menu where it lists th timers, it would really be nice to be able to right-click the timer and rename it. That way I can change the name to something that I can associate to its position rather than the generic name of the last mob killed.
BUG: When I left click to report a timer in the Fubar menu, I get an error:
Message: SendChatMessage(): Invalid escape code in chat message
Debug:
...face\AddOns\AtlasLoot\Libs\Tablet-2.0\Tablet-2.0.lua:971:
...face\AddOns\AtlasLoot\Libs\Tablet-2.0\Tablet-2.0.lua:956
During a trial test last night during a Kara clear run, r74023 refused to show the 20 minute timer up to Attumen. The Moroes timer started, but not that one, which is a small improvement...heh. Same problem as in the past before I switched to Trash Timers. Did not log out/relog or anything before the start of the run; logged in once.
This still needs work before it can be relied on in a raid (at least Kara & ZA raids). Maybe go back to old code, if it doesn't need updating for 2.4.x?
Here is hoping the new r74262 finally fixes the timer problems. Based on the log, doesn't look like it (looks specific to a single circumstance), but hoping anyway ;).
Really? Are you sure you don't have one of the bar options set wrong? ie to see all bars set:
Max time in minutes = 0
Time between bars = 0
Bar count = something more than 0
If this doesn't fix it turn on dev mode and try give me some feedback if you can. Haven't run kara in a few weeks but attumen timers worked last time I did. All timers in TK have been working perfectly (and I have been using candybars to make sure)
Really? Are you sure you don't have one of the bar options set wrong? ie to see all bars set:
Max time in minutes = 0
Time between bars = 0
Bar count = something more than 0
If this doesn't fix it turn on dev mode and try give me some feedback if you can. Haven't run kara in a few weeks but attumen timers worked last time I did. All timers in TK have been working perfectly (and I have been using candybars to make sure)
It wasn't the bars (which I had disabled because they haven't worked since February and I haven't tried them again), it was the timer in the FuBar text which didn't show up at any time through to Attumen. Yes, the three things you mention were set to 0.
Well not sure what to tell you. Ran kara just now and attumen timers worked perfectly. You sure the mod didnt go into standby for some reason? Maybe a mod conflict?
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumEdit: Also, I lost my Sunwell timers on a /reloadui. It may be related to this error, as I got the above error again and Incubator's FuBar icon didn't show at first.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumTo replicate the issue, I'd recommend reloading your UI while already in a raid and a raid instance.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumTimer[name] = {
[1] = 7049, --time left
[2] = true, --needs warning
[3] = true, --candybar need started
[4] = 25320 --UID}
Reloading without disabling the mod saves it as:
Timer[name] = {
[1] = 103456, --time left + GetTime()
[2] = false,
[3] = false,
[4] = 25320}
So does disable mod not get called when you reloadui? Other weird thing is I never directly set the saved variable timers = to the local timers so I can't figure out why if the mod is enabled when you reloadui it overwrites the correct saved values with the currently running ones. Anyone has any enlightenment for me feel free:P
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumBlazing Infernal
Felguard Slayer
Shadowsword Assassin
Shadowsword Lifeshaper
Shadowsword Manafiend
Shadowsword Soulbinder
Shadowsword Vanquisher
Unyielding Dead
If so I will change it I don't know sunwell plateau yet:(
I know for sure that all of the Shadowsword guys are in the Twins' trash too.
I'll pay more attention to trash mob names next week. (We're back up to M'uru this week, hopefully will get him down!)
Out of curiosity, though, why would you skip Kalecgos? He's easy...
Ugh, we're stuck on him again even after killing him once or twice. Don't give me flashbacks to when I was a kid and told people I didn't know how to ride a bicycle.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNo....
Each Shadowsword mob is the trash after Brutalus/Felmyst on the way to The Twins.
The Unyielding Dead are the adds that spawn in the Felmyst fight, these should be ignored.
The "Blazing Infernal" I *think* is some other language's version of the Volatile Fiend (trash on the way to the Twins), because I've never these that mob and I'm at the Twins weekly. These should be ignored as they are spawned constantly during the gauntlet event on the way to The Twins.
The "Felguard Slayer" is another one that I think is from a non-english client. I am guessing that these are the Shadowsword Deathbringers and those are also the trash on the way to the Twins, and should also be ignored because they are also spawned durign the gauntlet event.
BUG: When I left click to report a timer in the Fubar menu, I get an error:
Message: SendChatMessage(): Invalid escape code in chat message
Debug:
...face\AddOns\AtlasLoot\Libs\Tablet-2.0\Tablet-2.0.lua:971:
...face\AddOns\AtlasLoot\Libs\Tablet-2.0\Tablet-2.0.lua:956
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis still needs work before it can be relied on in a raid (at least Kara & ZA raids). Maybe go back to old code, if it doesn't need updating for 2.4.x?
Here is hoping the new r74262 finally fixes the timer problems. Based on the log, doesn't look like it (looks specific to a single circumstance), but hoping anyway ;).
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumMax time in minutes = 0
Time between bars = 0
Bar count = something more than 0
If this doesn't fix it turn on dev mode and try give me some feedback if you can. Haven't run kara in a few weeks but attumen timers worked last time I did. All timers in TK have been working perfectly (and I have been using candybars to make sure)
It wasn't the bars (which I had disabled because they haven't worked since February and I haven't tried them again), it was the timer in the FuBar text which didn't show up at any time through to Attumen. Yes, the three things you mention were set to 0.
Will run debugging next week.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumr74330 used. Forgot to turn on debugging; will tonight on another run with another character, though.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium