Quick Modding/Hacking Answers Thread

There's two things, the hacking tool (which just blindly applies hex patches to offsets) and the hackinator which is a gui for applying premade hacks.
The hackinator comes with a list, select an item to see details about the hack and adjust any parameters, then just press the button to apply it.

 

Does anyone know where the hitrects for bullets are stored?

 

they're in a struct with other bullet initialization data.
check the weapon hacks in booster's lab for some pointers, they're just xml files in the "hacks" folder.

 

they're in a struct with other bullet initialization data.
check the weapon hacks in booster's lab for some pointers, they're just xml files in the "hacks" folder.

Ok thanks

 

There's two things, the hacking tool (which just blindly applies hex patches to offsets) and the hackinator which is a gui for applying premade hacks.
The hackinator comes with a list, select an item to see details about the hack and adjust any parameters, then just press the button to apply it.

Thanks for the response, but how does one make a hack? I'm familiar with the workings of the hackinator, but it's how to make a functioning hack that's got me confused. I'm fairly inexperienced in regards to the coding/hacking part of cave story modding, so maybe there's some obvious fact I'm missing.

 

Thanks for the response, but how does one make a hack? I'm familiar with the workings of the hackinator, but it's how to make a functioning hack that's got me confused. I'm fairly inexperienced in regards to the coding/hacking part of cave story modding, so maybe there's some obvious fact I'm missing.

you don't *make* hacks with booster's lab, it's more a way of distributing them to the unwashed masses. If you wanted to write your own custom assembly hacks you'd use a combination of tools like ollydbg, doukutsu assembler, the reference documentation available around the forums, and a strong knowledge of x86 assembly.

 

you don't *make* hacks with booster's lab, it's more a way of distributing them to the unwashed masses. If you wanted to write your own custom assembly hacks you'd use a combination of tools like ollydbg, doukutsu assembler, the reference documentation available around the forums, and a strong knowledge of x86 assembly.

Ah, thanks. That gives me the answers I need.

 

I have been wondering, how does the game know which map to load for each map ID? I have looked at the code and it is an array, and with the <TRA command, it takes the map ID, multiplies it by 1000, then adds 4BF000 or 4DF020, pushes the address, then it calls function the at 481010 (sprintf) which probably stores the result in a pointer to that maps files. What I have been wondering is what is at those addresses. Is the filename string and the map name in game stored there?

 

yes

 

in the bullet functions

 

try...... reading the function list?

 

http://cave-story-modding.wikia.com/wiki/Cave_Story_Functions_List

 

two ????????

e: I just looked and it's there. Like, painfully obviously there.

 

If you can't find it from this i suggest going back and studying the fundamentals because this is very very easy

 

Yeah no problem

https://www.cavestory.org/forums/th...dding-tutorials-look-here-before-asking.1667/

 

That's not what I meant.

Jesus Christ what are you gaining from arguing

 

Nothing. Although something actually useful would be nice...

Open it up in Olly and check the functions, with the ASM guide telling you how the framerects would look like, maybe? If that isn't easily helpful to you, you can always try working the shaft. :^)

 

wow gee sorry I forgot my mind reading hat at the laundromat last week and yknow its just been such a hassle for me trying to guess what people want without it

 

Oho! Nobody bothered to mention that the Machine Gun lvl3's trail is AN ENTITY. THANKS A LOT.

It's almost like sometimes you have to figure shit out for yourself sometimes.

Nobody knows what you're looking for off the top of their head. We have tutorials on how to learn how to read assembly and documentation on the executable. All the tools are there, you just have to invest the time to put it all together.

 

I want study how to use 'boss' monster
Can I find example files?
Original's script are too hard to read