Region keying is broken in CensusPlus

[bringoutyourdead]

I have just discovered that CensusPlus is no longer correctly identifying the Region based upon the location of the logged in character.

Blizzard has changed something again.. sigh.

Example

US player creates an EU Battlenet account
creates a EU world of warcraft account
logs in from US region using enGB Locale
goes to German tab and logs in on German named realms.
Census works fine.
logs in on German realm that shares the same name as US realm.

CensusPlus isn't getting the region match and falls back to actual location of Player.. so realm is treated as US realm.
in game database is purged to protect data integrity as region has changed (as far as CensusPlus is concerned.)

DO NOT try to census other region realms if the same realm name exists in your own region.

[bringoutyourdead]

Refinement -- problem not as large as first thought.

One or more data entries in lib:RealmID has a bad capitalization on the realm name so no match returned, this caused my US client to default to US region.

If you find that your data is purged for some unknown reason..
open the CensusPlus window as you re-census the possibly problem realm.
Let me know which realm caused you the data loss (shows as wrong region)

I will be scanning EU realms from the US to see if I can catch any more naming errors.
If someone from the EU area would be willing to return the favor of running single census on US/Oceanic realm, it would be appreciated.

I expect any problems will be with realm names containing special characters .. such as , ` or -, but any realm might have a typo in the name

[bringoutyourdead]

EU-Aman'Thul

Oh Thank you Blizzard!!!

Every where I look the name for the realm is Aman'Thul

but if you do the API call GetRealmName while on that realm it returns the name Aman'thul

you can see for yourself if interested.. ignore the Blizzard warning about running scripts

/script local realm = GetRealmName(); print(realm)

sigh.