Announcement

**cabby** · January 11, 2010, 06:10 PM

It's showing as no waypoint addon so go into your Zygor options and in the waypoint section select TomTom from the dropdown and then reload the UI and see if that fixes it.

**lecharentais** · January 3, 2011, 03:47 AM

I had the very same problem yesterday, I installed Tom Tom, used it, but there still are several waypoints (Badlands, for example) that are not recognized by Zygor... Kind of annoying I must say...

Any suggestion?

**cabby** · January 3, 2011, 04:03 AM

Try Carbonite instead of TomTom. Carbonite seems to do a bit better but there are still some dead zones I think, and those issues are out of the Zygor/Carbonite author's hands I believe.

**Cartman** · January 3, 2011, 04:21 AM

Originally posted by lecharentais View Post

I had the very same problem yesterday, I installed Tom Tom, used it, but there still are several waypoints (Badlands, for example) that are not recognized by Zygor... Kind of annoying I must say...
Any suggestion?

Can you give the exact guide and step number where you have the problem? Also what language is your WoW client?
Let me guess, you are using a french WoW client? There seems to be another changed zone name. LibBabbleZone say Badlands = Terres ingrates. I think it is now Terres Ingrates.
you can check it by typing the following command in the chat window:
/script print(GetRealZoneText())

**lecharentais** · January 3, 2011, 04:51 AM

Absolutely, I'm french ^^ I dit not understand what you suggested me to do?

I could track back the pages, but now I'm in Northend, and it would be veeeeeeery long to get back to this specific step...

And, I tried Carbonite, but several locations are wrong, and furthermore some flypaths are just not available anymore for the Alliance (They seem to be Hordish now, but still appear in the guide).

**Cartman** · January 3, 2011, 05:01 AM

Blizzard messed around with the localization of zone names. They capitalized some zone names.
Badlands was formerly Terres ingrates but now seems to be spelled Terres Ingrates with the capital I.
The /script command (just copy it from my previous post and paste it in the chat window) shows the real zone name as the game spells it. If you are in a zone where a waypoint does not work you can run this command to show if it is different from the zone name in the guide window where the coordinates are. The zone names inside the guide come from a library called LibBabbleZone which translates the english zone names to other languages. This library needs to be updated if Blizzard changes zone names.
There were some zones already fixed in the library but there still are several zone names that need to be reviewed.
I'll look into this now to get at least the zones corrected that the guide uses.

**Cartman** · January 3, 2011, 05:04 AM

Originally posted by lecharentais View Post

And, I tried Carbonite, but several locations are wrong, and furthermore some flypaths are just not available anymore for the Alliance (They seem to be Hordish now, but still appear in the guide).

Do you use an up to date guide version?
There are some flight points in the 1-60 section that don't exist anymore (Auberdine) or switched sides (Southshore). A 2.0 guide version will not work with the changed 1-60 content.

**lecharentais** · January 3, 2011, 11:02 AM

I can't exactly answer to you, all I can say to you is that I bought the guide (excellent guide, anyway, combined with Carbonite) on friday, so I think it's up to date.

**Cartman** · January 3, 2011, 12:48 PM

If you encounter such things as completely wrong coordinates you can post them in the bugs section here so that it can be looked into by the developers.
The problem with the missing waypoint arrow in some zones with a french client should be solved soon, I uploaded a changed file so the developers can include it in the guide until the official library gets updated.

Announcement

No waypoint arrow

No waypoint arrow

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment