Bug when creating custom league OOTP 17

dbouch5 · 01-30-2017, 02:08 PM

I was excited to see I can create a league where I can make seasons based with a bunch of historical teams so I could include the 1927 Yankees against teams like the 2008 Phillies for example. Issue is when bringing all teams from these different eras the ages of the players during trades is laughable. Maybe when the league is set the ages of the players can stay what they were during that season and not based on the birth year? This really ruins the experience cause you can't exactly trust a trade trading for someone 100 years old.

Thanks
Dave

Sent from my iPhone using Tapatalk

TGH-Adfabre · 01-30-2017, 03:44 PM

You can turn off aging.

NoOne · 01-30-2017, 03:51 PM

you can fix this by hand if you want., but it would take a lot of effort - especially if the players aren't organized well (e.g. all the players from 1963 are lumped together.)

so, it realyl depends on that stuff as far as how viable this option is for you.

when i've imported players to a legaue that had a different year, it was easy for me to adjust this with a simple "=YoB - 30" formula in a spreadsheet... those players all were 30 years too old (or whatver #). use worksheet2, keept it separate and easier than scrolling 50 columns right and left. "=sheet1:a1 - 30" or there abouts - if a1 was the first value for YoB (show column headers when you export, but this one should stand out as a 4-digit number you will recognize either way)

your situation is different. you may need to go by team or whatever to adjust age (if that's how the player ages are lumped, like the '68 mets team, not a mets all-star all-time team). sort by columns if necessary, re-sort as it was when you first exported though, just in case that matters - it should not, but... not everything is made as it should be. i prefer not to make another trial and error if avoidable... you're welcome to see if the game cares about how it's sorted for re-import... a dB shouldn't care, though - it should handle it properly regardless.

so, export players, load into a spreadsheet. if my team and specific year - you need to make a formula to change the YoB column to an appropriate value. then fill down for the # of players that fit that formula... rinse and repeat as you go per team .. once finished, copy that "new" column you just mad over the YoB column (paste special - values only!!).

delete that formula column after you have transposed the values over the YoB column... the file should be back to the same format as when you exported it, except with new values in teh YoB column. import back to the game, and your player ages are now fixed.

nothing to do for the coaches' ages, i believe... unless they have their own export with a YoB column.

dbouch5 · 01-30-2017, 04:04 PM

Quote:

Originally Posted by NoOne

you can fix this by hand if you want., but it would take a lot of effort - especially if the players aren't organized well (e.g. all the players from 1963 are lumped together.)

so, it realyl depends on that stuff as far as how viable this option is for you.

when i've imported players to a legaue that had a different year, it was easy for me to adjust this with a simple "=YoB - 30" formula in a spreadsheet... those players all were 30 years too old (or whatver #). use worksheet2, keept it separate and easier than scrolling 50 columns right and left. "=sheet1:a1 - 30" or there abouts - if a1 was the first value for YoB (show column headers when you export, but this one should stand out as a 4-digit number you will recognize either way)

your situation is different. you may need to go by team or whatever to adjust age (if that's how the player ages are lumped, like the '68 mets team, not a mets all-star all-time team). sort by columns if necessary, re-sort as it was when you first exported though, just in case that matters - it should not, but... not everything is made as it should be. i prefer not to make another trial and error if avoidable... you're welcome to see if the game cares about how it's sorted for re-import... a dB shouldn't care, though - it should handle it properly regardless.

so, export players, load into a spreadsheet. if my team and specific year - you need to make a formula to change the YoB column to an appropriate value. then fill down for the # of players that fit that formula... rinse and repeat as you go per team .. once finished, copy that "new" column you just mad over the YoB column (paste special - values only!!).

delete that formula column after you have transposed the values over the YoB column... the file should be back to the same format as when you exported it, except with new values in teh YoB column. import back to the game, and your player ages are now fixed.

nothing to do for the coaches' ages, i believe... unless they have their own export with a YoB column.

Interesting but hopefully this can be fixed in future versions because it's a subset of choices, I never thought about doing what you are saying, I might be able to write some code to automatically do it too, just didn't think about it

Sent from my iPhone using Tapatalk

Curve Ball Dave · 01-30-2017, 07:55 PM

I don't understand this problem. I've created several league with teams from different eras. In every case the game just adjusted the players birth year so he'd be the correct age. For instance, if the league started in 2016 and Hank Aaron was 30 years old the season from which I imported the Braves, his birth year would be adjusted to 1986.

dbouch5 · 01-31-2017, 09:20 AM

Quote:

Originally Posted by Curve Ball Dave

I don't understand this problem. I've created several league with teams from different eras. In every case the game just adjusted the players birth year so he'd be the correct age. For instance, if the league started in 2016 and Hank Aaron was 30 years old the season from which I imported the Braves, his birth year would be adjusted to 1986.

I'll provide a screen shot tonight

Sent from my iPhone using Tapatalk

