Latency.3907

changes looks good at first shot. I am still concerned about not enough change to ele sceptor in spvp. The core issue not being addressed is the unending burning from the attack chains. The spamming of this condition cannot be removed fast enough with most builds and burning itself is one of the most powerful conditions for dmg. The duration should be reduced and it should not be as available on so many skills off low cooldown that fresh air offers.

If it gives unspecified error, it likely does not like your ip address/network. This happens often for VPNs where shared IP addressed are flagged by anet's website. Try using maybe your cell phone to register via cellular network or another network.

The mechanist pet distance change to affect stats is NOT a good idea since the player does not have fine control over mech positioning. This causes variation and randomness in some scenarios where it does not reflect upon the player's abilities. Please change the conditional aspect stats on the mech to be some other core mechanic for the mechanist. Maybe something related to profession's F1,F2,F3 skill activation or some other variable where the player is able to have a controlled burst of higher damage (similar to what is done for BS,Virt,Deadeye,..etc). The reward for higher damage needs to be from active player inputs NOT AI driven variations.

Adding link to screenshot for reference. This is clearly a math error in rendering code in ui for window mode gw2 usage cases. https://imgur.com/a/2dmjmBU

There was an update a couple of months ago which bugged the character rendering on preview and character screens. It has not been solved or fixed for windowed gw2 small than the display resolution. This is still broken when game is in window mode and smaller than actually display resolution. This is important for use cases where the screen is ultra sized and window mode is used to make the game screen smaller than the entire display. There is rendering cut offs where the graphics drawing of the character would be invisible depending on the window size compared to screen resolution. This case of window sized gw2 has not been patched and missed in the initial fix for some of the cases of the rendering bug.

Great changes throughout to raise the skill ceiling. Requiring more active gameplay to perform at higher level is great for the game where decisions second to second should be critical to performance. Several changes with taking out or lowering effectiveness of passive abilities is good direction. Active abilities require thought AND time on skills. Huge problem with passive abilities is requiring minimal maintenance and stacking power creep. Passives even if profession unique should be limited as they effectively increase baseline power due to BUILDs not on SKILLs of the players. In summary, this patch will ruffle feathers of a lot of people who have become reliant on unbalanced specs that relied on set it and forget it type abilities or boons to their characters. We need continue this path to better balance to encourage better build diversity which is lacking in all game modes.

I start my game with window option which launches it with smaller than monitor size as I use ultrawide monitor screen and not need the entire width. This appears to horizontally crop the character model in hero display off for rendering based on what percentage of your window occupies width wise on your reported monitor width. This is very bad UI breaking update which did not get proper testing. Not everyone always plays full screen mode. Please REVERT to the old HERO panel character rendering code as the new patch from 9/13 introduced bug a many.

Turn key is REQUIRED for precision control of mounts. Big part of population does not realize that turn keys are critical for superior control of the mounts in gw2. It is needed for fine control with griffin flight and roller beetles especially.

Having been with this franchise since 2005 with original release of guild wars 1, there have been solid and not so solid balance periods in both guild wars games. Given the circumstances and big public perception issues with justification and process that profession balance is being implemented. Arenanet needs to more to make the Profession Balance Design Process more Transparent. Ultimately, there is a big trust issue at the moment between a large swath of the most dedicated player base and "guild wars 2 developers" in general. I would hope the the METHOD that Arenanet uses to arrive at details of balance for profession balance involves MULTIPLE individuals for impartial vetting. The current state of profession balance projects an environment of favoritism of specifics professions and builds. Josh, your studio's action to qualify the current details and numbers used in the balance is important but as is the process which final numbers are vetted and determined. Player needs to understand "WHAT DOES ANET DO TO BALANCE?" Ultimately, big picture is important and anet is moving in right direction, but the DETAILED numbers in each skill and traits NEED to be compatible with the bigger picture. Currently, there is a big problem with perception whether true or not, that the final balance numbers and changes are not being done FAIRLY and it will be a long time before any changes come to correct them. An acknowledgement of current mistakes on this balance patch would go a long way.

Until recently, my script to retrieve inventory content into google sheets was working. For the past several days, I am getting hard 429 response whenever google scripts calls a urlfetch any of the gw2 json urls. This happens can happen on a single call so it is not my script being throttled. I suspect as the google only have limited number of IPs for execution of all app scripts in its cloud server, there is a hard block from the api server blacklisting or blocking google cloud ips at the moment. I'd like to request if perhaps all endpoints is restricted to authenticated only and the throttling be done per access token rather than IP as this causes issues on scripts on cloud services. (example is not able to run app scripts in google sheets to pull data from api)