We cache responses on our end which is, by default, configured for 5 minutes; apparently /v2/commerce/listings is configured with a 1-second cache time. So I guess no more frequently than once/second/item (otherwise you’re just wasting bytes).
List of things i think should be off limit when using Guild Leaders API key:
The characters equipment, inventory, bank, materials deposit, wallet, individual achievements.
Also what about PvP rank and FotM level? Would people feel offended if we knew their FoTM level and PvP rank?
Yeah, none of that is accessible in-game (e.g., your guild leader can’t currently see those details) so they won’t be available via the API. You’d need an API key for each guild member with the appropriate permissions (access to character data and inventories) to pull it.
As per the rest of it, even though the information is currently available in-game for all guildies, since this point has been raised a couple of times by different people I think the correct decision is to start by limiting the guild endpoints (roster, guild bank, ranks, logs, etc) to only guild masters.
I think the ideal solution is to add a permission into the guild ranks that enables that rank to have API access. That’ll give guild masters the ability to figure out the privacy situation themselves. Unfortunately, that involves interaction between quite a few subsystems so it’ll take awhile to implement.
Peters and I discussed the chronomancer traits thing today. We’ll try to get something out to you guys as soon as we can (next week at the earliest, obviously).
A couple notes on Dragonhunter. We went with this name because we felt it was evocative of the medieval witch hunters. Guardians consider themselves protectors of the innocent. Followers of their faith be it in honor, valor, etc. The origin of the dragonhunter is a more subtle nuanced version of this. Guardians fight for justice and the dragonhunter faction believes justice is the eradication of dragons and their minions. I understand this is a lot more high concept than Mesmer but at the end of the day we felt like we wanted to try and push a more mature theme here. I hope this helps explain our thinking. We had other generic names in mind but felt like it was important to have a mix of spec names that are generic fantasy, more Tyrian fantasy, and more high concept. This one falls more in the third category.
I can check on this, but the numbers of drops seems irrelevant. We hope for a certain number of players, so I would surmise that the drops would continue until we have reached the desired number of accounts, not the planned number of drops.
Again, I’m speaking casually, as a hypothesis, and I’ll confirm this.
I just believe that someone getting multiple portals is not impacting the chances of someone else participating in the beta.
Oh, and don’t forget: Increase your chances — sign up for the newsletter!
This merged thread contains a lot of feedback about the name Dragon Hunter. In addition, it merges a couple of polls or petitions. (Please note, the observation about forum petitions is correct: They are not something that we support or allow.)
Please keep your feedback about the name in this thread so that devs can read all your thoughts.
Randulf — this is the supplied information and I will add emphasis for the points that it makes:
Yes! We’ll be expanding the size of the pool of beta testers for future tests. We selected a small number of testers for the first round from our newsletter subscribers. Our next test will use this method as well as the “Portal to the Heart of Maguuma,” an in-game item which has a chance to drop from enemies in Dry Top and the Silverwastes. Players who find this item are guaranteed a spot in the next closed beta test!Signing up for the newsletter is not required to access the beta test if you’ve received one of these items. However, to get beta schedules, instructions on how to access the test, or any other beta-related information, you will still need to sign up for the newsletter. Make sure you sign up using the same e-mail address that you use for your game account.
I don’t see any cause for confusion or any need for change. Can you explain what’s unclear about any of that? It’s a little late to change a published article, but we’d like to know what points might be confusing for future reference.
Sorry, I can’t seem to quote you guys right now. But let me give you some info on the Portal drops and answer a few questions, too!
This is your final weekend to obtain an in-game drop of the Portal to Maguuma’s Heart
Valentino — exactly, and thanks! Here’s what you said
It’s simple:
Newsletter subscription= chance
Portal drop= guaranteed
Previous beta slots= wiped, you have to either be selected from the subscribers or drop a portal.
Bovan — I feel sure that all newsletter subscribers, whether they signed up 4 months ago or 4 hours ago, will have an equal change of being selected. This is because the selections will be made, randomly, from the newsletter subscription list at the time of the selecting. Hope that sets your mind at rest!
He said, as best I saw in the scrolling chat, that these are changes they are considering but are very much in flux. His thread asks for feedback and ideas.
Please use the existing thread for this discussion.
#1402500
Please..this is my third time trying to help my friend, he has not been able to reach the support for over a month now and this is really his last chance to get help, so please help him because there is no other way to do it then me trying to contact you.
His ticket number: #1402500
kind regards
Fia
I don’t suppose it would be possible to put up a temporary oauth2 endpoint that would allow us to get api keys for everybody we have a token for?
It would just make it a bit easier on my 830+ users …
Hmm, I’ll look into adding an endpoint to convert a refresh token to an API key. I can’t promise it’ll be implemented, but it would definitely make the migration much, much cleaner for existing users.
Would you consider removing the description field from the “New Key” form? Removing it will mean one fewer thing that might confuse an end user. Surely a key name would suffice.
Eh, I can remove it. Name is probably enough. I wasn’t sure how much metadata users wanted to attach to keys, so I erred on the side of caution. I don’t necessarily think that the end-users are as easily confused as the comments of the thread suggest, but realistically you guys are in much closer contact than I am (since they’re your end-users, not mine) so I’ll take your word for it.
With regards to links to generate a key with a given permission set — the reason we moved off OAuth2 was phishing (yes, I know) — basically we don’t want the expected flow to involve a third-party site linking to a login page. So the generate-a-key links are out. My solution for this is to just keep the number of scopes fairly low and with short, concise descriptions. Not going for an EVE-style permission system.
Gonna try to get some fixes into the account management system; they’ll probably land early next week:
Is there any way I can read from this using AJAX (xmlHTTPRequests)?
It’s not really well documented (since it isn’t normally how OAuth2 works, but) you can alternatively pass the API key via the ?access_token parameter instead of a header. The header’s what’s breaking the CORS restrictions.
Can you have an update on this ticket 1479138 its been 7 days until now no respond coming from the support group.
1479138 – disconnecting error message “a serious error has occurred that prevents the program from continuing to run Gw2.exe”.
All Cheers,
Philip
And tech! Tech is backlogged. We have a new tech support team that is currently growing so we’re catching up with the lag we hit when we transitioned teams. Right now there are two guys behind me digging through those tickets furiously and a third training the new guys.
We’ll be with you asap. In the meantime, be sure you’ve provided the GameAdvisor file requested in the automatic reply. That log has the info the team will need identify the cause of your issue.
Is there any chance that you could provide update about the spanish tickets as well? I found often posts where they claim it’s been a while with no response from Anet.
There is no backlog of Spanish tickets; except for Guild Wars. If you have a GW2 ticket do let me know the number so I can find out why you’ve not heard back from us. =)
Ok, I was able to solve it. What I noticed was my desktop clock was wrong. I set it to the correct time and it allowed me to log on. Hope this helps!
Sweeeeet. We were investigating this today. We’ll confirm the fix but several of you have had luck with it so I’m just going to go ahead and lift my drink to you, sir.
Just turned on the API key management interface (it’s replacing the OAuth2 client management stuff on the account site). Existing OAuth2 clients will continue to work until June 4th but the management bits for ’em have been turned off for good.
The core of that team rebuilt most of the commerce UI & backends in the two months before the game launched. The one piece that wasn’t changed? The part that took everything else down for the first two weeks. :-(
Getting things up & running again was really exciting, in an “oh god this is so much work” sort of way.
There are a lot of threads containing feedback on the Dragon Hunter. Thanks a lot for sharing your views.
We’re going to merge threads that contain feedback about this specialization into a single thread to enable the devs to most easily gather your feedback.
Threads on topics that are related but different, such as the name of the specialization, will be left separate from this merged feedback thread.
Thanks for understanding this housekeeping move, and keep your input coming!
Are you saying that getting a portal drop only gets me a “Chance” at the next beta? Because if that’s the case I’m going to cry, seeing as I spent 30 hours trying to get that portal and finally got it.
Oh gosh, Lily — I’m so sorry if you were concerned about that! Let’s be clear — I think the verbiage was clear, but again: If you get a Portal to Maguuma’s Heart you are guaranteed access to the beta test!
Thank you for asking about this. There are two chances to get in the beta, but the portal is a sure thing!
No it did not end yesterday. There were some rumours that the build ended it, but forum posts prove that the portals are still dropping, and that is as intended.
Why is it even possible to have more than 1 beta portal stone drop?
When I see people with two or more, i feel like crying.
Was it not possible to code it so it could only drop once per account?
Random is random. Some amount of duplication seems part of the randomness of the drops.
An improvement to this newsletter system is to send a confirmation email to the ppl who subscribed indicating that it worked. The lack of a confirmation email can create confusion. Ppl simply don’t know if newsletter registration worked or not.
What about only being a subscriber? Do we still got a small chance? I gave up on trying to drop a beta portal, I’m levelling an alt now, so I’m hoping I at least have a chance for having signed up for the newsletter.
Yes, you absolutely do have a chance through your newsletter subscription. Testers will come from the portal drops and from the newsletter subscription list.
It’s premature for you to ask for compensation for a system that has not been fully outlined or fully explored by you, as a player. I suggest your consider how long and how much use you got out of your items to reassure yourself you got full value. Also consider how every person who was unhappy with a balance build could make the a similar demand, and realize how unhealthy and unrealistic such a set of demands would be.
Wait for more information, please, before leaping to conclusions or making requests of this nature.
The questions in this thread, or the opinions expressed, have been fully explored and the topic can be closed.
But please keep in mind: The giving of the chests was explained in a post on this very forum. It was not intended as a “reward” or a “thank you” but was the outcome of removing beta access. If you’re offended, we’re sorry.
We’ve been asked about whether you must be a newsletter subscriber to get access to the beta test. Signing up for the newsletter is not required to be given access to the beta test. However, to get beta schedules, instructions on how to access the test, or any other beta-related information, you will need to sign up for the newsletter.
Anyone who finds a Portal to Maguuma’s Heart will have access. A certain number of testers will be selected from the newsletter subscriber list. So as you can see, being a newsletter subscriber has a dual benefit: You increase your chances of getting into the beta test, and you receive direct communication about the test and its schedule.
We have a very large and well-attended (by a dev) thread about RNG. You’re encouraged to add your thoughts to that thread, for maximum value and to avoid repeated commentary in multiple threads.
Blimey how many rares are you all salvaging for that to be a problem?? One of you please tell the Loot Fairy I want to be her BFF too lol
I was thinking the same thing.
As I recall, the warning was implemented at player request. Players were accidentally salvaging items that they did not intend to salvage, just as back in the day (GW) you could sell valuable items with a single click. So the devs added a confirmation process to ensure that you do exactly what you intend to do.
I don’t recall seeing a warning for green items, but I don’t mind a bit getting the message in relation to golds. But then, I’m not massively wealthy, either.
I have confidence that the team will be looking at the benefits as well as the “cost” in time and resources in relation to this situation. Members of our own team are colorblind and are able to offer suggestions on this topic.
With the inclusion of on-demand gliding as a game mechanic alongside the diving goggles mechanic and given the fact that there are quite a few other ways in which the player can fall, knowing well that they will survive or take no damage, these falling gutturals were removed from all characters as they make no sense and serve only to make your character sound weak-willed at best. We doubt they’ll be making a return ever.
Unfortunately not all the challenge mots are fixed. Please find the proper solution not the temporary fix.
There is no “temporary” fix as they are not all the same bug. They look the same on the player end but they are not all the same fix. Would be nice if it was.
As forum members have pointed out, threads with truly constructive criticisms are welcome. The front page — any page — proves that. Threads with a lack of constructive input, with a large number of offensive comments, with attacks or name-calling, or with a lot of off-topic comments are closed to allow the forum to continue on a relatively even keel.
There’s plenty of frustration venting on a regular basis, no worries there. Closure does not equate to censorship, it equates to reasonable moderation.
I’m hoping that once it stabilizes, more account attributes would be available via the authenticated API? Things such as characters and their attributes perhaps?
the one weird thing i get is that i usually have to select my choice (both map and accept/cancel) 2-5 times before the system accepts it. its the only place in the entire game that i have run into a problem like this.
I’ve seen this before too. I think it’s because the UI doesn’t register clicks while its being updated (which it does whenever someone else’s click is registered). I’ll ping Evan about it.
Wanted to point out that I’m still encountering this issue. I solve by double and triple clicking on my chosen map… after the single click doesn’t work. (because I always fall for it, trying to single click first)
While incredibly off topic, this is getting fixed.
