Zugg Software :: View topic - One prompt to rule them all! (multi windows)

Apprentice Joined: 26 Aug 2009 Posts: 141

Hi, I have the below in a .pkg all characters can see. If I separate each one "Sutex" "Halix" "Zarlix" into their own windows/pkg it works.
But trying to see if its possible to have an "all in one"

This is my effort so far. Tab lost with the correct syntax, how to get it to read the prompt and associated it with the name of the window, either "Sutex" "Halix" "Zarlix"
I have a group trigger that captures all the max values and names which is placed into a variable database, that's the @Sutex.maxhp you see and that works great.

This is the prompt trigger that is always displayed (%d)hp (%d)m (%d)mv > the below code is set too.

Adept Joined: 18 Jun 2019 Posts: 279

So it is the same code but for different chars.

Why not SWITCH?

("sutek") {$char="sutek";set more sutek stuff}
("halix") {$char="halix"; set more halix stuff}
("zartix") {$char="zartix" set more zartix stuff}

do $char
show ${char}vars
${char}hp=%1
${char}mn=%2
${char}mv=%3

etc

Why SAY and not WIN?

Plus, it is likely that if you don't qualify the hp mn mv vars at the top you are probably creating issues.
If you try

class/hp=value
class/mn=value
class/mv=value

...and you can SWITCH the hp_precentage also
#LOCAL $hurt_text
SWITCH (@hp_pct)
(@hp_pct<=20) {$hurt_text="dying"}
(@hp_pct<=60) {$hurt_text="hurting"}
(@hp_pct<=90) {$hurt_text="wounded"}
etc

#SAY "WHAT!"@heal_member "is" $hurt_text

I am guessing you can also do {$hurt_text=%ansi(blah,blah)}

Apprentice Joined: 09 Apr 2008 Posts: 168

also, and I think Shalimar would agree.

use ()'s in your #IF's
#if (@hp_difference<@temp_hp) {temp_hp=@hp_difference

#MATH can be removed entirely
hp_difference = (@Sutex.hp - @Sutex.maxhp)

Posted: Fri Mar 19, 2021 12:29 pm

No need for a switch when you have %window (named for the char) available.

All the stuff that needs to be exclusive to the character can be shunted off like so:

#EXECWIN %window {
#ADDKEY %window hp %1
#ADDKEY %window ma %2
#ADDKEY %window mv %3
hp_difference=(%db(@{%window},hp) - %db(@{%window},maxhp))
}

Apprentice Joined: 26 Aug 2009 Posts: 141

Apprentice Joined: 26 Aug 2009 Posts: 141

Apprentice Joined: 26 Aug 2009 Posts: 141

With the editor in CMUD this complied fired got output to the screen

Apprentice Joined: 26 Aug 2009 Posts: 141

Cant get it to stop looping and the values don't work, not working as intended I need to add %ismember to pull the correct Name out of the @heal_member too.

This fires on the normal prompt, suppose too, if! hurt dying etc.

#IF (%window = "Sutex") {
Sutex.hp = %1
Sutex.maxhp = %2
Sutex.ma = %3
Sutex.maxma = %4
}
#EXECWIN %window {"Sutex"}
#ADDKEY %window hp %1
#ADDKEY %window ma %2
#ADDKEY %window mv %3

hp_percentage (@Sutex.hp*100/@Sutex.maxhp)
#VAR heal_member Sutex
#IF (@hp_percentage<21) {
hp_difference=(%db( @{%window}, Sutex.hp) - %db( @{%window}, Sutex.maxhp))
#SAY {"Health Difference" %ansi( bold, white)~[ %ansi( bold, green)-@hp_difference %ansi( bold, white)~| %ansi( bold, cyan)@heal_member is %ansi( bold, blink, red)dying %ansi( bold, white)~| %ansi( bold, blink, red)@hp_percentage %ansi( bold, green)~% %ansi( bold, white)~]}
#abort 1}

#if (@hp_percentage<41) {
hp_difference=(%db( @{%window}, Sutex.hp) - %db( @{%window}, Sutex.maxhp))
#SAY {"Health Difference" %ansi( bold, white)~[ %ansi( bold, green)-@hp_difference %ansi( bold, white)~| %ansi( bold, cyan)@heal_member is %ansi( bold, red)hurting %ansi( bold, white)~| %ansi( bold, blink, red)@hp_percentage%ansi( bold, green)~% %ansi( bold, white)~]}
#abort 1}

#if (@hp_percentage<61) {
hp_difference=(%db( @{%window}, Sutex.hp) - %db( @{%window}, Sutex.maxhp))
#SAY {"Health Difference" %ansi( bold, white)~[ %ansi( bold, green)-@hp_difference %ansi( bold, white)~| %ansi( bold, cyan)@heal_member is %ansi( bold, blue)wounded %ansi( bold, white)~| %ansi( bold, blink, red)@hp_percentage %ansi( bold, green)~% %ansi( bold, white)~]}
#abort 1}

