Staredit Network

I was thinking about how you access files inside MPQ's and how we do not have completely complete listfiles, and I thought - Well, Starcraft has to access these files too, and to acess them it needs their name, so can't you find the names of the files in the starcraft data files or in the EXE?
Also, on the other hand, I'm volunteering my computer if someone wants to write a program to brute-force the remaining MPQ's.

You can monitor the SFileOpenFile calls and get the names that way... However, not all files are opened (unused files), and thus we can't use that way anymore, since no of the present unknowns are ever opened.

There is already a brute force namebreaker. Download Ladik's MPQ Editor at www.zezula.net

I have spent enormous amounts of time namebreaking, and this needs to be well coordinated if you want to make progress.

Solution: find someone with a beta version of starcraft and get them to use that on it to find the unused files

I have SC Beta. It *might* even have been through me that it got to the community of today.

I doubt that they are used in SC Beta either. Blizz didn't do a great job in cleaning up before releasing SC. And besides, other games have unknowns in their MPQs too, such as Lords of Magic SE and WarCraft II BNE

Hmm, have you ever tried using my file list creator MPQDraft plugin (SFList) on the Starcraft beta?

BTW, for those who don't know, it monitors SFileOpenFile and SFileOpenFileEx, as Ojan was talking about.

Solution: Remove the files and find what errors occour.

That doesnt help you figure out what their names are. The problem with that program is that it requires user interaction.

Just to clarify since a couple programs were mentioned, which program are you talking about?

SF: No, I haven't. I would, but it was a long time since I could log onto a server to play. Various attempts have been made to set up a working server for SC beta, but I've only been able to play on one, which was in 2003 or 2004...

I actually seem to recall me testing your file list creator on the beta, but it crashed the game upon loading, as far as I remember. I think I reported that to you. Well, it's not of relevance really, unless we can get a working server to begin with

These are the unknowns in SC Beta StarDat.mpq:

* An unknown filetype between cursor\Time.smk and dlgs\protoss.grp
* Two .pcx-files next to each other, between glue\battle.net\icons\number.pcx and glue\battle.net\icons\redlag.pcx. Could possibly be in their own folder, which would make namebreaking take five forevers.
* One .wav-file between sound\bullet\ngufir00.wav and sound\bullet\parfir00.wav. This one can most likely be found, given enough time and attention.
* Finally, one unknown filetype between sound\terran\marine\tmahlp01.wav and sound\terran\marine\tmapss00.wav. It's in the middle of the sounds\-files, and it's not a .wav file! I have an idea what it might be, and I'm testing it out....

Anyway, what we could do with a working server and if your file list creator works for the beta, is to crack the .wav-file if it's used, and possibly the .pcx:es... I belive the .pcx:es are just copies of other files though, so they might be unused... Dunno about the first unknown filetype... I'm attaching the files, so if anyone recognizes the unknown filetype's structure and have a clue what it might be, please tell me Also, does anyone recognize the sound of the .wav-file? It's Zerg, obviously, but what weapon / effect makes it? Been a while since I played SC

[edit=1]Cute. Attaching files doesn't attach files. The zip with the unknowns is available here[/edit]

[edit=2]w00t!!!! The second unknown in the middle of the sounds section has been found!! I just realized it was a .sfk-file. Googling it gave me this description: "A "Peak" file contains data that Sound Force use to quickly generate a 'preview' of a waveform / sound when editing. I think it's automatically crated by SF when you start working with an audio file (or maybe the first time the file is saved)."

The filename is sound\terran\marine\tmapss00.sfk Most likely some rubbish Blizzard forgot to remove

What makes this even better is the fact that it is currently exactly one year since the previous discovered unknown was cracked. Fate? [/edit]

One of the two unknowns in INSTALL.exe is a copy of swishout.wav from stardat.mpq the other one is also a copy of one from stardat I think.