Lost Souls directory structure - Revision history

http://wiki.lostsouls.org/w/index.php?action=history&feed=atom&title=Lost_Souls_directory_structure Lost Souls directory structure - Revision history 2026-04-30T15:51:23Z Revision history for this page on the wiki MediaWiki 1.8.2 http://wiki.lostsouls.org/w/index.php?title=Lost_Souls_directory_structure&diff=8878&oldid=prev Chaos at 23:11, 23 April 2008 2008-04-23T23:11:24Z

<p></p> <table border='0' width='98%' cellpadding='0' cellspacing='4' style="background-color: white;"> <tr> <td colspan='2' width='50%' align='center' style="background-color: white;">←Older revision</td> <td colspan='2' width='50%' align='center' style="background-color: white;">Revision as of 23:11, 23 April 2008</td> </tr> <tr><td colspan="2" align="left"><strong>Line 27:</strong></td> <td colspan="2" align="left"><strong>Line 27:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">===/d/''Various''===</td><td> </td><td style="background: #eee; font-size: smaller;">===/d/''Various''===</td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">Like Almeria, except not Almeria. Includes placeholders for other continents, some partially functional (/d/Tenochlan), others less so (/d/<span style="color: red; font-weight: bold;">Arrakis</span>), still others not really at all (/d/<span style="color: red; font-weight: bold;">Mordor</span>); other sorts of region (/d/Astra, which is meant to contain the Prime plane's outer space); and other planes of existence (/d/Exoma, /d/Umbra, /d/Amber).</td><td>+</td><td style="background: #cfc; font-size: smaller;">Like Almeria, except not Almeria. Includes placeholders for other continents, some partially functional (/d/Tenochlan), others less so (/d/<span style="color: red; font-weight: bold;">Akalahai</span>), still others not really at all (/d/<span style="color: red; font-weight: bold;">Esartur</span>); other sorts of region (/d/Astra, which is meant to contain the Prime plane's outer space); and other planes of existence (/d/Exoma, /d/Umbra, /d/Amber).</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">==/daemon==</td><td> </td><td style="background: #eee; font-size: smaller;">==/daemon==</td></tr> </table>

Chaos http://wiki.lostsouls.org/w/index.php?title=Lost_Souls_directory_structure&diff=4598&oldid=prev Chaos: /* /daemon */ 2007-09-06T02:27:42Z

<p><span class="autocomment">/daemon</span></p> <table border='0' width='98%' cellpadding='0' cellspacing='4' style="background-color: white;"> <tr> <td colspan='2' width='50%' align='center' style="background-color: white;">←Older revision</td> <td colspan='2' width='50%' align='center' style="background-color: white;">Revision as of 02:27, 6 September 2007</td> </tr> <tr><td colspan="2" align="left"><strong>Line 34:</strong></td> <td colspan="2" align="left"><strong>Line 34:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">''Chaos responds:'' Something like that. Our daemons are probably best understood by reference to Unix system daemons, which are programs that run continuously (usually) and handle some particular task; the most popular daemon is the HTTP daemon, or web server. Our daemons are similar: they're objects that hang out and handle some particular function. ''/daemon/armour'' manages the armour subsystem, tracking the armour type and armour style definitions; ''/daemon/weapons'' manages the weapon subsystem, tracking weapon types, weapon sizes, and ammunition types. These are examples of a class of daemon called '''broker daemons''' because their main function is handling definition objects and brokering requests for them; they're mainly found in /daemon. '''Control daemons''' are another major class; these live in the ~Project/dmn directories of individual projects, each serving as a central manager for its project. Other daemons just package up some similar functionality, such as ''/daemon/time''; some manage ongoing or specific-purpose processes of the game, such as ''/daemon/cron'', ''/daemon/autoheal'', and ''/daemon/shutdown''.</td><td> </td><td style="background: #eee; font-size: smaller;">''Chaos responds:'' Something like that. Our daemons are probably best understood by reference to Unix system daemons, which are programs that run continuously (usually) and handle some particular task; the most popular daemon is the HTTP daemon, or web server. Our daemons are similar: they're objects that hang out and handle some particular function. ''/daemon/armour'' manages the armour subsystem, tracking the armour type and armour style definitions; ''/daemon/weapons'' manages the weapon subsystem, tracking weapon types, weapon sizes, and ammunition types. These are examples of a class of daemon called '''broker daemons''' because their main function is handling definition objects and brokering requests for them; they're mainly found in /daemon. '''Control daemons''' are another major class; these live in the ~Project/dmn directories of individual projects, each serving as a central manager for its project. Other daemons just package up some similar functionality, such as ''/daemon/time''; some manage ongoing or specific-purpose processes of the game, such as ''/daemon/cron'', ''/daemon/autoheal'', and ''/daemon/shutdown''.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">Two of the universal characteristics of daemons is that they are never cloned and they are never in-game objects. I can conceive of circumstances that could create an exception to the former, but not the latter.</td><td>+</td><td style="background: #cfc; font-size: smaller;">Two of the universal characteristics of daemons is that they are never cloned and they are never in-game objects. I can conceive of circumstances that could create an <span style="color: red; font-weight: bold;">arguably legitimate </span>exception to the former, but not the latter.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">If you need to refer to a daemon that lives in /daemon in code, you will almost always be using the "service" macros for them, defined in ''/lib/services.h'' and its specific-purpose relatives in the ''/lib/services'' directory, which look like Daemon_Time, Daemon_Autoheal, Daemon_Shutdown, and so on. Another daemon, ''/daemon/services'', manages these. Besides being prettier than string pathnames, these use a special mechanism to make them faster than other methods you might use for referring to daemons.</td><td> </td><td style="background: #eee; font-size: smaller;">If you need to refer to a daemon that lives in /daemon in code, you will almost always be using the "service" macros for them, defined in ''/lib/services.h'' and its specific-purpose relatives in the ''/lib/services'' directory, which look like Daemon_Time, Daemon_Autoheal, Daemon_Shutdown, and so on. Another daemon, ''/daemon/services'', manages these. Besides being prettier than string pathnames, these use a special mechanism to make them faster than other methods you might use for referring to daemons.</td></tr> </table>

