BuzzerBeater Forums

Suggestions > Time to game is not correct above 100Hrs

Time to game is not correct above 100Hrs (thread closed)

Set priority
Show messages by
This Post:
00
199699.1
Date: 10/30/2011 01:50:11
Overall Posts Rated:
105105
The time until next game supports only 100 Hrs.
When the time is 100Hrs or more, you will see 99:59 until next game.
Why not changing it to be Days + Hrs until next game when Time >= 24 Hrs (for example).
[Exactly like it is when Time < 1Hr, when it shows the time upon Minutes and Seconds.]

[I think it is a bug, but I was requested to move it to this section... so... here it is]

This Post:
00
199699.2 in reply to 199699.1
Date: 10/30/2011 13:04:00
Overall Posts Rated:
3535
Agreed.

This Post:
00
199699.4 in reply to 199699.3
Date: 10/30/2011 19:14:06
Overall Posts Rated:
105105
Wrong visualization is a bug. It should show the correct time.

I don't understand why not calling it a bug, but it doesn't realy matter to me.
I don't earn anything from fixing bugs.
At least not from this game...
I suggest to fix this tiny issue. [BTW - fixing is when there is a bug that is needed fixing...]

Anyway, good luck with that!

This Post:
00
199699.5 in reply to 199699.4
Date: 10/30/2011 19:47:37
Overall Posts Rated:
237237
Wrong visualization is a bug. It should show the correct time.


If it is "wrong" by design then it is not a bug.

The BBs designed it to show 99:59!!

This Post:
22
199699.6 in reply to 199699.4
Date: 10/30/2011 21:19:48
Overall Posts Rated:
766766
In IT a bug is something which doesn't work how it was to be intended. Some developers will even suggest that a bug is only something which 'breaks' the system, although this is generally an old-school view on things.
If the clock showed 10 hrs to a game, and in fact, it was 20 hrs to a game, that would be a bug.

Us developers get a bit testy about people calling our hard slaved implementations 'bugs'. (Especially when you turn around to the customer, shove the specification doco in his face and say 'Thats what you bloody asked for!')....

So yes. Bug or no bug,
its a good suggestion. :)


This Post:
00
199699.7 in reply to 199699.6
Date: 11/01/2011 04:16:37
Overall Posts Rated:
105105
I don't see it this way.
If a design is wrong, than it is a bug in the design.

Anyway, I enjoy your product (this game).
So, keep up the good work!!!

[Definitions are not that important, improving what can be improved is the goal]

This Post:
33
199699.8 in reply to 199699.7
Date: 11/01/2011 05:40:57
Overall Posts Rated:
3535
Well, if you don't see it that way then you're wrong.
Sorry to break that to you.
It's not a matter of opinions here.

This Post:
00
199699.9 in reply to 199699.8
Date: 11/01/2011 22:05:25
Overall Posts Rated:
766766
the definition of a bug is a contentious issue not just within Buzzerbeater. Where i work people throw the word 'bug' around very loosely. When someone tells me there is a 'bug' i usually get very angry, because 99% of the time, ive just coded what they have asked for and they havent told me well enough.

The orange juice example - Client asks for a glass of orange juice. I give them Brand X orange Juice in a glass. They reply saying 'oh but i wanted Brand Y orange juice'.

well... they didnt ask for Brand Y, they just said 'a glass of orange juice'.... this is not a bug.

So seeing as though the english language is a very contentious language to learn, might i suggest that instead of using the word 'bug' - use the word 'Flaw' or.. 'problem'. or... 'something not quite right'.

Developers will love you more :)



This Post:
00
199699.10 in reply to 199699.9
Date: 11/02/2011 02:41:50
Overall Posts Rated:
105105
the definition of a bug is a contentious issue not just within Buzzerbeater. Where i work people throw the word 'bug' around very loosely. When someone tells me there is a 'bug' i usually get very angry, because 99% of the time, ive just coded what they have asked for and they havent told me well enough.
Then it is a bug at the System-Requirements.

The orange juice example - Client asks for a glass of orange juice. I give them Brand X orange Juice in a glass. They reply saying 'oh but i wanted Brand Y orange juice'.
well... they didnt ask for Brand Y, they just said 'a glass of orange juice'.... this is not a bug.
This is a "bug" at the customer request. As the customer does never has bugs, it is still the seller fault. :+)

So seeing as though the english language is a very contentious language to learn, might i suggest that instead of using the word 'bug' - use the word 'Flaw' or.. 'problem'. or... 'something not quite right'.
Developers will love you more :)
I didn't blame anyone, but it is a bug - SyRS, design or implementation. It doesn't matter.
The clock is supposed to display... the correct time.
The purpose of opening a bug is not to blame someone, but for improving the product current fault behavior.

It is funny, I've just wanted this feature fixed, and haven't thought it will cause too much noise, as it is non-mistakable a bug/wrong-behavior/whatever, and one that can be fixed easily and fast.
Instead the discussion came into defining what a bug is... :+)
Not that it annoys me or something, it is just surprising...

This Post:
00
199699.11 in reply to 199699.10
Date: 11/02/2011 04:00:25
Overall Posts Rated:
237237
Then it is a bug at the System-Requirements.

It is NOT a bug. The clock showing 99:59 is by design of the developers. Whats to say it is "wrong"? The BBs could have wanted it this way.

This is a "bug" at the customer request. As the customer does never has bugs, it is still the seller fault. :+)


It is NOT a bug. It is the customer being unclear about specification requirements. This is not sales and customer service. In IT the customer is NOT always right. It is more often just a matter of opinion and what angle you look at it.


So stop calling it a bug. Calling it a bug makes it sound a lot more dramatic than it should and implies that the BBs have done something wrong with their programming. This is clearly not the case as it is showing that by design.

It is an enhancement request.