A Team is the place where drafted players go. In this case, an Owner (person) wins a bid for a School (Player) and puts that School (player) into one of their roster slots.
Technically, there are limitations on a Team:
Which schools (players) can go into which positions. For example, most schools can only be either their conference or FLEX/BENCH)
A team needs to have a budget equal to or greater than the bid amount for the school (player)
The initial implementation of this Auction draft will assume that the person running the draft will enforce these restrictions instead of putting them in code at this point.
A Team object contains:
Team Name (string)
Team Owner (Owner object)
Team Budget (int) (all teams start at the same amount, and winning bids reduce this amount. Can't go below 0)
A list of positions and their drafted schools (players) - I'm not yet certain whether I'm going to hard code this into the team object (Big Ten, Big Ten, SEC, SEC, Pac 12, ACC, Big 12, Flex, Flex, RandomSmallSchool, Bench) or whether this can be configured for every draft. I'm leaning toward a default being loaded, but then being able to configure it leading up to the draft, either via the web interface or via configuration file. The school can pop up additional information, but that isn't critical at the start.
Upon further reflection, I think that the positions should be determined at the start of the draft. You would indicate the number and name of positions.
A Team is the place where drafted players go. In this case, an Owner (person) wins a bid for a School (Player) and puts that School (player) into one of their roster slots.
Technically, there are limitations on a Team:
The initial implementation of this Auction draft will assume that the person running the draft will enforce these restrictions instead of putting them in code at this point.
A Team object contains: