BuzzerBeater | BuzzerBeater Forums | Bugs, bugs, bugs

BuzzerBeater

	BuzzerBeater Forums
	Bugs, bugs, bugs > Game engine bug(s)

Bugs, bugs, bugs

Game engine bug(s) 4

Can't reach national team sche... 1

3rd game bug 2

matches yet to start. 49

22-10 Match delays 2

Live view isn't working 6

Walkover minutes 23

MVP 3

Boxscore old NT game 5

Unable to change e-mail adress 7

Missing PO game? 5

Random Game Shape? 10

Ratings system 3

whats with training 6

transfer bug 8

NT Schedule 19

No Sat/PO Game updates 3

table incorrect 4

Game Shape Training 2

this game 10

< >

Favorite Folders

Game engine bug(s)

Set priority

Show messages by

Search this Thread (Supporter Feature)

From: Pini פיני

This Post:

199070.1
Date: 10/21/2011 11:52:57 AM

Overall Posts Rated:

105

1) I've seen cases where the clock continue ticking about 5-7 seconds after the 24-seconds clock expired and nothing happened.
The result of it had been ball intercepted/stallen, but this shouldn't eat the clock that much.

2) I think I've seen a case where there was a foul when the 24-second clock had been in the range of 15-24 and the clock had been reset to 24 instead of continuing from the time of the foul.

3) There is a little bit unrealistic scenario where one team throws when the clock is at about 1-2 seconds to the "end of a quarter", and the other team is able to take a rebound, go to the other side of the court and make a lay-up.
It doesn't realy affect the game much, but it will be nice if it could be more realistic in this sense.

Mark Unread Ignore User

From: Boston Celts

To: Pini פיני

This Post:

199070.2 in reply to 199070.1
Date: 10/21/2011 3:56:22 PM

Overall Posts Rated:

345

1) I've seen cases where the clock continue ticking about 5-7 seconds after the 24-seconds clock expired and nothing happened.
The result of it had been ball intercepted/stallen, but this shouldn't eat the clock that much.

you are lucky, some experienced 30 seconds after the 24:) oldest bug in the book

2) I think I've seen a case where there was a foul when the 24-second clock had been in the range of 15-24 and the clock had been reset to 24 instead of continuing from the time of the foul.

it;s supposed to reset to 14 if it's with NBA rules, however considering step 1...:)

3) There is a little bit unrealistic scenario where one team throws when the clock is at about 1-2 seconds to the "end of a quarter", and the other team is able to take a rebound, go to the other side of the court and make a lay-up.
It doesn't realy affect the game much, but it will be nice if it could be more realistic in this sense.

these are all viewer bugs, and don;t actually affect the game:)

Mark Unread Ignore User

From: Pini פיני

To: Boston Celts

This Post:

199070.3 in reply to 199070.2
Date: 10/22/2011 7:08:21 AM

Overall Posts Rated:

105

2) I think I've seen a case where there was a foul when the 24-second clock had been in the range of 15-24 and the clock had been reset to 24 instead of continuing from the time of the foul.

It's supposed to reset to 14 if it's with NBA rules, however considering step 1...:)

Not exactly. It should be reset to 14 only when the 24-clock is below 14.
When the clock is above 14 the clock does not change and will continue form the time the foul commited.
This is a bug that can (very) easily be fixed.

3) There is a little bit unrealistic scenario where one team throws when the clock is at about 1-2 seconds to the "end of a quarter", and the other team is able to take a rebound, go to the other side of the court and make a lay-up.
It doesn't realy affect the game much, but it will be nice if it could be more realistic in this sense.

these are all viewer bugs, and don;t actually affect the game:)

They are bugs that should be fixed.
The user expects it to be as realistic as possible.

Last edited by Pini פיני at 10/22/2011 7:08:59 AM

Mark Unread Ignore User

From: BB-Marin

To: Pini פיני

This Post:

199070.4 in reply to 199070.3
Date: 10/24/2011 10:05:40 AM