-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WvW Objective Upgrade Status #118
Comments
Yeah, can definitely look into it. I know the WvW API server has access to the current upgrades, but I'm not sure what the status of upgrade progress is -- if that's not already passed around it might not be very feasible to expose. I also want to expose which guild upgrades are slotted (if any) in each objective, but that's going to take awhile to get out. |
Any update on this? The objective upgrades have been changed to be dolyak-based instead of time-based, so it'd be helpful to get the number of dolyaks delivered / remaining too. |
It's still on the backlog; I need a more detailed way of prioritizing tickets I guess. WvW is probably the next area I'm going to be working on after I finish up with the remainder of the PvP endpoint stuff (and some minor guild endpoint changes). Not sure how long they changes will take to implement, but it's fairly high up on the order of things to do, so there's that at least :< |
It'd be nice if this were re-prioritized based on the new scoring based on objective tier. |
At long last I think all the bits off this have been implemented. |
Hello,
Would it be possible to get the upgrade status (tier 0/1/2/3) of objectives in WvW (as part of /v2/wvw/matches)? The upgrades are based on timers now, so they can be loosely calculated based on time captured, but they're also affected by incoming dolyaks, which reduce the timer. So it'd be useful to get the definite status from the API.
It would also be helpful to get the estimated time of the next upgrade (which would be updated as dolyaks come in), if it's possible.
Something like this:
Thanks!
The text was updated successfully, but these errors were encountered: