Player Birthdates Wrong after Team Import

mwb6 · 03-30-2017, 11:38 PM

When creating a league of teams from different years and setting the starting date to 1950, the player's birthdays are not being calculated correctly so that they are set to be their age of the year imported. In looking at the player profiles, it looks like there is a calculation error because it lists the player's birthday as about 50 years earlier than it should be. As a result all of the players in the league are in their 70's and 80's instead of their 20's and 30's.

Let me know if it would be helpful to upload the league file.

mwb6 · 03-31-2017, 02:16 PM

I did a little more research into this, looking at some players and comparing their actual birthdays to what should have been calculated and what was calculated by OOTP18. What I'm seeing is that the closer the team is to the year I chose for the league to start (1950) the older the players were set to be.

Examples
On 1968 Team, player born in 1934, should be set to 1916 is set to 1867
On 1954 Team, player born in 1923, should be set to 1919 is set to 1856
On 1950 Team, player born in 1920, should be set to 1920 is set to 1853

NoOne · 03-31-2017, 07:57 PM

LoL! this is so easy to do, too... we are talking 1 little line of code with some rudimentary math...

year of league - year of player origin = x
yob - x

That simply is injected into the process that creates the player id and inputs all the values for the player's ratings and such... ???

done. when it's negative, it adds to the yob, as it should and reduces it when it is positive. why the heck is it more complicated than that? looks like there's multiplication/division of some sort going on in your example, lol.

endgame · 03-31-2017, 08:04 PM

The import can be misled or confused, if you alter the start date after import. FWIW. Sometimes it's a few players, other times a few coaches, etc..rarely across the board, but I wouldn't rule it out. To the best of my recollection, there's no message warning you this is a possibility. Granted, I've only experience it a couple of times over a lot of years, but the fact that I have seen it (having altered my start year often) would feel remiss not to mention it.

NoOne · 04-02-2017, 12:29 AM

not everythign is going through the same process, obviously... it's not something that should be "hit or miss", otherwise.

didn't '17 supposedly change yob? i know if it made that claim it wasn't functioning in '17, either.

coaches aren't accessible, but you can export players and fix YoB, if oyu want... if there are multiple origin years for the players, that's going to require more effort.

if per tearm, yousimply have to re-do the =equation per team and fill down for each team... 30 equations, 30 fill functions = all ages fixed... if they all come from teh same year, 1 equation, 1 fill function, all done.

if you have to do it per player... probably not worth it. i'd expect this to be fixed very easily. it's gotta be some bonehead mistake that anyone can make at anytime while coding. type-o or something... because this is grade-school level logic to write in regard to adjusting YoB.

mwb6 · 04-02-2017, 10:31 AM

Thanks for your reply ... I tried creating a new league making sure that the start year was set before I did anything else. In this case, I set it to 1970 and imported various teams from 70's and 80's. Same kind of problem effecting all players on all teams - screen shots of 72 A's and 87 Twins attached.
I can't recall if I had this problem with 17 - may need to try it there. Either way, I think it's a bug in 18 for this type of league. I assume that player's age impacts performance at some point.
I will try this again with the new build later today.

mwb6 · 04-02-2017, 10:33 AM

Quote:

Originally Posted by mwb6

screen shots of 72 A's and 87 Twins attached.

Forgot to attache the screenshots ...

mwb6 · 04-02-2017, 01:32 PM

I've tried several new leagues with the latest build and the problem occurs every time I use the "switch to historical team selection" option to create a new Fictional League made up of teams from various years. I've tried various start years and have left it at 2017 - it does not matter the players ages are being calculated incorrectly. I've tried playing a few games into a season and find that many players are immediately announcing their retirement (because they're 90+!) ...

I've created a half dozen new leagues today with 4 teams just to see if the behavior is consistent - and it is. This bug makes playing a league made up of teams from different years unusable.

If I can provide any additional information so that it can help get it fixed, please let me know.

mwb6 · 04-05-2017, 11:12 PM

Using an export file, I was able to write a series of excel equations to fix the birthdates and re-import - but it would be nice if this was fixed.

03-30-2017, 11:38 PM	#1
mwb6 Minors (Single A) Join Date: Apr 2012 Posts: 77	Player Birthdates Wrong after Team Import When creating a league of teams from different years and setting the starting date to 1950, the player's birthdays are not being calculated correctly so that they are set to be their age of the year imported. In looking at the player profiles, it looks like there is a calculation error because it lists the player's birthday as about 50 years earlier than it should be. As a result all of the players in the league are in their 70's and 80's instead of their 20's and 30's. Let me know if it would be helpful to upload the league file.

