Search results
From LSWiki
You searched for Definitions
There is no page titled "Definitions". You can create this page.
For more information about searching LSWiki, see Searching LSWiki.
Showing below up to 20 results starting with #1.
View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500).
No page title matches
Page text matches
- Lost Souls directory structure (12,901 bytes)
34: ...system, tracking the armour type and armour style definitions; ''/daemon/weapons'' manages the weapon subsystem...
45: ...damage types are all examples of things that have definitions. This is a good directory to explore to see how ...
73: ...hat are automatically generated by the descriptor definitions in /def/descriptor are kept. Most header files a...
76: ...provided by various system daemons and descriptor definitions. As an example, ''/lib/services/services_affilia... - Daemon (1,953 bytes)
3: ...system, tracking the armour type and armour style definitions; /daemon/weapons manages the weapon subsystem, tr... - Basic map area definition example (1,516 bytes)
14: ...on or map ability. This can be shared with other definitions. - Low Priority Projects (11,858 bytes)
100: ...surroundings). With this, we can update the race definitions with various ranges of vision (heat vision to 10'... - Man functions (5,575 bytes)
37: - <arguments> is a list of variable definitions in the
142: efun-redefinitions which do not use the "nomask" modifier. - Man block (1,223 bytes)
12: Example definitions are:
22: ... of the block. Definitions in an inner block hide definitions in - Man dialog (15,179 bytes)
271: macros. The definitions below are given using the macro names, but with - Man input core (6,532 bytes)
18: definitions are heavily relied upon to determine the behavior...
20: input type definitions in /def/input. - Man shape (8,096 bytes)
17: ... descriptors are not intended to be fully precise definitions of the
24: Shape descriptors rely heavily on the geometry definitions managed through
60: at geometry definitions in /def/geometry to see which fields they use. A... - Man descriptors (13,902 bytes)
16: descriptor definitions or create new ones, you should review this docume...
37: ...onging_Usage. You can see the descriptor's field definitions at the
346: in the descriptor definitions, which live in /def/descriptor. - Man descriptors core (16,885 bytes)
51: ===Descriptor Definitions===
204: void set_descriptor_definitions(mapping spec)
206: Defines fields in the descriptor as referring to definitions. The keys
212: integer code for definitions that have them, a string key otherwise), and the
218: ...ields in the descriptor as referring to arrays of definitions. - Man hooks (mechanism) (6,851 bytes)
109: ...sed rather than an array despite the integer hook definitions because - Man selection (26,617 bytes)
32: ==Selection Definitions==
34: Selection definitions are arrays like that shown above. Within selecti...
35: definitions, three kinds of element occur: operators, designa...
150: by any race definitions. The value is expected to be a string
546: Materials: Items are object material definitions. - Man projects (4,912 bytes)
51: Definitions /d/Domain/Project/def Project_Definitio...
52: ...tion objects (set, show, start, stop, and channel definitions). - Man materials (2,440 bytes)
11: material definitions, /def/material. This document is to give you a q... - Haaru Map Extension (7,632 bytes)
60: =Creating your definitions=
62: ...ably want to do is create your definitions. Your definitions rely mostly on the file '''/std/def/map_feature''... - Coding Class: Dagger (3,903 bytes)
44: ... them here is because we are using the power of [[definitions]] to our advantage. We tell the object that it's... - Coding Class: Dagger II (4,204 bytes)
57: ...to spend time playing with the various macros and definitions and seeing how they affect the generated look of ... - Task System (7,956 bytes)
17: * broker for task type definitions - Map Extension (5,342 bytes)
9: ** The map_area definitions are used to specify the bulk of your area's conte...
13: ...broker daemon to collect and grant access to your definitions above.
39: ...ase we want to load and register all of our map_* definitions
44: ... // Same as the above, but used for unloading the definitions.
View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500).
