QUOTE(Red2Blue @ Jan 29 2006, 09:06 PM)
Some people can actually hex the crud out of that program and program a little button for "save" or even better, extracting the data into a text format so they can easily throw it back into an editing program for their entertainment. Heh...
Trigger Viewer is the first step: LOADING (input) the triggers.
The second step is a program to: SAVING (output) the triggers.
I hope you know what you are doing to the sen community MindArchon.
Gj.
[right][snapback]416342[/snapback][/right]
No. It would take a
shitload of time, for lack of a better phrase, to do what you've described. Not only would you have to write a completely new function,
all done in assembly to an existing program that would call a bunch of functions in an outside dll using variables which you have no idea what are doing unless you spend another year figuring them out... but you'd also have to actually do the unprotecting stuff yourself. All this program does is load the data, not paying attention to many of the things the protection programs did (granted, stuff like Uberation gets to some trigger stuff like strings, CUWP slots, etc. in a different fashion than what is the regular .chk spec). A lot of the map data that's "protected" is pretty much untouched by this program.
Bottom line: he's not doing anything to the community. It would be much simpler, and in fact more effective, to write a completely new program if you wanted to make an unprotector.
QUOTE(Red2Blue @ Jan 29 2006, 09:18 PM)
I guess so... if you say its great...
It just makes me ask you: "where all those unprotecting programs come from."
So? Where? Where do those guys get their code for making their unprotectors?
From the protecting program itself.
This program? Ah, gives you all the code into one nice package. Is it that hard to slap a: "save map" button on it?
[right][snapback]416375[/snapback][/right]
If by "all those unprotecting programs", you mean the
one unprotecting program that was ever released, the answer is "just by looking at what the protection does."
That's the fastest way to do it, period. Definitely much faster than analyzing a bunch of obscure ASM load code as you said.
Yes, as I've said above, it
is "that hard to slap on a 'save map' button on it."