Zugg Software :: View topic

Wanderer Joined: 14 Jul 2004 Posts: 83

I've been giving myself a headache trying to figure this out and I'm beginning to think it's a lack of caffiene as it surely wouldn't be a lack of brain power. No sirree.

What I'm trying to do is to use an alias to create a variable then set a trigger to write information into that new variable. Here's what I have so far:

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

At this point, it's probably just better overall if you simply describe the task you want to do (the larger one in which this alias is supposed to be a part of.)

1)#trigger shouldn't even be in the alias, since it creates a permanent setting every time you run the alias (that is, if you run the alias 20 times then you get 20 identical triggers)

2)why are you even considering a renaming?

3)what the heck are you doing with tempvar1?

Wanderer Joined: 14 Jul 2004 Posts: 83

The mud I play on has a gating system with complex keys to it. To learn the key, you have to study the room. To be able to use the key, you either have to keep an outside file with them and cut and paste them into the command line or save them as variables. I prefer the latter. It's much quicker. I attempted simply having the Key is: portion set the variable to the name recorded now as tempvar1 and the key itself (*) to %2

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

It looks like you would be better off using database variables for this. Then you could have key value pairs corresponding to room name.

#alias findkey {study;roomname=%1;#T+ studyT}
#trigger "studyT" {Key is: (*)} {#addkey portalkeys {@roomname=%1};#T- studyT}

Then you could access your keys later. Something like this.

#alias gateto {open gate to %1 using @portalkkeys.%1}

Posted: Tue Mar 27, 2007 6:04 am

I believe there's a bug with rename anyway where settings that involve the newly-renamed setting aren't recompiled to reflect the new name. Until something forces them to recompile, they won't work.