Chaos http://wiki.lostsouls.org/w/index.php?title=Lost_Souls_directory_structure&diff=1959&oldid=prev Chaos: /* /lib */ 2007-05-22T16:14:18Z

<p><span class="autocomment">/lib</span></p> <table border='0' width='98%' cellpadding='0' cellspacing='4' style="background-color: white;"> <tr> <td colspan='2' width='50%' align='center' style="background-color: white;">←Older revision</td> <td colspan='2' width='50%' align='center' style="background-color: white;">Revision as of 16:14, 22 May 2007</td> </tr> <tr><td colspan="2" align="left"><strong>Line 72:</strong></td> <td colspan="2" align="left"><strong>Line 72:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">===/lib/descriptors===</td><td> </td><td style="background: #eee; font-size: smaller;">===/lib/descriptors===</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">This is where the header files that are automatically generated by the descriptor definitions in /def/descriptor are kept. Most header files are manually maintained; these are unusual in being created by the system.</td><td> </td><td style="background: #eee; font-size: smaller;">This is where the header files that are automatically generated by the descriptor definitions in /def/descriptor are kept. Most header files are manually maintained; these are unusual in being created by the system.</td></tr> <tr><td colspan="2"> </td><td>+</td><td style="background: #cfc; font-size: smaller;"></td></tr> <tr><td colspan="2"> </td><td>+</td><td style="background: #cfc; font-size: smaller;">===/lib/services===</td></tr> <tr><td colspan="2"> </td><td>+</td><td style="background: #cfc; font-size: smaller;">This directory contains header files created by ''/daemon/services'' to provide optimized access to "service" functions provided by various system daemons and descriptor definitions. As an example, ''/lib/services/services_affiliations.h'' is automatically generated based on information extracted from ''/daemon/affiliations''; it provides macros for addressing ''/daemon/affiliations'' itself and for using some service functionality provided by it.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">==/mod==</td><td> </td><td style="background: #eee; font-size: smaller;">==/mod==</td></tr> </table>

Chaos http://wiki.lostsouls.org/w/index.php?title=Lost_Souls_directory_structure&diff=1958&oldid=prev Chaos: /* /daemon */ 2007-05-22T16:09:30Z