dbouch5 · 02-03-2017, 11:52 PM

this is an example I was talking about that takes things away from reality

Sent from my iPhone using Tapatalk

Curve Ball Dave · 02-04-2017, 10:36 PM

I'm not saying that it didn't happen in your league. I'm saying it shouldn't have happened. Something went amiss when you created that league.

dbouch5 · 02-05-2017, 01:46 AM

turning off aging would take the point away from wanting to play multiple years with these rosters to see which team has the most long haul. Thanks for the thought though.

dbouch5 · 02-05-2017, 01:48 AM

Thanks TBD, I am going to check out different options, it should have happened which is why I titles this as a bug because I imagine no one foresaw this happening and yet somehow I did.

01-30-2017, 02:08 PM	#1
dbouch5 Bat Boy Join Date: Dec 2016 Posts: 7	Bug when creating custom league OOTP 17 I was excited to see I can create a league where I can make seasons based with a bunch of historical teams so I could include the 1927 Yankees against teams like the 2008 Phillies for example. Issue is when bringing all teams from these different eras the ages of the players during trades is laughable. Maybe when the league is set the ages of the players can stay what they were during that season and not based on the birth year? This really ruins the experience cause you can't exactly trust a trade trading for someone 100 years old. Thanks Dave Sent from my iPhone using Tapatalk

01-30-2017, 03:44 PM	#2
TGH-Adfabre Hall Of Famer Join Date: Sep 2007 Posts: 2,601	You can turn off aging. __________________ You mock me, therefore I am My wife

01-30-2017, 03:51 PM	#3
NoOne Banned Join Date: Apr 2015 Posts: 7,273 Infractions: 0/1 (3)	you can fix this by hand if you want., but it would take a lot of effort - especially if the players aren't organized well (e.g. all the players from 1963 are lumped together.) so, it realyl depends on that stuff as far as how viable this option is for you. when i've imported players to a legaue that had a different year, it was easy for me to adjust this with a simple "=YoB - 30" formula in a spreadsheet... those players all were 30 years too old (or whatver #). use worksheet2, keept it separate and easier than scrolling 50 columns right and left. "=sheet1:a1 - 30" or there abouts - if a1 was the first value for YoB (show column headers when you export, but this one should stand out as a 4-digit number you will recognize either way) your situation is different. you may need to go by team or whatever to adjust age (if that's how the player ages are lumped, like the '68 mets team, not a mets all-star all-time team). sort by columns if necessary, re-sort as it was when you first exported though, just in case that matters - it should not, but... not everything is made as it should be. i prefer not to make another trial and error if avoidable... you're welcome to see if the game cares about how it's sorted for re-import... a dB shouldn't care, though - it should handle it properly regardless. so, export players, load into a spreadsheet. if my team and specific year - you need to make a formula to change the YoB column to an appropriate value. then fill down for the # of players that fit that formula... rinse and repeat as you go per team .. once finished, copy that "new" column you just mad over the YoB column (paste special - values only!!). delete that formula column after you have transposed the values over the YoB column... the file should be back to the same format as when you exported it, except with new values in teh YoB column. import back to the game, and your player ages are now fixed. nothing to do for the coaches' ages, i believe... unless they have their own export with a YoB column. Last edited by NoOne; 01-30-2017 at 03:56 PM.

01-30-2017, 07:55 PM	#5
Curve Ball Dave Hall Of Famer Join Date: Oct 2006 Location: Chicago Posts: 2,392	I don't understand this problem. I've created several league with teams from different eras. In every case the game just adjusted the players birth year so he'd be the correct age. For instance, if the league started in 2016 and Hank Aaron was 30 years old the season from which I imported the Braves, his birth year would be adjusted to 1986. __________________ "Hitting is timing. Pitching is upsetting timing"-Warren Spahn.

02-04-2017, 10:36 PM	#8
Curve Ball Dave Hall Of Famer Join Date: Oct 2006 Location: Chicago Posts: 2,392	I'm not saying that it didn't happen in your league. I'm saying it shouldn't have happened. Something went amiss when you created that league. __________________ "Hitting is timing. Pitching is upsetting timing"-Warren Spahn.

02-03-2017, 11:52 PM	#7
dbouch5 Bat Boy Join Date: Dec 2016 Posts: 7	this is an example I was talking about that takes things away from reality Sent from my iPhone using Tapatalk

02-05-2017, 01:46 AM	#9
dbouch5 Bat Boy Join Date: Dec 2016 Posts: 7	turning off aging would take the point away from wanting to play multiple years with these rosters to see which team has the most long haul. Thanks for the thought though.

02-05-2017, 01:48 AM	#10
dbouch5 Bat Boy Join Date: Dec 2016 Posts: 7	Thanks TBD, I am going to check out different options, it should have happened which is why I titles this as a bug because I imagine no one foresaw this happening and yet somehow I did.