world_names.json is broken

#1 - May 28, 2013, 9:14 a.m.
Blizzard Post

Hello,

Since the update, the world_names.json is broken…

https://api.guildwars2.com/v1/world_names.json

World’s list is incomplete…

[{"id":“1018”,“name”:“Northern Shiverpeaks”},
{"id":“1006”,“name”:“Sorrow’s Furnace”},
{"id":“1011”,“name”:“Stormbluff Isle”},
{"id":“1007”,“name”:“Gate of Madness”},
{"id":“2002”,“name”:"Desolation"},
{"id":“1012”,“name”:"Darkhaven"},
{"id":“1008”,“name”:“Jade Quarry”}]

#4 - May 28, 2013, 9:56 a.m.
Blizzard Post

This can happen during the process of distributing a new patch of the game. That’s what happened in this case — the world names should be ok now. Also, events should have stabilized. Any events not in the list should be considered ‘inactive’.

#6 - May 28, 2013, 2:03 p.m.
Blizzard Post

Should we get in the habit then of interpreting these lists as “items/recipes/events found since the last server reset”, which then, for some relatively rare event chains, could be a day or so before some world discovers it, and I could foresee some being every other week/etc.

No, this is just a side-effect of how the event API works. All types of discovery are persistent; discovery doesn’t reset after a build. During a new patch, some of the APIs can temporarily show fewer results than normal while the new servers come online, but this should quickly resolve itself.

I have a script which dumps all the items and recipes to a local store. When I rerun it, it will download the list of ID’s, and then fetch any objects it didn’t have in the last run. I see 6-10 new items per day in recent days. I’d expect this to be asymptocially zero on non-patch days.

This is a good caching behavior.