Draining Shot bugfix

Beardimus

TheYKcid wrote: »

CatchMeTrolling wrote: »

Remember how many people was defending it.

It's just lagg, they said.

It's been here for 5+ years since beta, they said.

Spot on lol

Now where's the fix for Fear same thing?

Thogard

Beardimus wrote: »

TheYKcid wrote: »

CatchMeTrolling wrote: »

Remember how many people was defending it.

It's just lagg, they said.

It's been here for 5+ years since beta, they said.

Spot on lol

Now where's the fix for Fear same thing?

Fear and vamp drain have the same double animation thing, but at least they don’t allow you to attempt to break free during the first part, thereby resetting your GCD.

jcm2606

Can we please get this pushed to the live servers quicker? Just finished a BG match where both teams were filled with archers. The moment I'd start fighting somebody, instantly stunned with Draining Shot, every single fight.

TheYKcid

jcm2606 wrote: »

Can we please get this pushed to the live servers quicker? Just finished a BG match where both teams were filled with archers. The moment I'd start fighting somebody, instantly stunned with Draining Shot, every single fight.

It always perplexes me why ZOS prefers to publish exploits during PTS iteration one, instead of pushing the fix to live ASAP. They've already done the code so why delay?

They did the same thing with the rolldodge exploit (also pertaining to Draining Shot) back in Summerset—providing full details in the Wolfhunter PTS cycle week 1 notes, and giving people all the information they needed to exploit it out of their minds for the next 6 weeks on live.

jcm2606

TheYKcid wrote: »

jcm2606 wrote: »

Can we please get this pushed to the live servers quicker? Just finished a BG match where both teams were filled with archers. The moment I'd start fighting somebody, instantly stunned with Draining Shot, every single fight.

It always perplexes me why ZOS prefers to publish exploits during PTS iteration one, instead of pushing the fix to live ASAP. They've already done the code so why delay?

They did the same thing with the rolldodge exploit (also pertaining to Draining Shot) back in Summerset—providing full details in the Wolfhunter PTS cycle week 1 notes, and giving people all the information they needed to exploit it out of their minds for the next 6 weeks on live.

It's even more perplexing when you consider that source control systems (systems used to keep track of changes to a project and its code) have ways of doing this easily. Git -- one particular source control system -- has multiple ways of doing this.

If the Live version of the game and the PTS are in the same project, but are separate "versions" of the same project, then all that needs to happen is the particular changes for Draining Shot just need to be merged with the Live "version". Very easy.

Instead, if they are two separate projects, then Git has the 'cherry-pick' command for this very reason. Within the Live project, they can add a reference to the PTS project, then use 'cherry-pick' to apply the particular changes for Draining Shot from the PTS project, to the Live project.

They should do this more often, to be honest. A better method IMO would be to not talk about an issue until they're ready to push the fix to the PTS (to prevent easy exploitation, as you mentioned), then when it is pushed to the PTS host an event or something to get players onto the PTS to confirm whether the fix works. If it doesn't work, try again. Once the fix does work, just merge it with the Live version of the game, and push it in the next maintenance.