BuzzerBeater Forums

The point may be moot since the U21 already has 16 players. I should have checked that first.

The NT can carry 18, so two can be added for free. I don't know how big the enthusiasm hit is, but it will probably be worth taking the hit to make upgrades.

I've harped on this before in both the NT and U21 threads... the free roster spots are gold.

We are down by 46 so far, so I'll make a wild guess and state that we might lose this one

What on earth happened to our lineup???? I set it couple of days ago... now it's all messed up... Hope it turns out ok... I set it up after form update, this is weird...

Looks like we'll win anyways. No harm done.

Final standings:

Team W L PF PA %
1 España 7 0 887 720 1.000
2 Italia 6 1 757 692 0.857
3 United States 5 2 735 600 0.714
4 Deutschland 4 3 748 706 0.571
5 Australia 2 5 833 835 0.286
6 Chile 2 5 741 819 0.286
7 Canada 2 5 802 930 0.286
8 Hong Kong 0 7 669 870 0.000

With a full roster for the game vs Deutschland we could have played CT instead of TIE and even if we didn't win (which still would have been possible) we could have stayed close. With that we could have climbed to 6th.

Oh well

I posted in bugs forum, currently i get a crash anytime i try to set a scrimage for our NT team. Not sure if I get to set up one in time or not.

Server Error in '/BBWeb' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

A crash is always a critical bug. You need to reevaluate the scale... It impacts the user experience to a level that is not acceptable

Ouch, 1 enthusiasm doesn't do much good