BuzzerBeater Forums

ok, snuzers, the best thing is that they guarantee now that it will never happen again. So your complaint was not for nothing. You were completely right in everything you said, I agreed with it 100%. It was completely not fair. And they calling it "not a bug" was getting me upset too, the same way as the "dissapearing scrimmages" case. And the length of the season is irrelevant since only you can measure how important a victory is for your team or not.

But now we can celebrate that this bug is forever fixed, thanks to you and to the others that report bugs and help the improvement of buzzerbeater.

All I can say is "we'll see".....
I've only been playing for a couple of weeks, so I haven't been around for all the issues in development, but when I see a banner ad for something, I don't assume it's still in beta testing.....

I know I'm coming off as a bit of a jerk...ok a rather large one, but I'm hoping this game becomes what it can be.
It needs to be something Mr. Naismith would be proud of.....

I am just put off on the notion that the fundamental "game engine" is flawed. Having a player draw 35 personal fouls in a game is asinine and should never have been allowed to occur, much less have a team draw a total of 136 fouls. Even if every player on an NBA team fouled out, you'd only have 72 fouls...I had almost double that!!!! How does a player who has fouled out (6 fouls in the NBA) keep playing??

The logic should have been in place a long, long time ago for this situation to never occur and I'm glad it will now be a "thing of the past"....
What concerns me is that it occurred once, to multiple teams, something was said, and yet it occurred again before it was fixed..... In my series alone there are 6 games at least with this scenario........
if a fundamental rule of the game can be broken (players not fouling out with 6 fouls), then what is next? Free throws accidentally become worth 2 points? A blocked shot counts as a foul? If something that simple can't be managed, then future games shouldn't be played until it's fixed.
That's all......I'm done ranting.

Edited 9/17/2007 2:44:24 AM by snuzers


Edited 9/17/2007 2:54:43 AM by snuzers

p.s.: and I still cannot find a place where somebody referred to it as a non-bug. if so was said, it was surely a blunder.

there's no need for facts in the face of a good rant

p.s.: and I still cannot find a place where somebody referred to it as a non-bug. if so was said, it was surely a blunder.



Edited 9/17/2007 3:37:46 AM by BB-Domenico

My apologies, the first sentence from BB-Forrest in the Bugs, Bugs, Bugs conference,

this is related to the recent game engine bug ... which wasn't actually a game engine bug at all.

, stuck in my head.....
although he does say it is a bug....

I officially retract that portion of my earlier diatribe..... :)

Facts, we don't need no stinking facts........

ah.. yes....

as keeper of the game engine i am overly sensitive to things being called Game Engine bugs....
this is a bug.. but the correct fix for this bug is in the team reset code.. that has already been fixed...
however, it doesn't fix the teams that the team reset code with the bug had already been run on.

what's needed now is a complicated look into the database to find all those teams and reset their depth charts.
alternatively, we could start a list of afflicted teams and we can have admin go into their accounts and setup rando depth charts for them.

Edited 9/17/2007 10:33:47 PM by BB-Forrest


Edited 9/17/2007 10:33:59 PM by BB-Forrest