Zugg Software :: View topic - Why does this work as an alias, but it randomly aborts as an event?

Apprentice Joined: 24 Jul 2008 Posts: 109

I did a clean install to see if this got rid of my problem with events randomly aborting, but no dice.

Here is the text of both the event and alias.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Is "queue" and alias, or a mud command? If it is a MUD command you should use #SEND instead of #EXECUTE. If it is an alias we will need the contents of that alias for testing.

Apprentice Joined: 24 Jul 2008 Posts: 109

It's an alias that keeps a queue of commands to send to the MUD because actions have times associated with them:

queue alias:

Apprentice Joined: 24 Jul 2008 Posts: 109

Still have no clue what's causing this... hoping the error messages might provide some sort of hint to someone who knows more than me. Not being able to use events has been a hassle. :(

Enchanter Joined: 09 Sep 2007 Posts: 605

While I can't help you with your problem directly, I want to say several things:
1) There were some problems with #RAISE command, fixed somewhere in May. Maybe not all of them...
2) I've noticed that you have several different issues with your settings (not working gauges, events...) Have you tried export all of your settings to XML and create a new session? May be this will help? One time back it helped me in a very similar situation.

Apprentice Joined: 24 Jul 2008 Posts: 109

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Apprentice Joined: 24 Jul 2008 Posts: 109

Seriously? Whoa, great! I will mess with that as well.

You guys are awesome.

Apprentice Joined: 24 Jul 2008 Posts: 109

Oh, now this is really weird...

I exported to XML. I moved my old session file to another folder, entirely away from CMUD, as a backup. I opened CMUD and deleted the session from my list. Then I recreated it. Then I imported from XML.

Now, before I get to the *really* weird thing, here are a few things that were different than they had been when I imported them. First, I normally have two windows, side by side, above my main session window. One is "top" relative to the main window, and the other is "right" relative to that window. When I imported, that second window was still set to "right" but nothing was in the relative column, so it was just taking up the entire right side. I fixed that real quick and moved on. The second weird thing is two of my buttons on my bottom toolbar had their positions switched. I changed the priority of the second one to come before the first one and moved on.

However, I'm curious... is this just the XML importing/exporting being a little buggy, or is it a sign that my previous session was messed up in some way -- because the buttons had been (apparently) displaying contrary to their priority settings, for example? Or when you import from XML, does it give new priorities?

