|
DataMuseum.dkPresents historical artifacts from the history of: DKUUG/EUUG Conference tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about DKUUG/EUUG Conference tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: T s
Length: 1569 (0x621) Types: TextFile Names: »scope.doc«
└─⟦b20c6495f⟧ Bits:30007238 EUUGD18: Wien-båndet, efterår 1987 └─⟦this⟧ »EUUGD18/General/Gb/Docs/scope.doc«
scope Galactic Bloodshed scope CONCEPT: scope Scope represents the ``operative scope'' of certain commands. The operative scope (displayed along with AP's in the user's prompt, and changed with ``cs'') is similar to the tree-like directory level structure found in most computer systems, with the ``root'' directory being a ``universal'' scope followed by the various stars followed by the planets orbiting these stars. The scope can also represent a single ship. Commands are effected by the scope in a different manner than that which most operating systems treat their directory structure. For example, if the current scope is that of a star, the command ``navigate'', if given with no arguments, will prompt for a destination for each ship orbiting that star and each planet in that system. If the scope was the ``universal'' scope, navigate would prompt for each ship everywhere that the player owns. Many commands will not work at all in certain scopes. The syntax of a scope, when prompted for, is thus: path = ``:'' | ``#shipnum'' | ``/path'' | ``../path'' | name | ``path/name'' The shell will interpret a ``:'' as meaning the object of the current scope (star, planet, ship, etc). A ``/'' at the beginning of the string represents the root. A ``..'' or ``.'' represents the scope just above the current scope. ``#shipnum'' represents that ship. A number by itself will be interpreted as meaning a star or planet name. Specifying a name means to move to that star or planet. SEE ALSO cs, navigate, actionpoints