Staredit Network

Woww... this sounds really cool... i just want to test it but i have a little problem...
Is the link dead?

Wow, this is cool...

I hope they don't patch it...

It works perfectly fine for me, maybe the site was just down when you tried it.

I Just tested the demo maps and... what the hell is that freaky palette?!?
I'm sure it will blind anyone that plays over 5 minutes on the map
[attachmentid=18469]

Wow, that's kinda weird.

Anyways, reinstalled StarCraft to try this out, works fine for me, very cool.

That was a test for if SC loads the pallete files when the map is loaded.

Though ShadowFlare ownt me here, the reason DatLoader will come out superior is that it will be able to use combinations of triggers to allow the map to edit the memory. HaHA!

ADDITION:

LOL! does this mean that there is a Staredit.net effect in addtion to a Slashdot effect?

Dude, your should SERIOUSLY focus on making a program which will load the iscript.bin file instead.

Remember that guys idea about how you could call starcraft's functions to save effort or something...

I doubt I will get into this. After getting so hyped about EUDs coming into my life, and then having them destroyed in front of my eyes... the dream is dead.

This program, I wont be messing with. I'll give it 2 weeks. If it's still around, ill crack open the editor.

Looks interesting though...


Gj.

I agree completely with what DoA said - I don't see any possible way of "pathing it out" by Blizzard. Changing the priorities SC loads the DAT files from is absolutely safe, and blocking the ability to load files from within SCMs/SCXs (which are basically MPQ archives) would also prevent e.g. playing sound files from within them, which is something that is NOT going to happen as Blizzard (and other people) use them all around their campaigns.

Yes. There is no chance that this will get knocked out, though the memory locations might be shuffled, I think MPQDraft has a way around that.

Wrong, blizzard can block it (though not easily)