<p><span class="autocomment">/daemon</span></p> <table border='0' width='98%' cellpadding='0' cellspacing='4' style="background-color: white;"> <tr> <td colspan='2' width='50%' align='center' style="background-color: white;">←Older revision</td> <td colspan='2' width='50%' align='center' style="background-color: white;">Revision as of 16:09, 22 May 2007</td> </tr> <tr><td colspan="2" align="left"><strong>Line 36:</strong></td> <td colspan="2" align="left"><strong>Line 36:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">Two of the universal characteristics of daemons is that they are never cloned and they are never in-game objects. I can conceive of circumstances that could create an exception to the former, but not the latter.</td><td> </td><td style="background: #eee; font-size: smaller;">Two of the universal characteristics of daemons is that they are never cloned and they are never in-game objects. I can conceive of circumstances that could create an exception to the former, but not the latter.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">If you need to refer to a daemon that lives in /daemon in code, you will almost always be using the "service" macros for them, defined in ''/lib/services.h'', which look like Daemon_Time, Daemon_Autoheal, Daemon_Shutdown, and so on. Another daemon, ''/daemon/services'', manages these. Besides being prettier than string pathnames, these use a special mechanism to make them faster than other methods you might use for referring to daemons.</td><td>+</td><td style="background: #cfc; font-size: smaller;">If you need to refer to a daemon that lives in /daemon in code, you will almost always be using the "service" macros for them, defined in ''/lib/services.h'' <span style="color: red; font-weight: bold;">and its specific-purpose relatives in the ''/lib/services'' directory</span>, which look like Daemon_Time, Daemon_Autoheal, Daemon_Shutdown, and so on. Another daemon, ''/daemon/services'', manages these. Besides being prettier than string pathnames, these use a special mechanism to make them faster than other methods you might use for referring to daemons.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">Read access [[privileges|privilege]]: [[privileges#read_lib|read_lib]]</td><td> </td><td style="background: #eee; font-size: smaller;">Read access [[privileges|privilege]]: [[privileges#read_lib|read_lib]]</td></tr> </table>

Chaos http://wiki.lostsouls.org/w/index.php?title=Lost_Souls_directory_structure&diff=1620&oldid=prev Chaos at 10:50, 17 January 2007 2007-01-17T10:50:32Z

<p></p> <table border='0' width='98%' cellpadding='0' cellspacing='4' style="background-color: white;"> <tr> <td colspan='2' width='50%' align='center' style="background-color: white;">←Older revision</td> <td colspan='2' width='50%' align='center' style="background-color: white;">Revision as of 10:50, 17 January 2007</td> </tr> <tr><td colspan="2" align="left"><strong>Line 1:</strong></td> <td colspan="2" align="left"><strong>Line 1:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">This structure of this file mirror the LS directory structure. If you don't know how to navigate the directory structure, please read the [[Developer Primer]].</td><td> </td><td style="background: #eee; font-size: smaller;">This structure of this file mirror the LS directory structure. If you don't know how to navigate the directory structure, please read the [[Developer Primer]].</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">Occasionally you will see references to "the lib" and "Ain Soph". "Lib" is short for "mudlib", which is the set of files that the MUD uses as a base to work from. The official name of the mudlib that Lost Souls runs under is Ain Soph.</td><td>+</td><td style="background: #cfc; font-size: smaller;">Occasionally you will see references to "the lib" and "Ain Soph". "Lib" is short for "mudlib", which is the set of files that the MUD uses as a base to work from. The official name of the mudlib that Lost Souls runs under is Ain Soph<span style="color: red; font-weight: bold;">. There is a distinction between "lib" and "content" code; particular projects in the game are content, while the abstract support for rooms, items, and so on that they draw on is lib code. Or, to put it another way, a particular broadsword is content, while the general concept of broadswords is lib code</span>.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">==/d==</td><td> </td><td style="background: #eee; font-size: smaller;">==/d==</td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">This is where the <span style="color: red; font-weight: bold;">world </span>is. The "d" stands for "domain", which apparently used to mean something. Chaos claims that this stands for "deployed", but we all know he's a dirty liar.</td><td>+</td><td style="background: #cfc; font-size: smaller;">This is where the <span style="color: red; font-weight: bold;">majority of content </span>is. The "d" stands for "domain", which apparently used to mean something. Chaos claims that this stands for "deployed", but we all know he's a dirty liar.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">Read access [[privileges|privilege]]: [[privileges#read_d|read_d]]</td><td> </td><td style="background: #eee; font-size: smaller;">Read access [[privileges|privilege]]: [[privileges#read_d|read_d]]</td></tr> <tr><td colspan="2" align="left"><strong>Line 81:</strong></td> <td colspan="2" align="left"><strong>Line 81:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">==/obj==</td><td> </td><td style="background: #eee; font-size: smaller;">==/obj==</td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">This hierarchy mainly contains files that are intended to be physical objects in the game world; weapons, armour, comestibles, and so on. There are a few special <span style="color: red; font-weight: bold;">cases</span>.</td><td>+</td><td style="background: #cfc; font-size: smaller;">This hierarchy mainly contains files that are intended to be physical objects in the game world; weapons, armour, comestibles, and so on<span style="color: red; font-weight: bold;">. Files here mostly represent the intersection of lib and content; they are in-game content that's centralized at the lib level rather than belonging to any particular project</span>. There are a few special<span style="color: red; font-weight: bold;">-case directories under this hierarchy that are used for notably different purposes, however</span>.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">Read access [[privileges|privilege]]: [[privileges#read_lib|read_lib]]</td><td> </td><td style="background: #eee; font-size: smaller;">Read access [[privileges|privilege]]: [[privileges#read_lib|read_lib]]</td></tr> </table>

