Possible Way of Making Code Porting Better

I've been doing lots of code porting lately and have found that my preferred method of porting, HxD Hex Editor isn't truly meant for Gecko code porting. The only reason why I prefer this over code porting programs is because I can actually see the Hex and know if I'm making a mistake.

Now, what I've come across is 32 bit memory segments (ending in 0,4,8,C) that are very similar but change in just a few characters, usually near the beginning or end of the segment. Below is an example of some of the ones that I've found.

41 82 00 14
Can change to something like 41 82 00 18

3C 80 43 30
Can change to something like 3C 80 80 81

7F A0 1B 00
Can change to something like 7F A3 EB 78

It would be much easier if there was a Hex editor that could multi-select bytes instead of having to select an entire row. I have failed many times to port all sorts of codes because of this drawback. Just an idea.

Good observation
Because the original value CAN change, I respected this in my porting program. It basically tries templates until one worked reasonably and does NOT check if the original value is identical. It's almost as good as a human porter

The only problem is that it can return a wrong result but mostly it's correct. If you have the game you can easily test the ported code(s) so it's little efforts to port a ton of codes overall. Also you can use HxD or whatever to check if it looks right as well like you said, seeing is believing.