Silver Bugs

lykoswolf101

New member
Human Form
Boot Kick:
Frequently when you boot kick at someone on a staircase you can phase through them. This has happened to me consistently in games yet I've been unable to re-create it in a training range scenario. I'll include video footage.

Werewolf Form
Go for the throat:
Your m1 will not buffer when casting Go for the Throat without already holding it. If you press and hold m1 after casting you have to release and re-press the m1 key to continue auto attacking. If you hold m1 during transformation it also will not attack without releasing and pressing again. I have no video footage but this is easy to replicate.

Tail Whack:
Tail Whack consistently misses minions and does zero damage to them. I have no video footage of this
 

Attachments

Replying for more info about the Boot Kick bug as I've had it happen to me before quite often and always got confused. Managed to replicate it somewhat. Seems like its dependent on the stairs itself, as demonstrated between the two clips I've attached.
Note that some stairs are far more consistent than others, as shown in the first clip where it just never hits.
A fix for this is that jumping before using 2 makes it almost always hit.
View attachment SilverStairBootKickBugExample1.mp4

View attachment SilverStairsBootKickBugExample2.mp4
 
The M1 buffer issue happens for both Go For the Throat and Tail Whack. If you are already holding M1 before using either ability, you're fine. But if you weren't already swinging, then use either ability and hold down M1 during the ability animation, you will stand there doing nothing after the ability animation (no M1 attacking) until you release and repress M1.

It is by the way a timing issue, and the timing problem is different for each skill.

Go For the Throat: If you hit 1 then instantly press and hold M1, there's no problem. If you hit 1 then press and hold M1 while Silver is facing the player (midway through the ability animation), nothing will happen after the ability.

Tail Whack: If you hit 3 then instantly press and hold M1, you'll encounter the problem where nothing will happen after the ability. If you press 3 then pause briefly before pressing and holding M1, you won't encounter the issue.

The fact this happens at all, and with different timing for each, makes Silver feel inconsistent in wolf form. Especially since you have limited time, it's frustrating when you don't attack because of lost buffering.
 
Actually Silver has another M1 buffer problem:

In wolf form, if you hold down M1 and then use the item Vampiric Burst while continuing to hold M1, Silver will stop attacking. You have to release and repress to keep attacking after using Vampiric Burst, which unironically makes the item pretty bad on Silver until this is addressed because you lose swing time trying to rebuffer your attack.
 
want to add that silvers ult keeps getting refunded in some cases even after using it, silver is downright a mess with how clunky and bugged her abilities are now
 
The M1 buffer issue happens for both Go For the Throat and Tail Whack. If you are already holding M1 before using either ability, you're fine. But if you weren't already swinging, then use either ability and hold down M1 during the ability animation, you will stand there doing nothing after the ability animation (no M1 attacking) until you release and repress M1.

It is by the way a timing issue, and the timing problem is different for each skill.

Go For the Throat: If you hit 1 then instantly press and hold M1, there's no problem. If you hit 1 then press and hold M1 while Silver is facing the player (midway through the ability animation), nothing will happen after the ability.

Tail Whack: If you hit 3 then instantly press and hold M1, you'll encounter the problem where nothing will happen after the ability. If you press 3 then pause briefly before pressing and holding M1, you won't encounter the issue.

The fact this happens at all, and with different timing for each, makes Silver feel inconsistent in wolf form. Especially since you have limited time, it's frustrating when you don't attack because of lost buffering.
Honestly, it could be argued not to be a bug (but it certainly could be a quality of life)

The idea is that when you're biting, you're primal and hence you want to swing. Swinging a bit late, like in the wild, would have you staggering. But when you're swinging a tail, like an animal would, you would be locked out from swiping, so swing, orientate, then swipe. I know exactly what you are talking about, but my brain seems to just... accept it?

As if you're supposed to time when you start to hold M1. If that makes any sense?

I would not complain about a quality of life, but one can make a technicality that it's not a bug.
 
Actually Silver has another M1 buffer problem:

In wolf form, if you hold down M1 and then use the item Vampiric Burst while continuing to hold M1, Silver will stop attacking. You have to release and repress to keep attacking after using Vampiric Burst, which unironically makes the item pretty bad on Silver until this is addressed because you lose swing time trying to rebuffer your attack.
Unironically, however this is for sure a bug, and not a "skill issue".
 
Honestly, it could be argued not to be a bug (but it certainly could be a quality of life)

The idea is that when you're biting, you're primal and hence you want to swing. Swinging a bit late, like in the wild, would have you staggering. But when you're swinging a tail, like an animal would, you would be locked out from swiping, so swing, orientate, then swipe. I know exactly what you are talking about, but my brain seems to just... accept it?

As if you're supposed to time when you start to hold M1. If that makes any sense?

I would not complain about a quality of life, but one can make a technicality that it's not a bug.
This is 100% a bug lmao
 
This is 100% a bug lmao
Doesn't seem evident for me. But I do absolutely agree Vampiric burst should intend (by feel) to give you a sudden urge in power instantly.

Why is it a bug, if I may ask? It doesn't come across as a bug for me but something that helps the feel of playing as a werewolf.
 
Honestly, it could be argued not to be a bug (but it certainly could be a quality of life)

The idea is that when you're biting, you're primal and hence you want to swing. Swinging a bit late, like in the wild, would have you staggering. But when you're swinging a tail, like an animal would, you would be locked out from swiping, so swing, orientate, then swipe. I know exactly what you are talking about, but my brain seems to just... accept it?

As if you're supposed to time when you start to hold M1. If that makes any sense?

I would not complain about a quality of life, but one can make a technicality that it's not a bug.
This is the weirdest way to argue something is not a bug, brother just let the report alone, it's not that deep, this is not helpful.
 
