@mpi
From Tapestries MUCK
(Difference between revisions)
(explained @mpi) |
WhiteWizard (Talk | contribs) |
||
| Line 1: | Line 1: | ||
The @mpi command is useful for testing bits of [[MPI]] without having to implement them on something. If can be particularly useful for quickly testing syntax and making sure all yours :'s ,'s and {}'s are in place. To use the command, simply type:<br> | The @mpi command is useful for testing bits of [[MPI]] without having to implement them on something. If can be particularly useful for quickly testing syntax and making sure all yours :'s ,'s and {}'s are in place. To use the command, simply type:<br> | ||
| - | @mpi {some [[MPI]] | + | @mpi {some [[MPI]]} |
| - | The muck will | + | The muck will attempt to interpret your [[MPI]] string at this point, and return the results or an error. |
==Setting Targets== | ==Setting Targets== | ||
| - | + | A lot of [[MPI]] doesn't specify where something is and assumes [[this]], [[me]], or [[here]]. The result of this is needing to specify a location when using @mpi for testing. The same sort of issue occurs if your code is using {[[&cmd]]} or {[[&arg]]}. Examples of this are: | |
| - | A lot of [[MPI]] doesn't specify where something is and assumes [[this]], [[me]], or [[here]]. The result of this is needing to specify a location when using @mpi for testing. The same sort of issue occurs if your code is using {[[&cmd]]} or {[[&arg]]}. Examples of this are: | + | <mpi>@mpi {prop:someprop,me} |
| - | + | ||
| - | @mpi {prop:someprop,me} | + | |
@mpi {lcommon:{mklist:{name:me}},{list:AuthorizedUsers,here}} | @mpi {lcommon:{mklist:{name:me}},{list:AuthorizedUsers,here}} | ||
| - | @mpi {store:somevalue,someprop,#1234} «- #1234 is a dbref | + | @mpi {store:somevalue,someprop,#1234} «- #1234 is a dbref</mpi> |
| - | + | ||
| - | </ | + | |
The individual [[:Category:Functions (MPI)|MPI Functions]] do a good job of explaining which you can set a target with. | The individual [[:Category:Functions (MPI)|MPI Functions]] do a good job of explaining which you can set a target with. | ||
| + | |||
| + | [[Category:MUCK Commands]][[Category:Extended MUCK Commands]] | ||
Latest revision as of 14:49, 26 April 2007
The @mpi command is useful for testing bits of MPI without having to implement them on something. If can be particularly useful for quickly testing syntax and making sure all yours :'s ,'s and {}'s are in place. To use the command, simply type:
@mpi {some MPI}
The muck will attempt to interpret your MPI string at this point, and return the results or an error.
Setting Targets
A lot of MPI doesn't specify where something is and assumes this, me, or here. The result of this is needing to specify a location when using @mpi for testing. The same sort of issue occurs if your code is using {&cmd} or {&arg}. Examples of this are:
@mpi {prop:someprop,me} @mpi {lcommon:{mklist:{name:me}},{list:AuthorizedUsers,here}} @mpi {store:somevalue,someprop,#1234} «- #1234 is a dbref
The individual MPI Functions do a good job of explaining which you can set a target with.
