|
Takashi Beginner
Joined: 19 Feb 2004 Posts: 14 Location: USA
|
Posted: Tue Feb 24, 2004 8:03 am
Checklists possible? |
Hello again, this time i think i have a rather simple question, not a whole script. What i want to do is as follows:
On my current mud, i have about 4 characters i commonly log in as. These characters all use the same triggers, but this brings up problems and conflictions within them. All i want to do, is when zMUD links to the MUD is have a list of character names pop up in a second window. for instance:
Takashi---Log in
Rawh------Log in
Axis------Log in
Spiral----Log in
Something that looks like that would be nice if its possible, the words 'log in' being buttons that lead to the next menu. The next menu I would specialize for each character, and I was wondering if its possible to do a sort of checklist for what you want on or not.. for instance:
Turn on joiners? [Check]
Turn on auto-running scripts? [Un-checked]
etc, etc, etc.
The reason i want this checklist type thing is because I will have maybe 15, 20 things on this checklist. I know a #YESNO is possible to use but i would like to be able to look at them all at the same time. My one purpose of all of this is just to cut down on spam, and my constant changing of settings with aliases or just manually. Again, because so many things conflict, I'm running out of alias names!
I would greatly appreciate some instruction on this matter, weather its just directing me to a helpfile or getting me started writing what i need.
Thanks! |
|
|
|
Charbal GURU
Joined: 15 Jun 2001 Posts: 654 Location: USA
|
Posted: Tue Feb 24, 2004 10:36 am |
You might check out the #PICK command and %pick function. For the initial character selection, you'd want to specify the "o:1" argument to limit to to selecting only one (the default is to allow more than one thing to be selected):
#PICK {p:Select a character:} {o:1} {Takashi:Enable Takashi settings} {Rawh:Enable Rawh settings} {Axis:Enable Axis settings} {Spiral:Enable Spiral settings}
The italicized portions would be replaced by whatever code was necessary to enable the respective settings. For the next menu, the best thing to do might be to organize each setting into its own class folder and turn them all off (you can set them to automatically be disabled at connect if you want). Then use something like:
#PICK {p:Select specializations:} {*Turn on joiners:#T+ Joiners} {Turn on auto-running scripts:#T+ AutoRun}
That should enable the classes for the options you select. Build onto this list in the same way, using * to denote things that should be selected by default.
I hope that helps. |
|
|
|
Serentus Apprentice
Joined: 28 Sep 2001 Posts: 103 Location: USA
|
Posted: Tue Feb 24, 2004 11:00 am |
Another suggestion is to use buttons and put them in class that you turn on and off.
for example clicking the Log-in button for Takashi would #T+ TakashiCheckList where the class TakashiCheckList would have buttons for 'Turn on joiners' and 'turn on auto-running scripts' and class RawhCheckList would have other checklist buttons. I guess you would also need a 'done' button to use once you had selected all the options you wanted.
I used a system like this for managing skills and equipment between two characters that shared the same settings. |
|
|
|
Takashi Beginner
Joined: 19 Feb 2004 Posts: 14 Location: USA
|
Posted: Wed Feb 25, 2004 3:42 am |
Much thanks, I'll try this out and see if i can get it to work
:) |
|
|
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|