one way they could block it is to redo the exe mixing it up completely so the mpq commands are mixed up,
and it wouldn't be able to edit the exe since it couldn't find the properties it tries to edit
(would mess up modding completely, so they probably wouldn't do it since they support modding)

Doodle, the only problem with your program is that it will basically be patched over if one is released.

I actually found a file that I wrote a long while ago, telling you basically what files SC will load AFTER the map has been loaded.

Try these with SCMLoader, chances of them working are extremely high.

arr\flingy.dat
arr\sprites.dat
arr\units.dat
arr\orders.dat
arr\techdata.dat
arr\weapons.dat
arr\upgrades.dat
arr\portdata.tbl <-- ALL PORTRAITS AS WELL. (smk)
arr\portdata.dat
tileset\Twilight\shift.pcx
tileset\Ice\shift.pcx
tileset\desert\shift.pcx
tileset\Jungle\shift.pcx
tileset\AshWorld\shift.pcx
tileset\install\shift.pcx
tileset\platform\shift.pcx
tileset\badlands\shift.pcx
tileset\Twilight\ofire.pcx
tileset\Ice\ofire.pcx
tileset\desert\ofire.pcx
tileset\Jungle\ofire.pcx
tileset\AshWorld\ofire.pcx
tileset\install\ofire.pcx
tileset\platform\ofire.pcx
tileset\badlands\ofire.pcx
tileset\Twilight\gfire.pcx
tileset\Ice\gfire.pcx
tileset\desert\gfire.pcx
tileset\Jungle\gfire.pcx
tileset\AshWorld\gfire.pcx
tileset\install\gfire.pcx
tileset\platform\gfire.pcx
tileset\badlands\gfire.pcx
tileset\Twilight\bfire.pcx
tileset\Ice\bfire.pcx
tileset\desert\bfire.pcx
tileset\Jungle\bfire.pcx
tileset\AshWorld\bfire.pcx
tileset\install\bfire.pcx
tileset\platform\bfire.pcx
tileset\badlands\bfire.pcx
tileset\Twilight\bexpl.pcx
tileset\Ice\bexpl.pcx
tileset\desert\bexpl.pcx
tileset\Jungle\bexpl.pcx
tileset\AshWorld\bexpl.pcx
tileset\install\bexpl.pcx
tileset\platform\bexpl.pcx
tileset\badlands\bexpl.pcx
tileset\Twilight\trans50.pcx
tileset\Ice\trans50.pcx
tileset\desert\trans50.pcx
tileset\Jungle\trans50.pcx
tileset\AshWorld\trans50.pcx
tileset\install\trans50.pcx
tileset\platform\trans50.pcx
tileset\badlands\trans50.pcx
tileset\Twilight\red.pcx
tileset\Ice\red.pcx
tileset\desert\red.pcx
tileset\Jungle\red.pcx
tileset\AshWorld\red.pcx
tileset\install\red.pcx
tileset\platform\red.pcx
tileset\badlands\red.pcx
tileset\Twilight\green.pcx
tileset\Ice\green.pcx
tileset\desert\green.pcx
tileset\Jungle\green.pcx
tileset\AshWorld\green.pcx
tileset\install\green.pcx
tileset\platform\green.pcx
tileset\badlands\green.pcx
tileset\Twilight\dark.pcx
tileset\Ice\dark.pcx
tileset\desert\dark.pcx
tileset\Jungle\dark.pcx
tileset\AshWorld\dark.pcx
tileset\install\dark.pcx
tileset\platform\dark.pcx
tileset\badlands\dark.pcx
game\tminimap.pcx
game\tunit.pcx
rez\allyfltr.bin
rez\teamfltr.bin
rez\msgfltr.bin
dlgs\zerg.grp
dlgs\terran.grp
dlgs\protoss.grp
tileset\Twilight.vr4
tileset\Twilight.vx4
tileset\Twilight.grp
tileset\Twilight.cv5
tileset\Twilight.vf4
tileset\Ice.vr4
tileset\Ice.vx4
tileset\Ice.grp
tileset\Ice.cv5
tileset\Ice.vf4
tileset\desert.vr4
tileset\desert.vx4
tileset\desert.grp
tileset\desert.cv5
tileset\desert.vf4
tileset\Jungle.vr4
tileset\Jungle.vx4
tileset\Jungle.grp
tileset\Jungle.cv5
tileset\Jungle.vf4
tileset\AshWorld.vr4
tileset\AshWorld.vx4
tileset\AshWorld.grp
tileset\AshWorld.cv5
tileset\AshWorld.vf4
tileset\install.vr4
tileset\install.vx4
tileset\install.grp
tileset\install.cv5
tileset\install.vf4
tileset\platform.vr4
tileset\platform.vx4
tileset\platform.grp
tileset\platform.cv5
tileset\platform.vf4
tileset\badlands.vr4
tileset\badlands.vx4
tileset\badlands.grp
tileset\badlands.cv5
tileset\badlands.vf4
tileset\Twilight.wpe
tileset\Ice.wpe
tileset\desert.wpe
tileset\Jungle.wpe
tileset\AshWorld.wpe
tileset\install.wpe
tileset\platform.wpe
tileset\badlands.wpe
rez\glurdyp.bin
glue\ReadyP\PFrameH4.pcx
glue\ReadyP\PFrameH3.pcx
glue\ReadyP\PFrameH2.pcx
glue\ReadyP\PFrameH1.pcx
glue\ReadyP\PFrame4.pcx
glue\ReadyP\PFrame3.pcx
glue\ReadyP\PFrame2.pcx
glue\ReadyP\PFrame1.pcx
rez\glurdyt.bin
glue\ReadyT\TFrameH4.pcx
glue\ReadyT\TFrameH3.pcx
glue\ReadyT\TFrameH2.pcx
glue\ReadyT\TFrameH1.pcx
glue\ReadyT\TFrame4.pcx
glue\ReadyT\TFrame3.pcx
glue\ReadyT\TFrame2.pcx
glue\ReadyT\TFrame1.pcx
rez\glurdyz.bin
glue\ReadyZ\ZFrameH4.pcx
glue\ReadyZ\ZFrameH3.pcx
glue\ReadyZ\ZFrameH2.pcx
glue\ReadyZ\ZFrameH1.pcx
glue\ReadyZ\ZFrame4.pcx
glue\ReadyZ\ZFrame3.pcx
glue\ReadyZ\ZFrame2.pcx
glue\ReadyZ\ZFrame1.pcx
glue\scorePv\scorebox.pcx
glue\scorePv\pInset.pcx
glue\scorePv\untab.pcx
glue\scorePd\scorebox.pcx
glue\scorePd\pInset.pcx
glue\scorePd\untab.pcx
glue\scoreTv\scorebox.pcx
glue\scoreTv\pInset.pcx
glue\scoreTv\untab.pcx
glue\scoreTd\scorebox.pcx
glue\scoreTd\pInset.pcx
glue\scoreTd\untab.pcx
glue\scoreZv\scorebox.pcx
glue\scoreZv\pInset.pcx
glue\scoreZv\untab.pcx
glue\scoreZd\scorebox.pcx
glue\scoreZd\pInset.pcx
glue\scoreZd\untab.pcx
rez\gluScore.bin
game\thpbar.pcx
rez\timeout.bin
rez\gamemenu.bin
rez\abrtmenu.bin
rez\helpmenu.bin
rez\options.bin
rez\quit.bin
rez\quit2mnu.bin
rez\quitrepl.bin
rez\restart.bin
game\tFontGam.pcx
rez\savegame.bin
scripts\bwscript.bin
scripts\aiscript.bin
rez\loadgame.bin
game\pbrfull.pcx
game\pbrempt.pcx
unit\cmdbtns\ticon.pcx
unit\cmdbtns\cmdicons.grp
rez\statdata.bin
unit\wirefram\grpwire.grp
unit\wirefram\tranwire.grp
rez\statfluf.bin
rez\statlb.bin
rez\stat_f10.bin
rez\statport.bin
rez\statres.bin
game\icons.grp
rez\stat_txt.tbl
game\twire.pcx
unit\wirefram\wirefram.grp
rez\tips_dlg.bin
rez\tips.tbl
rez\wmission.bin
rez\lmission.bin
rez\video.bin

Yes but doing that would remove the cross-compatiblity in Storm (unless they update Warcraft II BNE, Starcraft, Warcraft III, Diablo, Diablo 2 and WOW at the same time).

Yes, they might have to...but thats what they usually do when a big patch comes out

But I don't think they really care about the cross-compatibility

I think patching this is extremely improbable. Instead of you people just countering the people that say it's impossible, why don't you just accept the fact that Blizzard won't patch it?

Over the years I have learned that you should never say someone won't do something, it often proves incorrect

like I mentioned early, they probably won't patch it, but theres a chance they will (they can if they tried )

I'm just trying to get everyone off the discussion "Do you think Blizzard will patch this?". Please, it belongs in a poll.

Make sure you see my list two posts back.

I was also taking a look at older posts. I think Game type slot 22 should be used for SCMLoader, since I am working on a modification of my own that will include it.

I already made one that uses number 27, would that number be fine? I plan on including this in the next release.

BTW, I don't think Blizzard will attempt to even make a patch to prevent use of this at all. A few reasons:

1) It apparently only works for UMS game type (I haven't seen it work for other game types on battle.net), so it couldn't be used for cheating to get more wins for ladder or non-ladder.
2) It can't be used to spread viruses through maps (unlike EUD).
3) It very likely would take much more work to prevent its use than they are willing to put into Starcraft.
4) They haven't done anything about MPQDraft, which essentially works about the same, does work on battle.net, and can have the exact same effects on gameplay; so why would they do anything about SCMLoader?

