What's the max. supported Cheat Code length?

[CosmoCortney]

Title says all.
I'm creating a cheat code for Wind Waker which contains a sort of RNG and does different modifications depending on what the RNG outputs. So far it's 0x9A0/2464 Bytes long. Enabling the cheat leads to a freeze and Dolphin won't be able to close without the task manager :/
The cheat is going to be about 3 - 4kB long in the end..

[mimimi]

I don't know what's the limit for AR codes, but for gecko codes there's a hard limit of 6KB. And that's for the codehandler and the codes. Check the size of the codehandler.bin file, it should be 4288 bytes, so you can use 1856 bytes for codes.

This limit comes from the fact that the codehandler and the codes at copied to 0x80001800 in memory, and the usable area ends at 0x80003000.

You can increase the number of codes you can use, by using a different codehandler, namely codehandleronly. You can get this from the source code of Gecko OS, Neogamma or various usb loaders. Its size should be 2736 bytes, so you can use 3408 bytes of codes. You need to replace the codehandler.bin with the other one, in the Dolphin installation folder, subfolder Sys.

Right now there's no warning or error when you use too many codes, so you just have to know the limit for now.

[CosmoCortney]

It's formatted as Gecko. The codehandler has 4.288 Bytes indeed. Can't we move it from 80001800 to 817B0000? This is where i've been executing my stuff since I have enough free space there. Gonna test it with the other one now. Hmm, the codehandler has quite a lot of padding (filling with zeros in the end). Can't we delete it to extent the space of codes?
EDIT: using the other codehandler also froze everything. At least I could close the Emulator without task manager.

[mimimi]

Do your codes work on a wii?

The gecko codes support isn't in a good place right now, so it could be a another issue that is unrelated to the number of codes you are using.

And why do you think you can use memory at this random offset?

[CosmoCortney]

Just tested it a bit on a gamecube (just verifying the assembly instruction i've hijacked is always executed).
(to answer the other question) from there I branched to 0x817B0000 because it's always free and offers much more space.
I could also try it as AR code. Early/shorter versions of the code worked fine. It's just a certain amount that freezes everything. So I'm trying to reduce some of the code which reduces the variety but not the amount of effects

[mimimi]

So you are writing asm code into memory? Then you should try flushing the instruction cache, as Dolphin has many issues with that. I *hope* that fixes stuff, but i actually don't know what is broken with the instruction cache.