Wanted: Some help creating a draft pick editor

[doug melvin]

Pierre's utilities used to be fantastic for this in 6.12, but there's nothing for 6.5. I know the layout of the tradedpicks.dat file, but have little experience coding outside of perl and bash scripts.


The anatomy of tradedpicks.dat is as follows:

Each 'line' contains 20 hexadecimal pairs.
1st line:
1st pair: total number of entries
remaining 18 pairs: 00

2nd line (and subsequent lines):
1st pair: rd of pick traded
next 7 pairs: 00
next pair: team no. of team that gives up the pick
next 3 pairs: 00
next pair: team no. of team that gets the pick
next 3 pairs: 00
next pair: entry number
next 3 pairs: 00


So, if the Yankees (Team 1) traded their 1st rd pick to Boston (Team 2), and the A's (Team 6) traded their 3rd rd pick to Pitt (Team 15):
02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01 00 00 00 00 00 00 00 01 00 00 00 02 00 00 00 01 00 00 00
03 00 00 00 00 00 00 00 06 00 00 00 0f 00 00 00 02 00 00 00

You can associate team names with their numbers from the Teams.dat file. Entry 0x0bb8-0x0be9 is Team Name 1
Entry 0x1770-0x17a1 is Team Name 2
Entry n*0xbb8 to n*0xbb8+31 is Team Name n

The last detail I'm a little less sure of. You can figure out the draft order from draft.dat. The beginning of that file consists of sets of 4 hexadecimal pairs:
line 1:
1st pair: team no. of team with 1st pick in the draft under normal circumstances
remaining 3 pairs: 00

Line 2: repeat until you get to end of a typical draft round.

[sporr]

You can still use Pierre's utility for 6.5. All you have to do is copy your league file from 6.5 over to v6, edit with Pierre's utility, do the draft in v6, and then copy the league folder back over to 6.5

[doug melvin]

I used to do that myself, but then started just editing the tradedpicks.dat file by hand-- it saves me a lot of time.

However, a few of my fellow commishes are having troubles with the hoops involved in going back to 6. I thought I'd at least toss the info I know out there, as the code should be relatively easy to pound out (heck, if I had Visual Studio for Windows, I'd do it myself).