[TQ Binaries] Discussion and documentation

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.

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?

Quote:

Originally Posted by lostsolder05 Why is there a 32 action limit in the first place?

Infinite loops?

Quote:

Originally Posted by lostsolder05 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?

I know, I've done that in the past when I didn't knew about that action type. They made this limit to prevent the server overloading, infinite loops causing the server to lag and crash eventually.

There's loads of error checks in the action handler that will never occur if your actions are correctly formatted, so TQ implementing an action limit doesn't surprise me. You could always raise it to higher if you reeeeally feel you need it.

Quote:

Originally Posted by Lateralus There's loads of error checks in the action handler that will never occur if your actions are correctly formatted, so TQ implementing an action limit doesn't surprise me. You could always raise it to higher if you reeeeally feel you need it.

Yes we've done this in the EO section for when you try to teach a pet a skill you can end up with about 100+ actions in a row, personally though I didn't put it pass 200 actions in case of a loop

I know it's been three years , most anyone is still interested in knowing how cq_action , cq_task , cq_npc actions ? I think I can still be useful for some programmers