#if (@hp_percentage<81) {
hp_difference=(%db( @{%window}, Sutex.hp) - %db( @{%window}, Sutex.maxhp))
#SAY {"Health Difference" %ansi( bold, white)~[ %ansi( bold, green)-@hp_difference %ansi( bold, white)~| %ansi( bold, cyan)@heal_member is %ansi( bold, blue)small wounds %ansi( bold, white)~| %ansi( bold, blink, red)@hp_percentage %ansi( bold, green)~% %ansi( bold, white)~]}
#abort 1}

This is my Group trigger which get all the high values puts then in a data base 'Everyone can see'

#IF (%10 = "Sutex") {Sutex.hp = %1;Sutex.maxhp = %2;Sutex.ma = %3;Sutex.maxma = %4}
#IF (%10 = "Halix") {Halix.hp = %1;Halix.maxhp = %2;Halix.ma = %3;Halix.maxma = %4}
#IF (%10 = "Zarlix") {Zarlix.hp = %1;Zarlix.maxhp = %2;Zarlix.ma = %3;Zarlix.maxma = %4}
#IF (%10 = "Karlix") {Karlix.hp = %1;Karlix.maxhp = %2;Karlix.ma = %3;Karlix.maxma = %4}

Posted: Mon Mar 22, 2021 11:02 am

You aren't doing it like in my example.

You abbreviated it to:

#EXECWIN %window {"Sutex"}

Yet %window is already Sutex (or one of the other char names) so unless you have a self-named alias, this does nothing.

--------------

In the same vein
%db( @{%window}, Sutex.hp)
should be
%db( @{%window}, hp)
because %window -IS- Sutex, you are trying to reference an @sutex.sutex.hp

---------------

Moving on to your group example, since you want everyone to have access to the data... move all the individual member data into a collective of group data.

$member=%db(@groupStats, %10)
#ADDKEY $member hp %1
#ADDKEY $member maxHp %2
#ADDKEY $member ma %3
#ADDKEY $member maxMa %4
#ADDKEY groupStats %10 $member

The only drawback of putting this data into a database is that gauges do not update properly. Gauges really like stand-alone variables.

Apprentice Joined: 26 Aug 2009 Posts: 141

Will read through more carefully what your suggesting thanks. below is to clarify my set up

.......................

My group trigger is in the 'Everyone can see' it controls updates my status buttons health mana, with their Max levels

~[{%s|}(%d)~/(%d){%s|}~]~[{%s|}(%d)~/(%d){%s|}~]~[{%s|}(%d)~/(%d){%s|}~] ~[{%s|}(%n)~] ~[{%s|}(%d)~] ~[{%s|}(%d) %w~] (%w)

#IF (%10 = "Sutex") {Sutex.hp = %1;Sutex.maxhp = %2;Sutex.ma = %3;Sutex.maxma = %4}
#IF (%10 = "Halix") {Halix.hp = %1;Halix.maxhp = %2;Halix.ma = %3;Halix.maxma = %4}
#IF (%10 = "Zarlix") {Zarlix.hp = %1;Zarlix.maxhp = %2;Zarlix.ma = %3;Zarlix.maxma = %4}
#IF (%10 = "Karlix") {Karlix.hp = %1;Karlix.maxhp = %2;Karlix.ma = %3;Karlix.maxma = %4}

The above trigger. Sets up a data based Variables Sutex, Halix, Zarlix, Karlix, in the 'Everyone.pkg.

Then My prompt displayed (%d)hp (%d)m (%d)mv > is in each Charterers .pkg * not shared*, and uses the HP and ma, *current vaules* for my buttons health mana bars on my status bar

All this works really well.

Posted: Mon Mar 22, 2021 12:38 pm

The trigger defining the variables could/should be in the shared package.
Just don't put variables you expect to update in a shared package, or everyone is trying to overwrite the shared data instead of making local data.
New variables are always defined in the root directory of the local session/window.

Apprentice Joined: 26 Aug 2009 Posts: 141

ok; thanks :)

Apprentice Joined: 26 Aug 2009 Posts: 141

Posted: Tue Mar 23, 2021 3:29 am

For the purpose of sharing vitals, it has to be in the shared package.
My @groupstats example was just trying to avoid the awkwardness of @{%window}.

Adept Joined: 18 Jun 2019 Posts: 279

This may be one of those things where DOCUMENTATION would be worthwhile. Should we get up a petition? Should we call the Queen for more paperwork?

However, I think, in the ADVANCED settings for the window/package, if you add the packages (accessible to other windows/packages) where the data is located it seems like that should do it...or you could qualify the data with the parent class of the variables.

I discovered that thing with %dbvar and gauges....it the same for buttons... because the data is not updated until you either click the button...or, if you go to the editor, click on the dbvar so that it gets updated.

Posted: Wed Mar 24, 2021 5:17 am

I did mention on at least one of these threads that @dbVars don't play nice with gauges (which are technically buttons).
But it's also a simple fix (relatively).
Set the buttons/gauges to use a static variable (@hp, @hpMax, etc).
Then edit your prompt trigger to save the data to both the local session variables and the shared session @dbVar, for the odd situation when that is needed.

Apprentice Joined: 26 Aug 2009 Posts: 141