Zephyrus.9680

Boon strip is the most straightforward solution and is good because it mostly targets zerg fights where boons are the biggest issue. It would have minimal effect on small scale/roaming contexts. Nerfing boon duration or boons themselves is another solution but this overly punishes supports in small scale contexts where you may just be giving 1-2 other players those boons rather than 5. So I think boon strip is still the better solution.

I've already seen it reduces fights since there's usually no way to defend in time after a scout call so almost no one even tries. Small team (or zerg) captures the camp and leaves. No fights. The disappointing part is this should have been obvious if anyone on the 'balance team' even plays the game mode outside of the boon ball. Previously camps were a major point for field fights because while there are no walls, the circle size give defenders a chance even if they were weaker. Now it's just capture camp and leave, no "PvP interaction" there anymore. I missing something? Or does Anet think a "PvP interaction" is when one side captures an objective against NPCs?

In my experience larger capture circles promote fights and sometimes even allow the weaker side to win. Making capture circles smaller seems like a bad and anti-PvP change. Karma trainers will like it though.

A) Match with them next time. B) Don't fight them? (Roamers are used to this) C) Get over it. Are you/they really going to get salty about it? D) Sit out the week.

#EUproblems That does seem chaotic. I'm on NA where almost everyone speaks Merican but I wonder if they could implement a chat translator like Google Translate API so all foreign languages are translated to the client's native language

Considering the disaster map that is Desert Borderlands, I'm not sure about new content. If it ain't broke... Also get the jumping puzzles out of WvW! I don't know if they should abandon servers entirely but switching things up like this is good. Would be cool if they alternate between server matchups and alliance matchups.

People that instantly blame Anet (Amazon servers) should understand there are multiple causes of skill lag and a lot of the time it isn't Anet/Amazon causing it. For instance, I almost never experience skill lag. If the servers are actually the issue, everyone on those servers should experience it, right? But usually they don't (sometimes, rarely, it really is the servers and THEN everyone sees it). Before upgrading my PC, I used to get skill lag when the CPU was reaching 100% during big fights. That was my PC. So there are multiple causes including CPU, ISP/geographic location relative to game servers, and finally the game servers themselves.

Compared to today, WvW was a wasteland 10 years ago. It was also much more imbalanced before they implemented server pairings. Back then, if for some reason someone actually cared about score they would bandwagon to the server that always won every week, every year. Which was BG on NA. It didn't mean anything though. It doesn't mean anything not just because population difference but timezone coverage differences. If you have more players from Asia and Australia (the dead time zones) you get disproportionately more score and consequently more victory points. Suggestions like the OC's that put the population weighting at the end of the week, completely fail to understand that players during low-pop hours have much higher impact on points unless this is specifically weighted for in each 120 minute skirmish period.

In thousands of hours of WvW I've not done the borderlands JP even once. The weekly won't get me to do it either. As long as the weekly can be completed without doing the JP or the "cap 10 shrines" I don't mind much but yes it would be nice to remove it. It's not WvW and has nothing to do with WvW.

They aren't that high drop rate but if you play WvW a lot you'll have hundreds of them. With decent base magic find one might drop every 6 hrs or so maybe? Anecdotally I agree with the above poster. Solo roamers should get good numbers of these spikes from camps. Probably from the supervisor. Also from tower and keep lords.

It would be great to get their account name but can't do that without targeting them. It's hard to target underground players like https://youtu.be/Z3nqLFBzlOY?si=ROs-EQs0-5ODfp8R Coincidentally, same matchup as OP with JQ.

Not sure how to target/report players underground. For example: I also "caught" one in a keep a few days ago except there was no one to catch because the lord was being attacked from under the map.

#1. If inner walls and doors are up, give "Marked" (sentry effect) around the lord. This will show when hackers are doing the thing. #2. If inner walls and doors are up, give lords a fixed 10,000 HP regen/sec in combat. That's about 1 player's worth of DPS. Or these can be unconditional effects. But the "inner doors and walls" condition makes it hardly affect anyone else. Either one of these or both can easily address the problem.

Bad idea in practice that would be inaccurate, achieve nothing and maybe make people even more scared to fight. Just as an example of how meaningless it would be, last week I had an 18 minute fight with ~5,138,000 damage near the EBG north keep entrance. They just kept coming back. I didn't go down at all and maybe took 100-150k damage in return or around 30-40 times less. How do you rate that? You don't. I was just doing normal weaver things from the backline, protected by the real heroes, competent support, frontline and midline. And facing a less skilled/numbered server that still likes to fight. If you want stats then use arcdps, keeping in mind it doesn't really mean much in an asymmetrical context like WvW. Otherwise there's WvW rank which is all there should be.

Accusations against other players are against forum rules. If you have video evidence you open a ticket and submit it to support, not the forums. But yes, there are players hacking, and yes they can get banned.

There are no downstate weeks and they don't "save" WvW. It's a fun change on occasion but overall it might make fights worse. I'd like no rally events though.

