**Floor ids are completely arbitrary and differ per map. Current floor detection is impossible and thus current sector detection BREAKS on maps with sectors lying ontop of each other.**
Another thing mentioned is reducing overall queries to said endpoint. Given sector id directly would also improve it as you don't have to query for floor to get the current sector (if given floor id). For said endpoint it makes sense to just throw all four ids in there, especially floor.
**Example**
Sector detection on a flat map: https://gfycat.com/CompetentReadyGilamonster
This would __not__ work flawlessly on - for example - Verdant Brink with sectors being ontop of each other as there is no way of calculating a floor.
Floor is the most important out of the four but because it makes little sense to not include all four **while we are at it**(!) I listed them all four. This would give us the complete hierarchy of IDs of a maps context from biggest to smallest.
**continent > region > map > floor > sector.**
Perfectly suited for any of said complex subresources of the continents endpoint such as:
``https://api.guildwars2.com/v2/continents//floors//regions//maps//sectors?ids=all``
https://api.guildwars2.com/v2/continents/1/floors/1/regions/4/maps/15/sectors?ids=all
And little extra weight on the overall size of Mumble Link since we are only dealing with those ids.
It's true that it's soothening any existential dread. Although it has a lonely characteristic which it shouldn't have considering its accessibility. It's an opportunity for any butt passing the central well area. I rate the "staring into the void"-bench 5/10