Looks like some of the API is broken...
Author of WvW Intelligence here.
Definitely appears to be an API issue. I’ve updated my site to better indicate the errors that are occurring.
I might even speculate that the China severs are being added to the world names API. Who knows?
Hopefully this means good things!
Can someone send ma a cached world_names.json?
gw2wvw.org
Thank you!
gw2wvw.org
I’m a bit disappointed that this has been going on for 4 days now and we haven’t even gotten acknowledgement of the issue.
Definitely not instilling confidence in the API.
Hi All, thank you for the report. Turns out there were more APIs affected by megaservers that I originally thought. I am working on a fix and hope to have it out shortly.
Hi All, thank you for the report. Turns out there were more APIs affected by megaservers that I originally thought. I am working on a fix and hope to have it out shortly.
Hi !
I know this is probably not the right thread, but I really need a fast answer since the API v1 is 1 year old and so are a lot of domain names we bought when creating sites 1 year ago ==> is there any chance that an "api v2" comes out and revives event-api-based sites by using megaservers ? => should I renew my domain name ?
https://forum-en.gw2archive.eu/forum/community/api/Events-API-2-0
thanks
Eowyn
Hi All, thank you for the report. Turns out there were more APIs affected by megaservers that I originally thought. I am working on a fix and hope to have it out shortly.
Hi !
I know this is probably not the right thread, but I really need a fast answer since the API v1 is 1 year old and so are a lot of domain names we bought when creating sites 1 year ago ==> is there any chance that an "api v2" comes out and revives event-api-based sites by using megaservers ? => should I renew my domain name ?
https://forum-en.gw2archive.eu/forum/community/api/Events-API-2-0
thanks
Eowyn
Don’t take this the wrong way, and it’s entirely my own opinion, but I don’t think you should expect an answer (or indication) from ANet on the state of your domain renewals. Even still, these questions should be sent directly to ANet’s community managers, and not blindly posted on forum threads.
It’s a bit…ummm…not their problem? More explicitly, they (or any company in a similar position) aren’t beholden to your particular business needs because they’ve provided public APIs.
Again, these thoughts are my own. I would expect that if dev energy is spent on this forum, it would be focused on only those discussions which are universally relevant to all API developers.
No they don’t have to decide whether I should renew my domain or not.
No they aren’t beholden on what you call my particular business.
But they probably know whether they have mid term plans of reworking the events API to make it work with MegaServers.
And API users (probably not only me) need info about it so that we can decide whether to renew domain names or not; info which imho Anet should give hints about.
I know that can’t promise "we"ll make event API 2.0 in 08/2014".
But they can say either
- events will probably not have a new API now, we’re sorry MegaServer system broke a few sites for good
OR
- we [may / are talking about / have plans for / don’t know yet if ] release an Event API based on MegaServers that could be used to adapt sites that were using the old API. No promise, it’s up to you to decide if you want to renew your domain in case this new API ends up being released
Any updates??? It has been 8 hours since the last dev post.
Jade Quarry Commander
I know this is probably not the right thread, but I really need a fast answer since the API v1 is 1 year old and so are a lot of domain names we bought when creating sites 1 year ago ==> is there any chance that an "api v2" comes out and revives event-api-based sites by using megaservers ? => should I renew my domain name ?
https://forum-en.gw2archive.eu/forum/community/api/Events-API-2-0
thanks
Eowyn
If you just use some critical thinking, it’s pretty obvious that the current way megaservers work would not be amenable to event-tracking. How do you know what megaserver shard you’re on? If the API tells you that shard #4 has X event up, how do you reasonably get yourself onto that shard?
Any realistically useful implementation of the API would require nontrivial changes or added features to megaservers, so I highly doubt anything will happen in the near future.
Hi All, thank you for the report. Turns out there were more APIs affected by megaservers that I originally thought. I am working on a fix and hope to have it out shortly.
Thanks for the update!
It’s been 4 days now – Still no update? …
Any updates? Might as well put my programming on hold for a while….
Jade Quarry Commander
I built a quick array table for anyone using PHP. This got around having to try to come up with more creative imports.
$world[1001] = "Anvil Rock";
$world[1002] = "Borlis Pass";
$world[1003] = "Yak's Bend";
$world[1004] = "Henge of Denravi";
$world[1005] = "Maguuma";
$world[1006] = "Sorrow's Furnace";
$world[1007] = "Gate of Madness";
$world[1008] = "Jade Quarry";
$world[1009] = "Fort Aspenwood";
$world[1010] = "Ehmry Bay";
$world[1011] = "Stormbluff Isle";
$world[1012] = "Darkhaven";
$world[1013] = "Sanctum of Rall";
$world[1014] = "Crystal Desert";
$world[1015] = "Isle of Janthir";
$world[1016] = "Sea of Sorrows";
$world[1017] = "Tarnished Coast";
$world[1018] = "Northern Shiverpeaks";
$world[1019] = "Blackgate";
$world[1020] = "Ferguson's Crossing";
$world[1021] = "Dragonbrand";
$world[1022] = "Kaineng";
$world[1023] = "Devona's Rest";
$world[1024] = "Eredon Terrace";
Founder, Gaiscioch Community [GSCH] | Gaiscioch Magazine | Twitch | YouTube | Twitter
Proud Resident of Mercenary Server Sanctum of Rall | 6 Year Extra-Life Charity Event Participant
I built a quick array table for anyone using PHP.
https://github.com/codemasher/gw2api-tools/blob/master/json/gw2_worlds.json
$worlds = json_decode(file_get_contents('gw2_worlds.json'), true);
foreach($worlds as $w){
// do stuff...
}
The API fixes will go out with our upcoming 5/20 release. I wasn’t sure of the date until recently.
Regarding a megaserver-compatible live events API: For a few reasons, there are no plans to build this in the short/medium term, unfortunately.
The API fixes will go out with our upcoming 5/20 release. I wasn’t sure of the date until recently.
And that date is?
The API fixes will go out with our upcoming 5/20 release. I wasn’t sure of the date until recently.
And that date is?
5/20?? Or: 20.05.2014.
oeps i had read v 2.0 release. guess i’m not quite awake yet.
my apologies
I hope this isn’t the intended result of the world_names fix…:
[{"id":"30","name":null},
{"id":"114","name":null},
{"id":"80","name":null},
{"id":"107","name":null},
{"id":"134","name":null},
{"id":"20","name":null},
{"id":"110","name":null},
{"id":"76","name":null},
{"id":"25","name":null},
{"id":"117","name":null},
{"id":"27","name":null},
{"id":"16","name":null},
{"id":"75","name":null},
{"id":"99","name":null},
{"id":"35","name":null},
{"id":"17","name":null},
{"id":"22","name":null},
{"id":"69","name":"Istan [D]"},
{"id":"93","name":null},
{"id":"128","name":null},
{"id":"147","name":null},
{"id":"82","name":null},
{"id":"31","name":null},
{"id":"81","name":null},
{"id":"55","name":null},
{"id":"2","name":"Borlis Pass [D]"},
{"id":"18","name":null},
{"id":"121","name":null},
{"id":"133","name":null},
{"id":"154","name":null},
{"id":"38","name":null},
{"id":"15","name":null},
{"id":"97","name":null},
{"id":"155","name":null},
{"id":"137","name":null},
{"id":"151","name":null},
{"id":"26","name":null},
{"id":"132","name":null},
{"id":"111","name":null},
{"id":"122","name":null},
{"id":"77","name":null},
{"id":"6","name":"Sorrow's Furnace [D]"},
{"id":"140","name":null},
{"id":"58","name":null},
{"id":"146","name":null},
{"id":"12","name":null},
{"id":"71","name":null},
{"id":"49","name":null},
{"id":"8","name":"Jade Quarry [D]"},
{"id":"139","name":null},
{"id":"90","name":null},
{"id":"41","name":null},
{"id":"86","name":null},
{"id":"68","name":"Blacktide [D]"},
{"id":"56","name":null},
{"id":"88","name":null},
{"id":"36","name":null},
{"id":"126","name":null},
{"id":"14","name":null},
{"id":"73","name":null},
{"id":"23","name":null},
{"id":"78","name":null},
{"id":"3","name":"Yak's Bend [D]"},
{"id":"72","name":null},
{"id":"19","name":null},
{"id":"92","name":null},
{"id":"157","name":null},
{"id":"109","name":null},
{"id":"83","name":null},
{"id":"130","name":null},
{"id":"104","name":null},
{"id":"65","name":"Kodonur [D]"},
{"id":"59","name":null},
{"id":"7","name":"Kaineng [D]"},
{"id":"95","name":null},
{"id":"145","name":null},
{"id":"131","name":null},
{"id":"57","name":null},
{"id":"9","name":"Fort Aspenwood [D]"},
{"id":"119","name":null},
{"id":"113","name":null},
{"id":"87","name":null},
{"id":"148","name":null},
{"id":"66","name":"Gandara [D]"},
{"id":"32","name":null},
{"id":"47","name":null},
{"id":"60","name":null},
{"id":"37","name":null},
{"id":"124","name":null},
{"id":"129","name":null},
{"id":"108","name":null},
{"id":"5","name":"Maguuma [D]"},
{"id":"141","name":null},
{"id":"50","name":"Dragon's Grove [D]"},
{"id":"98","name":null},
{"id":"127","name":null},
{"id":"143","name":null},
{"id":"156","name":null},
{"id":"118","name":null},
{"id":"42","name":null},
{"id":"40","name":null},
{"id":"158","name":null},
{"id":"70","name":"Vabbi [D]"},
{"id":"94","name":null},
{"id":"123","name":null},
{"id":"64","name":null},
{"id":"48","name":null},
{"id":"125","name":null},
{"id":"61","name":null},
{"id":"74","name":null},
{"id":"52","name":null},
{"id":"150","name":null},
{"id":"91","name":null},
{"id":"84","name":null},
{"id":"51","name":null},
{"id":"62","name":null},
{"id":"21","name":null},
{"id":"136","name":null},
{"id":"29","name":null},
{"id":"100","name":null},
{"id":"144","name":null},
{"id":"63","name":null},
{"id":"116","name":null},
{"id":"10","name":null},
{"id":"33","name":null},
{"id":"4","name":"Henge of Denravi [D]"},
{"id":"44","name":null},
{"id":"106","name":null},
{"id":"105","name":null},
{"id":"39","name":null},
{"id":"85","name":null},
{"id":"102","name":null},
{"id":"115","name":null},
{"id":"120","name":null},
{"id":"34","name":null},
{"id":"11","name":null},
{"id":"45","name":null},
{"id":"103","name":null},
{"id":"89","name":null},
{"id":"54","name":null},
{"id":"138","name":null},
{"id":"152","name":null},
{"id":"1","name":"Anvil Rock [D]"},
{"id":"53","name":null},
{"id":"96","name":null},
{"id":"43","name":null},
{"id":"67","name":"Kodash [DE] [D]"},
{"id":"24","name":null},
{"id":"112","name":null},
{"id":"153","name":null},
{"id":"135","name":null},
{"id":"28","name":null},
{"id":"101","name":null},
{"id":"46","name":null},
{"id":"149","name":null},
{"id":"142","name":null},
{"id":"13","name":null},
{"id":"79","name":null}]
Ah rats! Yes, turns out there was another aspect of megaservers I didn’t understand and wasn’t apparent in the development environment. We will need to temporarily disable that API until I can get it fixed for real.
I hope this isn’t the intended result of the world_names fix…:
snip
Good to see you already posted that, I was about to point that out aswell, seeing how i was going to use that api to make use of the wvw matches api. Guess I will have to settle for a static list for now.
Megaserver really does more harm than good. ._.
Ah rats! Yes, turns out there was another aspect of megaservers I didn’t understand and wasn’t apparent in the development environment. We will need to temporarily disable that API until I can get it fixed for real.
Any update on this?
Please give us the (dynamic) events api. It’s a powerfull tool for people to keep track on collection specific events. It is a positive way people stick to the game. Now you travel to a place in the hope that specific event is live. If i have to wait to long, i leave the area, resulting indisconfort and more easily leaving the game totaly. So please make it easy to see which event is running where. Keep you’re beautyfull game running the way gamers like it…not the way investers want it.
Please give us the (dynamic) events api. It’s a powerfull tool for people to keep track on collection specific events. It is a positive way people stick to the game. Now you travel to a place in the hope that specific event is live. If i have to wait to long, i leave the area, resulting indisconfort and more easily leaving the game totaly. So please make it easy to see which event is running where. Keep you’re beautyfull game running the way gamers like it…not the way investers want it.
Problem is:
- You currently have no way of telling what megaserver shard you are currently on and hence cant give that as a parameter to the events api
- Even if you knew that, you wouldnt have a way to travel to a specific megaserver shard where the event is currently running, ultimately making you wait around anyways
I do agree with you though. I would like to see this fixed sometime soon too.
Problem is:
- You currently have no way of telling what megaserver shard you are currently on and hence cant give that as a parameter to the events api
- Even if you knew that, you wouldnt have a way to travel to a specific megaserver shard where the event is currently running, ultimately making you wait around anywaysI do agree with you though. I would like to see this fixed sometime soon too.
Type /ip
That’s your megaserver.
The other problem is insurmountable, though :/
Problem is:
- You currently have no way of telling what megaserver shard you are currently on and hence cant give that as a parameter to the events api
- Even if you knew that, you wouldnt have a way to travel to a specific megaserver shard where the event is currently running, ultimately making you wait around anywaysI do agree with you though. I would like to see this fixed sometime soon too.
Type /ip
That’s your megaserver.The other problem is insurmountable, though :/
I meant in an automatic way, such as grabbing the world/shard_id and map_id from the mumble plugin and feeding it into another application.
Sadly, the mumble plugin currently returns rubbish when it comes to that, and we have no official events api we could feed that into even if we had it.
I was aware of the manual way of finding out what ip you are on, but that still isnt the same as a shard_id i suppose.
It could potentially work that way.
Consider something like map_details API which tracks available megaserver IPs for that particular map. map_details for Dry Top contains all instance of Dry Top currently running. Use that same IP to access event_details API which contains a list of all events currently running, including an IP field which ties into the instance the event is running on.
If that makes any sense.
There’s no way to travel to a particular megaserver instance (unless you know someone on the instance), but at least the API will allow tracking of events in your current instance of whichever zone map you’re in, since not all of them appear on the map.
It’ll probably still be a problem of keeping track of multiple instances of every map and keeping track of the IP.