Jim's Missile projectiles two and three don't hit if the first is blocked

If all three projectile from Jim's Missile are fired on same character and first is blocked, the other two don't hit. Is that the intended behavior?

It should be a block canceling skill but is sort of weak if the second and third don't pass the first block.

 

Same behavior as Double Axe To The Face iirc. Annoying, but consistent at least.

 

Like PKB said, it's not really a bug but a feature: Repeated targetting @ FAQ.

 

"Repeated targeting" seems to be case of not implementing something and calling it a feature. LOL

Like saying Jims magic missile also has the feature of not healing!

 

Fwiw, the FAQ (which I really should drop that title and just call it a glossary at this point) is not designed to identify "intentional features," it simply attempts to explain how things work in the game.

However, the question of a bug is something else as well. There are many things in the game that are not features, but still working as intended/expected.

Example: The fact that terrain attachments trigger in a certain order rather than simultaneously means that a character with Vengeance or SCA that gets damaged by terrain could move in one direction onto a different terrain square and take even more damage or move in the other direction onto another terrain square and not take any more damage. This is not a "feature," it's not even intended under the meaning that it was a desired effect when SCA (and later Vengeance) were added to the game, but it was functioning as expected.

Basically when new things are added to the game, they have to work with the existing game mechanics. If the interaction between them breaks the game in a way not anticipated, or with serious enough consequences, then it's a "bug" and either is changed, or removed from the game entirely. If it simply interacts with existing game mechanics in a way that is less favorable for the added thing than players might desire, it still might simply be an expected consequence of the new item.

So if by feature you mean something that is part of the explicitly desired design, you're probably right, it wasn't a feature, but at the same time if by bug you mean that it's something that goes entirely outside of the realm in which the mechanic was desired to work, I don't think it's a bug either.

That said, if you simply desired to make a [Suggestion] that it should be changed to work the way you want it to, I'd support such a change personally.