You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While TWoW serves up maps and unit positional data for most of their instances, many are multi-floored and don't automatically set the correct floor (or even show multiple floors) both by default or by SetMapToCurrentZone(). This results in proximity only working within the boundaries of the first floor of those instances. Those boundaries may contain whole or sections of other floors in which case proximity will still work with the first floor map, but if the player or group member moves outside the bounds there's no positional data to use.
This isn't a huge issue. It just turns it back into the functionality of default servers where instances don't have maps and proximity is limited to 28 yards(follow range) or spellcast checks.
There's a possibility that I could "fix" this within NotGrid, by doing.. some sorts of checks for every instance that's messed up and figuring out what floor to set it too based on X.. maybe if bossmob is in range then set to known floor. Or maybe have an option not to auto setmaptozone and have the player manually change their map to the correct floor. Both solutions are quite silly and I'm basing these ideas off of low level instances. If BWL/AQ/Naxx all set their floors correctly then I don't really care about it. And if they don't.. well I'm not leveling and gearing up to figure it out. I'll leave this as a known bug, but consider it to be the server's issue to fix.
The text was updated successfully, but these errors were encountered:
While TWoW serves up maps and unit positional data for most of their instances, many are multi-floored and don't automatically set the correct floor (or even show multiple floors) both by default or by SetMapToCurrentZone(). This results in proximity only working within the boundaries of the first floor of those instances. Those boundaries may contain whole or sections of other floors in which case proximity will still work with the first floor map, but if the player or group member moves outside the bounds there's no positional data to use.
This isn't a huge issue. It just turns it back into the functionality of default servers where instances don't have maps and proximity is limited to 28 yards(follow range) or spellcast checks.
There's a possibility that I could "fix" this within NotGrid, by doing.. some sorts of checks for every instance that's messed up and figuring out what floor to set it too based on X.. maybe if bossmob is in range then set to known floor. Or maybe have an option not to auto setmaptozone and have the player manually change their map to the correct floor. Both solutions are quite silly and I'm basing these ideas off of low level instances. If BWL/AQ/Naxx all set their floors correctly then I don't really care about it. And if they don't.. well I'm not leveling and gearing up to figure it out. I'll leave this as a known bug, but consider it to be the server's issue to fix.
The text was updated successfully, but these errors were encountered: