BuzzerBeater Forums

You've understand why they can put, salary caps ,just some kind of restrictions,if they put a salary cap ,there will be a wave of dissatisfaction,among many why there's should be MVP,HOF ,ATG ,if we cant train them ?why we're overbidding on rookies with the hope of making the next salary beast for the future team not only the NT.There should be restriction but not that kind ,My propositions is if you still wanna play dirty you've have to pay the price,not forbidding it doing it but making it harder to achieve,and the transfer fee think is gonna be good adittion in to the effort of melting the The iceberg's of piled money.

You haven't read right my suggestion. I wrote you could go over salary cap by training, you just couldn't go over it by buying players. So if someone is able to go by training to 2M wage bill even if cap is 1.2M he could do it. But if his wage bill is 1M, he could buy player just with 200k wage.
Luxury tax wouldn't solve at all the issue that started this discussion.

and how would the engine recognize how you're training or in the off-season when salary changes how would recognize what players you can buy ,if you sell you're trainee what will be the drop ?,what would be allowed to buy too many if's and no pattern which can be applied,they added the day trading restrictions so to lower the abusing of the market and now the most of the trading evaluated is resulted ,as net loss or break even ,very few profits.The financial issues should be solved with financial tools
And what about the bug's what about if i have a 300k salary trainee and i transfer listed it and if i bid it on my self or over bid due to im tanking have tons of money ,already is listed as transactions and i can use my 200+300k=500k salary cap meanwhile to buy a 500k salary monster while im allowed to buy for only 200k and in the end you'll whine because i'm cheating or what ?and If i Do it 2-3-5 times im over top with a 1 mill ?

Last edited by Coach_D at 5/13/2011 6:08:10 AM

Not too many if's.
If you are selling player he would be still calculated to salary cap unless he is sold. So tricks with buying him back wouldn't work.
If you are 200k under the cap before salary update, you can bid player which is 200k even if deadline is after update (but you have to buy bid him before salary update and if someone overbid you than you can't bid him again, because you would be over salary cap).
So there is need of just one condition implemented, when biding any player sum of all your wages + plus wage of all the players you bid and the one you are just bidding can't be over the cap.

all of this is not answering how the engine is gonna recognize all of this and how would recognize you're trainee and if I buy a 500k salary guy and he pop in say IS is he counted my trainee, and now i have 500k free salary , or if i buy 10 guys and train them for only 1 pop to sell them with profit how the engine s gonna determine which is my trainee ,and if you respond with only your draft ,ill say i don't wanna my draft pick suck you bb's are robbing me you're not allowing me to train whatever i like.you're interfering with my team and my politics and not giving me options.And script wise i dont know how can be implemented such a think ,while a fee is fee its got exact margins probably 2 line's of code and no one can take advantage of it

Actually the good thing about this is you can go over the cap, but only training. It would benefit long term financial decisions and stability on rosters (because once you are over the cap you wouldnt be able to bid for players at all, and you would only be able to improve by training)

No need to recognize it. No matter if you train player yourself or someone else has trained him, the only idea is to be under the cap at the moment of biding any player.

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.

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