Goto no longer working
 

Just today I noticed that /way and /carb goto no longer function. I have downloaded the latest git release and restarted wow.

That's strange, because it still works for me:

Maybe you forgot the last digits? They're required, even if they're 0.

He means out of zone waypoints do not work, it's something I already knew and was trying to decide the best way to restore it.

You use to be able to /goto Stormwind 44 32

You could even use just partial name /goto Storm 44 32 would place it in the first zone that matches Storm

But now Carbonite has no idea the map names to translate it. I could just restore the map names but that leads to the original reason map names were removed, /goto nagrand would have no idea which nagrand.

If there are multiple matches for the same position, we could display a list to let the user choose; internally, the list is linked to a waypoint with a mapid instead of the name. We could iterate over Nx.Zones and find those whose beginning match the string (or if its already a map id, use that one).

What I really need to find out is how Tomtom is doing it and handling it. The entire reason /way was added as an alias to /carb goto was to maintain the ability for people to create macro's that worked with either one, so if someone went to wowhead and saw a comment saying:

"easy pathing macro for tomtom"
/way westfall 33.9 33.2 Bucket behind tree
/way elwynn 48.2 48.1 Under the hogs head
/way redridge 88.2 48.9 Look up look way up

The exact same macro would work for Carb.

In that case, we should probably chose either the closest one or the one closest to the player's level (e.g. old Nagaland for players below level 90).

It is far easier to chose the id closest to the current id (which is probably also the desired behaviour). I have just committed a fix to just do that.