BuzzerBeater Forums

Suggestions > Game Clock and Shooting

Game Clock and Shooting

Set priority
Show messages by
This Post:
00
1679.1
Date: 10/10/2007 3:21:48 AM
Overall Posts Rated:
00
After watching my team barely sneak through to the second round of the playoffs, something struck me as odd about the game clock and when certain events occur.

More specifically, when situations like this arise:
4:30 Player A attempts three pointer from the wing
4:30 shot missed
4:30 Player B corrals the rebound

...and all of this happens with the same second?
To me this seems very unrealistic. Am I to believe all shots take less than a second to go through the air, miss, and be rebounded all at the same time?

I suggest maybe have the game clock go down by 1 second between when a player takes a shot and scores/misses (maybe even 2 seconds if it's a 3 pointer). This way the game report would look more like:

4:30 Player A attempts jump shot from the free throw line.
4:29 shot missed
4:29 Player B grabs the rebound

To me this would look much more realistic in the game report.

Unfortunately, a draw back to this would be that scores in games would surely decrease overall as there would be less time of actual "playing". But maybe this would make more sense now because the majority of teams that exist in the BB world are new and don't have that great of basketball players (in terms of ratings) mostly because of little/no extensive training times.

What do you guys think about this idea?


This Post:
00
1679.2 in reply to 1679.1
Date: 10/10/2007 4:08:42 AM
Overall Posts Rated:
00
I dunno. it doesn't seem like one second would make that much of a difference. It seems like that would make matchviewer code more complicated and therefore slower. My opinion for what its worth.

Congrats on making it to the finals of your conference!

This Post:
00
1679.3 in reply to 1679.2
Date: 10/10/2007 6:31:17 AM
Overall Posts Rated:
00
hey thanks for the congrats!

I guess my idea would be more of a presentation suggestion than anything, which wouldn't be worth complicating and slowing down the matchview for, that's for sure.

But thanks for sharing your view, I hadn't thought of it that way.