I was wondering what happened with that. Must have been a recent change in TipTac then. Since it worked fine a few days ago. Gas Nodes still work however..
Alright.. deleted my saved variables. reloaded and started over. I started to make a new default profile. When I put in the new name and hit the ok button I got this error. (which was the same as before) Using 67309.
Got a few errors last night while trying to arena.
1) The frame never updated correctly after these errors and after reseting the profile.
2) I could see all of the classes after some time but their names/health bars were missing.
3) This was with 67206 build
4) I am pulling these from swatter's saved variables. so formating might be off.
"Interface\\AddOns\\Proximo\\frame.lua:219: attempt to perform arithmetic on field 'partytargetheight' (a nil value)"
"(tail call): ?\nInterface\\AddOns\\Proximo\\frame.lua:219: in function `?'\n...Ons\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:146: in function <...Ons\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:146>\n[string \"safecall Dispatcher[3]\"]:4: in function <[string \"safecall Dispatcher[3]\"]:4>\n[C]: ?\n[string \"safecall Dispatcher[3]\"]:13: in function `?'\n...Ons\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:91: in function `Fire'\nInterface\\AddOns\\Ace3\\AceDB-3.0\\AceDB-3.0.lua:367: in function `SetProfile'\n...ce\\AddOns\\Ace3\\AceDBOptions-3.0\\AceDBOptions-3.0.lua:181: in function <...ce\\AddOns\\Ace3\\AceDBOptions-3.0\\AceDBOptions-3.0.lua:180>\n(tail call): ?\n[C]: ?\n[string \"safecall Dispatcher[3]\"]:9: in function <[string \"safecall Dispatcher[3]\"]:5>\n(tail call): ?\n...nfig-3.0\\AceConfigDialog-3.0\\AceConfigDialog-3.0.lua:700: in function <...nfig-3.0\\AceConfigDialog-3.0\\AceConfigDialog-3.0.lua:526>\n(tail call): ?\n[C]: ?\n[string \"safecall Dispatcher[3]\"]:9: in function <[string \"safecall Dispatcher[3]\"]:5>\n(tail call): ?\nInterface\\AddOns\\Ace3\\AceGUI-3.0\\AceGUI-3.0.lua:217: in function `Fire'\n...ns\\Ace3\\AceGUI-3.0\\widgets\\AceGUIWidget-DropDown.lua:68: in function <...ns\\Ace3\\AceGUI-3.0\\widgets\\AceGUIWidget-DropDown.lua:64>\n...ns\\Ace3\\AceGUI-3.0\\widgets\\AceGUIWidget-DropDown.lua:96: in function <...ns\\Ace3\\AceGUI-3.0\\widgets\\AceGUIWidget-DropDown.lua:90>\n"
"Interface\\AddOns\\Proximo\\Proximo.lua:631: attempt to index field 'highlightcolor' (a nil value)"
"(tail call): ?\nInterface\\AddOns\\Proximo\\Proximo.lua:631: in function <Interface\\AddOns\\Proximo\\Proximo.lua:570>\n(tail call): ?\n[C]: ?\n[string \"safecall Dispatcher[2]\"]:9: in function <[string \"safecall Dispatcher[2]\"]:5>\n(tail call): ?\nInterface\\AddOns\\Ace3\\AceTimer-3.0\\AceTimer-3.0.lua:140: in function <Interface\\AddOns\\Ace3\\AceTimer-3.0\\AceTimer-3.0.lua:114>\n"
Got this today on my Mage in AV. Most recent update of SCT/SCTD (66587/65634). Happened while fighting another Mage and she used counterspell on me (improved)
Also while looking through my log I found this error from sometime yesterday.
Date: 2008-03-27 14:53:38
ID: 8
Error occured in: Global
Count: 1
Message: ..\AddOns\sctd\sctd.lua line 485:
attempt to concatenate local 'msg1' (a nil value)
Debug:
(tail call): ?
sctd\sctd.lua:485: DisplayText()
sctd\sctd.lua:447: ?()
...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:146:
...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:146
[string "safecall Dispatcher[13]"]:4:
[string "safecall Dispatcher[13]"]:4
[C]: ?
[string "safecall Dispatcher[13]"]:13: ?()
...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: Fire()
Ace3\AceEvent-3.0\AceEvent-3.0.lua:70:
Ace3\AceEvent-3.0\AceEvent-3.0.lua:69
Arandorus, gonna have to give me more information than that. What were you doing? Raid/group/solo? etc...
I've gotten that error randomly as well. Mostly on my Mage when in AV. Happens at random times it seems as it popped up once while riding up the map at the start.
I rolled back to 40622 and it still didn't work. I think something may have changed on blizzard's end. I went so far as to dust off "moveanything" but it was not able to identify the frame for the pvp objective slider.
I did read somewhere that blizz now made it so you couldn't draw frames off screen, so that's probably why it's ending up in the middle.
I suspect all having this problem have our minimap at the bottom. So, with the mover not working, it tries to draw it in the default position under the minimap, which is offscreen, so it boots it to the center.
Actually.. My map is in the default position and I'm seeing this error as well.
0
0
So am I going to be unable to make a default profile?
0
0
1) The frame never updated correctly after these errors and after reseting the profile.
2) I could see all of the classes after some time but their names/health bars were missing.
3) This was with 67206 build
4) I am pulling these from swatter's saved variables. so formating might be off.
0
0
Got this today on my Mage in AV. Most recent update of SCT/SCTD (66587/65634). Happened while fighting another Mage and she used counterspell on me (improved)
Also while looking through my log I found this error from sometime yesterday.
0
I've gotten that error randomly as well. Mostly on my Mage when in AV. Happens at random times it seems as it popped up once while riding up the map at the start.
0
Actually.. My map is in the default position and I'm seeing this error as well.