| … | |
… | |
| 16 | |
16 | |
| 17 | You should have received a copy of the GNU General Public License |
17 | You should have received a copy of the GNU General Public License |
| 18 | along with this program; if not, write to the Free Software |
18 | along with this program; if not, write to the Free Software |
| 19 | Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. |
19 | Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. |
| 20 | |
20 | |
| 21 | The authors can be reached via e-mail at crossfire-devel@real-time.com |
21 | The authors can be reached via e-mail at crossfire.de |
| 22 | */ |
22 | */ |
| 23 | |
23 | |
| 24 | /* This file contains various #defines that select various options. |
24 | /* This file contains various #defines that select various options. |
| 25 | * Some may not be desirable, and some just may not work. |
25 | * Some may not be desirable, and some just may not work. |
| 26 | * |
26 | * |
| … | |
… | |
| 66 | * DEBUG - more verbose message logging? |
66 | * DEBUG - more verbose message logging? |
| 67 | * MAP_CLIENT_X, MAP_CLIENT_Y - determines max size client map will receive |
67 | * MAP_CLIENT_X, MAP_CLIENT_Y - determines max size client map will receive |
| 68 | * MAX_TIME - how long an internal tick is in microseconds |
68 | * MAX_TIME - how long an internal tick is in microseconds |
| 69 | * MANY_CORES - generate core dumps on gross errors instead of continuing? |
69 | * MANY_CORES - generate core dumps on gross errors instead of continuing? |
| 70 | * PARTY_KILL_LOG - stores party kill information |
70 | * PARTY_KILL_LOG - stores party kill information |
| 71 | * WATCHDOG - allows use of an external watchdog program |
|
|
| 72 | * |
71 | * |
| 73 | ***********************************************************************/ |
72 | ***********************************************************************/ |
| 74 | |
73 | |
| 75 | /* Use a very easy, non-challenging server? |
74 | /* Use a very easy, non-challenging server? |
| 76 | * Defining the COZY_SERVER will make the server much less challenging: |
75 | * Defining the COZY_SERVER will make the server much less challenging: |
| … | |
… | |
| 253 | /* GD */ |
252 | /* GD */ |
| 254 | |
253 | |
| 255 | #define PERM_EXP_GAIN_RATIO 0.10f |
254 | #define PERM_EXP_GAIN_RATIO 0.10f |
| 256 | #define PERM_EXP_MAX_LOSS_RATIO 0.50f |
255 | #define PERM_EXP_MAX_LOSS_RATIO 0.50f |
| 257 | |
256 | |
| 258 | /* |
|
|
| 259 | * WATCHDOG lets sends datagrams to port 13325 on localhost |
|
|
| 260 | * in (more-or-less) regular intervals, so an external watchdog |
|
|
| 261 | * program can kill the server if it hangs (for whatever reason). |
|
|
| 262 | * It shouldn't hurt anyone if this is defined but you don't |
|
|
| 263 | * have an watchdog program. |
|
|
| 264 | */ |
|
|
| 265 | #define WATCHDOG |
|
|
| 266 | |
|
|
| 267 | /* Enable the new material code - it needs some work. You can |
257 | /* Enable the new material code - it needs some work. You can |
| 268 | * enable this, and things will work, just you'll see a whole |
258 | * enable this, and things will work, just you'll see a whole |
| 269 | * bunch more materials show up, and thus a whole bunch more materials |
259 | * bunch more materials show up, and thus a whole bunch more materials |
| 270 | * in your inventory, and the sorting for them isn't really good. |
260 | * in your inventory, and the sorting for them isn't really good. |
| 271 | */ |
261 | */ |