03-31-2017, 08:04 PM	#4
endgame Hall Of Famer Join Date: Aug 2002 Posts: 16,842	The import can be misled or confused, if you alter the start date after import. FWIW. Sometimes it's a few players, other times a few coaches, etc..rarely across the board, but I wouldn't rule it out. To the best of my recollection, there's no message warning you this is a possibility. Granted, I've only experience it a couple of times over a lot of years, but the fact that I have seen it (having altered my start year often) would feel remiss not to mention it. __________________ "Try again. Fail again. Fail better." -- Samuel Beckett _____________________________________________

04-02-2017, 12:29 AM	#5
NoOne Banned Join Date: Apr 2015 Posts: 7,273 Infractions: 0/1 (3)	not everythign is going through the same process, obviously... it's not something that should be "hit or miss", otherwise. didn't '17 supposedly change yob? i know if it made that claim it wasn't functioning in '17, either. coaches aren't accessible, but you can export players and fix YoB, if oyu want... if there are multiple origin years for the players, that's going to require more effort. if per tearm, yousimply have to re-do the =equation per team and fill down for each team... 30 equations, 30 fill functions = all ages fixed... if they all come from teh same year, 1 equation, 1 fill function, all done. if you have to do it per player... probably not worth it. i'd expect this to be fixed very easily. it's gotta be some bonehead mistake that anyone can make at anytime while coding. type-o or something... because this is grade-school level logic to write in regard to adjusting YoB. Last edited by NoOne; 04-02-2017 at 12:34 AM.

03-31-2017, 02:16 PM	#2
mwb6 Minors (Single A) Join Date: Apr 2012 Posts: 77	I did a little more research into this, looking at some players and comparing their actual birthdays to what should have been calculated and what was calculated by OOTP18. What I'm seeing is that the closer the team is to the year I chose for the league to start (1950) the older the players were set to be. Examples On 1968 Team, player born in 1934, should be set to 1916 is set to 1867 On 1954 Team, player born in 1923, should be set to 1919 is set to 1856 On 1950 Team, player born in 1920, should be set to 1920 is set to 1853

03-31-2017, 07:57 PM	#3
NoOne Banned Join Date: Apr 2015 Posts: 7,273 Infractions: 0/1 (3)	LoL! this is so easy to do, too... we are talking 1 little line of code with some rudimentary math... year of league - year of player origin = x yob - x That simply is injected into the process that creates the player id and inputs all the values for the player's ratings and such... ??? done. when it's negative, it adds to the yob, as it should and reduces it when it is positive. why the heck is it more complicated than that? looks like there's multiplication/division of some sort going on in your example, lol.

04-02-2017, 10:31 AM	#6
mwb6 Minors (Single A) Join Date: Apr 2012 Posts: 77	Thanks for your reply ... I tried creating a new league making sure that the start year was set before I did anything else. In this case, I set it to 1970 and imported various teams from 70's and 80's. Same kind of problem effecting all players on all teams - screen shots of 72 A's and 87 Twins attached. I can't recall if I had this problem with 17 - may need to try it there. Either way, I think it's a bug in 18 for this type of league. I assume that player's age impacts performance at some point. I will try this again with the new build later today.

04-02-2017, 01:32 PM	#8
mwb6 Minors (Single A) Join Date: Apr 2012 Posts: 77	I've tried several new leagues with the latest build and the problem occurs every time I use the "switch to historical team selection" option to create a new Fictional League made up of teams from various years. I've tried various start years and have left it at 2017 - it does not matter the players ages are being calculated incorrectly. I've tried playing a few games into a season and find that many players are immediately announcing their retirement (because they're 90+!) ... I've created a half dozen new leagues today with 4 teams just to see if the behavior is consistent - and it is. This bug makes playing a league made up of teams from different years unusable. If I can provide any additional information so that it can help get it fixed, please let me know.

04-05-2017, 11:12 PM	#9
mwb6 Minors (Single A) Join Date: Apr 2012 Posts: 77	Using an export file, I was able to write a series of excel equations to fix the birthdates and re-import - but it would be nice if this was fixed.