I noticed that Destinations shows all the POI's as unknown now.
Further investigation shows me that GetCurrentMapZoneIndex() returns a value ONE LOWER than before the latest update for ALL areas.
Example:
While in Deshaan, GetCurrentMapZoneIndex() should return 11, but it returns 10.
I noticed that Destinations shows all the POI's as unknown now.
Further investigation shows me that GetCurrentMapZoneIndex() returns a value ONE LOWER than before the latest update for ALL areas.
Example:
While in Deshaan, GetCurrentMapZoneIndex() should return 11, but it returns 10.
The indexes of zone names are different: GetZoneNameByIndex(zoneIndex)
If you use a multi-language extraction as a lookup table or zoneIndex as language-invariant key in your saved variables, you need to re-evaluate.
By looking at just a few of them, you may think it is just a simple shift by -1 to make room for IC. But there are more deleted, inserted and moved zones.
Yeah checking deeper revealed that (at least in regards to the zones I use) then all but Craglorn, Glenumbra, Rivenspire, Stonefalls and Stormhaven has shifted - 1.
Yeah checking deeper revealed that (at least in regards to the zones I use) then all but Craglorn, Glenumbra, Rivenspire, Stonefalls and Stormhaven has shifted - 1.
I'll just update my data accordingly
This is my translation table: (-1=deleted, missing=unchanged)
It was created by comparing zone name of index case-insensitive from (now old) live and pts.
May this helps
This is my translation table: (-1=deleted, missing=unchanged)
It was created by comparing zone name of index case-insensitive from (now old) live and pts.
May this helps
Linear Mode
