Closed ChalyFlavour closed 2 months ago
after speaking to a lot of developers currently running and developing "verify" applications (such as bots for Discord, Mumble, TeamSpeak) i have added the wvw_world
attribute to the issue. I also mentioned a possible extension of the endpoint /v2/worlds
which, however, is not part of this issue
This data should now all be available in the API I think.
The endpoints are really new and might still change slightly, so feel free to report any feedback or still missing data, preferably on the GW2 Development Community Discord for now for faster turnaround and discussions.
Feature Description
Story
With the world-vs-world restructuring a "home world" would make no more sense for the world vs world when thinking about the world ID 1xxx (NA) or 2xxx (EU). Instead a new wvw_world ID should match the world IDs after wvw restructuring. Nowadays the
world
attribute in the/v2/account
endpoint is used for verification by most bots and voice chats.Description
We need to know in which match a player participates in. We also need to know in which match a guild participates in.
Optionally the current selected "world-vs-world" guild isn't available in the API.
Implementation
We need two extensions to the API (including suggested endpoint paths)
/v2/account
showing the newwvw_world
id (12001 for Moogooloo, 12002 for Titan's Staircase..)/v2/account
showing the current world-vs-worldmatch:id
the account participates in as well as its color./v2/wvw/matches/guilds/:id
listing allguild:id
that participates in the current match Optional/v2/account
showing the accounts currently selected/activeguild:id
for world-vs-worldI suggest not replacing the value of the current
world
as endless API application makes use of it. While not being part of this issue, it would totally make sense to extend the endpoint/v2/worlds
to retrieve the new "server" names.Example
Anything else?
No response