I am looking for an auto meld code to set up my demesne automaticly like i had for zmud. I also don't know how to import it from Cmud as a TXT file otherwise id do that.

Mechanicsforumplz?

aquacast blah blah blah
#alarm +10 {aquacast blah blah}
#alarm +20 {aquacast blah blah blah}
#alarm +30 {aquacast yadda yadda}


That's what I used.

^That's basically it, just hope you don't get ganked in the middle of it or anything.

Except pros do:

#ALIAS kdem {#VAR autodemesne 0}
#ALIAS adem {#VAR autodemesne 1;DEMESNE EFFECT 1;#ALARM +9.75 {
#IF (@autodemesne=1) {DEMESNE EFFECT 2;#ALARM +9.75
#IF (@autodemesne=1) {DEMESNE EFFECT 3;#ALARM +9.75
#IF (@autodemesne=1) {DEMESNE EFFECT ETCUNTILLASTONE;#Var autodemesne 0}}}}

However many open { you have, you need a } to close. CMUD color coding will highlight what {} you are closing as you add them, so just match up.

I even formatted it. Use KDEM if you get interrupted and the next alarm will fail, as you set all alarms within alarms, none of the others will be called.

G'day mate!

Desitrus' way is nicer if you tend to get interrupted a lot. You can also set variables to keep track of which effects have already been cast, so that when you resume, you're not recasting ALL the effects, just the ones that haven't already been.

Those nested ifs burns us. Switch statements are beautiful things...

I don't swing that way.

I don't see how a switch statement would much help simple boolean checks over time...

It doesn't "help" in terms of changing how the script functions. It helps in readability and debugging if problems arise. Nested ifs are ugly and the ability of cmud to do switch statements to avoid them is one of my personal favorite features.

I meant how would you incorporate a switch statement into that? The nested "ifs" are only recursing boolean checks, not checking for different values.

You wouldn't for that code. Didn't look at it closely enough. I was thinking it was more like this:

#ALIAS startdem {autodemesne = 0;autodem}
#ALIAS autodem {#SWITCH (@autodemesne == 0) {DEM EFFECT 1;#ALARM "DemTiming" +9.75 {autodem}} (@autodemesne == 1) {DEM EFFECT 2} (@autodemesne == 2) {DEM EFFECT 3} etc}

With triggers to indicate which effects you've already set (or when you want to advance autodemesne and run autodem) so you could do specific timing on the effects. Like for example I know aquamancers will tick quite a few of the effects off of the splashing from the heal spring.

Isn't it better to use some kind of DO AFTER kind of command?

Alarm = do after. If you get interrupted, though, it keeps on going.

thanks a bunch.

yes the effects where timed on the heal spring message.

This is what I am doing

Sparkling water splashes up over your body, healing your wounds.
#alarm +10 (aquacast healspring demesne)
#alarm +20 {aquacast needlerain demesne}
#alarm +30 {aquacast jellies demesne}
#alarm +40 {aquacast icefloe demesne}
#alarm +50 (aquacast tsunami demesne)
ERROR: Trigger "Sparkling water splashes up over your body, healing your

well that's confusing. When I think of an alarm I think of something that will alert me, not to DO things for me.

Oh well, I prefer MUSHClient better

You have the wrong braces on that line. You should be using { } not ( )

hrm I actually make use of an array instead of a switch, it makes it easier to modify demesne stuff (atleast for me)

#alias demdef {todem=@wanteddem;demesneloop}
#alias demesneloop {#if @noint {%pop(@todem);#if @todem {#alarm +10 {demesneloop}}}}
#alias int {noint=0}
#var wanteddem {forestcast squirrels demesne|forestcast spores demesne|forestcast pollen demesne|forestcast thorns demesne|forestcast swarm demesne|forestcast storm demesne}

Next part would need some trial and error modifying of timers since I have a demesne artifact

#alias demres {noint=1;#T+ demesneResume;demesne}
#var firstcall {Swarm} --> needs to be changed
#var temp {}
#var timevar {}
in class demesneResume
#Trigger {@firstcall%s(&temp)} {#T- demesneResume;timevar=(%mod(@temp,10) +6);#alarm {+@timevar} {demesneloop}} --> the 6 probably needs adjusting