198 - Error with patch 4.0.3a
Upon logging in, the following error occurs using 4.0.1 release 3:
Date: 2010-11-23 18:00:30
ID: 27
Error occured in: Global
Count: 4
Message: ..\AddOns\tomQuest2\tomQuest2.lua line 1555:
attempt to index local 'textCell' (a nil value)
- 4 comments
- 4 comments
Facts
- Last updated
- Jan 05, 2012
- Reported
- Nov 24, 2010
- Status
- Declined - We decided not to take action on this ticket.
- Type
- Defect - A shortcoming, fault, or imperfection
- Priority
- Medium - Normal priority.
- Votes
- 0
- Reply
- #4
gagou Jan 05, 2012 at 08:44 UTC - 0 likesI've closed all tickets, so if someone really want some fix or new features please post.
- Reply
- #3
gagou Nov 26, 2010 at 08:57 UTC - 0 likesI have made a few internal changes to achievements tracking to take into account the supermassive achievement. If I'm not mistaken it's the only achievement with a status bar criteria and a boolean criteria, I need to do a few tests and I'll make a release
- Reply
- #2
roncli Nov 25, 2010 at 19:21 UTC - 0 likesSorry, I don't know what I was thinking when I posted that. -_- Here's the stack:
Debug: (tail call): ? tomQuest2\tomQuest2.lua:1555: tomQuest2\tomQuest2.lua:1554 tomQuest2\tomQuest2.lua:1619: tomQuest2\tomQuest2.lua:1592 tomQuest2\tomQuest2.lua:1703: tomQuest2\tomQuest2.lua:1685 tomQuest2\tomQuest2.lua:2088: tomQuest2\tomQuest2.lua:2039 tomQuest2\tomQuest2.lua:5050: ?() ...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147: ...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147 [string "safecall Dispatcher[1]"]:4: [string "safecall Dispatcher[1]"]:4 [C]: ? [string "safecall Dispatcher[1]"]:13: ?() ...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: Fire() Ace3\AceEvent-3.0\AceEvent-3.0.lua:120: Ace3\AceEvent-3.0\AceEvent-3.0.lua:119
I've narrowed it down... Tracking the achievement "Supermassive" (from Lich King Raid, 10 or 25 player) appears to be causing the error.
- Reply
- #1
gagou Nov 25, 2010 at 14:17 UTC - 0 likesDo you have a lire detailed error report given by bugsack or any error reporting tool?
With so few information I'm not able to track the error correctly as the function with the error is called very often in the code.