Dear visitor, welcome to Gaming Insight Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.
BUG: Akil'zon - Range finder (fixed)
Even though you write that it's fixed by Blizzard, this still cause the Range Finder on Akil'zon to display an error..
Quoted from ""Frontpage""
[28/04/2011] Update #2: The map-based range check frame (distances other than 10, 11, 15 and 2and the arrow sometimes don't work properly in Cataclysm instances. This is a bug in WoW, note that the default World Map is also affected; you sometimes just can't see other raid members there. (Update 02/05/2011: Blizzard confirmed this issue, it will be fixed in the next patch.) Fixed by Blizzard.
Re: BUG: Akil'zon - Range finder
Looks like we have a wrong mapName then I think.
If you are in Zul'Aman could you open the map -> close it and then use this command:
and post the result?
(it should return something like: "ZulAman", number, number )
If you are in Zul'Aman could you open the map -> close it and then use this command:
|
|
Source code |
1 |
/dump GetMapInfo() |
(it should return something like: "ZulAman", number, number )
Requesting combatlogs + chatlogs (how to @ http://ninjapull.de/forumBridge/index.php?f=1&t=2691&p=31971&rb_v=viewtopic#p9577)
Re: BUG: Akil'zon - Range finder
Okay, did a quick test myself ...
/script print("DBM MapSizes ZulAman Height variable") --> prints correctly the height specified in MapSizes.lua (thus is loaded correctly)
/dump GetMapInfo() --> Like you said, returns "ZulAman" as mapName
/dump GetCurrentMapDungeonLevel() --> return "0"
This mostly means that the map is not set properly, so I did a:
/script SetMapToCurrentZone() --> Should set the map correctly (method also used in the RangeFrame function in case this happens)
after done that I did again:
/dump GetCurrentMapDungeonLevel() --> still returns "0"
So either they use "0" as the floor (mostly it starts at floor "1" and this is also specified in LibMapData (link)
Because of this we cannot calculate the distance between you and other people as we do not know the map dimensions.
/script print("DBM MapSizes ZulAman Height variable") --> prints correctly the height specified in MapSizes.lua (thus is loaded correctly)
/dump GetMapInfo() --> Like you said, returns "ZulAman" as mapName
/dump GetCurrentMapDungeonLevel() --> return "0"
This mostly means that the map is not set properly, so I did a:
/script SetMapToCurrentZone() --> Should set the map correctly (method also used in the RangeFrame function in case this happens)
after done that I did again:
/dump GetCurrentMapDungeonLevel() --> still returns "0"
So either they use "0" as the floor (mostly it starts at floor "1" and this is also specified in LibMapData (link)
Because of this we cannot calculate the distance between you and other people as we do not know the map dimensions.
Requesting combatlogs + chatlogs (how to @ http://ninjapull.de/forumBridge/index.php?f=1&t=2691&p=31971&rb_v=viewtopic#p9577)
Re: BUG: Akil'zon - Range finder (fixed)
it was fixed back in 5735, last core release was 5722
that said, several beta's have been tagged and put on curse since then.
also, see the sticky
<!-- l --><a class="postlink-local" href="http://www.deadlybossmods.com/phpbb3/viewtopic.php?f=2&t=1207">viewtopic.php?f=2&t=1207</a><!-- l -->
that said, several beta's have been tagged and put on curse since then.
also, see the sticky
<!-- l --><a class="postlink-local" href="http://www.deadlybossmods.com/phpbb3/viewtopic.php?f=2&t=1207">viewtopic.php?f=2&t=1207</a><!-- l -->
Quoted
*Anything marked as (Fixed) is already fixed in latest alpha and may or may not be fixed in current release but will be in next.
*Anything marked as (Confirmed) has been confirmed but has not had a fix applied yet.
*Anything marked as (Needs Review) is already known but needs more information or review from other authors.
*Anything marked as (Duplicate) already has an open thread on same issue.
*Anything marked as (Waiting) needs more information from poster.
*Anything marked as (Invalid) issue not related to DBM, working as intended, or is was fixed BEFORE last stable release (which means yours is broken because you're out of date).