BuzzerBeater Forums

Bugs, bugs, bugs > shotclock violation: decisive 3-pointer in OT

shotclock violation: decisive 3-pointer in OT

Set priority
Show messages by
This Post:
22
292616.1
Date: 2/26/2018 3:06:38 PM
South Dragons
DBA Pro A
Overall Posts Rated:
494494
Second Team:
South Dragons II
In today's NT game between Croatia and The Netherlands something strange happened.

In overtime with 19 seconds left (the score was 120-122 at that moment) Croatia hits a 3-pointer which actually was a shotclock violation. Their offense started with 46 seconds left, a foul was made with 36 seconds left. Remaining shotclock is 14 seconds and they hit the shot with 19 seconds left in the game. A very decisive 3-pointer after 27 seconds which shouldn't be possible.
(http://www.buzzerbeater.com/match/44862/pbp.aspx)

The shot was obviously the dagger in the game. If shot clock violation was called they would have fouled us immediately which would have sent us to the FT-line with already two points in front.

Is it a bug? Is there an explanation for this?

Last edited by Cowstreet at 2/26/2018 3:11:22 PM

From: Cowstreet

To: aber
This Post:
00
292616.3 in reply to 292616.2
Date: 2/27/2018 1:00:44 AM
South Dragons
DBA Pro A
Overall Posts Rated:
494494
Second Team:
South Dragons II
I'm not asking to be compensated for it. I know the GE doesn't work like this. But I haven't noticed this bug earlier. Probably because it doesn't happen at a crucial point in the game all the time. But I'm sure you can imagine how it feels when you seem to lose the game "due to" this specific moment.

This Post:
00
292616.5 in reply to 292616.1
Date: 2/27/2018 2:40:23 PM
TrenseRI
II.3
Overall Posts Rated:
35993599
Second Team:
ChiLeaders
I have to say I'm not familiar with this specific bug. The one ending up with a steal is a well known one, this one seems to be something different. I'll take a look at the GE on the next update.

This Post:
00
292616.7 in reply to 292616.6
Date: 2/27/2018 5:21:11 PM
Overall Posts Rated:
32293229
My best guess is that whatever code is in the viewer is one set of logic, but that the engine doesn't really handle a shot clock reset - it just calculates whatever the result of the possession is, and then using some other logic determines when that happens.