Help me test hackproofing hacks

So i've been doing a bit of research, and I need to test my findings. All you have to do is download this slightly modified doukutsu and place it in a normal, unmodified cave story folder. Then, try and play it. If it works, that is good. Now, try and do some assembly hacks to it. If you find your ability to hack it is significantly impeded, that is also good. If it works just the same as a normal one that is not good. Please report your results. Also, if you find my measures easy to defeat I'd like to know that too.

These methods I'm using are a little bit tedious to implement so I'd like to know if they actually work. I've done a fair bit of testing on my own but that can only tell me so much. One final note: by downloading you agree to not hold me responsible for anything that may happen as a result of using it or having it.

I mean, not that it should do anything bad. It's just a disclaimer. I promise. There's one just like it in the cave story readme.

EDIT: Never mind, I guess they fixed it in olly2.0

 

Didn't andwhy say something about not doing stuff like this?

 

Well it worked, it seemed to load slightly longer but it worked. Didn't crash or anything.

 

Good luck!

Didn't andwhy say something about not doing stuff like this?

WiiWare hacking, yes. But this is normal PC hacking.
Noxid is just wanting to hack-proof his hack so, if he releases, others can't easily modify and use the code for malicious purposes.
*Cough*Like replicate WiiWare on PC*Cough*
Runelancer did something like this with his own mod, but it was more of a complete re-arranging of the EXE to make it more efficient and give him more room for his hacks. Regular editors wouldn't work on it anymore, though.

 

Exactly.
Glad to hear it at least runs on other people's computers.
Now I just need somebody to try and modify it with olly...
Also, Rune rearranged the whole .exe? I wonder how he did that without it being an insanely tedious manual process.

 

All right, I've tested the exe. It plays just like the normal one.

I'm using OllyDbg version 2.0, the beta version! (if that makes any difference)

I was able to go into the polar star code and increase the speeds of the bullets. It worked.

Next I will try replacing some NPC behavior code.

As far as I can tell, the "NoDbg" thing does not seem to be working.

 

I think that's enough. I wasn't aware of the 2.0 version :0
I guess they must have fixed the exploits I used.
Hmm.

 

Re: Good luck!

WiiWare hacking, yes. But this is normal PC hacking.
Noxid is just wanting to hack-proof his hack so, if he releases, others can't easily modify and use the code for malicious purposes.
*Cough*Like replicate WiiWare on PC*Cough*
Runelancer did something like this with his own mod, but it was more of a complete re-arranging of the EXE to make it more efficient and give him more room for his hacks. Regular editors wouldn't work on it anymore, though.

No, you idiot. He said something about not making Cave Story unhackable in any way.

 

Someone's rather rude...

No, you idiot. He said something about not making Cave Story unhackable in any way.

Before you say that, you should probably provide a link first.
I've never heard him ever say anything about that, and it's already sorta been done before.
Also, I don't see why we shouldn't be allowed to prevent other people from stealing from our mods...

 

I thought one of the features of SP's new editor thing was some sort of "project file" setup to make mods unmoddable anyway?

 

I thought one of the features of SP's new editor thing was some sort of "project file" setup to make mods unmoddable anyway?

And then andwhy was like "no"

 

*Sighs*

And then andwhy was like "no"

Again, link please?
I looked through and never saw andwhy say "No project files".
Some people complained a bit, but it still looks like SP is including them in the Editor.

 

Re: *Sighs*

Again, link please?
I looked through and never saw andwhy say "No project files".
Some people complained a bit, but it still looks like SP is including them in the Editor.

I FINALLY found the thread. It wasn't andwhy, it was Jackalope.
Jackalope wrote:

 

No, you idiot. He said something about not making Cave Story unhackable in any way.

Well, it's impossible to make it unhackable anyway. You can make it harder to hack by applying optimization (and possibly obfustication, though I think that only applies to source code), but it'll still be possible.

 

Well, it's impossible to make it unhackable anyway. You can make it harder to hack by applying optimization (and possibly obfustication, though I think that only applies to source code), but it'll still be possible.

Of course, if he makes it much, much harder to hack, there is an extremely low chance that anyone has the technical ability to hack it. Thus, nobody will be able to abuse the new resolution (or whatever else NoDbg is for).

 

Yeah. NoDbg actually caused Olly 1.1 to crash when you opened it up. Also the game won't run while the debugger is running on it but that's hardly an inconvenience. I figured it might be worth it if it was something easy like that but I can't be bothered to rearrange my entire .exe or figure out some encryption alrogithm whatever thing.