Age 0, 350 lb players created

stealofhome · 03-11-2018, 09:21 PM

Trying to get a fictional league up and running (turning into the hardest thing ever). I found a ton of players who show up as 0 years old, 0 feet tall, and 350 pounds. They get put on waivers and claimed over and over again for all eternity, never age, never go away. Not sure where they even come from.

If I export the MLB rosters, they show as having a birth year, but in the actual game they don't. Anyone else have this problem?

NoOne · 03-11-2018, 09:34 PM

somethng is corrupted.

did you export and delete a player from teh exported files than import back? that will for sure screw up the DB. you cannot delete a player or row nor add a new player from/to the exported file, only modify exiting rows.

delete or add players in game only...before an export to be modified etc.

or it's just corrupted by some other means.

quick fix? try deleting all, including history/stats... then use a "fill" funciton for your entire league (league settings - visible on screen or in "available actions"). this is no different than how the game fills the league to start. it is, as always, different than the player creation process for the game as it runs...

(pro tip, start ~30 years pre-dated and sim to intended date to clear out seed players, then delete league history and stats = just like a new league starting day 1. Not necessary but avoids the need to constantly click auto-calculate modifers every so often for ~25 years before it levels out to a new equilibrium based on the new distribution of player ratings compared to the previous seed player's ratings - also provides a more robust FA pool starting year 1, more "normal" compared to what you will see in future.)

better idea: start over. no guarnatees the problem is fixed, otherwise. did you make a template by chance during game creation? that would speed teh process along... defniteyl make one RIGHT before you click "create league" during game creation process. that template at that time does not include a set of fictional players.. you can see template size drops from ~200mb or more to ~20mb or so.

i don't think you can make a temlplate after game creation due to your specific probelm, because it includes the players in the template file.. whch could be corrupted. worth a shot if you did a lot of custom stuff.

maybe delete all players before you create a template... maybe a "purge" on the global settings->database settings page will clear out any remnants of corruption too.

best to just start over in this context, methinks. net saving of time more likely.

endgame · 03-11-2018, 09:37 PM

That’s the strangest thing I ever heard, and now my imagination is equally corrupted.

NoOne · 03-11-2018, 09:43 PM

duplicate keyfields that are supposed to be unique or a player id split between 2 players due to deleting from an export etc... easy to do.. you can recreate the problem.

alhough i saw MAX ratings for nearly all players when i learned that lesson. i don't recall paying attention to weight. just a matter of what got shifted where as far as what is "wrong" visually... or if it's corrutption on the storage side, whatever randomly filled in that corrupted block on the drive. not much of a chance for a fix for either problem, really.

just imagine a slight shift in teh exported file data... and what that would do to every row after that point... the entire thng is jacked at that point. (multiple related tables not jiving together or worse)

stealofhome · 03-12-2018, 02:38 PM

Quote:

Originally Posted by NoOne

i don't think you can make a temlplate after game creation due to your specific probelm, because it includes the players in the template file.. whch could be corrupted. worth a shot if you did a lot of custom stuff.

There are all these little things that I didn't know...this might be the problem here because I had a template that I did before starting the game but then made some edits after the game started and saved a template. It is possible that these players were saved in a template without my knowledge as I wasn't checking these things at the time.

NoOne · 03-12-2018, 04:49 PM

i only meant that for your current corrupted league. you can easily make a template after creation under normal circumstances wihtout any fear of problems, if they do not exist of course - 99.9999% of time that will be the case as far as corruption at the hardware-level. self-inflicted stuff is upto us how often it occurs

just compare file size to an included template..

20-40 MegaBytes = safe to say no players are there unless it is a very tiny game world.

they are all stored in teh a data directory:

..\data\world_templates

my 30 team template is 26mb. a 40team template was ~40MB

the default.wtp, which includes real MLB and MiL players, is for non-fictional 2017 quickstarts - 210MB

it will be obvious by size, if this is what is causing the problem, it is woth the look. deduce the exact problem before deleting anything.

if you are using real playrs, it will be large.. definiteyl can't re-use template if problem persists when you test it with a new creation league.

stealofhome · 03-13-2018, 02:27 PM

Yes, looks like there was a group of players that got added to a template and carried along. Now I have to see if the problem happens again or if it was a one-time fluke. I do have a pretty unique template but thankfully one of the versions of it was not corrupted with these players.

NoOne · 03-13-2018, 10:01 PM

if you can remove the leagues and easily add them back, i think that will delete the players during the game creation process.. before it loads first time.

at the least, you don't hav eto fine tune the settings..

before that: like i said above, try deleting players, purge database, and re-fill leage (all 1 click stuff and wait for it to process - no effort). if it successfully clears all the tables and related tables, the corruption will be removed too.

if it leaves artifacts, no go... that's the hope of using the Purge function on database setting tab.

weigh what strategy costs the most time and avoid that until the end if possible.

03-11-2018, 09:21 PM	#1
stealofhome Hall Of Famer Join Date: Apr 2014 Posts: 2,282	Age 0, 350 lb players created Trying to get a fictional league up and running (turning into the hardest thing ever). I found a ton of players who show up as 0 years old, 0 feet tall, and 350 pounds. They get put on waivers and claimed over and over again for all eternity, never age, never go away. Not sure where they even come from. If I export the MLB rosters, they show as having a birth year, but in the actual game they don't. Anyone else have this problem?

03-11-2018, 09:34 PM	#2
NoOne Banned Join Date: Apr 2015 Posts: 7,273 Infractions: 0/1 (3)	somethng is corrupted. did you export and delete a player from teh exported files than import back? that will for sure screw up the DB. you cannot delete a player or row nor add a new player from/to the exported file, only modify exiting rows. delete or add players in game only...before an export to be modified etc. or it's just corrupted by some other means. quick fix? try deleting all, including history/stats... then use a "fill" funciton for your entire league (league settings - visible on screen or in "available actions"). this is no different than how the game fills the league to start. it is, as always, different than the player creation process for the game as it runs... (pro tip, start ~30 years pre-dated and sim to intended date to clear out seed players, then delete league history and stats = just like a new league starting day 1. Not necessary but avoids the need to constantly click auto-calculate modifers every so often for ~25 years before it levels out to a new equilibrium based on the new distribution of player ratings compared to the previous seed player's ratings - also provides a more robust FA pool starting year 1, more "normal" compared to what you will see in future.) better idea: start over. no guarnatees the problem is fixed, otherwise. did you make a template by chance during game creation? that would speed teh process along... defniteyl make one RIGHT before you click "create league" during game creation process. that template at that time does not include a set of fictional players.. you can see template size drops from ~200mb or more to ~20mb or so. i don't think you can make a temlplate after game creation due to your specific probelm, because it includes the players in the template file.. whch could be corrupted. worth a shot if you did a lot of custom stuff. maybe delete all players before you create a template... maybe a "purge" on the global settings->database settings page will clear out any remnants of corruption too. best to just start over in this context, methinks. net saving of time more likely. Last edited by NoOne; 03-11-2018 at 09:40 PM.

