Tapestries MUCK - User contributions [en]

@name

2007-07-05T12:43:28Z

Ash-Fox: Fixed registration link.

The '''@name''' command is used to change an object's name. This requires ownership of the object in question. The syntax is @name <object>=<name>, where <object> can be it's current name, or some unique portion of it, or the [[dbref]] of the object.

==Thing, Room and Program Names==
These are fairly unrestricted and can be quite long. Most notably, they can not start with a #, to differentiate themselves from [[dbref]]s.

==Exit Names==
Exits/actions functionally have multiple names. This is actually stored as a single string separated by semicolons. A common example is an exit that is a direction, such as north. It's common to give one or more abbreviations for the direction so the user does not have to type "north" in full. So:
@name #1234=north;n
This will allow a user to type either 'north' or 'n' to go through that exit.

Note, if you want to rename an exit by name, you have to use one of it's sub-names. So @name north;n=newname will not work. You would have to @name north=newname.

See [[gen-obv-exits]] for more information on exit naming conventions.

==Player Names==
Tapestries MUCK does not allow players to change their own names. This restriction is in place for a large variety of reasons, including people abusing @name changes to spoof others and insult others anonymously, but primarily it is because of ongoing work to integrate Tapestries MUCK with other services. Most web services and things like Jabber IM servers do not gracefully handle character name changes.

If you try and @name yourself you will get the error message: ''Only wizards can rename players.'' This is technically correct, [[wizards]] still retain the ''ability'' to change names. However, it is policy not to, so they won't.

Only cases where names are deemed to be ''accidentally'' in violation of the [[MUCK]] [[Policies]] will they be changed by the wizards. Cases were they are deemed to be intentionally in violation of the [[Policies]] will instead result in [[Policy Toading|toading]].

