AbilitiesObjectObject ProgrammingValueIndexLibrary
[ First Topic | Previous Topic | Next Topic | Last Topic | Index | Library ]

Object Identifier Object Identifier

Object identifiers are used to uniquely identify each object within the simulation's database. The abstract TIdentifier object grants this functionality to all descendent objects. Each identifier is composed of a 100-digit code that expresses the class name and the geographic location of each object within the simulation. All tables containing TIdentifier descendents are indexed based on the TIdentifier.ObjectKey property, which is a 100-character persistent string value.

The following chart lists all the segments of the TIdentifier.ObjectKey property:

Icon Segment Length Description
Class Name 40 The class name is derived from the Object PASCAL TObject.ClassName property, which is converted to upper case, and truncated to exactly 40 characters. This corresponds to the TMZObject.ClassName property, the persistent version of the TObject.ClassName property. There is a many-to-one correspondence between an object's ClassName and the table in which the object's persistent property values are stored. This directly links the Delphi Visual Component Library (VCL) and the MUDzilla Class Library (MCL).
Plane of Existence 10 MUDzilla organizes the Multiverse into a four-tiered hierarchy of geographical divisions, as expressed by the TDivision object. At the top of this hierarchy are the planes of existence. This 10-digit number is the identifier of the Plane of Existence in which the object was created, as expressed by the TPlane object.
Continent 10 This segment of the object identifier stores the 10-digit number associated with the continent in which the object was created, as expressed by the TContinent object.
Domain 10 This segment of the object identifier stores the 10-digit number associated with the domain in which the object was created, as expressed by the TDomain object.
County 10 This segment of the object identifier stores the 10-digit number associated with the county in which the object was created, as expressed by the TCounty object.
Identifier 20 This segment of the object identifier stores the 20-digit number associated with a unique identifier, TDivision.NextID. When an object is created, the current County's NextID property is used to assign the identifier segment of an object key. With 20 digits, up to 1020 objects of any class can exist concurrently per county.

Complete object names are expressed in dotted notation, starting with the simulation-specific name of an object (TIdentifier.MZName), followed by all the divisions from County to Plane of Existence, as in:

My Tower.City of New Zian.Zian.Fornae.Tolerien

Complete MCL names add the object's class name at the end of the string. as in:

My Tower.City of New Zian.Zian.Fornae.Tolerien.TROOM

See Also See Also:


AbilitiesObjectObject ProgrammingValueIndexLibrary
[ First Topic | Previous Topic | Next Topic | Last Topic | Index | Library ]


The MUDzilla Simulation System
Please e-mail us your comments and inquiries.
© 1994-2002 Myne Corporation

Myne Corporation