Quote:
Originally Posted by kstater
Ok, then how did my QB change. Bradford started week one. Then some how it pulled him in favor of Kerry Collins. Then somehow Caleb Henne played the next several weeks.
|
Several things could be in play here:
1. I initially had is set where if the owner didn't check in for more than one league week, that a bot would take over the management of your team. I've backed that off to 3 or 4 weeks now.
2. Rain Man mentioned the glitch where I had to reset one week and a lot of people's rosters got hosed.
3. During weeks 6 and 7 Caleb Henne was the only active QB on your roster. It isn't currently programmed to start a player once he becomes injured; you have to reset them as a starter manually. This is the reason that I had originally had the bot take over after 1 week of inactivity. The bot would have changed your starting QB.
4. In short, I designed the interface assuming most owners would check their rosters every league week.
5. A depth chart style interface would solve a lot of this and is probably the correct long term solution. I almost decided to add this during the short hiatus between games 7 and 8. But Rain Man is right -- it gets complicated fast if you want one player to back up more than one position. I think I came up with a solution, but it would have taken a week or more to code. I didn't want people to have to wait that long to start the simulations again.