OOTP Developments Forums - View Single Post

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?

03-10-2005, 02:40 AM	#5
koohead Hall Of Famer Join Date: Dec 2001 Location: Phoenix, AZ Posts: 3,231	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;