Cato and Player Histories

koohead · 03-09-2005, 01:45 AM

Does the Catobase utility have the same problem with Player Histories after a few years? I know Cato generates his own database player ID...but he still reads the history from the p####.txt file, right? So, as long as that "bug" exists in the game, then it'll exist for catobase??? Or does Jeff's unique player id take care of this problem?

NCBeachBum · 03-09-2005, 03:11 AM

I'm about 90% sure that I read a post from Cato some time back in which he stated that Catobase will not have this problem unless you have two players with both the same name and the same birthdate. But I could be wrong.

koohead · 03-09-2005, 10:03 PM

90% is good enough for me to give it a shot! Thanks for the reply.

Aordolin · 03-10-2005, 12:50 AM

not quite sure im getting what your asking totally but any biographical data changed will force cato to create a new playerid. so they could have the same name, birthday, but if they were different heigh/weight, had different origin it would create a new playerid in cato. I came across this when I noticed into my league I had spelled a state or country wrong or something like that and then suddenly found the player was duplicated in cato like it was 2 different players. Hope that explanation gives you what you were concerned about.

koohead · 03-10-2005, 02:40 AM

I think I understand you guys about the Unique Cato ID's. My concern is with the player histories and the text files created by the game itself. Because the OOTP engine recycle player id's and thus appends the history files as opposed to creates new ones after a player retires, how does the Cato utility handle that? Since cato just reads the txt files, wouldn't there be a problem?
For example...player id 1 plays for 20 years...and then retires. Next crop of rookies comes along, and the ootp engine reuses player id 1...and adds new draft information and accomplishments to the p1.txt file. Where/How/Does cato draw the line between "old" player id 1's history and "new" player id 1's history?

NCBeachBum · 03-10-2005, 03:37 AM

Well, my recollection of the explanation was this: that CatoBase creates it's own unique player ID, completely separate from the id assigned by OOTP. I had thought this ID was said to have been based upon their name and birthdate, but as Aordolin pointed out it may not be. Then, when you export at the end of the season, CB pulls out all the new information from the player file for that season and adds it to his file in CB. Since it only pulls it out for that season just completed, it wouldn't pull the older stuff from a previously existing player who had the same OOTP ID.
That was my understanding, anyway...... perhaps you can find the post, if you have better searching skills than I.

gubaru · 03-10-2005, 11:06 AM

Quote:

Originally Posted by koohead

I think I understand you guys about the Unique Cato ID's. My concern is with the player histories and the text files created by the game itself. Because the OOTP engine recycle player id's and thus appends the history files as opposed to creates new ones after a player retires, how does the Cato utility handle that? Since cato just reads the txt files, wouldn't there be a problem?
For example...player id 1 plays for 20 years...and then retires. Next crop of rookies comes along, and the ootp engine reuses player id 1...and adds new draft information and accomplishments to the p1.txt file. Where/How/Does cato draw the line between "old" player id 1's history and "new" player id 1's history?

It doesn't. If you import the player histories and OotP hasn't cleared the text file like it's supposed to, the history of the old player will be assigned to the new player in CatoBase. I'm in the process of editing my db/text files to fix this problem for some players in CatoBase now.

sporr · 03-10-2005, 11:30 AM

Unless you have some error or problem when OOTP proceeds to the next season, the game will change all pxxx.txt files to rxxx.txt as players retire and therefore you shouldn't have this problem with "reused" player histories.

koohead · 03-10-2005, 11:48 AM

Ah..I see. So its up to OOTP to move the p####.txt file to a r####.txt file. Problem solved as long as it works.

Thanks for all the replies!

sporr · 03-10-2005, 01:14 PM

Quote:

Originally Posted by koohead

Ah..I see. So its up to OOTP to move the p####.txt file to a r####.txt file. Problem solved as long as it works.

Thanks for all the replies!

Yeah, I know in the past OOTP did have this problem, but somewhere along the way it got fixed. Now, as part of the off-season processing, the game will perform this step automatically.

Aordolin · 03-10-2005, 03:24 PM

I remember that occasionally I would get a new player that would have some history data from a retired player that for some reason didnt get deleted, that may be what sporr is talking about. I havent seen that in a long time so it may have been fixed or I havent noticed it, even though it was really rare and easy to correct. (just delete the info from the players text file)

