this post was submitted on 18 Jul 2023
30 points (96.9% liked)

Guild Wars 2

1495 readers
1 users here now

Welcome to c/guildwars2 on the Lemmyverse.

SotM: Love Spooky Season (@avater)

Links

Official

Builds

Tools

Addons

Related Communities


founded 1 year ago
MODERATORS
 

Enjoy!

top 13 comments
sorted by: hot top controversial new old
[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (1 children)

ArcDPS broken on patch for now as a note.

Edit: is now up to date.

[–] [email protected] 5 points 1 year ago (1 children)

yep!

Usually does not take very long until an updated version is released.

[–] necropola 6 points 1 year ago (2 children)

@[email protected]

 jul.18.2023: updated for jul18 game build maybe.
 jul.18.2023: added kanaxai cm to default logging list.
 jul.18.2023: evtc: player added to table only if in combat.
 jul.18.2023: evtc: retired CBTS_EFFECT.
 jul.18.2023: evtc: added CBTS_EFFECT2 (changed orientation encoding).
 jul.18.2023: evtc/api: added CBTS_FRACTALSCALE (src agent is scale) on log start.
[–] necropola 4 points 1 year ago* (last edited 1 year ago)
jul.19.2023: fixed missing guids for effects since previous.
jul.19.2023: fixed cbts language since previous.
jul.19.2023: changed cbts_effect2 orientation (again, sorry) to original*1000 clamped to int16.
[–] [email protected] 3 points 1 year ago

“Maybe.” Lol. Love it. But yeah, worked for my 7pm EST raids (mostly) fine. My loader was being dumb so I had to redo everything and it crashed a few times setting up everything, but that could’ve been it or just because I was fucking with the food notification thing I hadn’t used before.

[–] necropola 6 points 1 year ago

GW2Wiki Game updates/2023-07-18

I'm getting a bit tired of this messing around with stuff that wasn't broken while not fxing stuff that actually is. Luckily in Open World pretty much anything works and so I'm just ignoring this patch, too. That is, I'm not adjusting any builds, unless I feel something is completely off when I actually play it.

[–] necropola 5 points 1 year ago* (last edited 1 year ago)
A Patch for a Patch of a Patch 😎

https://en-forum.guildwars2.com/topic/134006-game-update-notes-july-18-2023/?do=findComment&comment=1945970

  • Written in Stone: This trait now has a 25-second internal cooldown when granting an aura in PvP only.
  • Signet of Restoration: Increased cooldown from 25 seconds to 30 seconds in PvP only.
  • Signet of Water: Increased cooldown from 20 seconds to 30 seconds in PvP only.
  • Flamestrike: The first strike of this skill no longer inflicts burning in PvP only. Reduced the secondary burning duration from 1.5 seconds to 1 second in PvP only.
  • Dragon's Tooth: Reduced burning duration from 10 seconds to 5 seconds in PvP only.
  • Desert Empowerment: Fixed an issue that caused this trait to grant more barrier than intended in PvP and WvW.
  • Fixed an issue in the Silent Surf fractal that caused pets to be affected by the final encounter's boon stealing mechanic.
  • Removed a context menu "Invite" option that was erroneously enabled.
[–] [email protected] 5 points 1 year ago (1 children)

Today I learned they removed the barrier generation from Skill 1 on the Mace. That kind of makes alacrity harder to maintain uptime on. Especially with the Mechanical Genius trait where your 300(ish?) away and it increases the time of the mech skill cooldowns.

Looks like catalyst got some needed nerfs for PvP. I'm not familiar with the class to know if it's balanced yet but they were dominating PvP.

At this point I wonder if they intentionally make drastic changes to try and force the meta to change and requires players to innovate so it doesn't get stale.

[–] necropola 5 points 1 year ago* (last edited 1 year ago)

Today I learned they removed the barrier generation from Skill 1 on the Mace.

You mean Mace Blast formerly known as Barrier Blast, i. e. the 3rd skill of the Mace autoattack chain on Mechanist which apparently was stealth-nerfed in the June 27th update?

It's changes like these that I find rather disturbing.

When Mechanist was released in EoD neither Barrier nor Alacrity have been new concepts. So I have to assume that ArenaNet wanted the autoattack chain to provide Barrier and via Mech Frame: Channeling Conduits also Alacrity.

I further have to assume that they later (June 27th update) wanted to completely remove (not just adjust) Barrier and Alacrity generation from Mace autoattacks and move it to Energizing Slam (Mace 2, Leap) which is also not mentioned in the official patch notes.

  • So, which is/was wrong? The original version of the autoattack chain or the updated one?
  • Why not tell your players that and for what reasons you changed your mind?
  • Why not update the official patch notes, if you have forgotten to mention it?
  • Or did you think nobody would notice or care?

I'm not even sure that these undocumented changes are a big nerf to Barrier/Alacrity generation but it changes what you need to do in order to maximize it, i. e. you no longer need to outwait the autoattack chain, but (only) have to use Mace 2 every 6 seconds which you probably did anyway.

The knowledge (and hence skill) gap between average and highly proficient GW2 players is already huge which is one of the main reasons that balancing is so hard. And that's why I find not (properly) communicating changes to skills so disturbing.

[–] goomby69 5 points 1 year ago

I'm surprised they added so many new skins for the festival. I honestly expected the bare minimum with the expansion looming.

[–] necropola 4 points 1 year ago

MightyTeapot's July 18th Balance Patch Analysis

MightyTeapot's July 18th Balance Patch Analysis

[–] [email protected] 3 points 1 year ago (1 children)

One in the Chamber: Reduced bonus damage from 300% to 10% in PvE only.

Ouch! I don’t play Deadeye, but that seems like an insane nerf?

Nothing in the patch seems to be of any interest to me and my thief though 😅

[–] [email protected] 2 points 1 year ago

The patch dropped my golem dps by about 4k. Still good for qdps though (27k, no food, unrefined rotation)

load more comments
view more: next ›