BuzzerBeater Forums

I think your analysis is completely spot on. Now, as you both said, there are probably some uncertainties in the data, and the exact training increase v. height slopes might not be completely accurate, but I think the pattern is clear. JS forwards seems to bite the big one if you're using it for tall guys. Of course, there is less of an out of position penalty for playing a big man in the PF spot. so I can see times when JS forwards is good to do. Plus, it's a two position training, so you can add more guys to the mix, which can be useful if you have enough young guys.

But in the end, for big man training, the best way to boost both JS and IS is a combination of JS guards/wingmen, and IS@C.

For short guys, you can probably get a decent amount of IS training through a combination of 1v1f and JSf. You'll still get more training on that individual trainee if you do IS@C, at the cost of half the training slots, and more out of position penalty to performance.

Just posted a helper tool I made in Excel that converts the BB-Training Project analysis into a training modeler that includes the elastic effect. (229484.1) Hope you enjoy!

It's working good to me, I just have to change my language setting to English US and try a few times to upload the training, but I think it's because I always do it at the training update and many people are trying at the same time

no problems here

count me in in the having problems. I thought it may be because I'm use the latest Firefox beta.

Here's an oddity:
Uploaded my training for the week including a player I just bought.
He picked up his 48 minutes with his former team.
The training site does not recognize his training for the week.
Anybody else have that happen?

Normal.

Figured as much, was just my first.

I haven't updated much in a while, so I figured I owed one. So, I've added a new section: the bb-training blog! To quote from the first (and only) post:

Some of the analyses coming out of this project don’t lend themselves to a simple figure, or table, or whatnot, so I’ve put this blog up as a place to share some of the results in a more free-form setting. I also want to use it to explain a bit more about *how* the results are being acquired. This is important because for a lot of things, the data is not cut-and-dry clear, so I think it’s important that everyone be able to evaluate the methods for themselves, and decide how much to trust the results. So without further ado, our first blog post, on trying to identify and characterize the ever-elusive elastic effect.

Enjoy!