Quick Modding/Hacking Answers Thread

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.

 

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

I decided to explain what I did through pictures this time...

Spoiler

 

I decided to explain what I did through pictures this time...

Spoiler

View attachment 2692



View attachment 2693


View attachment 2694


View attachment 2695


View attachment 2696

The right click menu seems to be different than what I have, are you using version 1.10?
If not, try downloading it and try it again.

Also short question of my own: What tiles are used by the motionwall NPC?

 

The right click menu seems to be different than what I have, are you using version 1.10?
If not, try downloading it and try it again.

Also short question of my own: What tiles are used by the motionwall NPC?

Yeah, I had the version 2.0.1

Anyways I downloaded the 1.10

I did everything you said, aaaand olly just flat-out closes out when I save.
Hey, at least I didn't get that error.
And no, the changes were not saved.

 

Can someone please tell me how to edit the health of all the bosses that don't appear in Npc.tbl? (Eg. Ballos' 2nd/3rd form, The Undead Core, etc.)

The health for "big bosses" is hard coded into the executable, and is actually a part of their enemy AI. If you go to their ASM functions individually, you should be able to find somewhere in their enemy AI subroutine where they set their HP.

 

The health for "big bosses" is hard coded into the executable, and is actually a part of their enemy AI. If you go to their ASM functions individually, you should be able to find somewhere in their enemy AI subroutine where they set their HP.

So these big bosses, are they not their own entities?

Would there be any way to change them through the assembler?

 

So these big bosses, are they not their own entities?

Would there be any way to change them through the assembler?

They're special entities. They do bigger tile collision checks and stuff, but for the most part, they're a normal "entity", except that they don't appear in the npc table. A sort of super-entity.

I'd recommend using a disassembler to take a look at them at least, but theoretically, you could entirely overwrite their AI functions with the assembler.

 

Can I ask something?

If you offset an NPC, and the asm coding takes up more space than the original, does it overwrite the next NPC as well?

 

what do you mean "offset"

 

I believe the sets of code for each NPC are pretty close to each other so if you change the length of an NPC's code it will likely overwrite part of the next NPC's code.

 

If you offset an NPC, and the asm coding takes up more space than the original, does it overwrite the next NPC as well?

If you rewrite an NPC's AI function, and the new function is longer (in bytes, not commands) than the old function, then yes, it'll overwrite into whichever function is next (which is likely the next NPC), since you're trying to put a longer function into a smaller space.

 

If you rewrite an NPC's AI function, and the new function is longer (in bytes, not commands) than the old function, then yes, it'll overwrite into whichever function is next (which is likely the next NPC), since you're trying to put a longer function into a smaller space.

What if I put some code for the the said AI function in a completely different(and empty) part of the exe, and CALL to it during the NPC code? Then Retn it and it wouldn't take up any more space in the NPC code area?

Spoiler

Wait, f*ck, don't local variables, like not stay during a CALL function or something like that?

 

What if I put some code for the the said AI function in a completely different(and empty) part of the exe, and CALL to it during the NPC code? Then Retn it and it wouldn't take up any more space in the NPC code area?

Spoiler

Wait, f*ck, don't local variables, like not stay during a CALL function or something like that?

Calling another function will "mess up your local variables" if you set it up right, yes. Basically the function you called will/should no longer have access to the local variables from the function you are calling from. But instead of calling, you can just JMP to your code in the unused space elsewhere in the .exe, which would mean that you're never leaving the scope of the function you're in and could use the local variables. You'll want to be sure to JMP back to the end of the function at the end.

 

Calling another function will "mess up your local variables" if you set it up right, yes. Basically the function you called will/should no longer have access to the local variables from the function you are calling from. But instead of calling, you can just JMP to your code in the unused space elsewhere in the .exe, which would mean that you're never leaving the scope of the function you're in and could use the local variables. You'll want to be sure to JMP back to the end of the function at the end.

Wait, so now i'm confused.
If you could just JMP back and forth, what would CALL and RETN be good for?

 

because there are some benefits that come with not having to worry about having conflicts over local variables with every other block of code that could call a function. The rest is left as an exercise to the reader.

 

Wait, so now i'm confused.
If you could just JMP back and forth, what would CALL and RETN be good for?

To play nicely with the stack, i.e. so that the functions you are calling DON'T touch/mess up your local variables.

It's also so that you can call a function and it'll know to return to where it's called from, whereas if you JMP back and forth, the code block you are JMPing to can only JMP back to one spot. So the function can easily be called from multiple spots.