03-09-2005, 01:45 AM	#1
koohead Hall Of Famer Join Date: Dec 2001 Location: Phoenix, AZ Posts: 3,230	Cato and Player Histories Does the Catobase utility have the same problem with Player Histories after a few years? I know Cato generates his own database player ID...but he still reads the history from the p####.txt file, right? So, as long as that "bug" exists in the game, then it'll exist for catobase??? Or does Jeff's unique player id take care of this problem? __________________ GM - New Jersey Bears of the NPBL;

03-09-2005, 10:03 PM	#3
koohead Hall Of Famer Join Date: Dec 2001 Location: Phoenix, AZ Posts: 3,230	Good enough for me 90% is good enough for me to give it a shot! Thanks for the reply. __________________ GM - New Jersey Bears of the NPBL;

03-10-2005, 02:40 AM	#5
koohead Hall Of Famer Join Date: Dec 2001 Location: Phoenix, AZ Posts: 3,230	Unique ID's I think I understand you guys about the Unique Cato ID's. My concern is with the player histories and the text files created by the game itself. Because the OOTP engine recycle player id's and thus appends the history files as opposed to creates new ones after a player retires, how does the Cato utility handle that? Since cato just reads the txt files, wouldn't there be a problem? For example...player id 1 plays for 20 years...and then retires. Next crop of rookies comes along, and the ootp engine reuses player id 1...and adds new draft information and accomplishments to the p1.txt file. Where/How/Does cato draw the line between "old" player id 1's history and "new" player id 1's history? __________________ GM - New Jersey Bears of the NPBL;

03-10-2005, 11:48 AM	#9
koohead Hall Of Famer Join Date: Dec 2001 Location: Phoenix, AZ Posts: 3,230	Up to OOTP Ah..I see. So its up to OOTP to move the p####.txt file to a r####.txt file. Problem solved as long as it works. Thanks for all the replies! __________________ GM - New Jersey Bears of the NPBL;

03-09-2005, 03:11 AM	#2
NCBeachBum All Star Starter Join Date: Jul 2003 Location: Topsail Island, NC, USA Posts: 1,049	I'm about 90% sure that I read a post from Cato some time back in which he stated that Catobase will not have this problem unless you have two players with both the same name and the same birthdate. But I could be wrong.

03-10-2005, 12:50 AM	#4
Aordolin All Star Reserve Join Date: Apr 2004 Location: Houston, TX Posts: 586	not quite sure im getting what your asking totally but any biographical data changed will force cato to create a new playerid. so they could have the same name, birthday, but if they were different heigh/weight, had different origin it would create a new playerid in cato. I came across this when I noticed into my league I had spelled a state or country wrong or something like that and then suddenly found the player was duplicated in cato like it was 2 different players. Hope that explanation gives you what you were concerned about.

03-10-2005, 03:37 AM	#6
NCBeachBum All Star Starter Join Date: Jul 2003 Location: Topsail Island, NC, USA Posts: 1,049	Well, my recollection of the explanation was this: that CatoBase creates it's own unique player ID, completely separate from the id assigned by OOTP. I had thought this ID was said to have been based upon their name and birthdate, but as Aordolin pointed out it may not be. Then, when you export at the end of the season, CB pulls out all the new information from the player file for that season and adds it to his file in CB. Since it only pulls it out for that season just completed, it wouldn't pull the older stuff from a previously existing player who had the same OOTP ID. That was my understanding, anyway...... perhaps you can find the post, if you have better searching skills than I.

03-10-2005, 11:30 AM	#8
sporr Global Moderator Join Date: Dec 2001 Location: Muscatine, IA Posts: 8,277	Unless you have some error or problem when OOTP proceeds to the next season, the game will change all pxxx.txt files to rxxx.txt as players retire and therefore you shouldn't have this problem with "reused" player histories.

03-10-2005, 03:24 PM	#11
Aordolin All Star Reserve Join Date: Apr 2004 Location: Houston, TX Posts: 586	I remember that occasionally I would get a new player that would have some history data from a retired player that for some reason didnt get deleted, that may be what sporr is talking about. I havent seen that in a long time so it may have been fixed or I havent noticed it, even though it was really rare and easy to correct. (just delete the info from the players text file)