Quote:
Originally Posted by Fields
This is actually really good for helping you determine what's possible (if you put realistic numbers in there)
I believe the low/high goal needs to be corrected. I cannot get it to do a mix of the two. It seems to only rely on which is faster (and if a tie, do only high)
|
Yeah, that's how the code is written. If expected lineup+shooting time is shorter for one method, that's what they're going to try to do. It doesn't do an expected-value calculation because in my experience, drive teams don't plan on missing.
My justification is that a drive team will tend to always pick one in their strategy anyway, and they don't plan on missing, so accuracy doesn't get taken into account.
Edit: I just noticed I never pushed the actual app to github. Embarrassing...