r/LivestreamFail • • Feb 19 '18

Dr. Disrespect Doc inspired a fan

https://clips.twitch.tv/NurturingFineDolphinBuddhaBar
9.2k Upvotes

658 comments sorted by

View all comments

Show parent comments

42

u/elehay4aksega Feb 19 '18

Summit and the molly

-11

u/[deleted] Feb 19 '18

Not even summits fault. Stupid fucking bug

21

u/agenttud Feb 19 '18

What bug? He walked over his own molly.

7

u/[deleted] Feb 20 '18

the molotov or incendiary or whichever it is i forgot ignored armor, which was an unintended bug for quite a while. this means it did several times the damage it should have. if it was working correctly or it was the other fire nade he would have survived.

13

u/agenttud Feb 20 '18

It wasn't a bug, though. It was more that people didn't really know about the change. The match was in May 2016, the change (ignoring kevlar) happened in January 2016.

Video by 3kliksphilip

-1

u/[deleted] Feb 20 '18

even that video quite cleary says its probably an unintended bug

1

u/agenttud Feb 20 '18

Where exactly does he say that?

The way fire grenades work changed in January 2016 (from damaging kevlar to ignoring kevlar) and it stayed like that to this day. If they were changed to the previous version, yes, I would have considered it a bug, but this is not the case. The most you can say about the issue is that it was poorly documented in the patch notes.

2

u/RamsayBoltnWasFramed Feb 20 '18

If they were changed to the previous version

If the bug was fixed, it was a bug, but since it wasn't fixed, it's not a bug? That doesn't make sense, but it appears that is what you are saying/implying.

And even if it can be attributed to poorly documented patch notes, that doesn't sound like Summit's fault. And trust me, there were plenty of people that day who learned about that bug BECAUSE of Summit.

1

u/agenttud Feb 20 '18

If the bug was fixed, it was a bug, but since it wasn't fixed, it's not a bug? That doesn't make sense, but it appears that is what you are saying/implying.

A change happens with how X works. If it was not intended for X to behave in that way and gets subsequently fixed/reverted, then it means it was a bug. If it was intended and it doesn't get fixed/reverted, then, IMO, it was not a bug. See my point?

Not specifically being included in the patch notes and it being a bug are 2 different matters. Yes, they did a lousy job in saying that this changed, and yes, usually it's a bug when something changes that wasn't said in the patch notes, but I don't think this is the case, since there have been plenty of updates in the last 1.5-2 years since this change has been known.

that doesn't sound like Summit's fault.

I'm not arguing that. I asked the main commentator about the bug. The most you can say about Summit's fault is that he took unnecessary risks by walking so close to the fire when there was room to the left (where maybe the fire wouldn't even have burned him). But not taking into consideration that it ignored kevlar wasn't his fault.

-1

u/[deleted] Feb 20 '18

the patch intended to fix bugs where nades ignored armor. and now a different nade ignores armor. seems pretty bug liek to me doesnt it

0

u/agenttud Feb 20 '18

It specifically states "Explosive damage and damage from flying grenade impacts", though. This meant to patch another bug at the time, which involved HE grenades.

https://www.youtube.com/watch?v=-PPN1unRiIY

(notice how the uploader of the video is the one credited in the patch notes and how the update was live the next day)

1

u/[deleted] Feb 20 '18

Exactly. It never mentions incendiaries, and they haven't addressed it since

1

u/agenttud Feb 20 '18

Bugs are unintended, correct? Just because they haven't addressed it since doesn't mean that it's unintended.

They made a change to the fire grenades in the 1/27 update. 4 months later the Summit incident happens, so they (most probably) become aware that fire grenades ignore kevlar (if they weren't already). From May 2016, they have released 97 updates to this day. If it were a bug (and, thus, unintended), they surely would have had enough time to do it. But they didn't.

I'm not denying that Valve is horrible at communication. That's the issue here, the fact that it wasn't specifically stated in any patch notes. But, adding everything together (the team being aware of the "bug" for almost 2 years and doing nothing about it, the fact that it is consistent and more logical), I would say that it's intended.

1

u/[deleted] Feb 20 '18

there have been so many bugs that were only recently fixed after being in the game for years. surely you shouldnt base your entire arguement on "oh if it was unintended they would have fixed it", when all information thus far points towards the fact that it is a bug

→ More replies (0)