Chaos http://wiki.lostsouls.org/w/index.php?title=Lost_Souls_directory_structure&diff=1619&oldid=prev Chaos at 10:44, 17 January 2007 2007-01-17T10:44:53Z

<p></p> <table border='0' width='98%' cellpadding='0' cellspacing='4' style="background-color: white;"> <tr> <td colspan='2' width='50%' align='center' style="background-color: white;">←Older revision</td> <td colspan='2' width='50%' align='center' style="background-color: white;">Revision as of 10:44, 17 January 2007</td> </tr> <tr><td colspan="2" align="left"><strong>Line 1:</strong></td> <td colspan="2" align="left"><strong>Line 1:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">This structure of this file mirror the LS directory structure. If you don't know how to navigate the directory structure, please read the [[Developer Primer]].</td><td> </td><td style="background: #eee; font-size: smaller;">This structure of this file mirror the LS directory structure. If you don't know how to navigate the directory structure, please read the [[Developer Primer]].</td></tr> <tr><td colspan="2"> </td><td>+</td><td style="background: #cfc; font-size: smaller;"></td></tr> <tr><td colspan="2"> </td><td>+</td><td style="background: #cfc; font-size: smaller;">Occasionally you will see references to "the lib" and "Ain Soph". "Lib" is short for "mudlib", which is the set of files that the MUD uses as a base to work from. The official name of the mudlib that Lost Souls runs under is Ain Soph.</td></tr> <tr><td colspan="2"> </td><td>+</td><td style="background: #cfc; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">==/d==</td><td> </td><td style="background: #eee; font-size: smaller;">==/d==</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">This is where the world is. The "d" stands for "domain", which apparently used to mean something. Chaos claims that this stands for "deployed", but we all know he's a dirty liar.</td><td> </td><td style="background: #eee; font-size: smaller;">This is where the world is. The "d" stands for "domain", which apparently used to mean something. Chaos claims that this stands for "deployed", but we all know he's a dirty liar.</td></tr> </table>

Chaos http://wiki.lostsouls.org/w/index.php?title=Lost_Souls_directory_structure&diff=1618&oldid=prev Chaos: /* /def */ 2007-01-17T10:43:06Z

<p><span class="autocomment">/def</span></p> <table border='0' width='98%' cellpadding='0' cellspacing='4' style="background-color: white;"> <tr> <td colspan='2' width='50%' align='center' style="background-color: white;">←Older revision</td> <td colspan='2' width='50%' align='center' style="background-color: white;">Revision as of 10:43, 17 January 2007</td> </tr> <tr><td colspan="2" align="left"><strong>Line 40:</strong></td> <td colspan="2" align="left"><strong>Line 40:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">==/def==</td><td> </td><td style="background: #eee; font-size: smaller;">==/def==</td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">This is where definition files reside. Definitions are abstract files that determine certain generic properties of particular files. Races, anatomies, weapon types and damage types are all examples of things that have definitions.</td><td>+</td><td style="background: #cfc; font-size: smaller;">This is where <span style="color: red; font-weight: bold;">system-level </span>definition files reside. Definitions are abstract files that determine certain generic properties of particular files. <span style="color: red; font-weight: bold;"> </span>Races, anatomies, weapon types and damage types are all examples of things that have definitions<span style="color: red; font-weight: bold;">. This is a good directory to explore to see how the lib is set up</span>.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">Read access [[privileges|privilege]]: [[privileges#read_lib|read_lib]]</td><td> </td><td style="background: #eee; font-size: smaller;">Read access [[privileges|privilege]]: [[privileges#read_lib|read_lib]]</td></tr> </table>

Chaos http://wiki.lostsouls.org/w/index.php?title=Lost_Souls_directory_structure&diff=1617&oldid=prev Chaos: /* /def */ 2007-01-17T10:41:43Z

