Re: OSFM w/40 man and SCEA 4/13 additions imported
Thank you so much for your response !!!! The tons of info you provided is appreciated. It looks like this is the roster for me. Another question.... What does the 4/13 update mean in the name of this roster set ? This roster set does not update week to week does it ? Thanks again !!
I'm gonna help you out a bit because people have helped me out here for years and I've always tried to do the same back if I feel like I can save someone else hours of research even if it means reading one of my ridiculously long posts. 
Sorry for the clutter in your thread, @Millenium. (Consequently, why doesn't '@' tagging work in forums yet?)
It helps to understand from the start, that a lot of the ways roster files are made for this and other sports games (but particularly baseball where roster sizes change) exist to deal with limitations, quirks, options the game has for playing seasons or franchises. The next variable is how people like to play the game. Everything from controlling every single aspect of the game and all its managerial decisions across the league, to only focusing on one team but having control of all the others so you can modify what the computer generates on its own, to letting the computer have full control over everything and just going along for the ride with your favourite team.
These are the factors roster makers deal with...
1. With any roster file that has players spread throughout all the levels of baseball (MLB, AAA, AA, A) such as the original roster file, if you take it into a franchise or season, the game will use an official 40-man roster to begin your season with, just like real baseball teams do. It is a mathematical algorithm that attempts to take the best players available on that squad, so naturally, it causes several unrealistic choices. At the end of Spring Training in Franchise or Season, just like in real life, the CPU will cut that down to 25, again by its own algorithm choosing the best players on the team. The other 15 get added to the minors based again on the CPU's algorithm.
2. For the sake of offering realism (and to be just generally amazingly helpful people) roster makers have taken on a practice over the years of saying, the guys that are injured in real life to start the season we're gonna put in 'A' ball on the roster so you can have them off the MLB roster. You do with them what you please. Putting them in 'A' ball just gets them visibly out of the way and taking them off the 40-man in the roster file helps to keep them from being used.
3. Here's the part of the programming of the game that some of us use in our favour... If you send a roster file into a Season or Franchise, that already ONLY has 25 players on the 40-man roster, where you've taken the other 15 guys and placed them in the minors, we noticed several years ago that the CPU doesn't and won't realign the team or move people around when Spring Training ends. So if you're a roster maker, you can offer a roster file with 25-man rosters where the lineups and rotations are set already (according to your own research) and people using your rosters don't have to go to all the trouble because the game won't mess them up when the regular season begins. Like I said, "generally amazingly, helpful people".
4. Some people only want the 40 man roster locked in, but have no interest in all the teams looking like they do in real life, because they let the CPU create a sort of fantasy baseball world where the conditions are the same as opening day, but from that first crack of the bat they want their season to go in a completely self-contained direction that doesn't attempt at all to emulate what's happening in the real season. So, some roster makers offer 40-man rosters so that the teams are all accurate but it's understood that they'll get shuffled when the user's season begins. This is about making sure the 40 guys are correct but not caring much what the lineups look like.
So now, if you read all that, to your questions...
Maybe you already get this now, but "injured" is only a way of saying they're dropped into 'A' ball in the roster maker's file. if you make sure those injured guys aren't on the 40 man roster, then no they won't get brought up. But if you do put them in 'A' ball and KEEP them on the 40-man roster and they're a star player, they're pretty much guaranteed to be in the starting lineup when the rosters get reshuffled at the end of Spring Training because the CPU will think, "well, this really high-rated Cliff Lee guy is on the 40-man roster but in 'A' ball for some reason, so obviously I'm moving him to the MLB team". Even if you're only controlling one team, none of the CPU players removed from the 40-man will move up. It can happen to them during the season if there are injuries. Someone correct me if I'm wrong here.
The CPU has no way of knowing what "their starting position" is. Every player is just a number ranked in a list of other numbers and they'll go wherever the CPU thinks they should go based on stats, characteristics, and their teammates ratings as well. Again, someone correct me if I'm wrong.
I don't know that answer but downloading the file and looking at it is going to be the fastest way to get an answer.
In fact, downloading a roster file, playing with it, running simulation seasons, changing up the different important factors (the ones I mentioned above) is always going to be the best way to learn what the game does, why, and why the roster makers all offer what they offer. I've been playing The Show since 2007, and even I ran tests just this week to try playing my seasons in a new way that I've been thinking about. It was the only way to get my answers. It's the best way to see what happens and how the CPU behaves to find YOUR way of playing. Run a season/franchise, see what happens, "hmm...that didn't work...", delete it, start a new one, change the settings, "ok, good, but now I don't have the ability to change X...", delete it, modify the rosters, start a new one, etc etc etc. Then eventually you'll say, "Ohhhh.... that's why millenium/the OSFM team/Lisac did that with their file. So that you can..."
There is a tendency, not just in this forum, to talk amongst the community like all of us know every little detail, every part of the development of the different ins and outs of the game. Because of this, often, reading through a thread can feel like listening to some secret code and I'll be the first to say that I find it ridiculous to expect new people to read through 25 pages of posts just to learn one little detail that can be answered by one person in a fraction of the time. And "go search for it" isn't always a good answer because to search something, search terms need to be part of every answer and often an "answer" is part of a series of posts and not in one dictionary listing type of place. This is the flaw of the internet forum design/UI, it's never responded to the need for fast information from users that has already been asked before so forum members have taken to tearing anyone apart who dares ask, "When is the patch due?". In EVERY single instance, the time and anger it takes to put that person in their place is more than twice the time it would have taken to just say, "We don't know yet", lock the thread, and delete it. Done, problem solved. I think a chat window above the forum would solve this instantly.
The point is, it's good to ask, I don't see it as the crime others do. And I'm not telling you what to do in the future, but you'll be amazed what trying stuff yourself will teach you. You'll even learn a lot of the time, like I have, that there are ways of manipulating games that nobody else seems to know about and that you play in a way that nobody else does.
Oh yeah, this one is definitely already answered.
Sorry for the clutter in your thread, @Millenium. (Consequently, why doesn't '@' tagging work in forums yet?)It helps to understand from the start, that a lot of the ways roster files are made for this and other sports games (but particularly baseball where roster sizes change) exist to deal with limitations, quirks, options the game has for playing seasons or franchises. The next variable is how people like to play the game. Everything from controlling every single aspect of the game and all its managerial decisions across the league, to only focusing on one team but having control of all the others so you can modify what the computer generates on its own, to letting the computer have full control over everything and just going along for the ride with your favourite team.
These are the factors roster makers deal with...
1. With any roster file that has players spread throughout all the levels of baseball (MLB, AAA, AA, A) such as the original roster file, if you take it into a franchise or season, the game will use an official 40-man roster to begin your season with, just like real baseball teams do. It is a mathematical algorithm that attempts to take the best players available on that squad, so naturally, it causes several unrealistic choices. At the end of Spring Training in Franchise or Season, just like in real life, the CPU will cut that down to 25, again by its own algorithm choosing the best players on the team. The other 15 get added to the minors based again on the CPU's algorithm.
2. For the sake of offering realism (and to be just generally amazingly helpful people) roster makers have taken on a practice over the years of saying, the guys that are injured in real life to start the season we're gonna put in 'A' ball on the roster so you can have them off the MLB roster. You do with them what you please. Putting them in 'A' ball just gets them visibly out of the way and taking them off the 40-man in the roster file helps to keep them from being used.
3. Here's the part of the programming of the game that some of us use in our favour... If you send a roster file into a Season or Franchise, that already ONLY has 25 players on the 40-man roster, where you've taken the other 15 guys and placed them in the minors, we noticed several years ago that the CPU doesn't and won't realign the team or move people around when Spring Training ends. So if you're a roster maker, you can offer a roster file with 25-man rosters where the lineups and rotations are set already (according to your own research) and people using your rosters don't have to go to all the trouble because the game won't mess them up when the regular season begins. Like I said, "generally amazingly, helpful people".
4. Some people only want the 40 man roster locked in, but have no interest in all the teams looking like they do in real life, because they let the CPU create a sort of fantasy baseball world where the conditions are the same as opening day, but from that first crack of the bat they want their season to go in a completely self-contained direction that doesn't attempt at all to emulate what's happening in the real season. So, some roster makers offer 40-man rosters so that the teams are all accurate but it's understood that they'll get shuffled when the user's season begins. This is about making sure the 40 guys are correct but not caring much what the lineups look like.
So now, if you read all that, to your questions...
Maybe you already get this now, but "injured" is only a way of saying they're dropped into 'A' ball in the roster maker's file. if you make sure those injured guys aren't on the 40 man roster, then no they won't get brought up. But if you do put them in 'A' ball and KEEP them on the 40-man roster and they're a star player, they're pretty much guaranteed to be in the starting lineup when the rosters get reshuffled at the end of Spring Training because the CPU will think, "well, this really high-rated Cliff Lee guy is on the 40-man roster but in 'A' ball for some reason, so obviously I'm moving him to the MLB team". Even if you're only controlling one team, none of the CPU players removed from the 40-man will move up. It can happen to them during the season if there are injuries. Someone correct me if I'm wrong here.
The CPU has no way of knowing what "their starting position" is. Every player is just a number ranked in a list of other numbers and they'll go wherever the CPU thinks they should go based on stats, characteristics, and their teammates ratings as well. Again, someone correct me if I'm wrong.
I don't know that answer but downloading the file and looking at it is going to be the fastest way to get an answer.
In fact, downloading a roster file, playing with it, running simulation seasons, changing up the different important factors (the ones I mentioned above) is always going to be the best way to learn what the game does, why, and why the roster makers all offer what they offer. I've been playing The Show since 2007, and even I ran tests just this week to try playing my seasons in a new way that I've been thinking about. It was the only way to get my answers. It's the best way to see what happens and how the CPU behaves to find YOUR way of playing. Run a season/franchise, see what happens, "hmm...that didn't work...", delete it, start a new one, change the settings, "ok, good, but now I don't have the ability to change X...", delete it, modify the rosters, start a new one, etc etc etc. Then eventually you'll say, "Ohhhh.... that's why millenium/the OSFM team/Lisac did that with their file. So that you can..."
There is a tendency, not just in this forum, to talk amongst the community like all of us know every little detail, every part of the development of the different ins and outs of the game. Because of this, often, reading through a thread can feel like listening to some secret code and I'll be the first to say that I find it ridiculous to expect new people to read through 25 pages of posts just to learn one little detail that can be answered by one person in a fraction of the time. And "go search for it" isn't always a good answer because to search something, search terms need to be part of every answer and often an "answer" is part of a series of posts and not in one dictionary listing type of place. This is the flaw of the internet forum design/UI, it's never responded to the need for fast information from users that has already been asked before so forum members have taken to tearing anyone apart who dares ask, "When is the patch due?". In EVERY single instance, the time and anger it takes to put that person in their place is more than twice the time it would have taken to just say, "We don't know yet", lock the thread, and delete it. Done, problem solved. I think a chat window above the forum would solve this instantly.
The point is, it's good to ask, I don't see it as the crime others do. And I'm not telling you what to do in the future, but you'll be amazed what trying stuff yourself will teach you. You'll even learn a lot of the time, like I have, that there are ways of manipulating games that nobody else seems to know about and that you play in a way that nobody else does.
Oh yeah, this one is definitely already answered.
Comment