That reminds me, I couldn't find much straight forward info on the different trigger types and what situations they'd each be best for in the manual.

And personally I find the latter more legible.

ctrl+f the manual for "begin of line matching →", you'll see it there. and sure, whatever you like - the flexibility in organization is nice.

Yes, sorry. I explained that badly and wrote the wrong console name first time. Still, the funny spacing was there in both. It's fixed now, I added a setMiniconsoleFontSize("battcap",8) to the console creation script which somehow changed the font to something monospaced and got rid of the spaces when the font colour changed.

I don't understand why, but it works now so I'm happy.

I apologize if this is a bit off topic, but I'm not able to start a new thread for this question. I am absolutely in love with the world of Lusternia. It is thick and juicy and I want to bite into it so bad, but as I read over the forums and notice from experience how mind-numbingly crowded the affliction/cures list is, I realize that in order to be competitive I would need to purchase 3rd party software (essentially) to play a major part of the game for me. What kind of game design would almost make this necessary? But I'll try to step back and not assume it's necessary before asking pointedly. Would I seriously gimp myself without a trigger system? Thank you for any feedback.

The question is: do you want to be a combatant?

There will be no gimpage if all you're going to do is float around and quest and occasionally hit something.

There will be minor gimpage if all you're going to do is bash or influence; an autosipper and assisted bashing triggers make you a lot more productive than if you full manual.

There will be major gimpage if you plan to start fighting.

How do you make number print only the integer, with no decimals?

math.floor() is the function I think you're looking for.

Yep, thanks!

math.floor() rounds down to the nearest integer, while math.ceil() rounds up. Thought it best to mention that.

Is there a way to update the text on a button on the fly?

I don't think you can do that yet, unfortunately. Part of the reason I stick to labels.

This is a stupidly silly question, but having used Ubuntu for the past several months, I haven't a clue where to find the latest Windows Mudlet update. I looked on the website, but I believe there have been updates since 1.1.1? I'm not sure though...

Derp, thank you.

I'm trying to do a simple countdown timer for my bardsong. Ideally it will echo the time remaining every 30s, with reminders at 20s and 10s remaining to refrain. The problem is I don't know a whole lot of coding, or the particulars of Lua, so I'm not sure if there's an easy function to call.

My initial idea to take a variable, songTime, and have it set at 110s (current song length). Something would decrement it each second, while a separate timer would run and every 30s echo the current value of songTime. When it was less than 30 it would disable the timer, then do a special echo at 20s and 10s. The idea was that since it was controlled by a variable, any time I played the next stanza or refrained, I'd simply reset songTime and everything would keep working (the timer itself might proc at odd times, but I'd live. I'm honestly more interested in the refrain messages than anything).

But! Not only am I not sure that's the ideal way to do it, I don't know what functions to call to accomplish the decrement and value check. Bummer.

I tried another method, which seems even more labourous. Rather than a countdown, playing a stanza or refraining would call a separate function that would set up tempTimers for every 30s, as well as 20s and 10s remaining. Which works wonderfully, as long as I have no intention of actually playing more than 1 stanza or refraining. For this to work I need to build another function specifically to kill the tempTimers. So my general idea looks something like

function songTimerOn()
tempTimer(30s, ])
tempTimerMustDie1 = tempTimerID
end

function songTimerKill()
killTimer(tempTimerMustDie1)
end

using either my $song or $refrain alias (or other triggers, as need to keep the timer correct) would first try to kill any timers currently up, and then would create a new set of timers and log their ID to repeat the cycle forever. The problem is i have NO IDEA how to capture the tempTimer ID. The manual says the function returns the ID as a string, but how do i get it, store it, use it later?

I'm probably going about this completely wrongly, but such is novicehood. I am trying to learn, though, so I'd appreciate advice on how to make either or both of those ideas work, as well as ideas on the simple solution that I'm too unknowledgable to see. Thanks.

Some rather awesome person put the framework for animated timers on Aetolia's forums. I use this for my song countdown.
It is Cantor specific, so a few bits would have to come out, though. Let me know if this interests you and I will provide the specific code for the songs.

You're almost there Stratas. Here is what I have. My refraining is actually a little more complex because I have multiple songs (so it works out which song I'm playing and enables/disables separate triggers accordingly) - but I've cut that out for just the basic refraining. This does NOT echo anything like you wanted, but it -does- autorefrain for you. Especially nice if you don't have 8 minute songs

This is the trigger that makes the timer -

Trigger line:

Script:


As you can see it's set up to use M&M's do system. There is no reason that you couldn't just have send("perform refrain yoursong") instead.

Obviously that fires off song status. Therefore I have another trigger which on the last line of my song automatically sends through songstatus. So literally have a beginning of line substring for the final line of your song (for me it's "And thrust me into caverns deep) then have send("songstatus") as the script text.

Finally, to stop it refraining on and on when you've sustained, have a trigger for the sustaining line (You slow the playing of your instrument) set to killTimer(songtimer)

If any of that is confusing ask me IG. It might not be the best way to do things but it works for me Other people might know how to get the echoes you want at certain time intervals.

Note: You do not have to escape commas in mudlet regex triggers.

Thanks Tacita. I've got that running and it seems to work pretty well. It also helped solve my "how do I capture a tempTimer ID" question, which will surely be useful at some point.