Lag doesn't change how the game works, only the information that is getting back to the servers and other players. So it won't let you teleport multiple times in down state (desync can legit "teleport" you once), move across the map at artificial speeds, fly in the air, over walls, underground, other inaccessible areas, or instantly OOC. It's a difference between hacking vs exploiting though both should be banned. Anyway the teleport hack is somewhat common and can get banned. People taking those videos need to open the report menu and/or block the player to get the account name (in the video). Then submit it to support in a ticket. They will often get banned though probably not perma-banned if its the first time. It needs to be a ticket and it needs the account/character name since the ingame "botting" report wont do anything for this. Showing the videos on forums also won't do anything (don't show them on forums with the account name included).

I live near the NA servers and almost never see skill lag. Very rarely I will see 2-3 second skill lag at most, like maybe 3 times total in the last few months. If it is a server side processing bottleneck we should expect it to affect all players equally unrelated to ping. If it is a general internet issue it should happen randomly and not just in big fights. Is your CPU near 100% when the skill lag happens? In the past, skill lag that I attributed to the servers was actually my PC's CPU and disappeared after upgrade. In those cases my FPS was still smooth so I did not attribute it to my PC, but upgrading CPU did fix it.

Try updating the BIOS. I had a similar issue that is now fixed. Crash every 40 minutes or so. Several error messages including a Windows BSOD one time but usually the same graphics error message. DDR 5 RAM though AMD CPU. Fairly new machine from last year. Updated all drivers including monitor before that. Tested on lowest graphic settings, changed NVidia settings, etc... Finally updated BIOS and it fixed. Oddly did not have issues with other games. Since it's a new PC you could also try a ram test like Windows Memory Diagnostic. If you have 2 sticks, try with 1 stick and then the other so you can rule out the physical stick. If you have another graphics card or even onboard graphics you could test with that though its a pain.

All I can say is the issue was fixed for me. RAM interaction with the motherboard/BIOS would be my guess though maybe it was the GPU-BIOS interaction. I'm not sure if you're getting error messages or error logs. I was getting several different messages and often it would say it was a graphics error, but not always. Sometimes no message, it just crashed. One time I got a BSOD that crashed windows11. That was the hint for me that it was bigger than just the game. Even though other games seemed to run fine.

I think that was it but don't remember anymore. I looked into that stuff last year when I built the PC and set everything up then. After reading there were early issues with the RAM and BIOS, I still ended up forgetting to update the BIOS. Though maybe there wasn't an update at that point. Anyway 2 weeks later I can confirm the issue was completely fixed for me. No crashes since then.

I had similar issues with at least 4 different errors after the update, including that code. Here are the last 3 things I did (one of them seems to have fixed it): 1. Deleted (renamed) Local.dat file in C>Users>[username]>AppData>Roaming>Guild Wars 2. Running the game generates a fresh file. The new file the game generated was almost 4 times smaller so something was odd there. Make sure to export keybinds before deleting or renaming. 2. Delete all contents in AppData>Local>Temp or at least the GW2 related files (I deleted 8 GB of data there) 3. Most likely culprit: Updated BIOS to latest version. I completely forgot to do this before, even knowing DDR5 RAM was supposed to be janky on the new boards till updating the BIOS.

Edit: If you have a fairly new motherboard and DDR5 ram, try updating the BIOS. Or try it anyway. I believe this is what fixed it for me. The other thing to try is delete all contents in AppData>Local>Temp since GW2 stores a lot of temp files there. ------------- I've been getting game closes and sometimes graphics error messages since the expansion. It is particularly frequent in Armistice Bastion. I guess that place is extra intensive even just sitting there. Tried about 30 different things so far, updated drivers, redownloaded the game, downscaled windows resolution + min graphics settings, etc... The latest thing that might have worked was deleting (renaming) the Local.dat file to let the game generate it again. It's located in Users>[Username]>AppData>Roaming>Guild Wars 2. Redownloading the game doesn't do this. Export keybinds and screenshot settings before that though. My old file was 76MB and the fresh file is 20MB, even with identical settings saved so something was off there. What I read was the Local.dat gets bloated over time and potentially corrupted.

In general the reason they would do this is to mitigate chargeback fraud. But just use Paypal for 2nd account. You can even fund it with the same card as long as it comes from the PP account. Or you can open a support ticket if you didn't already to explain. Or "delete" the game?

Update: Issue appears fixed but doesn't seem like anyone else had the same issue. In case anyone else does I'll leave here the last 3 things I did: 1. Deleted (renamed) Local.dat file in C>Users>[username]>AppData>Roaming>Guild Wars 2. Running the game generates a fresh file. The new file the game generated was almost 4 times smaller so something was odd there. Make sure to export keybinds before deleting or renaming. 2. Delete all contents in AppData>Local>Temp (gw2 stores a lot of temp files there) 3. Most likely culprit: Updated BIOS to latest version. I completely forgot to do this before, even knowing DDR5 RAM was supposed to be janky on the new boards till updating the BIOS. Though the odd thing is, any other game I played didn't have any issues. /// Constant random crash to desktop every 40 minutes or so after SoTO. Essentially never happened before the update or maybe once every week or 2. Now sitting in Armistice Bastion it happens every 5 minutes sometimes and anywhere else with other players every 30-60 minutes. Never crashed in solo instance content so far though. Tried updating GPU driver, then reinstalling the update, then CPU drivers, monitor drivers, reinstalling the game, changing all settings to low, still happens. Anyone else getting this or have a solution?