OOTP Developments Forums - View Single Post

RunningMonk · 03-10-2014, 02:53 AM

so i've been setting up some templates for some games i want to play, but i've run into some problems.

i have things set to retire players according to history, but there are times when a player doesn't have anymore stats, so the game considers him retired. more often than not, this wouldn't matter much, as they're usually low rating players, but sometimes it'd be nice to have that guy on a team.

is there any way to circumvent this without me having to simulate the season to catch the players, and then manually assigning them when i restart the season? it's become a pain. especially when a player say, plays for SLN is 69, has no stats afterwards, so he's considered retired, but he was still under contract with SLN is 70, and then in 71 traded to PIT. the way i'm doing things now, i'd catch the 71 trade and assign him to SLN, but i've missed 70! so i have to start a new game, load the template for 70, and assign him to SLN there as well. add all the players that this happens to and it becomes a daunting task. lots of loading and reloading and new games and templates and saving and erasing (i'm attempting to have templates for 1956-2013).

in my mind, the best option would be if "retired" meant "no more stats AND no more transactions in the database".

another problem i've run into is i reset injuries at the end of each season, so that i can load any year for the templates i've made always have the full(er) rosters, is missing a player that had a career ending injury, and so was released by his team. poor fergie jenkins wasn't pitching for years! if injuries are rest the player just floats around as a FA, which is no good with historical transactions on. i figure there's no work around for this, i just have to be more vigilant.

things would be easier too if the database from the previous year stuck around into the next, but i guess that's not the important bit here.

anyway, i hope i've explained my problem fairly well enough. if not, i can clarify. i haven't looked into ootp 14 or 15, but maybe if this is fixed in those, i'll pick one up. otherwise, does anyone have any advice on this one? a different database of some sort? a setting i overlooked? any help would be appreciated. thanks!

03-10-2014, 02:53 AM	#1
RunningMonk Bat Boy Join Date: Oct 2012 Posts: 5	historical transactions question so i've been setting up some templates for some games i want to play, but i've run into some problems. i have things set to retire players according to history, but there are times when a player doesn't have anymore stats, so the game considers him retired. more often than not, this wouldn't matter much, as they're usually low rating players, but sometimes it'd be nice to have that guy on a team. is there any way to circumvent this without me having to simulate the season to catch the players, and then manually assigning them when i restart the season? it's become a pain. especially when a player say, plays for SLN is 69, has no stats afterwards, so he's considered retired, but he was still under contract with SLN is 70, and then in 71 traded to PIT. the way i'm doing things now, i'd catch the 71 trade and assign him to SLN, but i've missed 70! so i have to start a new game, load the template for 70, and assign him to SLN there as well. add all the players that this happens to and it becomes a daunting task. lots of loading and reloading and new games and templates and saving and erasing (i'm attempting to have templates for 1956-2013). in my mind, the best option would be if "retired" meant "no more stats AND no more transactions in the database". another problem i've run into is i reset injuries at the end of each season, so that i can load any year for the templates i've made always have the full(er) rosters, is missing a player that had a career ending injury, and so was released by his team. poor fergie jenkins wasn't pitching for years! if injuries are rest the player just floats around as a FA, which is no good with historical transactions on. i figure there's no work around for this, i just have to be more vigilant. things would be easier too if the database from the previous year stuck around into the next, but i guess that's not the important bit here. anyway, i hope i've explained my problem fairly well enough. if not, i can clarify. i haven't looked into ootp 14 or 15, but maybe if this is fixed in those, i'll pick one up. otherwise, does anyone have any advice on this one? a different database of some sort? a setting i overlooked? any help would be appreciated. thanks!