=== See Also ===
* [http://www.fur.com/tapestries/registration/ Character Registration] if you just want a different character.
* [[@toadme]] if you no longer plan to use this name.

[[Category:MUCK Commands]][[Category:Built in MUCK Commands]]
__NOTOC__

Connection issues

2007-07-05T12:17:26Z

Ash-Fox: Changed the instructions slightly so periods were not at the end of values that can be copy/pasted -- to prevent confusion/mistakes.

==Home router silent disconnects==

Probably one of the most common of issues encountered with home routers and idle connections.

Many home routers behave as NATs, the concept of a NAT is generally allow a network of computers share one IP address on another network, in this case the Internet. For address transversal to work, the router needs to keep routing information in memory of which connections are going where. Here is where in lies the problem.

The router's memory is finite, and generally home routers have very little memory. Many routers do not have the ability to check if a connection is still active if it's absolutely silent (no data passing through either side, quite a common case when you're in a quiet area on a MUCK and not communicating) the router will assume after a certain amount of time that the connection died and will remove the routing information from memory to free up memory to handle other/more connections.

Technical implementations for better checking mechanisms if a connection is still active do exist, but they require more memory and as such generally isn't found in home routers.

On many home routers which run on a embedded version of Linux (many of these use ipchains), this time limit is usually 900 seconds, although it can vary depending on what model and make of router you have. Generally this leads to silent disconnections after a bit of time.

Fortunately there is a workaround. You can increase the rate of 'TCP keep-alive' messages in the operating system (the computer you are using, not the router) to send messages periodically to the server to check if the connection is still alive. The default is value is 7200 seconds -- two hours under Linux and Windows. If the system sends these before the 'grace period' of dropping the connection, the router sees these messages and assumes the connection is still active and will not silently disconnect you.

Generally a value of 180 seconds is usually low enough to work around all the home routers I've encountered. --[[User:Ash-Fox|Ash-Fox]]

'''Warning: Do not set this value lower than 60 seconds or you may suffer a lot of connectivity issues.'''

===Under Linux===
This can be set on the fly by entering in the console as root:

'''echo 180 > /proc/sys/net/ipv4/tcp_keepalive_time'''

However, if you wish to set this permanently (applied when you start the system), you will need to change/add '''net.ipv4.tcp_keepalive_time=''' in '''/etc/sysctl.conf''' to say something like:

'''net.ipv4.tcp_keepalive_time=180'''

===Under Windows NT systems===
This can be set from a Administrator account:

Open regedit and browse to:

'''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters'''

If there is a key called '''KeepAliveTime''' edit it. If it doesn't exist, create it as a new dword key.

Set the integer to '''180000''' (this is 180 seconds in mini-seconds), then restart Windows for the new changes to take effect.

===Under Windows 95/98/ME systems===

Open regedit and browse to:

'''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VxD\MSTCP'''

If there is a key called '''KeepAliveTime''' edit it. If it doesn't exist, create it as a new string value.

Set the string value to '''180000''' (this is 180 seconds in mini-seconds), then restart Windows for the new changes to take effect.

Connection issues

2007-07-05T12:05:10Z

Ash-Fox: Fixed some slight mistakes, added slightly better explanations and added win9x information.

==Home router silent disconnects==

Probably one of the most common of issues encountered with home routers and idle connections.

Many home routers behave as NATs, the concept of a NAT is generally allow a network of computers share one IP address on another network, in this case the Internet. For address transversal to work, the router needs to keep routing information in memory of which connections are going where. Here is where in lies the problem.

The router's memory is finite, and generally home routers have very little memory. Many routers do not have the ability to check if a connection is still active if it's absolutely silent (no data passing through either side, quite a common case when you're in a quiet area on a MUCK and not communicating) the router will assume after a certain amount of time that the connection died and will remove the routing information from memory to free up memory to handle other/more connections.

Technical implementations for better checking mechanisms if a connection is still active do exist, but they require more memory and as such generally isn't found in home routers.

On many home routers which run on a embedded version of Linux (many of these use ipchains), this time limit is usually 900 seconds, although it can vary depending on what model and make of router you have. Generally this leads to silent disconnections after a bit of time.

Fortunately there is a workaround. You can increase the rate of 'TCP keep-alive' messages in the operating system (the computer you are using, not the router) to send messages periodically to the server to check if the connection is still alive. The default is value is 7200 seconds -- two hours under Linux and Windows. If the system sends these before the 'grace period' of dropping the connection, the router sees these messages and assumes the connection is still active and will not silently disconnect you.

Generally a value of 180 seconds is usually low enough to work around all the home routers I've encountered. --[[User:Ash-Fox|Ash-Fox]]

'''Warning: Do not set this value lower than 60 seconds or you may suffer a lot of connectivity issues.'''

===Under Linux===
This can be set on the fly by entering in the console as root:

'''echo 180 > /proc/sys/net/ipv4/tcp_keepalive_time'''

However, if you wish to set this permanently (applied when you start the system), you will need to change/add '''net.ipv4.tcp_keepalive_time=''' in '''/etc/sysctl.conf''' to say something like '''net.ipv4.tcp_keepalive_time=180'''.

===Under Windows NT systems===
This can be set from a Administrator account:

Open regedit and browse to '''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters'''.

If there is a key called '''KeepAliveTime''' edit it. If it doesn't exist, create it as a new dword key.

Set the integer to '''180000''' (this is 180 seconds in mini-seconds), then restart Windows for the new changes to take effect.

===Under Windows 95/98/ME systems===

Open regedit and browse to '''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VxD\MSTCP'''

If there is a key called '''KeepAliveTime''' edit it. If it doesn't exist, create it as a new string value.

Set the string value to '''180000''' (this is 180 seconds in mini-seconds), then restart Windows for the new changes to take effect.

Connection issues

2007-07-05T11:21:42Z

Ash-Fox: Fixed formatting

==Home router silent disconnects==

Probably one of the most common of issues encountered with home routers and idle connections.

Many home routers behave as NATs, the concept of a NAT is generally allow a network of computers share one IP address on another network, in this case the Internet. For address transversal to work, the router needs to keep routing information in memory of which connections are going where. Here is where in lies the problem.

The router's memory is finite, and generally home routers have very little memory. Many routers do not have the ability to check if a connection is still active if it's absolutely silent (no data passing through either side, quite a common case when you're in a quiet area on a MUCK and not communicating) the router will assume after a certain amount of time that the connection died.

On many home routers which run on a embedded version of Linux, this time limit is usually 900 seconds, although it can vary depending on what model and make of router you have. Generally this leads to silent disconnections after a bit of time.

Fortunately there is a workaround. You can increase the rate of 'TCP keep-alive' messages in the operating system (the default is 7200 seconds -- two hours under Linux and Windows) to send messages periodically to the server to check if the connection is alive. The router will see this and assume the connection is still active and won't silently disconnect you.

Generally a value of 180 seconds is usually low enough to work around all the home routers I've encountered. --[[User:Ash-Fox|Ash-Fox]]

Under Linux, this can be set on the fly by entering in the console as root:

'''echo 180 > /proc/sys/net/ipv4/tcp_keepalive_time'''

However, if you wish to set this permanently, to be set on boot, you will need to change/add '''net.ipv4.tcp_keepalive_time=''' in '''/etc/sysctl.conf''' to say something like '''net.ipv4.tcp_keepalive_time=180'''.

Under Windows, for some obscure reason it has timing upto the mini-second:

Open regedit and browse to '''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters''' if there is a key called '''KeepAliveTime''' edit it. If it doesn't exist, create it as a new dword key.

Set the integer to 180000 (this 180 seconds in mini-seconds), then restart Windows for the new changes to take effect.

Connection issues

2007-07-05T11:21:03Z

Ash-Fox:

==Home router silent disconnects==

Probably one of the most common of issues encountered with home routers and idle connections.

Many home routers behave as NATs, the concept of a NAT is generally allow a network of computers share one IP address on another network, in this case the Internet. For address transversal to work, the router needs to keep routing information in memory of which connections are going where. Here is where in lies the problem.

The router's memory is finite, and generally home routers have very little memory. Many routers do not have the ability to check if a connection is still active if it's absolutely silent (no data passing through either side, quite a common case when you're in a quiet area on a MUCK and not communicating) the router will assume after a certain amount of time that the connection died.

On many home routers which run on a embedded version of Linux, this time limit is usually 900 seconds, although it can vary depending on what model and make of router you have. Generally this leads to silent disconnections after a bit of time.

Fortunately there is a workaround. You can increase the rate of 'TCP keep-alive' messages in the operating system (the default is 7200 seconds -- two hours under Linux and Windows) to send messages periodically to the server to check if the connection is alive. The router will see this and assume the connection is still active and won't silently disconnect you.

Generally a value of 180 seconds is usually low enough to work around all the home routers I've encountered. --[[User:Ash-Fox|Ash-Fox]]

Under Linux, this can be set on the fly by entering in the console as root:

'''echo 180 > /proc/sys/net/ipv4/tcp_keepalive_time'''

However, if you wish to set this permanently, to be set on boot, you will need to change/add '''net.ipv4.tcp_keepalive_time=''' in '''/etc/sysctl.conf''' to say something like '''net.ipv4.tcp_keepalive_time=180'''.

Under Windows, for some obscure reason it has timing upto the mini-second:

Open regedit and browse to '''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters''' if there is a key called ''KeepAliveTime'' edit it. If it doesn't exist, create it as a new dword key.

Set the integer to 180000 (this 180 seconds in mini-seconds), then restart Windows for the new changes to take effect.

User talk:Kles

2007-04-25T06:02:38Z

Ash-Fox:

Thanks for helping out around here. :) --[[User:WhiteWizard|WhiteWizard]]<sup>([[User talk:WhiteWizard|talk]])</sup> 20:28, 24 April 2007 (PDT)

*Greetings, I wrote the MPI syntax highlighting language script -- I was forwarded to your user page over the issues and I've added/fixed the missing things (I've sent WhiteWizard the new script). If you find anything else wrong or have any suggestions, leave me a note my discussion page. Thanks =) [[User:Ash-Fox|Ash-Fox]] 23:02, 24 April 2007 (PDT)

User:Ash-Fox

2007-03-31T08:45:08Z

Ash-Fox: /* Notes to self */

Ash-Fox enjoys putting [http://en.wikipedia.org/wiki/Slinky slinkies] on an [http://en.wikipedia.org/wiki/Escalator escalator].

==Notes to self==
*Ask a moderator to delete the old MPI_ articles (which are redirects for the time being) and categories (moved the MPI articles to a better naming convention in categories).
*Write decent descriptions for MPI categories.
*Look over the MPI functions and see if they fit into more than one category or create additional categories if needed.
*Consider doing basic stubs on each command the MUCK supports, using text from the 'help' command.

LocationCount (lc)

2007-03-31T08:40:29Z

Ash-Fox: Added to 'MUCK Commands' category.

[[Category:MUCK Commands]]
This command gives you a count of the number of people that are in a each public area. By default it will not list any area with less than 2 people (this is the "Threshold".) You can specify different thresholds after the command, such as "locationcount 1" to get a list of every area with 1 or more people in it.

The command can be abbreviated (and usually is) as simply "lc".

Sample output:

Area ### Description (Threshhold 2)
------------------------- --- ---------------------------------------------
Layleaux Town............ 295 Largest town; north side of the lake
Auction House.......... 8 Slave Auctions (t plaza;s)
Bull's Gym, The........ 7 Fitness Center & Hangout (t bullgym)
Cistern, The........... 2 Town Sewer System (t cistern)
Feedery Barn & Grill... 3 Weight Gainer's Bar (t cafevore; feed)
Fox Plaza.............. 50 Central Gathering Spot (t plaza; out)
Golden Lash, The....... 13 BDSM Club (t goldenlash)
Hermaphrodite Haven.... 27 Herm themed Bar/hotel (all welcome) (t HermH)
Lining, The............ 40 Gay/Bi/Straight BDSM Bar (t lining)
Lion's Den............. 18 Bars, Beach Hotel and Parks (t lionsden)
Merriam's Pub.......... 19 Erudite Erotica (t merriam)
Mystic Stables......... 15 Stud Farm and Horseback Riding Area (t mystic)
Plush Pile, The........ 3 Plushie Store/Play Area (t plushpile)
St. Mary's............. 7 School for Wayward Furs (t school; e)
Shimmering Sun Club.... 7 Reptilian-Themed Lounge and Resort (t sunclub)
Truth Or Dare.......... 8 (t plaza; out; se)
Velvet Underground..... 15 Everyone welcome - come in, have fun! (t vunder)
Vor Cafe............... 8 Predator/Prey and More (t cafevore)
Northern Forest.......... 17 Forest north of Layleaux
Secret Moon............ 10 Treehouse (t secretmoon)
East Forest & Mountains.. 2 The area to the East of Layleaux
Arvandor............... 2 Treedwellers Housing and more (t Arvandor)
Lake Alodaelia........... 4 In or Above the Lake (t ferry)
Temple of Divinity..... 4 Egyptian Area for rituals/breeders (t divine)
The Cloud Castle......... 2 Old Muck Center (t castle)
The Oceans of Tapestries. 8
Island of Dr I.N.Sane.. 2 Heavy Scenes Island (t insane)
Katatraz Prison Complex 2 Prisoner/Guard Roleplay and More (t katatraz)
Macro Zone, The........ 3 Macrophiles/Microphiles Area (t macro)
Unlinked Rooms........... 347 Unapproved Building
--- Total Online 685 ------------------------------------------ lc v2.1 ---

[[Category:MUCK Commands]][[Category:Extended MUCK Commands]]

@name

2007-03-31T08:40:04Z

Ash-Fox: Apparently there is already a commands category called 'MUCK Commands', using that instead.

[[Category:MUCK Commands]]
== help @name ==
The @name command helpfile entry is:
<br><tt>@name <object>=<name> [<password>]. Sets the name field of <object>
to <name>. <name> cannot be empty; a null name is illegal.
<password> must be supplied to rename a player. Wizards can rename
any player but still must include the password.</tt>

== The @name Policy ==
The @name command is locked and can not be used. That means your current name is your "forever-name."

The [[fail]] message for @name says 'Only wizards can rename players.' This may give the impression that players can request or petition [[wizards]] to change their name, but wizards will not go into the business of name-changes.

=== Changing your Name ===
Please just [http://www.fur.com/tapestries/registration go back to the web page] and generate a new [[character]].

=== Managing your Names ===

To manage your 'names':

#Learn [[@toadme]] to delete names/[[alt]]s
#As with most [[:Category:MUCK Commands|commands]], use #help for help, as in '@toadme #help'
#Learn to use the [http://www.fur.com/tapestries/registration registration form] to create new names/alts
#Make sure your [[spam filter]] does not hinder our email validation
#To validate, click link in email, and then click 'Verify' on the page itself
#If validation went wrong, your alt will be [[recycle]]d and you must re-register

@name

2007-03-31T08:37:44Z

Ash-Fox: Added to Commands category and fixed commands link to point to that.

[[Category:Commands]]
== help @name ==
The @name command helpfile entry is:
<br><tt>@name <object>=<name> [<password>]. Sets the name field of <object>
to <name>. <name> cannot be empty; a null name is illegal.
<password> must be supplied to rename a player. Wizards can rename
any player but still must include the password.</tt>

== The @name Policy ==
The @name command is locked and can not be used. That means your current name is your "forever-name."

The [[fail]] message for @name says 'Only wizards can rename players.' This may give the impression that players can request or petition [[wizards]] to change their name, but wizards will not go into the business of name-changes.

=== Changing your Name ===
Please just [http://www.fur.com/tapestries/registration go back to the web page] and generate a new [[character]].

=== Managing your Names ===

To manage your 'names':

#Learn [[@toadme]] to delete names/[[alt]]s
#As with most [[:Category:Commands|commands]], use #help for help, as in '@toadme #help'
#Learn to use the [http://www.fur.com/tapestries/registration registration form] to create new names/alts
#Make sure your [[spam filter]] does not hinder our email validation
#To validate, click link in email, and then click 'Verify' on the page itself
#If validation went wrong, your alt will be [[recycle]]d and you must re-register

Comments (MPI)

2007-03-31T05:00:20Z

Ash-Fox: Removed from MPI Functions category -- not a function.

[[Category:Definitions and Details (MPI)]]
=comments=

Only 26 levels of recursion are allowed, so funcs that deep return literally. In loops, a max of 256 iterations are allowed before they exit automatically.

Lists have a maximum size of 256 lines, or 4096 characters, whichever is less.
All matching will be done relative to the trigger object first, then relative to the triggering player, if nothing was matched in the first pass.

The 'me' and 'here' keywords always are relative to the triggering player.
The trigger object is referred to by 'this'.

Store (MPI)

2007-03-31T04:57:21Z

Ash-Fox: Added 'see also' link.

[[Category:functions (MPI)]][[Category:Property Handling (MPI)]]
=store=
<mpi>{store:val,prop}
{store:val,prop,obj}</mpi>
Stores a string value in a given property.

If no obj parameter is given, then it stores the property on the trigger object. Otherwise, it will store it on the given object.

If you specify a propname that is protected, you will get a Permission Denied error.

You are only allowed to store properties on objects controlled by the owner of the trigger object. The trigger object is the object that triggered the evaluation of the MPI commands.

This function returns the string that is stored as the prop value. If you store a null value in the property, then it will remove the property if it is not a propdir.

It will clear the value of the prop if it IS a propdir.

==See also==
*MPI function: [[Propdir (MPI)|propdir]]

Listprops (MPI)

2007-03-31T04:50:56Z

Ash-Fox: Corrected link(s) with new MPI naming scheme.

[[Category:functions (MPI)]][[Category:Property Handling (MPI)]]
=listprops=
<mpi>{listprops:propdir}
{listprops:propdir,object}
{listprops:propdir,object,pattern}</mpi>
This function will return a list that contains the full names of all the sub-properties contained by the given propdir.

If not given, object defaults to the trigger object. If a pattern is given, the sub-properties in the propdir are each compared against the smatch wildcard pattern, and only those that match are returned in the list. This comparison is only done on the last part of the property name after the last /.

Also refer to [[Propdir (MPI)|PROPDIR]] and [[Smatch (MPI)|SMATCH]].

List (MPI)

2007-03-31T04:49:51Z

Ash-Fox: Added link.

[[Category:functions (MPI)]][[Category:Property Handling (MPI)]]
=list=
<mpi>{list:listname}
{list:listname,obj}</mpi>
Returns a string, containing a carriage-return delimited list of individual lines from a property based list.

A property based list is a series of properties that are consecutively numbered. The server understands several different formats, and can also read in property lists in either the propnameX format, or the propname#/X format.

It does NOT evaluate the contents of the list for embedded [[MPI]] commands.

If no obj argument is supplied, then it looks for the list somewhere down the environment from the trigger object. Otherwise, it looks for the list down the environment from the given object.

Lastused (MPI)

2007-03-31T04:48:34Z

Ash-Fox: Corrected link(s) with new MPI naming scheme.

[[Category:functions (MPI)]][[Category:Database Related Functions (MPI)]]
=lastused=
<mpi>{lastused:obj}</mpi>
Returns the time and date that obj was last used.

The number returned is suitable for use with {[[Convsecs (MPI)|convsecs]]}.

Kill (MPI)

2007-03-31T04:47:51Z

Ash-Fox: Corrected link(s) with new MPI naming scheme.

[[Category:functions (MPI)]][[Category:Time Functions (MPI)]]
=kill=
<mpi>{kill:processID}</mpi>
Kills a process on the timequeue, that was possibly created by {[[Delay (MPI)|DELAY]]}.

If the process ID it is given is 0, then it will kill all processes done by that trigger object. If the process to be killed was not set off by that trigger, and was not set off by any object that the owner of the trigger owns, then this will error out with Permission denied.

If no process is found, this returns 0. If a process was found, and the permissions were okay, then the process is killed, and {[[Kill (MPI)|kill]]} returns the number of processes killed. Usually 1.

Func (MPI)

2007-03-31T04:44:14Z

Ash-Fox: Corrected link(s) with new MPI naming scheme.

[[Category:functions (MPI)]][[Category:Macros and Functions (MPI)]]
=func=
<mpi>{func:name,vars...,def}</mpi>
This effectively defines a function in [[MPI]], with the given name, that takes the given named variables.

The function is not immediately evaluated, so it needs to be invoked later, to do anything. Here's an example:
<mpi>{func:sqr,val,{mult:{&val},{&val}}}</mpi>

This defines the function 'sqr', that takes a single argument. That argument is stored in the 'val' variable. The function will multiply the value of the number passed to it, by itself, returning the result.
It's invoked like:
<mpi>{sqr:10}</mpi>

Effectively, the above {[[Func (MPI)|func]]} declaration is the same as the following macro, and in fact, it's internally handled the same way:

<mpi>_msgmacs/sqr:{with:val,{:1},{mult:{&val},{&val}}}</mpi>

You can define a function that takes more than one argument, but the maximum number of args you can pass to the function is seven. Example of multiple arguments:

<mpi> {func:names,list,numsp,flagsp,
{parse:v,{&list},
{name:{&v}}
{if:{or:{&numsp},{&flagsp}},
{lit:(}
{if:{&numsp},{ref:{&v}}}
{if:{&flagsp},{flags:{&v}}}
{lit:)}
}
}
}
{names:{contents:here},1,1}
</mpi>

Ftime (MPI)

2007-03-31T04:42:22Z

Ash-Fox: Fixed up the formatting, added 'Timefmt' and rearranged some text.

[[Category:functions (MPI)]][[Category:Time Functions (MPI)]]
=ftime=
<mpi>{ftime:format}
{ftime:format,tz}
{ftime:format,tz,secs}</mpi>
Returns a time string in the format you specify.

If specified, tz is the number of seconds offset from GMT. If specified, secs is the systime to use, instead of the current time. <mpi>{ftime:%x %X %Y,{tzoffset},0}</mpi> will return the date and time for systime 0, for the local time zone of the server.

See [[Timefmt]] for the %subs that you can use in the format string.

Foreach (MPI)

2007-03-31T04:37:13Z

Ash-Fox: Fixed up the formatting and added links for commands.

[[Category:functions (MPI)]][[Category:Looping Functions (MPI)]]
=foreach=
<mpi>{foreach:var,list,expr}
{foreach:var,list,expr,sep}</mpi>
This evaluates expr for each and every item in the given list.

On each evaluation, the temporary variable var will contain the value of the item under scrutiny.

var will only be defined for the duration of expr, and will be undefined after the {[[Foreach (MPI)|foreach]]} construct finishes. If sep is given, then it uses that string as the item seperator in list, instead of the usual carriage return character.

sep can be multiple characters long.

This structure returns the result of the last evaluation of expr.

Example:
<mpi>{foreach:thing,{contents:here},{tell:{name:{&thing}}}}</mpi>
This will display the name of every object in the room, then it will return the name of the last object it displayed.

Force (MPI)

2007-03-31T04:35:59Z

Ash-Fox: Corrected link(s) with new MPI naming scheme.

[[Category:functions (MPI)]][[Category:Database Related Functions (MPI)]]
=force=
<mpi>{force:object,command}</mpi>
Forces the given player or thing to do the given command. The thing forced must be [[@flock]]'ed to the trigger object, or the trigger object's owner, and it must be set XFORCIBLE, or else this function will get a Permission Denied error.

This function returns a null string.

{[[Force (MPI)|Force]]} cannot force a thing-object to do something, if it is set Dark, is in a room set Zombie, or is owned by a player set Zombie.

Filter (MPI)

2007-03-31T04:35:06Z

Ash-Fox: Corrected link(s) with new MPI naming scheme.

[[Category:functions (MPI)]][[Category:Looping Functions (MPI)]]
=filter=
<mpi>{filter:var,list,expr}
{filter:var,list,exp,sep}
{filter:var,lst,exp,sep,s2}</mpi>
This evaluates expr for each and every item in the given list.

On each evaluation, the temporary variable var will contain the value of the item under scrutiny. This function returns a list containing all of the items from the input list, for which expr evaluated true. var will only be defined for the duration of expr, and will be undefined after the {[[filter (MPI)|filter]]} construct finishes. If sep is given, then it uses that string as the item seperator in the input list, instead of the usual carriage return character.

If s2 is defined, then it will use that string to seperate the items in the list it returns, instead of the normal carriage return. sep and s2 can be multiple characters long.

Exits (MPI)

2007-03-31T04:34:16Z

Ash-Fox: Fixed up the formatting

[[Category:functions (MPI)]][[Category:Database Related Functions (MPI)]]
=exits=
<mpi>{exits:obj}</mpi>
Returns a list of all the exits on the given object.

The owner of the trigger object has to control obj, or else this errors out with Permission Denied.

Programs and exits never have exits attached to them.

Delay (MPI)

2007-03-31T04:32:55Z

Ash-Fox: Added link(s) for function(s).

[[Category:functions (MPI)]][[Category:Time Functions (MPI)]]
=delay=
<mpi>{delay:secs,expr}</mpi>
Evaluates the given expression, then puts the result of that on the timequeue, to execute after the given number of seconds.

At that time, the string is evaluated again, and displayed to the user, or to the room, depending on whether it was run from a regular message such as [[@succ]], or from an omessage such as [[@osucc]].

Since the expression is evaluated both before and after being delayed, you need to put MPI code that is to run after the delay within a {[[Lit (MPI)|lit]]:expr} command. If a {[[Delay (MPI)|delay]]} evaluation is a null string, then the notify or notify_except will not be done.

{[[Delay (MPI)|delay]]} will return the process ID of the event it puts on the timequeue.

Delay (MPI)

2007-03-31T04:30:54Z

Ash-Fox: Fixed up the formatting and added links for commands.

[[Category:functions (MPI)]][[Category:Time Functions (MPI)]]
=delay=
<mpi>{delay:secs,expr}</mpi>
Evaluates the given expression, then puts the result of that on the timequeue, to execute after the given number of seconds.

At that time, the string is evaluated again, and displayed to the user, or to the room, depending on whether it was run from a regular message such as [[@succ]], or from an omessage such as [[@osucc]].

Since the expression is evaluated both before and after being delayed, you need to put MPI code that is to run after the delay within a {lit:expr} command. If a {delay} evaluation is a null string, then the notify or notify_except will not be done.

{delay} will return the process ID of the event it puts on the timequeue.

Definitions (MPI)

2007-03-31T04:29:15Z

Ash-Fox: Is not a function, removed from function category.

[[Category:Definitions and Details (MPI)]]
=definitions=

A Trigger object is the object that the MPI script is evaluated from.

A List is a string containing several individual substring items, seperated by carriage return characters.

A property based list is a set of consecutively numbered properties that each contain one string in a list of strings. Property based lists are often numbered like: listname1, listname2, listname3, listname4, &c. Another popular format is listname#/1, listname#/2, listname#/3, etc. MPI can read in either of those formats, and several more, for that matter.

For logical constructs, a string value of "0", or a null string ("") are both considered false. Any other value is considered true.

Created (MPI)

2007-03-31T04:26:10Z

Ash-Fox: Corrected link(s) with new MPI naming scheme.

[[Category:functions (MPI)]][[Category:Database Related Functions (MPI)]]
=created=
<mpi>{created:obj}</mpi>

Returns the time and date that obj was created. The number returned is suitable for use with [[Convsecs (MPI)|convsecs]].

Center (MPI)

2007-03-31T04:24:31Z

Ash-Fox: Fixed up the formatting

[[Category:functions (MPI)]][[Category:String Functions (MPI)]]
=center=
<mpi>{center:string}
{center:string,fieldwidth}
{center:string,fieldwidth,padstring}</mpi>
Takes a string and pads it to fit the given fieldwidth, with the string center justified.

If no padstring is given, it assumes that it will pad the string with spaces.
If no fieldwidth is given, it assumes that the field width is 78 characters.

Example:
<mpi>{center:Hello,10,1234567890}</mpi>
would return the string "123Hello12"

Add (MPI)

2007-03-31T04:23:44Z

Ash-Fox: Fixed up the formatting

[[Category:functions (MPI)]][[Category:Math Functions (MPI)]]
=add=
<mpi>{add:expr1,expr2}
{add:expr1,expr2,expr3...}</mpi>
Returns the sum of the values of expr1 and expr2.

If more than two args are given, then this will add all the args together and return the result.

2007-03-31T01:47:09Z

Ash-Fox:

[[Category:functions (MPI)]][[Category:Connection Related Functions (MPI)]]
=ontime=
<mpi>{ontime:player}</mpi>
Returns player online time in seconds.

If the given player is not connected, or is not a player object at all, then this will return -1.

This returns the online time for the most recently connected connection, if there are multiple connects.