Quote:
Originally Posted by kckid4u
Well, it certainly wasn't me. I've bought every version since time began and certainly never said I wouldn't be buying this version.
|
So have I, since stb3k.
Quote:
You got me there!
Basically, for me, this used to be a feature in previous versions of OOTP, and it worked very well, so I don't see why there would be any problems in it working again. It's pretty simple, and I'm pretty sure if given the option, 99.9% of the game's users would love to see this feature return.
|
Ok, since you asked, I'll try to explain in a briefer and clearer way in a programmer's POV of why the depth chart is redundant.
I'll use my team as an example, rather than listing positions.
Starting SS: Amsalu Mbingu. Worst hitter in my lineup. Excellent middle infielder, the best in the league.
On the bench I have:
MIF Jemke Koolen. Even worse of a hitter, but should (hopefully) retire at the end of the season, but is on the verge of getting his 500th homerun. Currently has 498.
MIF Vin Palermo (as myself.
) A very promising young middle infielder with very raw talent, and higher current hitter ratings than Koolen and Mbingu.
If I were to place Koolen above Palermo in the pinch hit depth chart, this is how it would work with the AI:
The AI will use the depth chart strictly. (Otherwise, it's a waste of space if it skipped Koolen and went for Palermo instead.) The AI also wants to maximize its chances of winning a ballgame.
Scenario I:
The AI, when it decides it may be time for a pinch hitter; generally when the L/R split favors the pitcher and the rating of the current hitter (Mbingu) that is coming up; doesn't present a good chance of bringing home the run....the AI would do a check between Mbingu and Koolen. If the AI decides Mbingu presents a better chance of bringing home the run, then Koolen will not be brought in to pinch hit because the AI was programmed to maximize its chances to win the ballgame. If Koolen will not be brought in to pinch hit for Mbingu, then Koolen will never be brought in to pinch hit for anyone. Ever. Because Mbingu is the worst hitter in the starting lineup, but is still better than Koolen. Except maybe for an injury or something. If Koolen is never brought in, then Palermo cannot be brought in either since he is lower in the depth chart.
If the AI was allowed to skip to a lower spot in the depth chart to perform a check on Palermo, it violates the depth chart that you want the AI to use. Without the depth chart, it would use Palermo anyway, thereby making it redundant.
Also, if you want the AI to definitely use the pinch hitter on top of your depth chart for the lowest-rater hitter in your starting line-up, it would probably disrupt the logic of the AI to try to win a close/late game. How/when would the AI ever decide to use Koolen in favor of Mbingu? It couldn't, because there is never a better time than any others to use him, because he is and always will be, the worse of the two hitters. You would also disrupt the AI for other players who purchased OOTP, because they may not ever want to replace anyone in their starting lineup for a pinch hitter.
Scenario II
Palermo is on top of the depth chart ahead of Koolen. Scenario II is also useless, because the AI would use Palermo without the DC anyway.
Scenario III
(Solution of using a simple check box in strategy screen in post number 40)
Scenario III for use in a depth chart gets even more complicated if you take the situation as described in post number 41, involving more players on your team. The end result of which would revert back to Scenario I, only it would take a more complicated, convoluted loop than the first Scenario without accomplishing what you, as the end-user, would be satisfied with.
You can easily do away with a depth chart, which would have to place necessary restrictions on the AI to follow the thing strictly, due to the second scenario. Hence, post number 41 describing the usefulness of two different check boxes for player strategies involving pinch hitting. This wouuld keep the AI flexible enough to follow your wishes as much as possible while still trying to win a close/late game as well (Post #41....hint, hint!).
Post number 41 is where I would get my Scenario III for the depth chart problem. This is a scenario in which more than two players would be involved on the bench, and more than one player in the starting lineup. Once again, as described is in post number 41.
Notes:
1. If a program has a redundant piece of code in it that doesn't make much of a difference whether that code is there or not, it is by far always better to just remove said piece of code, in order to simplify the entire code. For one, if your program contains an AI, a simpler code makes for a better-functioning AI. Smaller code also makes for quicker loading times and smaller file sizes. Always a plus especially for those d/l the game; and even more especially for those playing in online leagues.
2. Sorry. I kept this as brief as possible. Hopefully this post makes more sense than post number 40. If you are confused about what I meant in post 41, then please, go ahead and say so if you are confused, and truly want to know what I was talking about. I shall try my best to clarify.