Revision as of 19:21, 14 February 2018

Locking Things in TinyMUX

There are a LOT of different ways you can lock things in the TinyMUX game system.

Basic Commands

There are, however, two basic commands:

• @lock
• @unlock

@lock

This command locks something in a specific way.

@lock[/<type of lock>] <object>=<key>
@lock <object>/<attrib>

By default, @locking something will stop everyone from going through it. This includes you.

@unlock

This command unlocks something in a specific way.

@unlock[/<type of lock>] <object>=<key>
@unlock <object>/<attrib>

By default, @unlocking something will allow ANYTHING and ANYONE to go through it. The lock you had set on it is completely wiped.

You can find these in game via 'help @lock' and 'help @unlock' respectively.

Types of Locks

You can see the information below by checking the IG helpfile 'help @lock locks' to find the various locks you can set with @lock.

Lock Keys

The true flexibility of locks comes in the number and variety of keys you can use for them.

Since the average player will likely never need anything more complicated than a list of other players or, say, motleymates who know the secret password, we are going to skip over almost all of that lovely variety and only focus on what people will actually be using.

If you want to read more about it, check 'help @lock keys' IG, or the table below. The <object> is the *Name or #dbref of the person/item being used as a key.

Special Characters

There are some important characters to learn when you are dealing with locks.

Examples of Locks

If this is still confusing, no worries. Here are some examples of what the locking code looks like in action, to try and take the scary out.

Exits

In this section, I will present a scenario in bold text and follow it with the lock code which would accomplish that scenario.

The exit's DBREF is going to be #1234 and its name is Exit <EX>. Its alias is ex (so you don't have to type Exit <EX> every time you want to walk through it).

My character's name is Cupcake. Cupcake's DBREF is #5678.

I will be using its dbref in the examples below, because it is always safest to work with the dbref of an object, in case there are multiple objects nearby with similar names.

• I want to be the only person who can go through my exit.

@lock #1234=*Cupcake

Now, if I know my own dbref, I don't need the * in front. I can just write...

@lock #1234=#5678

The asterisk tells the code that the letters following it are a player's name, and it should look for a PLAYER object in the database named Cupcake.

• I want only yours truly and my friend Sally to be able to get into my secret clubhouse.

@lock #1234=*Cupcake|*Sally

• I want to lock an exit so only approved players can get through it.

This uses the "evaluation" key type. The key will be set to APPROVAL/1, so when someone attempts to go through the exit, the exit will run the code in the APPROVAL attribute. If the code does not return a 1, that person will not be allowed through.

@lock #1234=APPROVAL/1
&APPROVAL #1234=hasflag(%#,approved)

Objects

Same text as above! My imaginary name is still Cupcake. My Object is #99.

• I have a logging object, but I don't want anyone else to be able to pick it up while I'm logging a scene with it.

@lock #99=*Cupcake

Pages

Same text as above! My imaginary name is still Cupcake, but since I'm locking myself, I can just use 'me' instead of my name.

• So, Dirk the Skinflayer has been harassing me via pages, and I can't get him to stop. I want to block him from reaching me that way.

@lock/pagelock me=!*Dirk

Rooms

My name is still Cupcake! My imaginary room is called My Imaginary Room(#5555), but since I'm standing in it, I can just use 'here' instead of its name or dbref.

• I @set here=jump_ok so my friends Sally, Pink and Charles could have a custom command to @tel into my space, but I don't want EVERYone to be able to do it.

@lock/tportlock here=*Cupcake|*Sally|*Pink|*Charles