Game:

Pokémon Gold and Silver (1999)

Duration: 10:52

4,994 views

26

Ever wondered why a lot of ASM hacking is undocumented? You try to explain this shitastrophe! I still can't find it...

I might find it eventually... by god-forsaken LUCK!!! Some fawken accident or perfect timing to find the correctly loaded code.

Ever wondered why? Here's an answer.

We can't always explain our ASM hacks. I'm sure something is somewhere for this... but not even hackers always know.

I can't explain half the shit I do, because it's like:
Me: (digging for hours, find it, do shit, create magic)
Person: "How did you do it?"
Me: "Um, stuff..."

...Yeah.......stuff........ this is probably to answer all aching questions that assembly hackers (like me) have to deal with.

It's painful to not have an answer for people who want to know too... painful... then have people doubt/hate you because you didn't document it. We break our backs over this simple shit.

Even changing Miku's overworld sprite palette required a similar "digging" scenario... worse than this... this is... easy compared to the flag for Miku's palette......

This is why shit takes so long to do sometimes too, when making discoveries... it may also be the reason why ASM hackers dislike posting their findings, I find myself exhausted after to even post my findings. Nothing personal.

Also, in case anyone is confused to what I am doing, D116 is where Trainer/Wild Pokemon are flagged as catchable or not. 02 is a Trainer, and determines the Pokemon is uncatchable. Obviously other flags determine a Trainer's beginning/end actions too, so the actual code has to be manipulated instead of the actual value that is set. 01 is for Wild Pokemon to be catchable.

This is one of the millions of hurdles for hacking that can occur in an ASM hacker's day.

In fact, without documentation, it would be even more digging just to find the start of where flags are set, and LOADS of testing just to find a result. You can get lost, and even never find something without knowing what the actual value is set to.

This can make things a shit-ton harder for any hacker, for obvious reasons.

A mixture of RAM/ROM have to be used to find things properly.

My guess is that there's a function somewhere when the player selects/throws the Pokeball, that sets the setting. I can't find it yet, of course. It could be using a completely different setup that passes the value like hot-potato. It's crazy.

Other Statistics