Home Oma spews about: IF Statements Arrays Sorting Lists Loops in Loops (embedded loops) While Wait, I want MM to WAIT!! (and you can) Searching and Search Engines MM Speed'o Parsing Using a Wildcards Misc. Tidbits: Custom LoopCount Var Name: Did you know you can name the "LoopCount" variable when making loops? Yup! It's not documented, but here's how -- it's simple. /loop {start,end,SomeVarName} so /loop {1,10,Oma} would set the "LoopCount" variable as "Oma" /loop {1,3,Oma} {/showme $Oma} would output in showmes: 1, 2, 3 Cheating @Var(): I often cheat the @Var() proc to custom build and then extract variable info. Particularly in quest scripts, but it's a fairly handy trick to use. Say you have a number of vars you want to store for similar information, in quests this is common due to using player names for so many things (scores, etc). Say I want to keep score vars for each player. Something like "NameScore" for each person.. When they tell me "score" I want to access their variable that contains the score info, but "%0 telepaths you, 'score'." only gives me the name ($0). Now I can abuse @Var().. and tack "$0" to "Score" and retrieve the variable. Joe telepaths you, 'score'. /action {%0 telepaths you, 'score'.} {tell $0 @Var($0Score)} Simple no? It's a cheat, but it works nicely. /gag + /action + /showme vs. /substitute Substitutes create a lot of strain, as you might notice if you have a number of them. If possible try using /gag, /action, and a /showme (via the action) to "substitute" text. Depending on what you're doing, the gag and action combo is often faster than using substitutes. You see a lot of flowing text, blinding your vision as some lengthy spammy spew streams across the sky. /gag {^You see a lot of %0 the sky.} {} /action {^You see a lot %0 the sky.} {/showme {Argh! The blinding spew!}} And something you can't do in a substitute is add color to that showme if you so desire. Home