Zugg Software :: View topic

Apprentice Joined: 10 May 2011 Posts: 111

Hey guys,

I have a setup that tracks my subdued mobs by counting down a variable on a gauge. Each mob has a separate gauge. In order to save space, I'm trying to set it up so that when the countdown expires, the gauge fades out and the next closest-to-0 gauge takes it place. Kind of like cooldown bars from WoW or any other MMO. Code for gauge attached below.

Wizard Joined: 22 Mar 2007 Posts: 2320

To make it disappear, simply disable it with the #T- command. One way would be to have an Expression trigger (a trigger which fires when a specific expression is TRUE) which tests whether @TaggeCD=0. Something like:

Apprentice Joined: 10 May 2011 Posts: 111

Rahab,

Thanks for the info!

The first portion worked like a charm! For anyone else wondering, the trigger I used to enable the gauge back with the #T+ was the original trigger that sets off the gauge countdown. =)

For the second portion, inserting that code turns it into MM:SS format, but will read 0:32 instead of 5:32 (minutes are not showing while seconds are, and accurately loop from 59-0. Any idea on this fix for the minutes?

Thanks!

Posted: Wed May 11, 2011 2:42 pm

Tagge Subdue: %format("&d:&02d", (@TaggeCD/60), %mod(@TaggeCD,60))

The brackets are required around the expression to force the calculation otherwise it just ends up as a string like 600/60 for instance.

Apprentice Joined: 10 May 2011 Posts: 111

Awesome! Working as described! =)

Another question:

I am having the gauges line the side of the screen and count down delays.
I want them to appear in order of shortest delay until longest delay. Is there a way to do this? Perhaps some trigger to sort gauge priority on time left on each variable?

Wizard Joined: 22 Mar 2007 Posts: 2320

You can change the priority of a setting with the %priority() function.

That's actually pretty cool--I hadn't noticed that until I went checkin the docs just now.

Apprentice Joined: 10 May 2011 Posts: 111

Can you give me a code example of this please? My head takes a minute to wrap around code like this. =)

For example, if I have Gauge1 (time controlled by VariableA) and Gauge2 (time controlled by VariableB). How would I make it to display whichever gauge is ending soonest?

Thanks!

Wizard Joined: 22 Mar 2007 Posts: 2320

Let's do this in a more general way, so that you can sort any number of gauges by time remaining. Let us assume that the variable @GaugeList contains a database matching the names of all the gauges to the related time-remaining variable, something like: "Gauge1=VariableA|Gauge2=VariableB|Gauge3=VariableC". The following would be a very crude way of sorting the gauges--a much better sorting routine could be designed. This is to give you an idea how it could be done.

Apprentice Joined: 10 May 2011 Posts: 111

Okay, so, I need to make a Variable called @gaugelist, and have the gauge names equaling the variables that determine their countdown. The code you posted, where am I supposed to put it?

Wizard Joined: 22 Mar 2007 Posts: 2320

That was one example of how you could do it. There are hundreds of ways you could do it. I don't know how you currently have your triggers and buttons set up. This was intended to show you the principles so that you could figure out how to use it yourself. Without a whole lot more information about your triggers and buttons, we simply cannot tell you how to do this for your case.

You have misunderstood the @GaugeList variable I described above. As I described it, @Gaugelist contains _both_ the name of the gauge _and_ the name of the variable which is associated with that gauge. So, if Gauge1 is based on VariableA, and Gauge2 is based on VariableB, and Gauge3 is based on VariableC, then you could have:
@GaugeList = {Gauge1=VariableA|Gauge2=VariableB|Gauge3=VariableC}

This is called a database variable, where Gauge1, Gauge2, and Gauge3 are the keys, and VariableA, VariableB, and VariableC are the values of those keys. You can use the %db function to find the value associated with a key, or use the syntax @variablename.keyname, as I do above. There are numerous other functions you can apply to database variables as well.

You don't have to do this with a database variable--that is just one possible way to do it. However you do it, you somehow need to know the names of the gauges and the variables associated with those gauges.

Where are you supposed to use it? Again, that depends on all the rest of your code. I have no idea how you are setting the countdowns on your gauges. Perhaps you could put this code into whatever trigger you are using to set the initial countdown values. Or perhaps you need to do it some other way.

Apprentice Joined: 10 May 2011 Posts: 111

Thank you for all of the info. I'm trying to learn as we patch along here... Here's a sample of a gauge setup for me.

Wizard Joined: 22 Mar 2007 Posts: 2320

Okay, that looks good. Straightforward setup. You could probably just insert the code I put above in the beginning of the "You create and position..." trigger, but since I expect you have a lot of triggers like this, it will be easier if you don't have to put this into every single one.

So, create an alias, maybe named SortGauges. Put my code into SortGauges. In the "You create and position..." trigger (and every similar trigger for the other gauges), add a line with the command SortGauges. Then, all you have to do is create a new variable, listing every gauge and it's variable:

Apprentice Joined: 10 May 2011 Posts: 111

Rahab,

Sorry for the late reply. Got it working like a champ! Thank you so much!