Well, that’s not what I’m trying to say but that is, in fact, true and intended by Blizzard you use Syms Teleporter instead of destroying TL if you’re in range of it and press the interaction key.
But what I’m trying to say is the bug TacoReaper had and you too apparently:
where if you pressed “R1” (TL key “E” on PC don’t know which one on xbox) TL gets sometimes destroyed and goes on a 2s cooldown could be to the whole layout or just for Sombra so to test it someone who has a console version of Overwatch would need to try it with sym by going into a private game, picking Sym, place teleported, then stay in range of it but instead of pressing the interaction key press the Key that’s bindet to Transloceter on Sombra and teleported on Sym and see if it will teleport you (what it should not because you don’t press the interactions key) Its kinda hard to explain and I sadly can’t test it my self
What I basically want to test is, is the bug just Sombra related or overall interaction key related.
I aware of that bug but blizzard already said they fixed this one on PTR so I did not include it in my list
Well, I guess so if TL gets destroyed by pressing the button to use it.
It’s kinda gamebreaking and makes her even more inconsistent right now I’m not even sure anymore if they even tested her new changes intern with this many obvious bugs?
especially the game-breaking one I mean WTF Blizz stop with nerfing her and fix her bugs instead plz.
I’ve got a bug for you to add to the list, but I sadly have no video or photo evidence:
Enemies will detect Sombra in range and see her, but Sombra will not have the DETECTED! notification pop up.
I just had this happen a moment ago and I was pretty confused as to how the guy knew I was there if he didn’t see me. Killcam showed me as clearly visible, though.
I will try to find that bug in the next few days and record it thanks for the hint I will add it as soon as I managed to recored it.
Well its probably not as easy finding bug in the game code as most of us (me probably included) and it’s probably also really annoying work to do. So lets try to make there work a little bit easier by finding the trigger behind the bugs that should make it easier to find them in the code (or at least I think it does)
That is the thing, we been made it a lot easier for Blizzard. Thank you for this post for sure by the way, but we made Blizzard job easier when we make very well constructed threads such as this one… all they have to do is acknowledge these type of threads and potential try and fix them while informing that these x bugs are being fixed in the upcoming patch.
Added one bug where Bastion’s animation does not get canceled by EMP it finishes and kicks him out again.
I could not find this one yet to record it but I will keep on looking to add it with a Video
That’s cute thanks >///< xD
I agree we tell them that there are bugs but for them to find the reason for this bug is still a big task. If we look at the TL Beyblade bug they and we know it has something to do with the coding of TL but where do you start looking for it? You probably would need to go over the whole coding of TL and test various changes in the coding. That’s why I want to narrow the bugs down as far as I can maybe even find a trigger or reason why the bug is happening sadly that’s a rare find (ノ﹏ヽ)
Added one bug that shows the stunning message after translocating shortly before getting stunned without getting actually stunned.
Well, its just what I think it what we can do the most the problem right now is a lot of them seem to be related to registering things like destroying objects, Killing heroes, Shields and but at the same time it does not seem ping related especially in bug 4, 2, 5, 10 and 15
The rotating platforms on Junkertown has always been like that. They are more like the payload. The platforms are not setup like most payloads and will not kick you out if you get underneath them.
My clips (Pivot 1 and 2) are the same bug. In both cases the Translocator has to become obstructed when used. This causes the game to pick a different point for the teleport.
Another example of it on Route 66
www.twitch .tv/videos/293553125
It also shows up on the Practice Range.
Ok I will correct myself on the route 66
I know they are triggered the same way but I keep the one that brings you into objects and the one that translocates you onto the wrong position as 2 bugs because the outcome is pretty different. And it really needs to be fixed I mean the one I get translocated onto the point is extremely broken I think.
Thanks for telling me
I also tweeted it out to a few people (sty and fitzy more will follow) in hope they see it and will raise the awareness of these exploit
btw. @Mesonnaise do you have time for some testing?
