Scenario: Had this occur today, got busy at work and I have multiple players who are not playing with backups resting on the bench that I can’t use today now. 
Proposed idea: What if RosterOrg allowed me an option to set a “Depth Chart” for each position such that let’s say I have Josh Bell and Jared Walsh I could set Bell as my starter and Walsh as a backup. In the case the Bell doesn’t start and I’ve enabled the “Depth Chart option” then Walsh would be subbed in automatically.
Dave Cameron asked for this in like 2016 or 2017.
Ultimately setting lineups is a huge reason why people engage with the site and their league and removing the ~90s ritual of setting lineups would have a really negative impact on Ottoneu engagement.
On top of that, depth charts can get extremely complicated quickly with multiple eligibilities, etc.
So, this is not going to happen.
That makes sense, I know I’m the type of user that would come in daily regardless of a depth chart. But I’m an abnormal user and I can see how this would negatively impact overall engagement, I didn’t think of that!
Thanks for the response!
If it could also incorporate platoon splits, that would be great too! For example, Arraez is 2B1 if and only if a RHP is starting.
I agree that setting daily lineups is one of the best parts, but what if the auto depth chart feature only kicked in to protect from having an empty slot due to a postponement? Is that too niche of a feature to spend time on?
I was in a game that allowed for the points to be counted for the backups to count if the starters didn’t play. This would be for positional players only.
I find myself going back throughout the day to see if my starters have been scratched before the games begin. In that stye you would have a starter and you would select a backup from your bench and you would get his points only if the starter didn’t play.
Has this been talked about before? This way it relies less on when you set your lineup.
Thoughts?
Per this thread, there is little to no chance of this happening.
What are the drawbacks?
You would still set your lineups but would have backups.
“backups” with multiple eligibilities gets very complicated very quickly. I’m not sure how further to explain this.
To fully implement something like this, the end user would need to have some knowledge of programming to assign priorities. It would take a nontrivial amount of time to set up and not be very intuitive for some (and probably not very fun for people who do know how to do this sort of thing).
So imagine having the end user having to program something like in basically a script such as the following:
SELECT
CASE
WHEN Guerrero=‘In MLB Lineup’ THEN Guerrero
WHEN Arraez=‘In MLB Lineup’ AND Arraez=‘Available’ THEN Arraez
WHEN Belt=‘In MLB Lineup’ THEN Belt
ELSE NULL
END AS 1B
FROM team_roster
Note: here Available would mean that Arraez wasn’t already in the lineup at another position. You’d also have to order the 2B entry ahead of the in the code if you wanted Arraez to start at 2B rather than 1B if both were open that day.
And that’s just what you would need to script out for just one position where you had a depth chart of three players. It would get very tedious very quickly to have to do this for a full lineup across all positions, let alone across multiple teams.
It would be a relatively high bar to entry and probably wouldn’t be a whole lot of fun for most people. You can only go so far with a GUI because of the challenge of assigning priorities to players who have multi-position eligibility. I can’t see a way around the end user needing to learn how to write some sort of script.
The alternative is to reward continuous engagement (i.e., the status quo). That seems like a better approach to me.
If this sort of thing appeals to you, there might be a way to leverage Selenium to auto-adjust your lineups. IDK. I don’t have that level of skill (or interest) in setting something like that up.
EDIT: To say nothing of the risk that someone failing to close a loop or whatever crashes the site. Pretty sure it would be chaos very quickly.
I am not a programmer but I do know this . I was in Game Day Ritual for 13 years before joining here and it worked.
I just had this same thought today. Right now I have to keep checking in until lineups are announced to see who is actually playing today. Sometimes the early games have already started by the time the late game lineups are announced.
Perhaps the implementation could just be as easy as having a “backup lineup” that you can fill out with any players not in the “active lineup”. If the “active lineup” player is not in the real-life lineup when they are released, it would switch to the player for that position in the “backup lineup”. This way there is no multi-positionality logic necessary, as the player has to manually set where they want that player in the “backup lineup”. It seems like this would still work fine with the auto-bench option as well, e.g. if both players are not in the real-life lineup, it would remove both from the “active lineup”.
If this is complex to implement it’s not a huge deal, but it is a quality of life enhancement that is worthwhile IMO. I am happy to check into the website every day, in fact, multiple times a day, but sometimes I just can’t check in during the narrow window between lineup announcements.
Again, I cannot be more clear: there is not ever going to be a depth chart-type system or a backup lineup system built.
This is exactly why the auto-bench toggle exists - the site will put players to the bench that aren’t playing, making those lineup slots available for you to put players into later in the day.
This sentence is self-contradicting. Without knowing how complicated it is to implement it is impossible to know if it is a qualify of life enhancement that is worthwhile to pursue.
I believe even the simplest ‘back up’ system would be overly complicated to implement from both a user interface perspective and a back end perspective for extremely minimal advantage over the existing auto-bench feature. I have no interest in spending any of my time building this system and do not see that changing any time in the future.