version 1.45 | | version 1.46 |
---|
| | |
/* | | /* |
* static char *rcsid_config_h = | | * static char *rcsid_config_h = |
* "$Id: config.h,v 1.45 2002/11/26 07:55:24 garbled Exp $"; | | * "$Id: config.h,v 1.46 2002/11/26 08:08:00 garbled Exp $"; |
*/ | | */ |
| | |
/* | | /* |
| | |
* MAX_TIME - how long an internal tick is in microseconds | | * MAX_TIME - how long an internal tick is in microseconds |
* MANY_CORES - generate core dumps on gross errors instead of continuing? | | * MANY_CORES - generate core dumps on gross errors instead of continuing? |
* PARTY_KILL_LOG - stores party kill information | | * PARTY_KILL_LOG - stores party kill information |
* SECURE - Allow overriding values with run time flags? | | |
* WATCHDOG - allows use of an external watchdog program | | * WATCHDOG - allows use of an external watchdog program |
* | | * |
***********************************************************************/ | | ***********************************************************************/ |
| | |
#define PARTY_KILL_LOG 20 | | #define PARTY_KILL_LOG 20 |
*/ | | */ |
| | |
| | |
/* | | |
* If SECURE is defined, crossfire will not accept enviromental variables | | |
* as changes to the LIBDIR and other defines pointing to specific | | |
* directories. The only time this should really be an issue if you are | | |
* running crossfire setuid/setgid and someone else could change the | | |
* values and get special priveledges. If you are running with normal uid | | |
* privelidges, then this is not any more/less secure (user could compile | | |
* there own version pointing wherever they want.) However, having nonsecure | | |
* can make debugging or other developement much easier, because you can | | |
* change the paths without forcing a recompile. | | |
* | | |
* NOTE: Prior to 0.93.2, the default was for this to be defined (ie, | | |
* could not change values on the command line/through environmental | | |
* variables.) | | |
*/ | | |
/* | | |
#define SECURE | | |
*/ | | |
| | |
| | |
| | |
/* Use permanent experience code? | | /* Use permanent experience code? |
* This code allows players to build up a small amount of 'permanent | | * This code allows players to build up a small amount of 'permanent |
* experience' which reduces the effect of large experience drains, such as | | * experience' which reduces the effect of large experience drains, such as |
| | |
* CSPORT - port to use for new client/server | | * CSPORT - port to use for new client/server |
* DMFILE - file with dm/wizard access lists | | * DMFILE - file with dm/wizard access lists |
* DM_MAIL - address of server administrator | | * DM_MAIL - address of server administrator |
* DUMP_SWITCHES - enable -m? flags for spoiler generation | | |
* LIBDIR - location of archetypes & other data. | | * LIBDIR - location of archetypes & other data. |
* LOGFILE - where to log if using -daemon option | | * LOGFILE - where to log if using -daemon option |
* MAP_ - various map timeout and swapping parameters | | * MAP_ - various map timeout and swapping parameters |
| | |
#endif | | #endif |
| | |
| | |
/* | | |
* If you want to regenerate the spoiler.ps file, you have to recompile | | |
* the game with DUMP_SWITCHES defined. If defined, it turns on the | | |
* -m -m2 -m3 -m4 switches. There is probably no reason not to define | | |
* this | | |
*/ | | |
| | |
#define DUMP_SWITCHES | | |
| | |
/* LOGFILE specifies which file to log to when playing with the | | /* LOGFILE specifies which file to log to when playing with the |
* -daemon option. | | * -daemon option. |
*/ | | */ |