Zugg Software :: View topic

Beginner Joined: 09 Nov 2002 Posts: 14

First, I have three packages involved:

carnage.pkg is a module.
main.pkg is a window.
bot.pkg is a window.

I am using this as a trigger command:

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

Make sure that each window has a check next to carnage in the Window Properties. If there's no checkmark there, triggers in the carnage package won't fire in that window.

Beginner Joined: 09 Nov 2002 Posts: 14

Yup, one of the first things I checked. There are several triggers in that package, including one other that's in the same class auto.assist is that fire just fine.

Beginner Joined: 09 Nov 2002 Posts: 14

Okay, updated.. but the issue still persists.

I did realize that I never mentioned I was using beta 3.29...

I realized the original issue I was having was that the trigger would fire in one window, then turn itself off, and since it was in a shared module the trigger wasn't available for the other window to work with. Implementation failure, but easy enough, we just move on to a conditional instead of turning the thing off and on.

Apprentice Joined: 12 Apr 2004 Posts: 134 Location: USA

This may be off base and I'm still new to Cmud code, however I was doing the same sort of thing, sharing triggers between windows; but I think there is an issue with timing. For example if the trigger is called by the line in one window, and called at the same time by the same like in the other window, it already acting due to the first call. In my instance in both windows at the same time I had a trigger to #gag a tells, but it would not gag the second window. After mucking around with various things I simply copied the trigger and placed the clone in the second screen now they both #gag correctly.

Beginner Joined: 09 Nov 2002 Posts: 14

Beginner Joined: 09 Nov 2002 Posts: 14

And, I hate to keep blowing up my own thread... but I also added another trigger to the same class the other two are in. This one triggers off the character's own hits to toggle the inCombat flag as my MUD implements a 3 round lag for using the assist command whether it's successful or not, I don't want the assist trigger firing if someone's already engaged. This also works in both windows:

Apprentice Joined: 12 Apr 2004 Posts: 134 Location: USA

In the second window, the tanks window, does the tank see his own name. in the first window it may say

complex misses ....

But in the tank screen does it also say

complex misses, or maybe you miss. In other words is the key you included in as part of the @tank variable?

Beginner Joined: 09 Nov 2002 Posts: 14

No, he does not. I will frame the situation a little better. There are two windows Main and Bot. In Main is Stasheff, in Bot is Teibidh. My primary MUD has mobs that switch targets fairly regularly, in addition to the fact that I switch off whichever one is tanking to let the other regen, so they need to both be able to assist each other or another character. Here is sample combat output from the Bot window, the one that won't fire, before and after I manually enter Teibidh in to the fight.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Beginner Joined: 09 Nov 2002 Posts: 14

I see the logic there, very straight forward. I have two questions... In your #IF expression you have && is that the equivalent of && or is that something different? Second question: My understanding is that logically your statement and my statement are ... well, identical. Can you offer any ideas as to why this would work and the one I was using wouldn't?

Don't get me wrong, I'll try it this afternoon when i get a chance to play and if it works i"ll mail you a hug... I'm just curious as to why this would work or ... more accurately... why mine wouldn't?

Beginner Joined: 09 Nov 2002 Posts: 14

Okay, I figured out what the problem is, but not an elegant solution... actually, I do know a solution, but I need help getting it working.

The trigger only seems to use the @tank variable from the Main window, even though it will accurately use the @inCombat and @autoAssistEnabled variables from the bot window and, in the action resulting from the trigger, the @tank variable from the bot window...

Main Window:
connected character = Ixythik
@tank=drydd
@autoAssistEnabled=1
@inCombat=0

Bot Window:
connected character = Drydd
@tank=Ixythik
@autoAssistEnabled=1
@inCombat=0

In this scenario Ixythik WILL assist Drydd, but Drydd will NOT assist Ixythik unless I take out the ^ (trigger only on newline) from the beginning of the trigger statement and have ixythik say "drydd hits a" which immediately results in Drydd attempting to assist Ixythik... in other words, the actual trigger statement uses the main window's @tank variable but the action resulting from the trigger uses the correct window's @tank...

Now, if we change it so:

Main Window:
@tank=Ixythik
@autoAssistEnabled=0

Bot Window:
@tank=Drydd
@autoAssistEnabled=1

Okay, two things changed here: In Ixythik's window we have set the @tank variable to Ixythik. He will NEVER see "Ixythik hits..." with this MUD... never. The other thing we did was set the @autoAssistEnabled variable in Ixythik's window to 0, which means that in theory if Ixythik did happen to see "Ixythik hits..." he still wouldn't do anything.

Now, if I have Ixythik hit something as soon as Drydd sees "Ixythik scratches..." he jumps in and assists Ixythik, even though the tank variable in his window is set to Drydd. If they were simply flipped around, though, I could almost understand it... but they're obviously not. If Drydd were using all the variables from Ixythik's window then his autoAssistEnabled would be 0, which means that though the pattern would match the #if expression would be false and no assist command would be issued... I'm thinking bug... but below is the XML for my entire session, it's a work in progress, so don't mind the mess... please let me know if you see anything that explains this behavior...

So, the solution I have in mind is instead of simply calling @tank to call @\main\tank and @\bot\tank. I should be able to use the %window function to put the window name in there, but it doesn't work... What should I type to make @\%window\tank a viable variable name that correctly replaces %window with the name of the window it's in (If that even makes sense...)?

Bot window:

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Beginner Joined: 09 Nov 2002 Posts: 14

And it does work, perfectly. Thank you again, and thank you for the explanation. This will likely prevent many new holes in my wall from head bashing in to it in the future.