SC can only read SCX/SCM. ;o StarEdit can read chk.
Well aren't you a party pooper.
This is stupid, the program is:
from pyscumslib import *
map_data = read("scenario.chk")
write(map_data, "new_scenario.chk")
And you don't give us the source of pyscumslib.
This is completely useless.
I should point out that I did you big favor. You wanted a community map editor and I gave you something that's easy to both read and write a starcraft map, separates the sections so they can be modified however you want, and written in python because it rocks as a language. PS. read the comments next time.
For convenience, here they are:
##the data is stored in the data structure of a map. these are the keys:
##['TECx', 'UPRP', 'IOWN', 'COLR', 'IVE2', 'STR ', 'DIM ', 'VCOD', 'WAV ', 'MASK', 'PUNI', 'VER ', 'MBRF', 'OWNR', 'TILE', 'MTXM', 'PUPx', 'MRGN', 'SWNM', 'PTEx', 'FORC', 'TRIG', 'ISOM', 'UPGx', 'DD2 ', 'UNIT', 'UPUS', 'ERA ', 'THG2', 'SPRP', 'UNIx', 'TYPE', 'SIDE']
##each key (they are just strings) represents that particular section in the data
##to access it, use something like map_data["SIDE"]
##map_data["SIDE"] would return something like:
##['05', '05', '02', '01', '00', '02', '01', '00', '07', '07', '07', '04']
##refer to how scenario.chk is organized for what it means.
##example: in the above, 05 is "user selectable" so player 1 is set as "user selectable"
##player 2 is also set as "user selectable"
##if we wanted so player 2 was zerg, we change it like:
##map_data["SIDE] = ['05', '00', '02', '01', '00', '02', '01', '00', '07', '07', '07', '04']
Post has been edited 1 time(s), last time on Jan 9 2009, 12:09 am by Doodan. Reason: flame removed
None.
Although it's really simple if you know anything about reading and writing binary files.. so probably like three of you.
