Yes, I'm hoping the same thing. I really appreciate you trying to help me work it out though.

All I know is that something bad is happening in this stretch of code. It should never try to smoke myrtle.

You eat a horehound blossom.
Prudence rules your psyche once again.
2788h, 3603m, 3823e, 6p, 14830en, 19439w exkdb-
Zacc's eyes lose their focus suddenly.
2788h, 3603m, 3823e, 6p, 14830en, 19439w exkdb-

Dregar's aura of weapons rebounding disappears.
Dregar cracks a battered tahto staff precisely into your right arm, causing
smoke 145539

The problem, I think, is that your prompt trigger is set to fire on GA/EOR (nocr|prompt options) instead of CR/LF. zMUD has this long standing bug where it doesn't always fire prompt triggers correctly. You'll notice that your debug numbers aren't echo'd after you cure your recklessness. I'm guessing that you have some prompt failsafes for tracking things, but at any rate, you should change your prompt to add the linebreak and fire on newline only.

I have a feeling that's going to break a lot of things for me. heheh. But no matter! At least there is a solution, I don't care about a long debugging time as long as it's fixable. I used to have a linebreak, but I didn't like it because it made my screen more spammy with all the blank lines. guess I'll turn up my resolution again.

How would you do this exactly? I know you can add in the linebreak within Lusternia, but how do I set up my prompt trigger to only fire on the newline? Would I just cut everything in my curren't prompt trigger, then create a new state, and paste it in there? But what would the pattern for this new state be, since it's just a blank line.

Would I just use something like "%s" to account for the whitespace?

And thanks for the help, I was hoping you would have replied to this by the time I woke up. heheh.

In the game (which I'm sure you already know): CONFIG PROMPT ADD LINEBREAK

In the trigger: check "Trigger on Newline" and uncheck "Trigger on Prompt"

In a scripted trigger, such as in my combat system: #TRIGGER {^prompt pattern here} {code here} instead of #TRIGGER {^prompt pattern here} {code here} "" {nocr|prompt}

Alright, thanks, I got that done. : )

A couple more questions:

1. Below is what my prompt looks like now. I guess there is no way for me to get that information back out to the side of my prompt? I see a lot of people who have their information being printed out to the side, is there no way for me to accurately do that?
3342h, 3229m, 2712e, 10p, 14830en, 19510w exdb-
1 1 1 1 0

2. I have an alias that uses the %line2 function to check to see if the previous line was a prompt. This is very important to my how my system works. Will doing %line3 skip the newline and catch the third line back?

3. It seems odd I'm having to do this. Does Palisade have to do prompt things this way in order to be accurate? Also, does changing my promptline to work like this somehow solve the problem of my smoking myrtle while off herbbalance? It looks like all it's going to do for me is print the information correctly.

And thanks again, I appreciate the help.

1. Look into using #PSUB instead of #SAYP (or whatever you're using now).

2. Using the %line variables is a bad idea, in my opinion. Palisade doesn't use anything like this. I set and unset flags to track important lines or just build multi-state triggers to catch the lines in the right order. One key thing to note about zMUD is that anything you echo from your scripts counts as a line in the trigger line counting (for the "within n lines" or %line stuff).

3. Without knowing exactly how you're tracking your balances, I can't say if this will fix your problems with premature herb usage. I can tell you that it'll make your prompt triggers 100% reliable, and that can't be a bad thing.