Ryan.6951

Not only does the new feast prioritize below all other food buffs including the 10 minute version from the (better imo) blaster... It ALSO prioritizes below [malnourished] which means a mandatory 5 mins of malnourished after the 30 mins buff, since it can't renew itself or supercede the [malnourished] status. Even if they don't buff it to a poor mans ascended to make it viable or in some other way compared to foods costing under a silver... the fact that you can't eat it when you have malnourished on you is laughably broken.

"hmm in the middle of a global depression when tons of our players are losing their jobs and facing uncertainty, what can we do for them?" "force them to buy new computer hardware instead of a $5/month service that works great, making sure they have no spare $ to spend on gems" "give that man a raise"

bump, if you don't want to make your game playable without a supercomputer, let us play on our rented supercomputers please.

You literally can't, their system doesn't allow any account to have the same password as another account has or has ever used. Once a password has been set to a GW2 account it is dead for any other GW2 account forever. What? No. This is not accurate. Anet stores hashed passwords (we assume) and because of the way they're calculated you cannot re-create the original entered password from the hash. Ergo, you cannot confirm any 2 passwords are the same, or stop the same password from being used on multiple accounts. Also, I have had multiple accounts with single shared passwords at one point.

This is poorly thought out. Now instead of using unique strong single application passwords for each individual account, you are incentivising me to use one common easy to type password. We all know that's counterproductive to increasing security. Good intentions, bad implementation, awful communication, and even worse security consequences. Do you have any devs who use something like lastpass, or are interested in security in general? Anyone could have weighed in on this and explained to the rest of the team why removing user options and forcing them to manually enter passwords for potentially dozens of different account always inevitably leads to password sharing; which then INEVITABLY leads to password compromise.