BuzzerBeater Forums

BB Global (English) > BuzzerBeater's Best (B3-season16)

BuzzerBeater's Best (B3-season16) (thread closed)

Set priority
Show messages by
This Post:
00
181976.113 in reply to 181976.110
Date: 5/13/2011 7:49:42 AM
BC Hostivař
II.2
Overall Posts Rated:
11991199
Second Team:
Jirkov
As I wrote, if someone else brings any interesting idea I can support it as well.
I'm really worried about B3 future. Without any changes I expect B3 become competition for savings teams very soon and highly probably it would be the only strategy for B3 win. The only question is how many savings teams will build B3 team each season. I expect every other season there will be more and more these competitors.

This Post:
00
181976.115 in reply to 181976.114
Date: 5/13/2011 7:24:27 PM
BC Hostivař
II.2
Overall Posts Rated:
11991199
Second Team:
Jirkov
Maybe we don't understand each other well.
Last season there was no tanking team using his money to build team for B3. VS is in my eyes first tanking team ever which used tanked money to build team which could fight for B3 title. Even with 1,6M overall salary ESV Laim had just 3 really great players, so it's not even starting 5. He also made several mistakes, but I can't specify them because I hope someone else can make similar mistakes. VS has already had great starting 5, with really good one backup for PG/SG, second one for PF/C and decent backup for SF. And I think he hasn't been finished with his purchases yet. I don't think injuries are real danger for him, too much injuries needed. There are two main possibilities how to stop him: 1) his mistakes (mainly tactical) 2) another tanking team using saved money for the same strategy as VS.
Also enthusiasm use in his league is no problem for him, he can play TIE every league games. Game shape is also not problem (you probably know why).
And I'm not talking about final 32. There are too many team which can go into final 32. Personally I think I can go into final 32 with 8-0 record, probably my roster will be one of strongest (let's say one of top 10), but I don't expect my team to be danger for VS even if I buy another bigman that would make my roster comparable with my last season roster (but probably I don't plan to buy any bigman for this purpose).

The game is still very young, so almost all tanking teams are still in period of tanking, I think B3 concept have worked quite well so far (except for season 14 final), but I'm worried about the future as tanking teams starts using his savings and we will see if I'm right with opinion that now begins area of tanking B3 winners (if there are no changes in the game) or kamikaze B3 winners (that end after B3 win or starts tanking period).

Last edited by rwystyrk at 5/13/2011 7:28:10 PM

Message deleted
This Post:
00
181976.117 in reply to 181976.115
Date: 5/13/2011 8:22:33 PM
Overall Posts Rated:
916916
Why not a salary cap like the NBA?



From: Sparkle

This Post:
00
181976.118 in reply to 181976.117
Date: 5/13/2011 11:18:06 PM
Overall Posts Rated:
2525
The salary cap suggestion was brought up numerous times in the past but it didn't really take off.

So instead of capping salary, why not we focus on the club economy instead? Teams cannot go over a certain amount on their weekly balance, like -300k excluding transfers or else the club's account manager will step in. This should have the dual effect of helping new teams destroying themselves economically by buying cheap, huge monster players without knowing the repercussions.

This Post:
00
181976.119 in reply to 181976.118
Date: 5/14/2011 2:19:18 AM
BC Hostivař
II.2
Overall Posts Rated:
11991199
Second Team:
Jirkov
In what moment it would be checked?

This Post:
00
181976.120 in reply to 181976.119
Date: 5/14/2011 2:46:58 AM
Overall Posts Rated:
2525
Weekly, during the weekly economic update. It's when your account manager tells you to do something about it or he'll start listing your top earner to balance the books. This will cover scenarios where teams load up near the max, then season updates happen and their trainees push them over.

It will also need to be checked during bids on the transfer list if the new player's salary will push the team too much in the red. If it does, the bid cannot be made.

This is just off the top of my head, I'm sure there might be more scenarios to cover.

This Post:
00
181976.121 in reply to 181976.120
Date: 5/14/2011 4:18:32 AM
BC Hostivař
II.2
Overall Posts Rated:
11991199
Second Team:
Jirkov
I have one problem with this idea. Revenue could be very different in different weeks due to difference of attendance income and merchandise. So one week you can be ok whilst the other not.

This Post:
00
181976.122 in reply to 181976.121
Date: 5/14/2011 4:45:34 AM
Overall Posts Rated:
2525
It's just a rough idea, plenty of edges to sand off.

This fluctuation is expected and I was also thinking along the same lines on how to get around economic cash fluctuation. A two tier cap instead of one. The first softer cap (Maybe from -100 to -300k) will render you unable to purchase newer players. The second harder cap (maybe at -600k) is when your BB Accounts Manager steps in. The difference between the first and second cap should be sufficient to cater for any fluctuations in economy.

Exceptions. There will be one week during the normal season where some teams might not have a home game. In this event, the previous week's attendance revenue (Accountants like to go by hard, relevant data) will be used to determine if the club is operating too much in the red.

This Post:
00
181976.123 in reply to 181976.122
Date: 5/14/2011 4:59:15 AM
BC Hostivař
II.2
Overall Posts Rated:
11991199
Second Team:
Jirkov
I have one issue on this idea. For B3 purpose it could mean higher salary cap for team from big countries due to TV contract, otherwise in big countries teams can have more trouble with attendance income. So I prefer more salary cap than your idea. Salary cap could be set different for different league levels but the same all around the world. Your idea finally is kind of floating salary cap, but I think too complicated to understand for many users and also much complicated to implement.
I think any idea how the solve the problem should be as simple as possible.

Advertisement