Quote:
Originally Posted by cogeorge93
The same thing applies for CO binaries. For massive chains of actions, during ages we found a trick that bypasses the limit in a way that the script it's not affected. I personally use "type=1071, param=<Second(s) ActionID>".
Also, you can do action loops.
|
You can bypass the limit in OllyDbg. There's an error message produced when you go over the limit, you can use that error message to easily find the area were it's checking if you go over the 32 action limit an then JMP it.
Why is there a 32 action limit in the first place?