<p><span class="autocomment">/def</span></p> <table border='0' width='98%' cellpadding='0' cellspacing='4' style="background-color: white;"> <tr> <td colspan='2' width='50%' align='center' style="background-color: white;">←Older revision</td> <td colspan='2' width='50%' align='center' style="background-color: white;">Revision as of 10:41, 17 January 2007</td> </tr> <tr><td colspan="2" align="left"><strong>Line 40:</strong></td> <td colspan="2" align="left"><strong>Line 40:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">==/def==</td><td> </td><td style="background: #eee; font-size: smaller;">==/def==</td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">This is where definition files reside. Definitions are abstract files that determine certain generic properties of particular files. Races, anatomies, weapon types<span style="color: red; font-weight: bold;">, </span>damage types<span style="color: red; font-weight: bold;">, </span>are all examples of things that have definitions.</td><td>+</td><td style="background: #cfc; font-size: smaller;">This is where definition files reside. Definitions are abstract files that determine certain generic properties of particular files. Races, anatomies, weapon types <span style="color: red; font-weight: bold;">and </span>damage types are all examples of things that have definitions.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">Read access [[privileges|privilege]]: [[privileges#read_lib|read_lib]]</td><td> </td><td style="background: #eee; font-size: smaller;">Read access [[privileges|privilege]]: [[privileges#read_lib|read_lib]]</td></tr> </table>

Chaos http://wiki.lostsouls.org/w/index.php?title=Lost_Souls_directory_structure&diff=1616&oldid=prev Chaos: /* /daemon */ 2007-01-17T10:40:56Z

<p><span class="autocomment">/daemon</span></p> <table border='0' width='98%' cellpadding='0' cellspacing='4' style="background-color: white;"> <tr> <td colspan='2' width='50%' align='center' style="background-color: white;">←Older revision</td> <td colspan='2' width='50%' align='center' style="background-color: white;">Revision as of 10:40, 17 January 2007</td> </tr> <tr><td colspan="2" align="left"><strong>Line 31:</strong></td> <td colspan="2" align="left"><strong>Line 31:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">''Chaos responds:'' Something like that. Our daemons are probably best understood by reference to Unix system daemons, which are programs that run continuously (usually) and handle some particular task; the most popular daemon is the HTTP daemon, or web server. Our daemons are similar: they're objects that hang out and handle some particular function. ''/daemon/armour'' manages the armour subsystem, tracking the armour type and armour style definitions; ''/daemon/weapons'' manages the weapon subsystem, tracking weapon types, weapon sizes, and ammunition types. These are examples of a class of daemon called '''broker daemons''' because their main function is handling definition objects and brokering requests for them; they're mainly found in /daemon. '''Control daemons''' are another major class; these live in the ~Project/dmn directories of individual projects, each serving as a central manager for its project. Other daemons just package up some similar functionality, such as ''/daemon/time''; some manage ongoing or specific-purpose processes of the game, such as ''/daemon/cron'', ''/daemon/autoheal'', and ''/daemon/shutdown''.</td><td> </td><td style="background: #eee; font-size: smaller;">''Chaos responds:'' Something like that. Our daemons are probably best understood by reference to Unix system daemons, which are programs that run continuously (usually) and handle some particular task; the most popular daemon is the HTTP daemon, or web server. Our daemons are similar: they're objects that hang out and handle some particular function. ''/daemon/armour'' manages the armour subsystem, tracking the armour type and armour style definitions; ''/daemon/weapons'' manages the weapon subsystem, tracking weapon types, weapon sizes, and ammunition types. These are examples of a class of daemon called '''broker daemons''' because their main function is handling definition objects and brokering requests for them; they're mainly found in /daemon. '''Control daemons''' are another major class; these live in the ~Project/dmn directories of individual projects, each serving as a central manager for its project. Other daemons just package up some similar functionality, such as ''/daemon/time''; some manage ongoing or specific-purpose processes of the game, such as ''/daemon/cron'', ''/daemon/autoheal'', and ''/daemon/shutdown''.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">Two of the universal characteristics of daemons is that they are never cloned and they are never in-game <span style="color: red; font-weight: bold;">items</span>. I can conceive of circumstances that could create an exception to the former, but not the latter.</td><td>+</td><td style="background: #cfc; font-size: smaller;">Two of the universal characteristics of daemons is that they are never cloned and they are never in-game <span style="color: red; font-weight: bold;">objects</span>. I can conceive of circumstances that could create an exception to the former, but not the latter.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">If you need to refer to a daemon that lives in /daemon in code, you will almost always be using the "service" macros for them, defined in ''/lib/services.h'', which look like Daemon_Time, Daemon_Autoheal, Daemon_Shutdown, and so on. Another daemon, ''/daemon/services'', manages these. Besides being prettier than string pathnames, these use a special mechanism to make them faster than other methods you might use for referring to daemons.</td><td> </td><td style="background: #eee; font-size: smaller;">If you need to refer to a daemon that lives in /daemon in code, you will almost always be using the "service" macros for them, defined in ''/lib/services.h'', which look like Daemon_Time, Daemon_Autoheal, Daemon_Shutdown, and so on. Another daemon, ''/daemon/services'', manages these. Besides being prettier than string pathnames, these use a special mechanism to make them faster than other methods you might use for referring to daemons.</td></tr> </table>