Since I'm the creator of it and no one else has seen my code, don't argue with me on point #3. Well, at least about how much work it would be for them, anyway.

Slot 27 it is then.

Do you have any other plans for this?

You mean plans for features in newer releases?

Well, you can look here for some things I plan on doing: http://www.staredit.net/index.php?showtopic=28068

One thing I will state here is that I plan on putting in some type of auto-updater or at least notifications when new versions are available. Either way I do it, it will check when SCMLoader is started. This is to make sure that anyone using it will have a version that supports all of the features needed for any maps they might download, but mainly just to keep the version consistent between users of SCMLoader so they don't get desynced when playing SCMLoader-enabled maps on battle.net.

Changing units names uses string space in the maps, right? If so, then modifying the names in the tbl files would save the string space that you would have used for some of the unit names.

BTW, has anyone ever tried changing the number of strings in the chk section for that and tried opening in the campaign editor to see if it supported using that different number of strings? (especially more strings)

I'm wondering, if you edit the TBL file to change the text under the unit names, then start the game with someone who isn't running it, will it desync? I don't think it will, but just checking. Is it possible to replace unit graphics with custom sprites with this or no?

I'm not sure, you will have to try it to find out whether it will desync or not. I don't think it will, though. Currently it is not possible to replace unit graphics with this. I am going to look into ways of doing it, though. I have a couple of ideas: replace the graphics in memory or find a function in Starcraft that I could call to force it to reload a graphic or all of the graphics.