apoch on master
/v2/pvp/seasons: add .ranks. Merge pull request #535 from ar… (compare)
apoch on master
add missing name tag to /v2/rac… Merge pull request #609 from Th… (compare)
I was looking at https://wiki.guildwars2.com/wiki/PvP_Build#Sigils and had trouble requesting these sigils and runes.
For example, looking at the Sigil of Absorption(PvP) page, we see it's supposed to have an id of 81266 (hover over "Game link" chat code). The equivalent in PvE has an id of 72872.
request for Sigil of Absorption(PvP): https://api.guildwars2.com/v2/items?id=81266
"text": "no such id"
curl -H 'Accept: application/activity+json' https://ravenvale.lubar.me/_item/20546/_emoji) but Mastodon won't accept any emoji over 50 kilobytes. Example: https://render.guildwars2.com/file/06DF4AD10F92FDC3AB0EA1D8411038D44758BD52/66654.png
** Processing: 66654.png 256x256 pixels, 4x8 bits/pixel, RGB+alpha Reducing image to 3x8 bits/pixel, RGB Stripping metadata... Input IDAT size = 57664 bytes Input file size = 57771 bytes Trying: zc = 9 zm = 9 zs = 0 f = 0 IDAT size = 50755 Selecting parameters: zc = 9 zm = 9 zs = 0 f = 0 IDAT size = 50755 Output IDAT size = 50755 bytes (6909 bytes decrease) Output file size = 50812 bytes (6959 bytes = 12.05% decrease)
Request: WvW Skirmish Reward (Pip Count) Current Progress
by Butters.2807 in API Development
Hi there, I'm just curious. Is there any plans to add an endpoint to the API to return the Current Pip progress on the Weekly Skirmish Rewards. Eg "Platinum Chest, 3rd Tier, 5 Pips".
It would be so useful. As i already have a semi-automated spreadasheet that predicts timings for finishing chests and works out how many weeks / hours etc until you can acquire the armor set you want.
This may be a weird request, but would it be possible to add the timestamp of the last aetherium generation tick to guild info?
I noticed in my own guild hall that without any speed upgrades aetherium seems to always generate based on when aetherium capacity was last made available. That is, the capacity upgrade was unlocked at
2019-04-29T04:30:54.000Z(using up all 500/500 aetherium, changing the available capacity from 0 to 1500) and the ticks have been happening every 60 seconds on the :54 of the minute. Before that, the mine was unlocked at
2019-04-28T20:11:29.000Z(changing the available capacity from 0 to 500) and the ticks seemed to be happening around halfway through each minute.
This is technically something that applications could calculate for themselves, but it gets very messy, especially if the guild log doesn't include enough information due to upgrades being done a while ago.
This is the last piece needed to replicate the guild hall upgrade UI on a website.
(Also, just as a side note, some of the early upgrades like ore synthesizer 1 don't seem to require their building even though they do require it ingame.)
As of today's patch some backend changes to support the API have gone live. I will be working to bring some of the benefits of those changes over the coming weeks. One of the changes broke the mounts endpoint for several hours today (it is now fixed), but in return all missing mount skins have been added to the API.
Recent API Updates
Here are the changes in list format:
I recently mentioned some backend changes I made that went live with yesterday's patch. As a result I am rolling out some fixes that weren't possible before.
The daily achievements you see in-game are different depending on which expansions you own for that account. Because listing the daily achievements doesn't require an API key, there are flags on each achievement that describe the access requirements for each.
The way those requirements were represented changed at some point in the past to be a bit more complex. I have updated the API to understand the new format and I've bumped the schema version.
Recent API Updates
Most probably don't remember me but I used to co-author a C# library that provides an abstraction for the GW2 API. Unfortunately changes in my personal life stopped me from working on it about 5 years ago and the project became no longer maintained. If you check out the NuGet page you can see that the last update was in 2015. And that update was mostly just for bug-fixes...
Rather than attempting to modernize an outdated library that's riddled with design issues (all my fault, of course) and outdated dependencies, I decided to take a fresh stab at it. I created a new Git repo and completely started over, using modern C# and .NET.
This discussion exists for me to find out what people are doing these days:
- Are you currently using C#?
- Are you interested in using an API client library written in C#, for C#?
- Are you interested in collaborating on such a project?