Chaos http://wiki.lostsouls.org/w/index.php?title=Lost_Souls_directory_structure&diff=1615&oldid=prev Chaos: /* /daemon */ 2007-01-17T10:40:09Z

<p><span class="autocomment">/daemon</span></p> <table border='0' width='98%' cellpadding='0' cellspacing='4' style="background-color: white;"> <tr> <td colspan='2' width='50%' align='center' style="background-color: white;">←Older revision</td> <td colspan='2' width='50%' align='center' style="background-color: white;">Revision as of 10:40, 17 January 2007</td> </tr> <tr><td colspan="2" align="left"><strong>Line 29:</strong></td> <td colspan="2" align="left"><strong>Line 29:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">''Twilight writes:'' This is where daemons are. What are daemons you ask? Good question. Basically I think they are objects that control, handle, and store data. Right?</td><td> </td><td style="background: #eee; font-size: smaller;">''Twilight writes:'' This is where daemons are. What are daemons you ask? Good question. Basically I think they are objects that control, handle, and store data. Right?</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">''Chaos responds:'' Something like that. Our daemons are probably best understood by reference to Unix system daemons, which are programs that run continuously (usually) and handle some particular task; the most popular daemon is the HTTP daemon, or web server. Our daemons are similar: they're objects that hang out and handle some particular function. ''/daemon/armour'' manages the armour subsystem, tracking the armour type and armour style definitions; ''/daemon/weapons'' manages the weapon subsystem, tracking weapon types, weapon sizes, and ammunition types. These are examples of a class of daemon called '''broker daemons''' because their main function is handling definition objects and brokering requests for them; they're mainly found in /daemon. '''Control daemons''' are another major class; these live in the ~Project/dmn directories of individual projects <span style="color: red; font-weight: bold;">and serve </span>as central <span style="color: red; font-weight: bold;">managers </span>for <span style="color: red; font-weight: bold;">the </span>project. Other daemons just package up some similar functionality, such as ''/daemon/time''; some manage ongoing or specific-purpose processes of the game, such as ''/daemon/cron'', ''/daemon/autoheal'', and ''/daemon/shutdown''.</td><td>+</td><td style="background: #cfc; font-size: smaller;">''Chaos responds:'' Something like that. Our daemons are probably best understood by reference to Unix system daemons, which are programs that run continuously (usually) and handle some particular task; the most popular daemon is the HTTP daemon, or web server. Our daemons are similar: they're objects that hang out and handle some particular function. ''/daemon/armour'' manages the armour subsystem, tracking the armour type and armour style definitions; ''/daemon/weapons'' manages the weapon subsystem, tracking weapon types, weapon sizes, and ammunition types. These are examples of a class of daemon called '''broker daemons''' because their main function is handling definition objects and brokering requests for them; they're mainly found in /daemon. '''Control daemons''' are another major class; these live in the ~Project/dmn directories of individual projects<span style="color: red; font-weight: bold;">, each serving </span>as <span style="color: red; font-weight: bold;">a </span>central <span style="color: red; font-weight: bold;">manager </span>for <span style="color: red; font-weight: bold;">its </span>project. Other daemons just package up some similar functionality, such as ''/daemon/time''; some manage ongoing or specific-purpose processes of the game, such as ''/daemon/cron'', ''/daemon/autoheal'', and ''/daemon/shutdown''.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">Two of the universal characteristics of daemons is that they are never cloned and they are never in-game items. I can conceive of circumstances that could create an exception to the former, but not the latter.</td><td> </td><td style="background: #eee; font-size: smaller;">Two of the universal characteristics of daemons is that they are never cloned and they are never in-game items. I can conceive of circumstances that could create an exception to the former, but not the latter.</td></tr> </table>

Chaos