Direin wrote: ↑Fri Feb 18, 2022 5:55 pm
Hi! Could you please tell me how you managed to find Bypass Ingredient Check on Craft and Transmutation options? I'm new to game hacking and I really want to know how one should approach finding craft-related stuff. All I want to know is how it could be done, step by step, or at least a general idea. I'm ready to pay you
I can't remember the details. Try asking me about a table I've done more recently. This hack is not intuitive, just looking at it I can't tell what it's accomplishing. More than likely I found the spot where the checking for ingredients began and the hack is to jump past all the checks for the different slots to the code that gets run when a success happens.
Some general thoughts: You can find a hack like this by following the cmps and tests and noting where successful crafting threads diverge from unsuccessful ones. (this is just an example, I can't remember how it works in this game) If I had to find something like this right now, I would place a stack of ingredients into the crafter, search for the stack count, and then craft something. Repeat until I found and confirmed the stack count in memory. Then I would "find out what accesses this address" and watch what accesses that stack count when I hit the craft button. Hopefully, not too many different things. You need to go through each one and see what's happening. There's gonna be code that writes to the address, that's the code that changes the stack count. So you know that code and everything past it is gonna be past the code you care about. You want the code that checks the stack count, not the code that changes it. From here, I would start looking at the assembly. I know this is vague and may not be entirely helpful to you depending on your knowledge level. Apologies if that's the case. I do remember the craft/transmute hacks were unusually annoying to create. If you're a very beginner, I would try hacking some Unity games first. The mono data collector and dissector can give you some plain language insight into what's going on at the assembly level (and dnSpy can give you even deeper insight by showing you the pre-compiled code).
If you have specific questions, feel free to msg me.