Anyway, here's the really weird thing. I went and typed in an alias that worked fine before and now it completely froze the program. Happens every time. I wouldn't have figured out *why* if I didn't have a status bar showing me what's in the "command queue" I showed up above (the "queue" alias; the status bar is #SHOW @rtqueue). The alias I typed in happened to start with the very alias I started this thread with, so it's easier for me to explain to you guys what happened.

Basically, when I type in the alias now, it just *spams* the crap out of CMUD on that WHILE loop. It went through and spammed "hum march" and "stop hum" pseudo-infinitely, I guess, and as best I can tell that's what's locking up the program. This means it completely disregarded the #WAITFOR commands.

Does anyone have any idea what this means, or why it's doing that now, or... anything at all about any of this? I'm just more confused than when I started. Exporting and importing seems to have made things far worse.

It's not a huge deal since I can just restore my old session folder, but I'm completely stumped and I just. Cannot. Understand. Why. I keep getting all these weird errors and bugs with CMUD. Any advice, any at all, would be helpful. I don't know what to do anymore. I ran memtest twice, even though I'm not having problems with other programs, because the errors are so weird and random that it seemed RAM could be causing it. No errors at all, though. I uninstalled and reinstalled CMUD twice, no change. I'm running Windows XP if it matters. :-/ At the end of the month I'm going to be using a different computer and I'm curious if I'd have the same problems on it, but my trial will run out before then. I'm really waffling back and forth on whether I should buy the full version since I can't seem to get it to work. On the one hand, it seems like it should be fixable because other people seem to run it fine, and if I could get it to work it does everything I could possibly ask for... but on the other hand, if I can't get it to work reliably, there's no point. To be clear, it's not a knock on the program itself, it just seems like there's some weird issue, maybe with this specific computer or something, that I can't identify. I don't want to use any other client, though. :(

Apprentice Joined: 24 Jul 2008 Posts: 109

Enchanter Joined: 09 Sep 2007 Posts: 605

Apprentice Joined: 24 Jul 2008 Posts: 109

I'm completely open to my scripts having errors in them. It's just that when I post stuff, like the first post here, no one points out that I've done something wrong, and I (obviously) don't see it. It seems to be fine. :-/ I don't get, for example, what would make CMUD skip #WAITFOR commands. Maybe having some weird trigger somewhere would lead to a domino of strange errors? I dunno what else to think. For what it's worth, I've been getting weird errors from the moment I installed CMUD. Maybe one of the very first triggers I made is to blame? Maybe there's some character I should have escaped but didn't, and it works on the surface but not in actuality? I'm really stumped as to what, though. Escaping with tildes seemed to freak things out, so I went and changed any trigger patterns that were at all complicated to REGEX, but that only made things a little more stable, and only in regards to those specific triggers...

It's good to know the XML import is broken and it's not just me. Phew, thank you!

My bad about the #command in the status bar. I hadn't looked at it since the program had just crashed, but you're right, all I have there is "@rtqueue" and it shows up correctly. No #SHOW.

Apprentice Joined: 24 Jul 2008 Posts: 109

Looking at the very first triggers I made, is there anything wrong with these patterns?

, "*"$
chants*:*$
sings*:*$
whispers, "
you, "

For example, even with the $, might those asterisks mess things up? Or do quote marks need an escape and I didn't know? Or do colons? All I have assigned to those triggers is highlight commands, and they highlight lines correctly, but maybe there's more going on beneath the surface. My other early triggers are very basic, no special characters aside from ^ and $.

Wizard Joined: 22 Mar 2007 Posts: 2320

In order to tell whether your code has bugs, we really would need to see the code.

One way to figure out where you may have a problem is to turn off all of your triggers, then turn them on one by one until you start to see problems. Other than that, I don't have enough information.

Apprentice Joined: 24 Jul 2008 Posts: 109

You mean like, all of it? Because I posted the alias above, and the other alias it references. (Not trying to be snarky, just clarifying.)

Posted: Wed Aug 06, 2008 6:18 pm

Any of the wait commands can cause issues as they spawn new threads and then you have to be certain you know what you are doing and you're not going to try to set the same variable in different threads which can become easy if you have a couple of aliases setting the variable one of which also contains a wait command.

Ultimately if you want us to find out where something is going wrong then you need to provide everything that is related to what you are trying to achieve. So all the aliases, triggers, variables etc and really the easiest way of doing that is to export it all via xml and paste it here. We should then be able recreate what you have and see what is going wrong. Sample output would help for us to test the settings.

Apprentice Joined: 24 Jul 2008 Posts: 109

Ah... well, I know that I have only the one thread dealing with the vocset variable, for example, above. None of my other scripts have anything to do with it. But I get what you mean.

I still think something is crazy with my computer and CMUD, but FWIW here's all the things related to this particular event.

Here is the commandqueue_handler class. Since actions in the game take time, and no other actions can be completed during that time, this queues them up and sends one ever time the is no more wait time. Nearly every command I want to send to the game must go through this class. If something is wrong here, it could very well explain why so much stuff is messed up.

Posted: Tue Aug 12, 2008 5:08 pm

Btw, you don't need to use #EXECUTE all of the time to execute aliases. You only need to use #EXECUTE when you have a variable or expression that contains the command you want to execute.

For example, if your alias is called "emptyqueue" then you don't need to do:

#EXECUTE emptyqueue

Just doing

emptyqueue

works just fine. The only time you need to use #EXECUTE is if the command is stored in a variable, like:

Apprentice Joined: 24 Jul 2008 Posts: 109

Ohhh, thank you! I will give that a shot!

Enchanter Joined: 09 Sep 2007 Posts: 605

Nattie... If I remember it right, when I ran your script on my machine last week, after your "emptyqueue" alias CMUD show 3 threads are running. Is this what you think CMUD should do? Check your threading logic once again, may be this will help you.

Apprentice Joined: 24 Jul 2008 Posts: 109

Alright, I changed this to not have #EXECUTEs, so now it is:

Apprentice Joined: 24 Jul 2008 Posts: 109

Posted: Tue Aug 12, 2008 7:28 pm

I'm not getting your "argument still on stack error" here, so maybe I'm not testing it correctly. Here is what I did:

1) Run CMUD and close the Session window. Open Settings Editor
2) Copy the full "vocals" class in the post above. Paste it into NotePad and change the < character to a & lt ; (without the spaces).
3) Copy the edited Notepad text and then right-click on the Tree view in the settings editor and select Paste.
4) Copy the full "commandqueue_handler" class in the post above. Right-click on the tree and select Paste
5) Find the "zvocals" alias and then copy/paste your new code (without the #execute) into the alias and click Save Changes.
6) Select New/Event and enter "zevent" as the name. Then paste the same code into the event and click Save Changes.

OK, now on the command line, if I type:

zvocals

then it displays:

stop hum
hum march

with a small delay between them. If I type:

#RAISE zevent

then it also displays the same text with the same small delay. So I don't get any error from this.

My guess is that some other script is running that I am not able to test because I'm not connected to your MUD. Try running the Script Debugger window and see what script is running right before the "argument still on stack" error is shown.