I am currently using v3.04, so this may be fixed by now..
I have two aliases set up. One to create a trigger and one to remove it. I have to do it this way, since I need to be able to change the name of my target, but I also need to shut off the trigger fast. Disabling it would possibly work, but then I would still have to edit/remove it manually to change the target.
The first script command sets up the trigger correctly. However, typing the alias to delete it seems to execute the script, but when I look in the triger list, the trigger is still in the list and appears to still be enabled. I am not sure if this is only an artifact though or if the trigger still is active, since in the process of trying to test this the network my mud is on went down. It does appear however that the trigger was never removed.
I have two aliases set up. One to create a trigger and one to remove it. I have to do it this way, since I need to be able to change the name of my target, but I also need to shut off the trigger fast. Disabling it would possibly work, but then I would still have to edit/remove it manually to change the target.
The first script command sets up the trigger correctly. However, typing the alias to delete it seems to execute the script, but when I look in the triger list, the trigger is still in the list and appears to still be enabled. I am not sure if this is only an artifact though or if the trigger still is active, since in the process of trying to test this the network my mud is on went down. It does appear however that the trigger was never removed.