Blink bugged still

Community General Discussion
1

Why is it still bugged? It’s been 15 years Blizzard.

2 Likes
2

What’s the bug? Colliding with all the annoying ground clutter?

3

Colliding with nothing at all, but there’s something there somehow.

4

Does it look like you’re rubber-banding when it happens or do you just not blink the full distance?

5

There was talk of fixing blink to make it behave like a warrior’s leap. The game, for a leap, checks to see if a warrior could “get” to the place they’re leaping and if the answer is yes, the leap happens. The leap is not terminated due to all the ridiculous things which can terminate a blink. This is at least how I recall the conversation I had last year.

Blink needs to check the endpoint and also not travel in a straight line parallel to the base plane of the game. Blink should work up a slope. Blink should never send you backwards (it does). Blink should not truncate on some pebble or plant.

5 Likes
6

Ah I see, did it just not work out as Blizz wanted so they scrapped the idea?

7

There certainly are technical issues being worked on and then you have priority lists. Blink “works” most of the time. Unfortunately what should be edge cases crop up too often. I am hoping the ideas discussed last year on fixes are implemented. I suspect if done there might not even be a patch note. We shall see.

1 Like
8

Ya I don’t need a patch note to say blink has been fixed, as long as it doesn’t bug anymore I’d be thrilled.

1 Like
9

Over the years I’ve gotten a pretty good sense for where blink is likely to bug out (based on the terrain and objects etc) so I don’t find it a big issue, but there are still places where it really sucks - mainly certain boss rooms where you just can’t blink effectively because it’s too buggy, so you just don’t have your mobility on that fight. That’s pretty rare but it does happen on the occasional dungeon/raid boss.

It would be awesome to not waste a charge/cooldown when you accidentally blink in a bad spot, like even if they didn’t fix anything else I’d be pretty happy with that.

This stopped happening to me when I disabled the “momentum” option (that makes you blink in the direction you’re moving). Still a bug of course, but in the meantime.

10

That’s weird. IMO, blink needs to behave like DHs’ Fel Rush. Warriors’ Leap has it’s own issues that need to be resolved like “No path available”. If you are leaping, a path is irrelevant. I don’t know if it is just impossible to code or what but I wish they could get it right. I don’t know how many times I’ve tried to leap to another plane like an elevator or mountain side etc and either fell to my death or just couldn’t do it. Either way, it threw me off and interrupted my gameplay at the very least. Same goes for the OP’s topic with Blink, how many times have I tried to use Blink and gone nowhere because of terrain. I agree it’s long overdue for this to be addressed. There are things like this about the game that are just irritating, like invisible barriers on railings that you can’t jump over that just don’t physically make sense. I’ve always hoped they would iron this stuff out.

11

I don’t see a problem except sometime going through objects,stairs,walls etc. and getting stuck.

12

Never had that to happen ,blinking backwards ,unless you are using displacement.

1 Like
13

You should google fel rush dc and fel rush bug before asking something like this.

14

It’s not still bugged. They added “or until reaching an obstacle” to the tooltip. It now works perfectly.

It should be targettable like leap, too.

15

Hmm. Ok. I never experienced any issues with Fel Rush. Maybe it needs fixing as well. :man_shrugging:

16

Dat blink…didn’t get ya very far, did it?

2 Likes
17

Out of curiosity, how would this interact with walls?
Obviously it sounds like a much more appropriate way for it to interact as anyone who has played a Mage knows how frustrating it can be to “clip” on the edge of a stair or something.

My question though, is if it acts like a Warrior leap and simply asks “can I get there”, as it is not targeted like leap isn’t it missing out on the vital “in line of site” check that leap performs?

Also how would this work for short blinks? Currently (and the whole issue with clipping small objects) blink collides with terrain to stop you flying off a boat for example, or blinking through a wall instead stopping you.
Would you be able to do that still, or would it simply say “path not available” or similar and only allow the full blink?

18

Not quite sure I agree with this… pretty sure that would be way too busted.

Is it bad that Fel Rush has so many issue that when you say this I’m not sure which “one” you are referring to :joy:

Bwonsamdi coming out with the real feels. It’s almost like they are directly referring to the bug.

1 Like
19

There will always be problems with blink because of how character coding and terrain coding interact.

blink operates under a linear trajectory of ‘x’ yards. With bumpy, un-passable terrain, blinks effects will come into conflict with the parameters surrounding terrain that is not accessible to player characters.

The code then goes through its check list, to try and make the best possible end destination that ensures the criteria of blink and terrain hold true. This means you will get sometimes wonky, and inconsistent results.

With infinite landscapes upon which Blink may be cast, Blizzard would have to redefine the limits in their world building engine, when specifically interacting with blink.

1 Like
20

Noooo. See this is why I’m actually hesitant for
Blizzard to fix blink, they might just make it a version of some other movement skill instead of the unique one it is. I love blink, I’d rather have it occasionally bug out.

That is a very good point I hadn’t thought of, intentional short blink can be great and it wouldn’t be worth losing that capability…