Would faking the Blizzard signed maps be more good or bad?

Whether it is possible or not, technically, would it be better or worse?

PROS:
Switch between maps
Create folders
Change directories
Save maps

CONS:
Can be used to crash computers
Possibly send viruses
Hacking a blizzard map
Abuse

Now to look at it literally, we can already crash maps by running a never ending loop, sometimes causing their computer to crash, we could play a million sfx at once, crashing computers. We can implement a virii into a map with MPQ editing, everyone already hacks the mpq in one way or another (it's how we mod right?) And abuse, yes you can create stupid folders that mean nothing or save alot to waste space. But what about an installer that installs useless crap? That can install a bunch of useless stuff.

I think (whether it IS possible or not) that we should find the header code and crack it (I hear its 128-bit encryption, VERY HARD) or Blizzard should just allow them anyways.

What do you think?

In my opinion, no. Due to the amount of morons and otherwise jackasses on BNet, there'd be too much abuse of this feature, and not enough benefits by using it in campaigns.

Personally, if people can actually find a way to do this, or Blizzard allows it, I'm giving up on custom games.

If people change MPQ and ****, how can they make a virus work in a map. . . :////

There is no way to open a file that has nothing to do with WC3 ;)

You can put anything, ANYTHING into an MPQ file. MPQ is basically another form of compression (like a zip). But running it out of the mpq is another issue. Even if you open the map you would still need to directly run an infected file. And yes this would be abused. The only thing they should allow is the map changing thing (which is allowed in single player but not multi :( ), but saving and loading and the like should never be enabled. There are simply too many assholes out there who would make stupid crap for no reason. Making "a million SFX" will only crash the computer forcing you to reboot. Making a million save game on your computer will do a lot more than make you just reboot...

When we take into accout that that feature would ONLY affect Singleplayer, the risk isn't very high. Singleplayer maps are not spread at Bnet. A user has to download them manually off some site. So the user has to browse a site and decide whether he wants to download a map or not. Additionally sites like WC3C would ban everyone who posts an abusive map here, plus it would warn users about new "virus" maps.

Fyre I don't know if its a good idea, I know in multiplayer in SC there was a program that could fake it but B.net eventually institued some check (It may even be in place with War3) (It would say something like this map failed the database test, Please try downloading it from Blizzard.com/wahtever the link was to the map of the week).
They could also have this hardcoded somewhere so you couldn't get away with it.

As far as the risks as long as you act like mature programmers and don't use this as a way to make the map save ad-infinuim so my Comp and everyone elses crashes 8000 times, there is no danger. Anyway the cache functions and save game functions won't even run in multiplayer, the cache must be flushed at the end of each mplayer game, circumventing this will make your cache file full of worthless information (How many units you killed all the stuff you see on the gametable) and most like it won't let you do a write to it anyway.

Well what about making it so you have to have the proper MPQ then? That way you can't just distribute a map, it will have to be a mod, or a campaign, and people don't normally download them unless they hear good things about them anyways. Normally it's just the beta testers that get their hands on it, and if they like it, or it doesn't screw stuff up, they will tell people about it. If it is abused, and it crashes someone's computer, the person would, like SCFreak said, be banned, and the map would be removed. It wouldn't last too long. It's just like a virus, once it is found out about, something is done about it, making it obsolete.

Ugh...

I have said it before and I will say it again.

There should be a hardcoded limit on saves per map, 3 a game. And keep updating the saves and deleting the old ones. Only let it delete saves and nothing else -hardcoded.

Viruses aren't a threat, unless blizzard stupidly allows .exes in mpqs/maps.

And whatever other bullshit you can think of I can figure out a comeback to.

I've got an idea, only be able to delete files that either

A. Triggers in this game created

-or-

B. Saves in a WCDir\MP\Saves\-Map-

I don't even see the point of being able to make save games anyways, someone explain what the point is. I understand caches, but why save games? And, again. MPQs can store ANY-THING. The issue is running that thing...

Who knows, someone gets curious and goes through your MPQ and they see Setup.exe, they click and bam, a trojan. I voted on undecided, I think it would help for select projects, but not for the general public. Someone blizzard trusts, which is themselves, no one else.

Yes but someone please tell me why saving games would even be needed? I understand caching, I understand map switching, but not saving..

Jugding from how blizzard states there liscene agreement they could quite simply ban you or worse, as much as i would love to see those features in a map, it would be risky, i feel of course blizzard may eventaully make a map changing system for w3m/w3x in single player only.

Personally, judging from how difficult it may be to create several linked maps, i think people would be able to judge from a professinal campaign or not.

I'm torn what side of the fence I'm on. But to answer Ekkruker:

We are not talking about being able to make savegame files, exactly. What people mean by the save-game thing is that there are some triggers in WE that you can only use with a Blizzard signature on the map. The two most notorious are Save Game and Load Game. These triggers are key to creating multi-map RPGs like the TFT Orc campaign and indeed are what the Orc campaign uses. (Because it's Blizzard-signed, so it can use 'em, of course.) The way it works is one saves the current state of the current map (like where creeps and units and things are) and then loads the new map. Later, when you return to the old map, it loads the saved version and picks up right where it left off when you left. See the Orc campaign for the classic example. (Anytime you change maps like going into the caves or the valley of the thunder lizards, it's using these triggers.)

Anyway, point is that while this can be simulated TO AN EXTENT with triggers and the cache and things, there are limits to what you can do with the cache and it's rather complicated. Thus people wish they could sign their maps Blizzy-style to use these triggers. But the same way, code could theoretically save a map repeatedly until it fills up the hard drive. And that's one of the fears of abuse of this system.

So now you know, and knowing is half the battle.... .NET!

Blizz could enable only a change map function that saves the current game and loads the other map.
This way the system can't be abused coz right after making the savegame it loads the other map.