Zugg Software :: View topic - [1.10] #ALARM triggers in seperate packages

Wanderer Joined: 07 Oct 2001 Posts: 71

I am still having a lot of the same troubles with Alarms created in seperate packages not functioning at all.

Alarms created in a seperate package are still not functioning for me, while alarms created in the session window work perfectly.

If you create a non functioning Alarm in a seperate enabled published package, and dragging it into the session window, it will still fail to function, until you close, reopen cmud, and connect to the session.

Posted: Sat Oct 14, 2006 6:17 am

You'll have to give me the exact step by step method you are using to create the package and the alarm.

Here is what I did:

1) Press ESC to close the session selection window
2) Click Settings to open the settings editor
3) Select File/New Package. Entered the name Test
4) Select New/Trigger. Entered +5 for the pattern and "It works" for the script. Then selected Alarm from the Type selection at the bottom
5) Clicked Save Changes and waited
6) 5 seconds later, it displayed "It works" in the main window.

So it seems to be fine here.

Wanderer Joined: 07 Oct 2001 Posts: 71

Followed your steps exactly. Here's a screen shot as well. As you can see the 10 second alarm in the session window has fired multiple times, while the 3 second alarm in the seperate package has not fired once.

This is a brand new clean install of cmud, so I'm really stuck on what the problem could be.

Wanderer Joined: 07 Oct 2001 Posts: 71

So I uninstalled cmud, rebooted my machine, reinstalled 1.10 - just to make sure.

Played around with it some more, and still could not get an alarm in a seperate package to work correctly. Here are some other abnormal things that I was experiencing.

If I created an alarm in a seperate package "Test", it was non-functional, if I dragged the alarm into the session window settings, it remained non-functional.

However, if I created an alarm in the session window, it function perfectly; if I then dragged this alarm from the session window into the package, the alarm continued to function propperly.

So now I'm even more confused on where the hang up is coming from.

Posted: Sat Oct 14, 2006 5:48 pm

Try using +3 instead of -3. -3 is for the actual MUD connection time, and your external package isn't attached to any particular MUD connection. In other words, imagine that you have multiple windows connected to multiple MUDs. Maybe some windows are connected and others are disconnected. If you have an alarm in a separate package, then which connection does it run on?

Anyway, try using +3 and see if that makes any difference.

Wanderer Joined: 07 Oct 2001 Posts: 71

Ok yes that was what my problem was with the Alarms in seperate packages. So my next question, is... is there another syntax I can use that will loop an alarm (like the -3) in a seperate package? Or do I just create a new alarm at the end of the alarm?

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

For alarms

+ is a one time alarm
- Is fired after x connection time
* is fired every x time
and an alarm without a symbol is fired AT that time

So you want #Alarm test {*3} {#ECHO go}