I would like to request specific information exposed via the Mumble Link API.
I know that we already use a lot of space in there but as discussed there is still much room for more information in the extended context.
Previously I requested some states from the customized soundtrack system (Ref.: https://wiki.guildwars2.com/wiki/Customized_soundtrack ) to be exposed that would help with seamless overlay development and popular marker and path helper tools:
~ = As seen used by the customized soundtrack system.
$ = A well known and highly popular (and tolerated) third party addon exposes it already for other developers to use.
I would like to still expand on that with information that would improve readability of the continents API endpoint and its very complex subresources.
The information I would like to see are ids relevant to the map id that is already exposed:
Most importantly I'd like to explain why I would want the floor id. Floor ids are arbitrary values that do not just depend on height of the player and differ per map (i.e. floor 1 on Queensdale can be different compared to floor 1 on another map.). They cannot be calculated and it makes it difficult to distinguish between sectors given the subresource found under the continents endpoint and impossible on non-flat maps for the reasons explained earlier.
Knowing the sector could save resources and performance for marker and path systems and augmented stuff.
On the other hand giving the sector id directly would reduce queries as one does not need to query the floors first to get a specific sector object. Same goes for the continent id.
So because there aren't many more sizes to a maps context (continent > region > map> floor > sector) I request that you consider - if you look at the complexity of the "continents" subendpoints - that it makes sense to just expose all four of above ids - while we are at exposing the most important of them that is floor - to improve access to the very complex continents endpoint.
Furthermore, it was stated that the API nor MumbleLink exposes enough data to detect the current floor which means that the continents endpoint and a large portion of its data contained in subresources is in fact useless for augmented overlay developers that rely on MumbleLink. A pity because it would open up huge space for improvements in regards to performance and resource handling.
Ref.: https://github.com/arenanet/api-cdi/pull/2 (Highlighted statement: https://i.imgur.com/nAdaOSD.png)