Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider uncommenting Vivisect Restore scenario #152

Closed
keneanung opened this issue Mar 13, 2016 · 6 comments
Closed

Consider uncommenting Vivisect Restore scenario #152

keneanung opened this issue Mar 13, 2016 · 6 comments
Labels
enhancement Pull requests for enhancement or feature requests medium priority simple difficulty

Comments

@keneanung
Copy link
Contributor

Reported by Aerek:
Currently, it's in the code but commented out. I'm not sure about the reasons for this.

@keneanung keneanung added enhancement Pull requests for enhancement or feature requests help wanted simple difficulty medium priority labels Mar 13, 2016
@vadi2
Copy link
Contributor

vadi2 commented Mar 13, 2016

It's gameable, people can then force a restore long enough to behead you.
Need to work with a vivi expert on this.

On Mon, 14 Mar 2016 6:30 am keneanung, notifications@github.com wrote:

Currently, it's in the code but commented out. I'm not sure about the
reasons for this.


Reply to this email directly or view it on GitHub
#152.

@Esync7
Copy link

Esync7 commented Mar 15, 2016

Restore balance was adjusted a while back. Unless you have confusion, an Infernal shouldn't be mathematically able to Behead you. Maybe an Apostate, but you'd have to be locked already.

Either way, you can always disable it via vconfig2 or script enabling/disabling via API, (Which I do) so why does it need to be commented out entirely? It's difficult/dangerous to send newbs/neophytes mucking around in Svo's code to fix this once they do face Vivisect for the first time.

@vadi2
Copy link
Contributor

vadi2 commented Mar 15, 2016

It should've never been turned on or be visible before, it was doing more
harm than good (and misleading people into helping).

On Wed, Mar 16, 2016 at 6:55 AM Aerek notifications@github.com wrote:

Restore balance was adjusted a while back. Unless you have confusion, an
Infernal shouldn't be mathematically able to Behead you. Maybe an Apostate,
but you'd have to be locked already.

Either way, you can always disable it via vconfig2 or script
enabling/disabling via API, (Which I do) so why does it need to be
commented out entirely? It's difficult/dangerous to send newbs/neophytes
mucking around in Svo's code to fix this once they do face Vivisect for the
first time.


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#152 (comment)

@Esync7
Copy link

Esync7 commented Mar 16, 2016

Err. All right. We'll have to respectfully disagree on that. Some Vivisect curing is better than no Vivisect curing. Right now, everyone using Svo will die to a 2-leg Vivisect, every time. Keeping that scenario commented out is handing easy Vivisects to any DSL Infernal that exists.

I just tested it, there's nuance on the topic. It looks like damaged legs are counting toward Restore at the reduced rate (which is intended) but arms are counting at full rate. I've bugged it, seems against the intended balance, but in the meantime:

  • 2x damaged leg + 2x crippled arm Restore is clocking a consistent 10s EQ. (No Diadem)
  • One each damaged arm/leg + crippled arm/leg is taking the full 12.5s EQ. (No Diadem)
  • Behead is clocking consistently 10.5 seconds, and the Infernal has to recover balance (1.9 sec on DSL) before starting it. (12.4s total)

This means that if you Restore to stop Vivisect on a leg/leg setup, (the standard setup) you will regain EQ and can stand 2.4 seconds before Behead completes. If the Infernal can trick you into restoring with damaged arm/leg + crippled arm/leg, then he has a -chance- to Behead you if he reacts perfectly, but several classes still have options to prevent this. (like Arc) If you have a Diadem or are Quick-Witted, then you'll recover EQ before Behead finishes in all cases, and can stop it no matter your class.

Can Vivisect Restore be abused? Yes. So can a lot of other curing options. But dying to Behead some of the time is better than dying to Vivisect all of the time. Can disable it by default if you like, but this is a legitimate option that I've used to stop Vivisect (including Behead) for years, and it should be there. It's certainly no more harmful that the any-crippled-limb-while-prone option, which is a terrible idea.

@CUltiris
Copy link

CUltiris commented May 6, 2016

I agree 100% with Esync7 on this one. I died immediately and repeatedly with no apparent way to beat a vivi using SVO until I un-commented this scenario. Having the restore scenario available forces other methods of play. If it's not behead then it's repeated disembowels.

@keneanung
Copy link
Contributor Author

More discussion about this: http://forums.achaea.com/discussion/comment/316534/#Comment_316534

The overall tenor seems to be that this scenario should be added again

keneanung added a commit to keneanung/svof that referenced this issue Jan 9, 2017
On popular demand, this restore strategy is now restored. Fixes svof#152
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Pull requests for enhancement or feature requests medium priority simple difficulty
Projects
No open projects
Development

No branches or pull requests

4 participants