Quote:
Originally Posted by Mike Donlin
Couple of impressions so far:
1. Establishing a baseline worked, but I could only get it to register on a 1-250 scale. I don't know if the changes tracked are ultimately according to my rating system (20-80) because, well, see below.
2. It would be very convenient if the output text file also grabbed a player's age; similarly, if it could track potential changes in addition to ratings ones.
3. Game has to be closed in order for the program to run; otherwise, you get an error saying that some free agent file is in use.
4. It takes a long time to run, and it is very finicky about other programs running at the same time. I haven't actually seen the output because I think it needs to have no other programs running and I have too much work to do this morning not to have them running!
But this is an intriguing start. I have long wanted something like this so that I can run a bunch of tests without having to transfer everything over to Access. Thanks again.
|
Thanks very much for the feedback. A couple of things....
The baseline only uses the 250 scale. It's much easier to track changes on the 250 scale because the resolution is much higher. Also, it takes a very, very long time to convert every single rating for every single player. So leaving the baseline at 250 was prudent. The program compares the baselines on the 250 scale to the .CSV on the 250 scale, then converts either the change or then converts each to the scale of your choice.
It would be pretty easy to add ages to the player reports and baseline. Only a few extra lines of code. Thanks for the suggestion.
It does actually track potentials, too. Maybe you didn't have any potential changes? Or maybe it's a bug. But I've gotten it to track potentials, I'm sure.
When you say it takes a long time to run... do you mean creating the baseline, or tracking changes? On my pretty slow and old work computer, I was able to create a baseline on an all minors level 63-year old universe in about 20 seconds. Tracking changes may take longer depending on how long it's been since you ran the baseline and what ratings scale you use. Basically, the more changes the program detects/tracks, the longer it will take. Again, on my slow and old work computer, I was able to track changes after a week of simming and using the 250 scale in about 30-45 seconds.
I'll check the free agent thing. It mostly depends on what program you have the files open with. Excel and Word don't like to share files with other programs, so it'll probably throw an error if you have one of the .CSV files open. Even OOTP will complain about a file in use if you try to do a .CSV dump when a MS Office program has one open. I used TextPad to open a lot of the .CSV files and leave them open with no problem.
So, if you were using excel or word to look at .CSV files, try using something like TextPad (it's free) and the devTracker won't care. I was able to have the game open, run the baseline, look at the baseline and .CSV with Textpad, sim a week or so, create a new .CSV dump and track changes without closing any of it. So I'm willing to bet it's whatever program you're using to open the .CSV files.
Thanks again for the feedback, and please give me more input when you get the chance.