Examine
Command Information |
|
Keyword |
examine |
Type |
BuiltIn |
Arguments |
<object> |
<pattern> |
|
Usage |
examine |
examine <object> |
|
examine <object>=<pattern> |
Purpose
Examine the properties of an object.
Syntax
To examine the properties of the current room:
examine
To examine key data of an object:
examine <object>
To examine object properties matching a specified pattern:
examine <object>=<pattern>
Parameters
<object>
- The target object to retrieve vital object and/or property data for.
<pattern>
- An expression pattern used to display specific object properties.
Examples
Example 1
If Jaxen is standing in a room she doesn't own named Taproom and she wanted to view the vital object data for it, she would type:
examine
Jaxen would see:
Owner: Alkani
Example 2
If Alkani is standing in a room he owns named Taproom and he wanted to view the vital object data for it, he would type:
examine
Alkani would see:
Taproom (#99999RJ) Owner: Alkani Parent: Master Room (#99998RD) Type: ROOM Flags: JUMP_OK {eval:{list:/room/taproom/desc}} Key: *UNLOCKED* Chown_OK Key: *UNLOCKED* Container Key: *UNLOCKED* Force Key: *UNLOCKED* Created: Wed Nov 1 21:40:36 PDT 2017 Modified: Wed Nov 1 21:41:16 PDT 2017 Lastused: Wed Nov 1 22:01:36 PDT 2017 Usecount: 0 [ Use 'examine <object>=/' to list root properties. ] Memory used: 1080 bytes Contents: Alkani(#99997PBCJM1) No exits.
Example 3
If Lepus wanted to view the vital object data for an object he owned named Holographic Projector, he would type the following:
examine Holographic Projector
Lepus would see:
Holographic Projector(#99999) Owner: Lepus Value: 1 Type: THING Flags: Key: *UNLOCKED* Chown_OK Key: *UNLOCKED* Container Key: *UNLOCKED* Force Key: *UNLOCKED* Created: Wed Nov 1 19:04:42 PDT 2017 Modified: Wed Nov 1 19:38:00 PDT 2017 Lastused: Wed Nov 1 20:55:20 PDT 2017 Usecount: 3 [ Use 'examine <object>=/' to list root properties. ] Memory used: 1577 bytes Home: Lepus' Home (#99998RJ) Location: Lepus(#99997PBC) No actions attached.
Example 4
If Morticon wanted to view all of the base properties for an object called Automation Controller, they would type the following:
examine Automation Controller=/*
Morticon would see:
- dir /_/:(no value) - dir /obj/:(no value) - dir /ctrl/:(no value) - lok /chlk:Morticon(#99997PBC) - str /notes:Turn in SED board meeting minutes tomorrow 5 properties listed
Example 5
If Jaxen wanted a complete view of all properties for an object called Vinyl Album, she would type the following:
examine Vinyl Album=/**
Jaxen would see:
- dir /_/:(no value) - str /_/de:A dusty album sleeve with no image and a name, written in marker, faded by time. - dir /songlist/:(no value) - dir /songlist/tracks:(no value) - str /songlist/tracks/1 - Happy Days Are Here Again - str /songlist/tracks/2 - Why Yes! We Have No Bananas - str /songlist/tracks/3 - Brother, Can You Spare a Dime? - str /songlist/tracks/4 - Playmate - str /songlist/tracks/5 - Monday, Bread and Butter - str /songlist/tracks/6 - A Little Kiss Each Morning - str /songlist/tracks/7 - Stardust - str /songlist/tracks/8 - Goodnight, Moon 12 properties listed
Example 6
If Alkani had a specialized object named Disk Performance Monitor and wanted to view all of the disk serial numbers (SerNo), he would type:
examine Disk Performance Monitor=/obj/ddm/*/SerNo
Alkani would see:
- str /obj/ddm/16/SerNo:1S181YM0E0417AE40 - str /obj/ddm/17/SerNo:1S181YM0E0417AE47 - str /obj/ddm/18/SerNo:1S181YM0E0417BE29 - str /obj/ddm/26/SerNo:1S181YG1214174CD6 - str /obj/ddm/27/SerNo:1S181YG1214174A40 - str /obj/ddm/36/SerNo:1S121YM000417AE4F - str /obj/ddm/37/SerNo:1S181YM040417BC4E 7 properties listed.
Example 7
If Alkani had a specialized object named Disk Performance Monitor and wanted to view write performance entries (WritesPS and WritesIO) for disk drive modules (ddm) 16, 26, and 36, he would type:
examine Disk Performance Monitor=/obj/ddm/*6/Writes*
Alkani would see:
- str /obj/ddm/16/WritesIO:21 - str /obj/ddm/16/WritesPS:212 - str /obj/ddm/26/WritesIO:87 - str /obj/ddm/26/WritesPS:203 - str /obj/ddm/36/WritesIO:87 - str /obj/ddm/36/WritesPS:405 6 properties listed.
Caveats
The examine command is capable of examining the vital object data and properties of objects. A player may only get details on objects they own or control. Wizards may obtain this information for any object which exists in the SpinDizzy MUCK System.
Calling examine by itself defaults to using the player's current location of the object. This is the same as calling examine here manually to view the vital object data.
If the optional <pattern> parameter is supplied, object properties are displayed according to the specified parameters. The filter may include specific strings, the wildcard indicator *, and/or the greedy wildcard indicator **, as in the examples above.
Related
Properties - Information about Object Properties
lsprop - List Object Properties
Parent Topic
List of SpinDizzy MUCK System Built-In and Local Commands