Zugg Software :: View topic

Beginner Joined: 08 Jan 2006 Posts: 13

ERROR: argument still on stack: 0

I get it twice when I hit this macro

Posted: Fri Nov 12, 2010 2:52 pm

Missari you're going to need to give additional information here. You said you get this error, when you hit the macro but you have not told us what key the macro is mapped to. You reference a "function up top" but you don't mention what that function is. You also reference several variables in your macro code but you do not provide values for those variables. Without that information, there is little that can be done to assist you.

Please provide this information so we can take a closer look.

Beginner Joined: 08 Jan 2006 Posts: 13

I'm sorry, I thought it was obvious that the macro was the long code box in my original post. It's mean to check the variable "toxtype" and send a string similar to 'envenom dhurive with x;envenom dhurive with x' to the mud, change the toxtype variable to a new value so that the next time I use it it does something different and finally run the alias 'dhuriver' to choose which attack string to send to the mud.

The function is !@i( "prone") and runs the script in the second code box. It's just a shortcut for %ismember, because I'm lazy.

The sync variable is '1' when I'm running the macro, the function returns '1', it sends the wipe dhurive string, runs the #SWITCHs and sends the envenom string, then gives that error before finally running the alias at the bottom.

I was mistaken when I said 'macro' the macro(Numpad key 0) uses the alias for which the code is above.

Beginner Joined: 08 Jan 2006 Posts: 13

So, the issue was at the very end of the script I was using sync=0 to set sync to 0 to prevent spamming, I changed this to #var sync 0 and the error goes away.

Edit: And the TRUE issue was that there were 2 extra spaces in front of sync=0, I deleted these spaces and sync=0 worked just as error free as #var sync 0.