Page 1 of 1

Nost Devs: Show hunters some LOVE for once and fix Autoshot.

PostPosted: Sun Nov 08, 2015 6:53 am
by Seanimoose
I've noticed that autoshot is super funky on this server. I'm surely not the only one. I think most long time hunters would agree something doesn't feel right about it. But I know we have to go on more than feels to get any fixes in. Sorrens not working as well as the stop cast after arcane shot bug all lead me to be very suspicious there are some major flaws in it's coding here.

So here's my big gripe:

The biggest undressed bug with autoshot on Nostalrius is that it gets cancelled when INITIATED mid air/moving. This is most noticeable while opening up on a target with arcane/serpent sting while moving and or jumping. Here on Nost, you get a "can't do that while moving" error message. This is wrong, this should not exist and did not exist in vanilla (or any iteration of this game). You SHOULD be able to start your autoshot cast while moving and/or while midair, you simply can't finish the cast in these positions, you must wait until you land/stop moving for a moment. It's was always this way on retail and on Nost it's just flat out not working correctly.

Notice in this 1.12 video the hunter NEVER gets this message and the initiation of his autoshot cast is never interrupted while A) midair 180 jumping/kiting B) moving on ground

https://www.youtube.com/watch?v=vQF1EwVAe9k

Thoughts anyone? This is actually a pretty big deal in PvP.

Confirmation from some more old school hunters such as myself? This can't just be my muscle memory playing tricks on me. Hunters have been shown virtually no love from the Nost dev team since release. So I'd like to see something on this one. If we can get some more confirmation/proof from other hunters that would be fantastic. I'd certainly be willing to post this bug to the tracker. Though I haven't searched it, I doubt this is mentioned on there.

Re: Nost Devs: Show hunters some LOVE for once and fix Autos

PostPosted: Sun Nov 08, 2015 7:03 am
by Nano
We're aware of this bug already and are working on a fix. In the future, the suggestions forums is the wrong place for bug reports.