03-11-2018, 09:37 PM	#3
endgame Hall Of Famer Join Date: Aug 2002 Posts: 16,842	That’s the strangest thing I ever heard, and now my imagination is equally corrupted. __________________ "Try again. Fail again. Fail better." -- Samuel Beckett _____________________________________________

03-11-2018, 09:43 PM	#4
NoOne Banned Join Date: Apr 2015 Posts: 7,273 Infractions: 0/1 (3)	duplicate keyfields that are supposed to be unique or a player id split between 2 players due to deleting from an export etc... easy to do.. you can recreate the problem. alhough i saw MAX ratings for nearly all players when i learned that lesson. i don't recall paying attention to weight. just a matter of what got shifted where as far as what is "wrong" visually... or if it's corrutption on the storage side, whatever randomly filled in that corrupted block on the drive. not much of a chance for a fix for either problem, really. just imagine a slight shift in teh exported file data... and what that would do to every row after that point... the entire thng is jacked at that point. (multiple related tables not jiving together or worse) Last edited by NoOne; 03-11-2018 at 09:46 PM.

03-12-2018, 04:49 PM	#6
NoOne Banned Join Date: Apr 2015 Posts: 7,273 Infractions: 0/1 (3)	i only meant that for your current corrupted league. you can easily make a template after creation under normal circumstances wihtout any fear of problems, if they do not exist of course - 99.9999% of time that will be the case as far as corruption at the hardware-level. self-inflicted stuff is upto us how often it occurs just compare file size to an included template.. 20-40 MegaBytes = safe to say no players are there unless it is a very tiny game world. they are all stored in teh a data directory: ..\data\world_templates my 30 team template is 26mb. a 40team template was ~40MB the default.wtp, which includes real MLB and MiL players, is for non-fictional 2017 quickstarts - 210MB it will be obvious by size, if this is what is causing the problem, it is woth the look. deduce the exact problem before deleting anything. if you are using real playrs, it will be large.. definiteyl can't re-use template if problem persists when you test it with a new creation league. Last edited by NoOne; 03-12-2018 at 04:54 PM.

03-13-2018, 02:27 PM	#7
stealofhome Hall Of Famer Join Date: Apr 2014 Posts: 2,282	Yes, looks like there was a group of players that got added to a template and carried along. Now I have to see if the problem happens again or if it was a one-time fluke. I do have a pretty unique template but thankfully one of the versions of it was not corrupted with these players.

03-13-2018, 10:01 PM	#8
NoOne Banned Join Date: Apr 2015 Posts: 7,273 Infractions: 0/1 (3)	if you can remove the leagues and easily add them back, i think that will delete the players during the game creation process.. before it loads first time. at the least, you don't hav eto fine tune the settings.. before that: like i said above, try deleting players, purge database, and re-fill leage (all 1 click stuff and wait for it to process - no effort). if it successfully clears all the tables and related tables, the corruption will be removed too. if it leaves artifacts, no go... that's the hope of using the Purge function on database setting tab. weigh what strategy costs the most time and avoid that until the end if possible.