AtecainCorp.

Bro, to be an excellent hacker, one must learn ASM hacking, and no, I don't understand ASM either but I'm going to

ASM is not hard, not hard at all. It is the simplest language known to man, encompassing less than 40 words with very strict structures and no exceptions. Let's get that straight. Second of all, have you ever seen the coding of the game??? I have looked through thousands of lines of code in the game and modified structures galore. I know exactly what needs to be done to expand things. I know that every single routine has an overflow check to make sure that things aren't loaded that shouldn't be. The only reason your "hack" works on Ruby is because the check was misplaced for 411 instead of 386 like it should have been. This does not exist on any new games. The check is specifically set for 386.

However, the other coding that specifically designates RAM to store the flags doesn't get expanded. I can almost guarantee that if you see Pokemon #411 but not catch it, it will make another Pokemon be marked as caught that shouldn't be.

Now, you said your method was better because it doesn't use ASM. Did you even read Doesnt's tut? Now where in there does it tell you to use ASM? No where. It just says: "Go here, type this, go here, type this, etc." Why? Because he did all of the ASM coding for you, which he didn't actually need to write any of it at all. It was simple line changes to allow for expansion. He actually didn't write an physical code. He made super small changes to the existing code.

Also, how many Pokemon does your "hack" support? 25 max? And only on Ruby? Huh, do you know how many people still hack Ruby? Probably 10. All the rest use FR and Emerald. For those, there is absolutely no way your "hack" will work. Doesnt's tut supports up to 1020 Pokemon and can be ported to other games.

I'm going to tell you the truth: your childish comments have made you the laughing stock of several other websites. This is not because you tried to find another way. No, we all agree that trying new things is good. It is the way that you completely disrespect hackers that have put hours of research into this topic and you won't even listen to them. How many times did I have to tell you to repoint before you finally realized it was a major issue??? (At least 5 if you don't want to go look because you're too lazy.)

"I do not want listen anyone." - And that is why you will never learn.

"And all you specialy blocked it to make hackers work harder." - I DID NOT BLOCK YOUR TUT. I let it out in the open and it got destroyed. Let me repeat: "I DID NOT BLOCK YOUR TUT."

I don't think you understand the definition of spam.

Stop spamming threads about your tutorial. This is your final warning. Any further advertising will result in punishment.

Hey, your tutorial: What about Emerald?

Wherever there is a pointer to it. Use a Hex editor to find them.

The footprints table begins at the offset given in the ini for PGE and ends at least 387*4 bytes after.

Yes, I just did some math, and repointing the footprints table does clear you up enough room to expand the 25 extra dex entries. So, if you alter your tutorial to do that, I will approve it.

Yes, repoint those and repoint the dex table.

You asked them to help you solve footprints. Just admit that you were wrong and repointing is necessary. I've been wrong thousands of times and the only way to move foward and improve is to admit it and fix your mistake.

Really? If they weren't important, why were you looking so hard for a fix? I can reference over 5 different messages to multiple people about it. Don't lie to me.

IDK how to do it for Ruby, sorry.

Oh, how oddly convenient. You broke footprints by not repointing the table. Didn't I tell you you would see something broken and then not know why?

So yeah, I hope you learned a lesson. You need to know what you are doing when you try expanding things. As a general rule of thumb, if it is bigger, repoint.

24 07 D3 08 24 07 D3 08 94 12 D3 08 60 21 D3 08 14 2B D3 08 0C 36 D3 08 E8 43 D3 08 B4 4D D3 08 D4 58 D3 08 8C 66 D3 08 0C 70 D3 08 C4 78 D3 08 60 84 D3 08 78 8D D3 08 B0 96 D3 08 A4 A2 D3 08 54 AD D3 08 84 B8 D3 08 78 C5 D3 08 10 CF D3 08 38 DA D3 08 0C E4 D3 08 08 F0 D3 08 68 FA D3 08 C4 05 D4 08 DC 0F D4 08 18 1B D4 08 70 25 D4 08 E8 31 D4 08 A8 3B D4 08 D8 46 D4 08 98 53 D4 08 0C 5E D4 08 CC 69 D4 08 70 77 D4 08 38 81 D4 08 1C 8C D4 08 C4 96 D4 08 E0 A2 D4 08 24 AC D4 08 90 B6 D4 08 94 C0 D4 08 5C CB D4 08 78 D4 D4 08 C8 DF D4 08 CC EB D4 08 48 F5 D4 08 78 00 D5 08 90 0B D5 08 68 18 D5 08 F0 20 D5 08 30 2B D5 08 70 35 D5 08 F8 40 D5 08 DC 4A D5 08 50 56 D5 08 40 61 D5 08 D0 6C D5 08 D4 77 D5 08 58 85 D5 08 C0 8E D5 08 C4 99 D5 08 3C A5 D5 08 9C AF D5 08 4C BC D5 08 FC C8 D5 08 F0 D2 D5 08 60 DE D5 08 7C EC D5 08 08 F6 D5 08

This is just part of the data you are overwriting. Do you know what this is? This a massive pointer table. I am currently looking into what it points to.

You couldn't possibly have tested everything. Also, I have checked my figures. I know all about this table since I am writing a tool to edit it. Turns out, each entry is actually 36 bytes. So, 36 x 25 = 900. That is almost a kilobyte of data that is being overwritten without care. You need to change your tutorial to repoint the table. If you don't it will result in serious consequences to your rom. In fact, right now I am going to go check out what exactly you are overwriting.

What game are you hacking this on?

Oh, I see. I'll try to figure it out when exams over.

That's what I'm doing, you need asm to extend the readable spaces

NO. You don't get it. You are corrupting the rom.

~Jambo51, esteemed ASM hacker:~
Jambo51: it works by pure coincidence
Jambo51: not because his method actually works
Jambo51: like, if you tried to do the same with FR, it would fail completely
Jambo51: I'm guessing Ruby doesn't have the same type of limiter that FR or Emerald do
Jambo51: I 100% agree with your refusal to post it

First, you need to check it on other roms. Then you need to repoint the dex entries. Those "bad" pointer you talk about clearing in your tut? That is data that is used for something!!!!!!!!!!! You are just obliterating it. You can't do that. I am saving hacking by preventing this. Fix your tut and then I will allow it.

No, you don't get it. You just overwrote 500 bytes of data without caring. What if all of the code for the battle tower was in there? Now that is broken and you wouldn't know until you tried to play it and you wouldn't know what caused it. I am an ASM hacker and programmer. I know what data corruption is and I will not allow your tutorial in until you understand what you have done. This is how bugs are born.