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

erm, i know that i know very little on this subject, but in the bonus campaign, didnt they just do a mass cache save?

1 thing you can try... (Using Lost Temple)

Maybe the header is generated by everything in map, including the map version (how many times it's been saved) and when you save as a different name, it has a different map version. Try using Zepir's editor to decrease the save version value of the original Lost Temple by 1, save with Zep's. Then load it up in WE and save it as the same file (the copy you jsut edited ofcourse) and then try the header hack.

I haven't tried hexxing it all so I don't know what it looks like, but this could be worth a shot.

BTW: At the time of this post, it was 25 yes and 24 no.

Er, first of all, to answer Bloody_Sorceror, they did not merely do a mass cache save, at least not to my knowledge. If you look close, you can see when you return to a map that the map picks up EXACTLY where you left it. And you can go and edit those mapfiles and look at the triggers yourself. Just because they won't work without a Blizzard signature doesn't mean they won't appear in the map when you check out its triggers. (Because they were left in the editor for some reason even after we were stopped from using them. My only explanation for why this is was so that we could load stuff like the TFT Orc campaign to look for examples without it causing errors looking for triggers that don't exist.)

As for the header/footer stuff, I don't know a heck of a lot, only what the Warcraft III Map File Spec says: That the footer starts with NGIS. (SIGN spelled backwards and not NIPS as previously reported) The data in the footer seems to change based on several factors which so far no one has worked out. It is clearly based in some sense on the contents of the map. Is has also been suggested that it is probably encrypted in some way, and most likely with a very difficult-to-break 128-bit RSA-like encryption scheme. 'Dem's da bad news.

But I've never actually done diddly myself to investigate how it might be calculating the footers, only that it clearly is dependent somehow on the contents of the map, i.e. just copying footers from Blizzy maps will do you no good.

Interestingly enough, the mapchange is possible in multi, i played a RPG that used it, i dunno weather he hacked the blizzard stuff or not, but at 3 points we jumped maps, we lost somone the first time but after that it worked fine.

The map-changing functions work on nob-blizzard signed maps, but you cannot save/load maps.

you know blizzard are probably bullshitting everyone when they say that the triggers could be used to damage somones computer and such, they probably just dont want to release them.

I think other posts have proven that they could be used to damage other computers. All that is needed is a trigger, running on an infinite loop, that saves the game.

35263526, do you actually read the posts?

I'm my post I explained how "abuse" could be easily and simply avoided.

Read the f***ing posts, man.

the fact of the matter is, using WCIII triggers you cannot damage somones computer, the old conspiricy theory. I have my dad and his entire IT team backing me up on this, its actually extremly hard to damage a computer in any way, yes you might be able to crash WCIII with it or maybe even corrupt it, but i can do those two things already by running certain triggers on infinite loops.

Please, please, please, let us stop arguing. There seem to be a great many misconceptions running around here. Pheonixiv, no one is suggesting WC3 triggers could physically harm a computer. There is little you can do in software to actually damage components, which is the only thing I can assume your father was referring to since it is certainly possible to damage the operating system and data and such with software, else viruses would never exist.

The unadulterated fact, as I understand it, is this: Since none of us really know the extent of the power of these triggers since we can't use them, we can only conjecture, guessing at best- and worst-case scenarios and trying to see ways they could be fixed. At worst, the triggers could give effectively unfettered hard drive access to the map, opening a security hole the size of Sri Lanka that any hacker would dream of. On the other hand, at best, the triggers don't have nearly that power because of intelligent limits on what they can do, (placed by Blizzard, in case we ever were to hack into them) but there's still the possibility of flooding the hard drive with files. With enough space used up, performance could be significantly dampened, especially on systems that rely heavily on Windows' swapfile. Irreparable damage is unlikely if the triggers have reasonable locks on them that would prevent, say, overwriting key Windows files with a WC3 map. (If not, all kinds of havoc could be created.) But it could still cause annoyance and damage, and for someone who doesn't know how to clear up enough hard drive space with the Windows Recovery Console to boot up, it could cause even worse trouble.

But in the end, we don't know much. The argument about damage potential is just an offshoot of the topic at hand: Can and should we hack the Blizzard sig? We have no proof that these could do damage. But there is definitely a clear potential, clear enough that there is debate over whether to tread into these waters and clear enough to make Blizzard lock them in the first place. And we will never know the truth until someone DOES hack the code. I only hope that whoever does is responsible enough to check whether it's safe before they release the secrets, in case it proves Blizzard did not put reasonable limits on the triggers. I would be interested to know the results of such, even if it meant the information would be kept secret forever.

Right now, the vote is just barely against hacking the maps. So... Back to the topic at hand. To hack or not?

no my father and his IT team were backing me up in both hardware damage and serious software damage, it might be possible to place a virus inside the map, but we can do that anyway. Its the age old Conspiricy theory that every company uses when they have some technology that they dont want to let go of.

I think that it shold be done. Mainly because the pros outweigh the cons, I mean anyone and I mean :( ANYONE:( can crash a computer or damage software. It would be so amazingly useful if we could just use those oh-so-holy blizz-signed trigs, insted of having to put heaps of work into doing workarounds like mass-cache-triggers to save everything on a map like in the wa3x orc campaign, I mean it would be pretty :D sweet:D .


(I'm starting to wish I was a hacker, if only for this reason.)

P.S. If any one does figure out how to do this send me how or something that can.

Ciao.

You guys are forgetting something. We already can spam up peoples harddrives. There is a thing called 'Save Game Cache'. You could run an unlimited loop saving those while you played a map, and you wouldnt notice. The only difference in saving maps is that they're bigger so it would just take a shorter time.

Maybe blizzard is bluffing about their saving actions. If it were true only bliz could use them, they would hide them in the editor.

I havent gotten the hacked auth yet tho.

True. But the problem is that the Game Cach doesn't work in multiplayer, but if the save-game triggers were enabled, they would.

I continue to state the basic fact that running an infinite loop that saves the game or saves an object to the game cache would fill up a person's harddrive. And although it would be relatively easy to remove such a file, Windows will not start if there is no hard-disk space left. I have a Linux boot CD that does not require a hard-drive at all in case of virus attacks that do this sort of thing.

ThePersonThing: I have reported you to the moderators because of your rudeness and flaming. I hope they take serious action against you as there is no room for people like you on these boards. Regardless of what could be done to stop the triggers being abused, no-one can deny that in their current state they could cause serious problems if enabled. Control your anger.

35263526 , I for one belive you deserved that and there is a diffence between flaming you and just saying the words ****ing, if he were flaming you it would look more like this

.
not
.

ok, maybe I went a little overboard, but you get the point.