23 - Error directly after reaching 80
What steps will reproduce the problem?
1. Level a character from 79 to 80
2. _Don't reload UI in any way_
3. Mouse over TitanWG
What is the expected output? What do you see instead?
One would expect to see the usual popup. However, since the player has just reached the level requirement for VoA, the popup tries to display the uninitialized VoAData entry for the player.
What version of the product are you using?
1.1.5, but comparing the code interacting with VoAData it still seems to be there for 1.1.6.4.
Do you have an error log of what happened?
Attempt to index '?' at line 373: nil.
Rephrasing that to 1.1.6.4 that would be line 391.
Please provide any additional information below.
This problem can be fixed by an extra check inserted before line 391:
if not VoAData[TitanWG_realm] then
VoAData[TitanWG_realm] = {}
VoAData[TitanWG_realm][TitanWG_player] = {}
else if not VoAData[TitanWG_realm][TitanWG_player] then
VoAData[TitanWG_realm][TitanWG_player] = {}
end
This code has not been tested, mainly because I don't reach level 80 every day :D.
| User | When | Change |
|---|---|---|
| Rothpada | Nov 20, 2009 at 16:54 UTC | Changed status from Accepted to Fixed |
| Rothpada | Nov 19, 2009 at 19:04 UTC | Changed milestone from None to 1.1 Changed component from None to TitanWG |
| Rothpada | Nov 19, 2009 at 19:04 UTC | Changed status from New to Accepted |
| CMTitan | Nov 18, 2009 at 15:36 UTC | Create |
- 1 comment
- 1 comment
Facts
- Last updated
- Nov 20, 2009
- Reported
- Nov 18, 2009
- Status
- Fixed - Developer made requested changes. QA should verify.
- Type
- Defect - A shortcoming, fault, or imperfection
- Priority
- Medium - Normal priority.
- Votes
- 0
- Component
- TitanWG
- Milestone
- 1.1
Reported by
Possible assignees
-
- Manager
- Author
- Reply
- #1
Rothpada Nov 19, 2009 at 19:04 UTC - 0 likesNice ;) A funny thing is I have a DK that just hit 80 but I must not have moused over the addon until I had reloaded the UI somehow. Anyhow, what you surmise sounds exactly correct. I'll put a fix in and push it out in 1.1.7.1. Thanks again CMTitan, m