Zugg Software :: View topic

Posted: Sun Aug 12, 2012 4:14 pm

Alias name should only be one word.

Apprentice Joined: 10 May 2011 Posts: 111

Can it be made into two, or is that a strict no-go?

Wizard Joined: 22 Mar 2007 Posts: 2320

An alias cannot be multiple words, so you can't have an alias "xconfig testclass". Instead, I suggest making the alias be "xconfig", with two parameters, one for the name of the class, and the other the on/off. You might also do a single #IF statement with an Else clause, instead of two #IF statements. Like so:

Sorcerer Joined: 15 Apr 2011 Posts: 809

You could use a command input trigger to have a two word "alias", but Rahab's code is more flexible.

Apprentice Joined: 10 May 2011 Posts: 111

Sorcerer Joined: 15 Apr 2011 Posts: 809

Sure, just check if the plugin is on before writing to the window. Assuming they're each in a class, it might look something like this:

Apprentice Joined: 10 May 2011 Posts: 111

Posted: Mon Aug 13, 2012 12:56 pm

before the if statement, add:

#LOCAL $line3

Apprentice Joined: 10 May 2011 Posts: 111

Works great, Shalimar. Thanks much! To get a better hold on this, I'm understanding that it declares it as a variable? What does it do for this script?

Posted: Mon Aug 13, 2012 1:23 pm

thats exactly right, local variables need to be declared
if they are only defined inside if statements, they get thrown out when the if is done, due to scoping

Apprentice Joined: 10 May 2011 Posts: 111

Ah, okay. Thanks.

Wizard Joined: 22 Mar 2007 Posts: 2320

In more detail:
Local variables need to be declared before the value is used or tested. The explicit way of declaring local variables is with the #LOCAL command. However, setting the value of a local variable also implicitly declares it. So if you set the value of a local variable (e.g., with "#VAR $varname ..." or "$varname = ...") before the value is ever used or tested, then technically you don't have to use #LOCAL. It is still good programming practice to use #LOCAL even in these cases, if for no other reason than that it helps you remember. It can prevent problems where you initially are setting the value first but later edits introduce situations where the variable is used before it is set.

Apprentice Joined: 10 May 2011 Posts: 111

Ah, gotcha. I generally have been using the "$varname = " for alot of the scripts I have been doing, just didn't know exactly what it did, I suppose. Thanks, Rahab.

Apprentice Joined: 10 May 2011 Posts: 111

Going back to the config alias, was trying this to make it easier:

Sorcerer Joined: 15 Apr 2011 Posts: 809

If you want +ShipBuild to be a literal string, you need to put it in quotes. Without quotes, it's trying to add. In general, you should always put literal strings in quotes, so your alias would look like this:

Apprentice Joined: 10 May 2011 Posts: 111

Thank you. =) Had to fix it from being a 100% literal string with case issues by changing it to

Apprentice Joined: 10 May 2011 Posts: 111

Sorcerer Joined: 15 Apr 2011 Posts: 809

We'd need to see how you're setting the variable. If you're using an alarm that fires every second and adds one to the variable, just make it subtract one instead, and instead of starting the variable at 0 start it at 7200 (seconds in two hours).

Apprentice Joined: 10 May 2011 Posts: 111

The variable is MSDP. The MUD automatically updates the variable every second.

Sorcerer Joined: 15 Apr 2011 Posts: 809

All right... just use (7200 - @BOTTINGTIME) instead then.

Posted: Wed Aug 15, 2012 9:15 am

I just want to clarify something... CMUD variables most certainly can use underscores. I have several variables in that very format. I do not know where Rahab got the idea that variables cannot, so the MSDP should work. *shrug*

Aliases also allow underscores, by the way.

Wizard Joined: 22 Mar 2007 Posts: 2320

Hm. I've had problems with it in the past, and I vaguely recollect others having problems with underscores in variables too. I'll check again.

Beginner Joined: 06 Mar 2014 Posts: 12

So I put this together this will initialize MSDP on any mud and setup reporting for every available msdpvar