Quick Modding/Hacking Answers Thread

Can someone tell me the asm offsets for the health of each of the 'major room bosses?'

I mean like Balfrog, Monster X, Ballos' third form etc

 

Eh... Hi guys.
So I saw something about debug saving, and I wanted to do that, but I have never ever EVER done hex editing before. Could someone help me out with this?
***link is here

 

Can someone tell me the asm offsets for the health of each of the 'major room bosses?'

I mean like Balfrog, Monster X, Ballos' third form etc

I would also like to know these.

 

Eh... Hi guys.
So I saw something about debug saving, and I wanted to do that, but I have never ever EVER done hex editing before. Could someone help me out with this?
***link is here

You just open cave story in a hex editor (like HxD - google it). Seek to the offset and change the value (make sure it overwrites the pre-existing value and doesn't add a value). Just change the values already there to what RuneLancer specified.

 

Well do you have a 32 or 64-bit OS? Google how to find out if you don't know.
Download the 64-bit version of ollydbg if you have 64-bit windows. And if that doesn't work, try this out - haven't used it and of course there are no guides around here that show it but it seems to do what olly does

Uh, I can't seem to find a 64-bit olly anywhere... do you know where it is?

 

Uh, I can't seem to find a 64-bit olly anywhere... do you know where it is?

Is a 64-bit OllyDbg even needed? Cave story isn't 64-bit(as far as I know) and I use the 32-bit version myself and haven't had any problems.
Also there isn't a 64-bit OllyDbg yet as far as I'm concerned.

 

Uh, I can't seem to find a 64-bit olly anywhere... do you know where it is?

It seems that 64 bit Ollydbg v2.0 is still being made...
http://www.ollydbg.de/odbg64.html

 

Is a 64-bit OllyDbg even needed? Cave story isn't 64-bit(as far as I know) and I use the 32-bit version myself and haven't had any problems.
Also there isn't a 64-bit OllyDbg yet as far as I'm concerned.

I honestly blame my shitty laptop for the error.

 

I honestly blame my shitty laptop for the error.

Try explaining the exact steps you take(Starting from after you opened whatever you were using OllyDbg for) that causes the error.

 

Is a 64-bit OllyDbg even needed? Cave story isn't 64-bit(as far as I know) and I use the 32-bit version myself and haven't had any problems.
Also there isn't a 64-bit OllyDbg yet as far as I'm concerned.

CS is 32-bit, but that doesn't really have much to do with what version of olly you use - x64 bit olly will run better on x64-bit computers.
I'm pretty sure there's an x64-bit olly and that I have it downloaded, but I could be wrong. Of course if there isn't, @Kenzo_ITC should consider the other disassembler I linked.

 

Try explaining the exact steps you take(Starting from after you opened whatever you were using OllyDbg for) that causes the error.

I actually made a thread explaining my problem in the technical issues.

Spoiler

YOU EVEN REPLIED TO IT, SAYING THAT I SHOULD JUST TRY TO REPORT THE PROBLEM, WHICH REALLY DIDN'T HELP.

 

Can someone tell me the asm offsets for the health of each of the 'major room bosses?'

I mean like Balfrog, Monster X, Ballos' third form etc

 

I actually made a thread explaining my problem in the technical issues.

Spoiler

YOU EVEN REPLIED TO IT, SAYING THAT I SHOULD JUST TRY TO REPORT THE PROBLEM, WHICH REALLY DIDN'T HELP.

I already know this, but I think I had the same error when I used ollydbg about two weeks ago, later than when you started the thread and me answering.
I'm just asking what you did to try and help, no need to get so aggressive tbh.

 

I already know this, but I think I had the same error when I used ollydbg about two weeks ago, later than when you started the thread and me answering.
I'm just asking what you did to try and help, no need to get so aggressive tbh.

Sorry, I wasn't trying to go off as aggressive.

Well here's how it went:

1. Set up olly, everything's fine...

2. Load up Dokutsu, everything's still fine...

3. Changed some offsets, and copy to excutable.

4. Try to exit out and it says:

"Would you like to save your changes?"

I click yes, and then that's when the error happens...

 

are you sure the file is not read-only

 

are you sure the file is not read-only

It shouldn't be unless he's modding the Japanese version.

 

that's great but your statement doesn't contribute to a solution and only serves to take away from my attempt to diagnose the situation

 

Sorry, I wasn't trying to go off as aggressive.

No problem, don't worry.

Well here's how it went:
1. Set up olly, everything's fine...
2. Load up Dokutsu, everything's still fine...
3. Changed some offsets, and copy to excutable.
4. Try to exit out and it says: "Would you like to save your changes?"
I click yes, and then that's when the error happens...

Try editing whatever you wanted to edit, right click whatever you changed and select copy to excutable>all modifications, and then select copy all. Right click in the new window and select save file to save. Then see if it worked.
I might be wrong here since I can't really test wether it works or not right now, but I haven't gotten the error with this method.

 

Try editing whatever you wanted to edit, right click whatever you changed and select copy to excutable>all modifications, and then select copy all. Right click in the new window and select save file to save. Then see if it worked.
I might be wrong here since I can't really test wether it works or not right now, but I haven't gotten the error with this method.

Tried it, and it gave me the exact same error...

are you sure the file is not read-only

It's not, I checked before-hand.

I know it's something to do with my laptop cause I can use olly just fine on the computers at my school.

 

Tried it, and it gave me the exact same error...

When did the error appear? Because if you got this when trying to exit&save again you clearly haven't manually saved.