GregR_2
Footballguy
I was hoping to make use of MFL's option to allow backup players. The website's feature just has the website allow you to specify a number of players as backups when setting a lineup. It is then up to the league to define offline what the criteria are for a backup being used, determine if they are met, and for the commish to manually change the lineup and recalculate the results accordingly.
I'm fine with all that, but I thought up some abuse for the feature and was wondering if anyone else has been down this road and has suggestions on how to craft rules to use the feature without allowing the abuse. First, it's important to note that players can be moved in and out of our lineups until their own game starts, at which point they are locked either in or out. The way I was looking to use the backup is that the backup only scores if the starter got a DNP (did not play) or was marked as Inactive in the NFL.com Gamebook.
So here's the situation. You have a backup in an early game, and starters in a late game. The backup RB goes off for 200 yards and 5 TDs, but the starters haven't played yet. The website would allow you to go switch out one of your starters for another late game player who is out or doubtful or otherwise is more likely to meet the criteria by which the backup would be used, in the hopes to get the points from the backup whose results you already know.
The same issue is there of course if the backup does absolutely nothing. Rather than gamble on your injured starter who was doubtful figuring your backup would cover well if he sat out, maybe you remove him and stick in a RB you wouldn't have otherwise played since he's likely to play and can't do worse than the backup who faltered.
I think the ability to change your lineup for players whose game hasn't started is more important than having backups, so I don't want to just disable that option. I prefer not to restrict people from changing starters just because the backup has played already, both because I think owners should have that flexibility, and because I don't want to have to comb the transaction logs each week to see if anyone did just that.
Anyone have any ideas how to implement backups without hitting this kind of problem? While I don't necessarily think my owners will use this kind of loophole, I have thought that before of people and been thoroughly disappointed by the reality.
I'm fine with all that, but I thought up some abuse for the feature and was wondering if anyone else has been down this road and has suggestions on how to craft rules to use the feature without allowing the abuse. First, it's important to note that players can be moved in and out of our lineups until their own game starts, at which point they are locked either in or out. The way I was looking to use the backup is that the backup only scores if the starter got a DNP (did not play) or was marked as Inactive in the NFL.com Gamebook.
So here's the situation. You have a backup in an early game, and starters in a late game. The backup RB goes off for 200 yards and 5 TDs, but the starters haven't played yet. The website would allow you to go switch out one of your starters for another late game player who is out or doubtful or otherwise is more likely to meet the criteria by which the backup would be used, in the hopes to get the points from the backup whose results you already know.
The same issue is there of course if the backup does absolutely nothing. Rather than gamble on your injured starter who was doubtful figuring your backup would cover well if he sat out, maybe you remove him and stick in a RB you wouldn't have otherwise played since he's likely to play and can't do worse than the backup who faltered.
I think the ability to change your lineup for players whose game hasn't started is more important than having backups, so I don't want to just disable that option. I prefer not to restrict people from changing starters just because the backup has played already, both because I think owners should have that flexibility, and because I don't want to have to comb the transaction logs each week to see if anyone did just that.
Anyone have any ideas how to implement backups without hitting this kind of problem? While I don't necessarily think my owners will use this kind of loophole, I have thought that before of people and been thoroughly disappointed by the reality.
Last edited by a moderator: