Zugg Software :: View topic - Using Gauges and Windows for a health checker....

Newbie Joined: 16 Aug 2007 Posts: 9

I've been fumbling with some triggers that I just can't seem to do what I want. I suppose to start I will list my objective.

I want to take the results of a group display command, have the results captured to either a window or gauge button, or both. I want the gauges to be colorized, updated when i check the group display, and when i click on one of the gauges, it will execute a predetermined action.

Make sense? Let me tell you what I've got now (its a sloppy culmination of several other things I've found)

Posted: Thu Aug 16, 2007 10:13 am

The #gauge command probably isn't the best way to do this - it's intended for creating new gauges and not for updating existing ones. You can't easily update one part of the gauge without updating all parts of the gauge. zMUD really expects you to use variables for the current value of the gauge, which it will then check and update on its own.

So with that said, is there an upper limit to the number of people you can have in a group? I'd create that number of gauges, using variables for the caption and values (and the command, if you want that to change too) and then disable the ones I don't need. Then just use your trigger there to give the variables proper values.

Newbie Joined: 16 Aug 2007 Posts: 9

ok, what i'm probably looking to do is to make a list of #buttons, 13 in all. i haven't done programming in years, so what is the most efficient method to take

Posted: Thu Aug 16, 2007 10:47 am

Gauges will recolour themselves for you. They have the options "Value", "Max" and "Low". There's a Gauge colour, a background colour, and a low colour. When the value falls below the Low value, the gauge will be coloured the Low colour. No need to do it yourself.

You're really expected to make buttons with the GUI in zMUD. It's very difficult to support the many, many options that buttons can have (take a look at the helpfile for the #button command) in the TINTIN-like zScript syntax.

If you need that many buttons, I'd have them as part of a sidebar. Change them to Panel 2 and Right aligned. Colour them however you like, and since they're going to be very similar, you could just copy and paste the first one 12 times and then change the details (variable names etc).

The trouble with that text you just gave is that there's no way for the script to know when the list has finished. It needs to know when the list has ended because there could be any number of people in the group. That said, here's something you can try (or something to give you an idea anyway)

#trig {Your group consists of:} {membercount=1;#loop 13 {#var %concat("Group_",%i) ""};#t+ membertrig}
#cond {some way of knowing the list has ended, possibly your prompt} {#t- membertrig;#loop 13 {#if (@{%concat("Group_",%i)}) {#call %btnenable(%concat("GroupBtn_",%i),1)} {#call %btnenable(%concat("GroupBtn_",%i),0)}

#trig "membertrig" {~(%s%w~) (%d)/(%d) hit, (%d)/100 move (%w)} {#addkey %concat("Group_",@membercount) CurrentHealth %1;#addkey %concat("Group_",@membercount) MaxHealth %2;#addkey %concat("Group_",@membercount) CurrentMove %3;#addkey %concat("Group_",@membercount) Name %4;#add membercount 1} {disable}

In short, this script assumes that your 13 buttons are called GroupBtn_X where X is a number 1-13. It stores the current health, max health, current moves, and name of the group member in data record variables called Group_X. To use those values in the buttons, just use @Group_1.currenthealth, @Group_2.maxhealth, @Group_4.name and so on.

I haven't tested this, but hopefully you understand the idea.

Newbie Joined: 16 Aug 2007 Posts: 9

ok, im gonna take a break from numbers and variables and come back to hit this again in an hour or so, i appreciate the help.

oh, fyi - here is what i see exactly in a group of 2(just for example's sake) before and after i type the 'group' command

< 654h/654H 159v/159V Pos: standing >
<> group

Your group consists of:
( Head) 654/654 hit, 159/159 move Julian
(Front) 435/435 hit, 130/130 move Kwyrl

< 654h/654H 159v/159V Pos: standing >
<>

Posted: Thu Aug 16, 2007 10:58 am

Since your MUD sends a blank line after the list (that's pretty much ideal) you can use the patterns ^$ or $ to match it.

Newbie Joined: 16 Aug 2007 Posts: 9

fyi - i hate the zscript formatting :P its such a pain to debug syntax errors with.

Newbie Joined: 16 Aug 2007 Posts: 9

Ok, I got the first part of your code to work, btw its

Posted: Thu Aug 16, 2007 5:26 pm

Be careful with that first part, you're missing a couple of braces. The #cond command isn't part of the #trig command's script, it's a separate command that creates trigger states. Look it up.

I made a typo with the first #trig command - it needs two more closing braces } right at the end for it to work. Whoops :(

The second is being annoying - the syntax is valid, but it's not working. Just create the trigger manually, give it the ID "membertrig", disable it, and paste in the script. The contents of the script (from addkey %concat() Currenthealth to #add membercount 1) doesn't have any syntax errors when I paste it that way.

Newbie Joined: 16 Aug 2007 Posts: 9

okies status here
pattern