Originally Posted by Shinni
Most of this is probably not possible because a map and a zone are two completely different things.
A map is what you see on the ingame map, the 2d representation of some area.
A zone is a complete 3d area. Essentially everything separated by a loading screen is a zone. For instance all of the overworld Craglorn is one zone, and each delve in craglorn is another individual zone, but Belkarth is part of the Craglorn overworld 3d area and thus is not an individual zone.
If a player is in Belkarth for instance, the map's name is Belkarth but the zone's name is Craglorn.
So for instance WouldProcessMapClick to return a zoneId/Index wouldn't make any sense because when you have the craglorn map open and your cursor is over belkarth, it would just return the current zoneId.
|
While you are right that a zone and a map are not the same thing, for the functions in my post it's not true.
The functions in question only cover the zone maps + tamriel and aurbis (everything you see in the location tab on the map).
Tamriel and Aurbis currently return -1 for GetCurrentMapZoneIndex(), but they could just add 2 placeholder ids for them.
WouldProcessMapClick also does not return a mapIndex for cities like Belkarth (you get true, nil in that case).
So almost all of these are covered by the zone system and thus it should be easy to replace them.
GetMapName and GetPlayerLocationName probably won't be as easy to replace, but they could at least make sure that they return zone names where they are available in order to make them compatible with the other functions.