I've been working at maps for SC for a few years now... I've decided to try something new, I would like to edit campaign maps. But alas I can figure out how to get to them... I have the MPQ viewer, but I can't find the things.
I'd love your help if anyone can give it.

open stardat.mpq and make sure you have a listfile

I'm not looking for scx/scm files, am I?
In that case what am I looking for?
If I am looking for scx/scm files, I don't see them..

I think they are on the SC CD, but I may be wrong.

You are wrong. There's only 1 big data file

I can't tell you what you are looking for, but I know that you can download the campaigns as scm/scx files.
Try to google it. I forgot where I saw them. sry

But if you want to integrate your maps into the starcraft campaign you can't just use/replace scm files. You will need some kind of alternative executable I think. Saw this in other custom campaigns where you could click on the Protoss image to start instead of choosing it manually from the map folders.

WOOPS, it's on the cd - i checked.
open install.exe with WinMPQ... there you can see all the missions. For each mission, just extract all of the files with that name (e.g. protoss1/staredit/...). this will include sound files.

Genius NudeRaider, pure genius...

Actuly, I wasn't to use some of the mission maps and change trigger/units. Making a few of the missions occur in the same places as the main missions... I'm looking for some of the instillation maps.

chk files? Is this right? If so how does i use em?
~Edit~
..... WOW....Change the extension....I restate wow.... I can believe that it was that easy..
Thanks guys... for helpin me find em!

~Edit 2~
I think the blizz guys acutly used staredit to make these maps

Post has been edited 2 time(s), last time on Oct 5 2007, 4:36 am by Guy_Apollo.

Blizz did not use regular staredit. They used a slightly modified version. The only main difference I could notice by playing would be that it gave them access to all the campaign AI's, obviously.. there were probably more differences, though.

well, they still ended up as .scm and .scx files