Doesn't seem evident for me. But I do absolutely agree Vampiric burst should intend (by feel) to give you a sudden urge in power instantly.

Why is it a bug, if I may ask? It doesn't come across as a bug for me but something that helps the feel of playing as a werewolf.

This issue isn't unique to Silver.

Graves:
Grasping Hands: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.
Borrowed Decree: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Grey Talon:
Spirit Snare: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Ivy:
Entangling Thorns: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Kelvin:
Frost Grenade: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Geist:
Essence Bomb: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.
Life Drain: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

McGinnis:
Mini Turret: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.
Medicinal Specter: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.
Spectral Wall: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Paige:
Bookwyrm: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.
Captivating Read: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Paradox:
Pulse Grenade: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Rem:
Tag Along:
Lil Helpers: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Seven:
Static Charge: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Sinclair:
Spectral Assistant: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.
Rabbit Hex: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Vindicta:
Stake: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Viscous:
Puddle Punch: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Vyper:
Lethal Venom: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Warden:
Binding Word: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Wraith:
Project Mind: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Yamato:
Flying Slash: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Some notes:

1) I mentioned a lot of characters/abilities, but not all of them. I tested all of them. It affects less than half of them, but quite a lot even so. It's inconsistent and feels bad, controls don't respond to user expectation - this is a bug, not design intent.

2) I believe this is a forum for reporting bugs. It's up to developers to accept, reject, ignore, or fix bugs. It is not up to users to call out other users to "prove" something is a bug, or argue with other users about what is or is not a bug. It's especially not a forum to argue "hey you shouldn't fix that bug because personally I'm cool with it". I'd kindly ask you keep threads clear of personal opinion about other people's bugs. If you have opinions about bugs you'd love to stay in the game, please take it to the private suggestion forums. Thank you.
 
This issue isn't unique to Silver.

Graves:
Grasping Hands: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.
Borrowed Decree: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Grey Talon:
Spirit Snare: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Ivy:
Entangling Thorns: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Kelvin:
Frost Grenade: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Geist:
Essence Bomb: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.
Life Drain: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

McGinnis:
Mini Turret: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.
Medicinal Specter: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.
Spectral Wall: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Paige:
Bookwyrm: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.
Captivating Read: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Paradox:
Pulse Grenade: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Rem:
Tag Along:
Lil Helpers: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Seven:
Static Charge: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Sinclair:
Spectral Assistant: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.
Rabbit Hex: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Vindicta:
Stake: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Viscous:
Puddle Punch: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Vyper:
Lethal Venom: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Warden:
Binding Word: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Wraith:
Project Mind: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Yamato:
Flying Slash: Pressing and holding M1 immediately after using ability causes gun fire to NOT buffer.

Some notes:

1) I mentioned a lot of characters/abilities, but not all of them. I tested all of them. It affects less than half of them, but quite a lot even so. It's inconsistent and feels bad, controls don't respond to user expectation - this is a bug, not design intent.

2) I believe this is a forum for reporting bugs. It's up to developers to accept, reject, ignore, or fix bugs. It is not up to users to call out other users to "prove" something is a bug, or argue with other users about what is or is not a bug. It's especially not a forum to argue "hey you shouldn't fix that bug because personally I'm cool with it". I'd kindly ask you keep threads clear of personal opinion about other people's bugs. If you have opinions about bugs you'd love to stay in the game, please take it to the private suggestion forums. Thank you.
Honestly, you're the first to first to answer my question, so thank you for that. Considering all those cases, it seems more than likely to be a bug. I'm in agreement. It's important to distinguish what is and isn't a bug, no? We are discussing about the bug reports, no? Because heavy melee cancelling is a bug, depending on what technicality we are speaking about. If we don't care about that, then what are we even reporting? How can we report something when it's not clear it is a bug? People get so angsty about it, it's really weird. We have to agree on matching a definition, no?

I was not saying it wasn't a bug, but rather it was merky, to me at least. I was using soft language for that reason. I've played umvc3, and I know that buffering is a big part of skill expression. Hence, if I do have an stance about keeping the bug (because I now agree), I will indeed post it privately (as that is about current characters).

Entertainment of thought is not the same thing as suggestion. So I don't appreciate being put words in my mouth.
This is the weirdest way to argue something is not a bug, brother just let the report alone, it's not that deep, this is not helpful.
And your comment is?

Ah geez, I wonder why some forums are public/private... At least when I report something or correct someone I'm not an asshole about it.
 
Last edited:
Honestly, you're the first to first to answer my question, so thank you for that. Considering all those cases, it seems more than likely to be a bug. I'm in agreement. It's important to distinguish what is and isn't a bug, no? We are discussing about the bug reports, no? Because heavy melee cancelling is a bug, depending on what technicality we are speaking about. If we don't care about that, then what are we even reporting? How can we report something when it's not clear it is a bug? People get so angsty about it, it's really weird. We have to agree on matching a definition, no?

I was not saying it wasn't a bug, but rather it was merky, to me at least. I was using soft language for that reason. I've played umvc3, and I know that buffering is a big part of skill expression. Hence, if I do have an stance about keeping the bug (because I now agree), I will indeed post it privately (as that is about current characters).

Entertainment of thought is not the same thing as suggestion. So I don't appreciate being put words in my mouth.

And your comment is?

Ah geez, I wonder why some forums are public/private... At least when I report something or correct someone I'm not an asshole about it.
You're the one who's rude. Extremely rude. Did I do something to you? Do I deserve you being rude to me on my bug report? Do you not consider me to be a human being? Could you stop being so rude?
 
Back
Top