MUCK Reference Guide/Building and Object Creation - Revision history

Marr0w at 16:57, 15 July 2019

2019-07-15T16:57:57Z

Marr0w: /* Fake Items */

2014-10-25T20:10:47Z

‎Fake Items

Marr0w: /* Deleting/Removing Rooms or Items */

2014-10-17T21:35:55Z

‎Deleting/Removing Rooms or Items

Marr0w: /* Deleting/Removing Rooms or Items */

2014-10-17T21:33:40Z

‎Deleting/Removing Rooms or Items

Marr0w: /* Deleting/Removing Rooms or Items */

2014-10-17T21:33:27Z

‎Deleting/Removing Rooms or Items

Marr0w: /* Deleting/Removing Rooms or Items */

2014-10-17T21:32:51Z

‎Deleting/Removing Rooms or Items

Marr0w at 21:32, 17 October 2014

2014-10-17T21:32:14Z

Marr0w at 23:56, 13 October 2014

2014-10-13T23:56:19Z

Marr0w: /* Fake Items */

2014-10-13T23:52:42Z

‎Fake Items

Marr0w: /* Fake Items */

2014-10-13T23:46:48Z

‎Fake Items

@@ Line 9: / Line 9: @@
   @open [exit name];[alt name1];[alt name 2]=[room dbref]
   @desc [room dbref]=[room description]
 </code></div>

@@ Line 66: / Line 66: @@
 <div style="width:45%;"><code>
-  @set [object]=/_Fake/[Object Name]/Ok?:yes
+  @set here=/_Fake/[Object Name]/Ok?:yes
-  @set [object]=/_Fake/[Object Name]/Name:[Object Name]
+  @set here=/_Fake/[Object Name]/Name:[Object Name]
-  @set [object]=/_Fake/[Object Name]/Desc:[Description]
+  @set here=/_Fake/[Object Name]/Desc:[Description]
-  @set [object]=/_Fake/[Object Name]/ANSIDesc:[ANSI Description]
+  @set here=/_Fake/[Object Name]/ANSIDesc:[ANSI Description]
-  @set [object]=/_Fake/[Object Name]/HTMLDesc:[HTML Description]
+  @set here=/_Fake/[Object Name]/HTMLDesc:[HTML Description]
 </code></div>

← Older revision		Revision as of 21:35, 17 October 2014
Line 81:		Line 81:
	Alternatively you can <code class="muck">@rec [Item Name]</code>. Because of spacing and abbreviating this is not recommended as there is always a greater chance of confusion this way. Using the dbref number is more exact. Just make sure you don't get the number wrong!		Alternatively you can <code class="muck">@rec [Item Name]</code>. Because of spacing and abbreviating this is not recommended as there is always a greater chance of confusion this way. Using the dbref number is more exact. Just make sure you don't get the number wrong!

		+	{{Note}} ''@rec'ing an object cannot be undone. Also, keep in mind that the next item created will inherit the dbref of the last object recycled.''

	----		----

@@ Line 77: / Line 77: @@
 So you've made a mistake or you just don't want that extra door to the bathroom in your bedroom. Well, the solution is simple: <code class="muck">@rec [#dbref]</code>. While staff can remove anything a player, or player with a build bit (depending on settings), can only remove objects they own.
-Let's say for example that we want to remove [[Johnny_C|Johnny's]] [[Johnny_C/Dread_Daggers|Dread Daggers]]. This item humorously has the dbref number of #666. All objects you own will show the dbref number in parenthesis after the item name. In this case it's <code class="muck">Happy Noodle Daggers(#666)</code>. To remove the daggers from the game we'd use the command <code class="muck">@rec #666</code> as long as you own the item. Alternatively you can <code class="muck">@rec [Item Name]</code>. Because of spacing and abbreviating this is not recommended as there is always a greater chance of confusion this way. Using the dbref number is more exact. Just make sure you don't get the number wrong!
+Let's say for example that we want to remove [[Johnny_C|Johnny's]] [[Johnny_C/Dread_Daggers|Dread Daggers]]. This item humorously has the dbref number of #666. All objects you own will show the dbref number in parenthesis after the item name. In this case it's <code class="muck">Happy Noodle Daggers(#666)</code>. To remove the daggers from the game we'd use the command <code class="muck">@rec #666</code> as long as you own the item.
 ----

@@ Line 77: / Line 77: @@
 So you've made a mistake or you just don't want that extra door to the bathroom in your bedroom. Well, the solution is simple: <code class="muck">@rec [#dbref]</code>. While staff can remove anything a player, or player with a build bit (depending on settings), can only remove objects they own.
-Let's say for example that we want to remove [[Johnny_C|Johnny's]] [[Johnny_C/Dread_Daggers|Dread Daggers]]. This item humorously has the dbref number of #666. All objects you own will show the dbref number in parenthesis after the item name. In this case it's <code class="muck">Happy Noodle Daggers(#666)</code>. If this where a room, you could teleport to it at anytime with the command <code class="muck">tel #666</code>. To remove the daggers from the game we'd use the command <code class="muck">@rec #666</code>. Alternatively you can <code class="muck">@rec [Item Name]</code>. Because of spacing and abbreviating this is not recommended as there is always a greater chance of confusion this way. Using the dbref number is more exact. Just make sure you don't get the number wrong!
+Let's say for example that we want to remove [[Johnny_C|Johnny's]] [[Johnny_C/Dread_Daggers|Dread Daggers]]. This item humorously has the dbref number of #666. All objects you own will show the dbref number in parenthesis after the item name. In this case it's <code class="muck">Happy Noodle Daggers(#666)</code>. To remove the daggers from the game we'd use the command <code class="muck">@rec #666</code> as long as you own the item. Alternatively you can <code class="muck">@rec [Item Name]</code>. Because of spacing and abbreviating this is not recommended as there is always a greater chance of confusion this way. Using the dbref number is more exact. Just make sure you don't get the number wrong!
 ----

@@ Line 65: / Line 65: @@
 Rather than creating objects for decoration in rooms and having to lock them down to prevent people from stealing them, you can just create a fake object. Fake items, or looktraps as they're actually called, are done very simply using @set and the information is stored in the room itself.
-<code class="muck">
+<code>
-@set here = _details/<name;alias1;alias2>:<description of object>
+  @set <object>=/_Fake/<Object Name>/Ok?:yes
 </code>
 ----

← Older revision		Revision as of 23:46, 13 October 2014
Line 69:		Line 69:
	</code>		</code>

		+	More information and examples can be found [http://www.rdwarf.com/users/mink/muckman/looktraps.html here].
	----		----