you had too many ends

if table.contains(enemies, matches) then blah else blah end

No, I want it to end if the first thing is true. If I'm afflicted with something I don't want to cure, the function should just stop right there.

Return will exit a function. You can return a value as well, with "return " and your function will equal whatever you returned.

CODE

function foo(num)
  if num % 2 == 1 then
    return "odd"
  else
    return "even"
  end
end

echo(foo(3) .. "\\n") will echo "odd" to your screen. (And a line break.)

Awesome, thanks! I knew it would be something stupid simple like that.

Oh I see, so in this case you'd continue to re-target each time a beast dies, instead of waiting for the command or for a new one to appear? One reason I took the extra steps is sometimes pilots prefer you to wait for their command, because it might endanger the crew or something like that... not 100% sure.

Mudlet uses Lua, right?

In Lua you can use 'not' to change the value, ie:
if not null then
print("True!")
else
print("False.")
end

I'm 99% sure that if there is something you can target, you should be shooting at it. The only problem might be target priority, but that's not hard to do either.

EDIT: Slight nitpick, Esano. Lua uses nil instead of null.

@Lilia:
I save the aetherbeast target as a variable, then I trigger ^A battle turret is not targeting anything\\.$ to target the aetherbeast again.

Edit: Only time there might be a problem is if the vortex spawns two different aetherbeasts. Then, yeah, manual.

Yeah, that's what I do. If you shouldn't be firing, you'll generally be told to 'deactivate your turret', in which case you'll deactivate the whole folder. I've got folders for each module that are always locked, and I only unlock them when I'm on that module.

mine actually a table to either add all called out targets, or add spawned targets (I prefer working with spawned targets but meh some pilots don't like that). And if it is empty and you get attacked it targets the attacking creature. I then track things that blow up, if the list is not clear, retarget with priority on karbs.

When it comes to aetherhunting, I have a semi-sophisticated system set up. Whenever an aetherbeast appears, I insert the name of the beast into a table. Then, when it comes to targeting, I iterate through that table, and if there's a Dragon, or Scyllus, or Gargantuan, then I'll target and kill them first. After that beast dies, I'll check if there's anything left in the table, and if so, I'll target them and repeat the process. If there's a Karibidean, I'll still add them to the list, but I won't target them unless all other aetherbeasts are dead. And as far as roaming beasts that you sometimes have to kill, I made an alias 'aa ', which will add that aetherbeast into my targeting table, and do it all over again. Pretty cool, and that allows me to not have to do too much manual anything!

When I enter the editor to write something, in this case the examined in a design, it forces a single space before the examined. Any ideas on how to fix this?

If it's not removed in latest pre-release yet, then it will be in the next one. Can't fix it right now, though - besides leaving the first line blank.

Get someone who doesn't use mudlet to edit it for you, or use nexus for editing.

or just use the ingame editor

Is there a built-in Scripting Event that goes off when a new line comes in from the game? If not, I can easily make up something, but I'd rather not reinvent the wheel here.

I must be really dunce here, I'm trying to highlight a complete line that contains a variable, but the highlight is only on the part of the line that isn't a variable.

e.g.

The floor shakes as you fire a blast that slams into (.*)

How do I include (.*) in the coloured part?

(and while on this topic, can I colour the line and the variable within it as two separate colours)?

To select the entire line:


I'm not exactly sure how to color the variable one way, and the line another, though I suppose it would be some way similar to coloring the entire line.

yes, it's called a trigger

Not exactly what I was going for... But meh, it'll have to do.