1 |
/* |
2 |
CrossFire, A Multiplayer game for X-windows |
3 |
|
4 |
Copyright (C) 2002 Mark Wedel & Crossfire Development Team |
5 |
Copyright (C) 1992 Frank Tore Johansen |
6 |
|
7 |
This program is free software; you can redistribute it and/or modify |
8 |
it under the terms of the GNU General Public License as published by |
9 |
the Free Software Foundation; either version 2 of the License, or |
10 |
(at your option) any later version. |
11 |
|
12 |
This program is distributed in the hope that it will be useful, |
13 |
but WITHOUT ANY WARRANTY; without even the implied warranty of |
14 |
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
15 |
GNU General Public License for more details. |
16 |
|
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 |
19 |
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. |
20 |
|
21 |
The authors can be reached via e-mail at crossfire-devel@real-time.com |
22 |
*/ |
23 |
|
24 |
/* This file contains various #defines that select various options. |
25 |
* Some may not be desirable, and some just may not work. |
26 |
* |
27 |
* There are some options that are not selectable in this file which |
28 |
* may not always be undesirable. An example would be certain |
29 |
* treasures that you may not want to have available. To remove the |
30 |
* activation code would make these items worthless - instead remove |
31 |
* these from the treasure file. Some things to look for are: |
32 |
* |
33 |
* prepare_weapon, improve_*: Allow characters to enchant their own |
34 |
* weapons |
35 |
* ench_armour: Allow characters to enchant their armor. |
36 |
* |
37 |
* In theory, most of the values here should just be defaults, and |
38 |
* everything here should just be selectable by different run time |
39 |
* flags However, for some things, that would just be too messy. |
40 |
*/ |
41 |
|
42 |
/* There are 4 main sections to this file- |
43 |
* Section 1 is feature selection (enabling/disabling certain features) |
44 |
* |
45 |
* Section 2 is compiler/machine dependant section (stuff that just |
46 |
* makes the program compile and run properly, but don't change the |
47 |
* behavior) |
48 |
* |
49 |
* Section 3 is location of certain files and other defaults. Things in |
50 |
* this section generally do not need to be changed, and generally do |
51 |
* not alter the play as perceived by players. However, you may |
52 |
* have your own values you want to set here. |
53 |
* |
54 |
* Section 4 deals with save file related options. |
55 |
*/ |
56 |
|
57 |
/******************************************************************* |
58 |
* SECTION 1 - FEATURES |
59 |
* |
60 |
* You don't have to change anything here to get a working program, but |
61 |
* you may want to on personal preferance. Items are arranged |
62 |
* alphabetically. |
63 |
* |
64 |
* Short list of features, and what to search for: |
65 |
* CS_LOGSTATS - log various new client/server data. |
66 |
* DEBUG - more verbose message logging? |
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 |
69 |
* MANY_CORES - generate core dumps on gross errors instead of continuing? |
70 |
* PARTY_KILL_LOG - stores party kill information |
71 |
* WATCHDOG - allows use of an external watchdog program |
72 |
* |
73 |
***********************************************************************/ |
74 |
|
75 |
/* Use a very easy, non-challenging server? |
76 |
* Defining the COZY_SERVER will make the server much less challenging: |
77 |
* no stats loss on death, much less experience loss, and party members |
78 |
* are treated by pet monsters as the owner itself when moving "through" them. |
79 |
*/ |
80 |
#define COZY_SERVER 1 |
81 |
|
82 |
/* |
83 |
* Make it impossible to pk outside the arena. |
84 |
*/ |
85 |
#define PROHIBIT_PLAYERKILL 1 |
86 |
|
87 |
/* Use balanced stat loss code? |
88 |
* This code is a little more merciful with repeated stat loss at lower |
89 |
* levels. Basically, the more stats you have lost, the less likely that |
90 |
* you will lose more. Additionally, lower level characters are shown |
91 |
* a lot more mercy (there are caps on how much of a stat you can lose too). |
92 |
* On the nasty side, if you are higher level, you can lose mutiple stats |
93 |
* _at_once_ and are shown less mercy when you die. But when you're higher |
94 |
* level, it is much easier to buy back your stats with potions. |
95 |
* Turn this on if you want death-based stat loss to be more merciful |
96 |
* at low levels and more cruel at high levels. |
97 |
* Only works when stats are depleted rather than lost. This option has |
98 |
* no effect if you are using genuine stat loss. |
99 |
* |
100 |
* The BALSL_.. values control this behaviour. |
101 |
* BALSL_NUMBER_LOSSES_RATIO determines the number of stats to lose. |
102 |
* the character level is divided by that value, and that is how many |
103 |
* stats are lost. |
104 |
* |
105 |
* BALSL_MAX_LOSS_RATIO puts the upper limit on depletion of a stat - |
106 |
* basically, level/max_loss_ratio is the most a stat can be depleted. |
107 |
* |
108 |
* BALSL_LOSS_CHANCE_RATIO controls how likely it is a stat is depleted. |
109 |
* The chance not to lose a stat is |
110 |
* depleteness^2 / (depletedness^2+ level/ratio). |
111 |
* ie, if the stats current depleted value is 2 and the character is level |
112 |
* 15, the chance not to lose the stat is 4/(4+3) or 4/7. The higher the |
113 |
* level, the more likely it is a stat can get really depleted, but |
114 |
* this gets more offset as the stat gets more depleted. |
115 |
* |
116 |
*/ |
117 |
/* GD */ |
118 |
|
119 |
#define BALSL_LOSS_CHANCE_RATIO 100 |
120 |
#define BALSL_NUMBER_LOSSES_RATIO 100 |
121 |
#define BALSL_MAX_LOSS_RATIO 100 |
122 |
|
123 |
|
124 |
/* Don't edit these values. They are configured in lib/settings. These are |
125 |
Simply the defaults. */ |
126 |
|
127 |
#define BALANCED_STAT_LOSS FALSE |
128 |
#define PERMANENT_EXPERIENCE_RATIO 25 |
129 |
#define DEATH_PENALTY_RATIO 20 |
130 |
#define DEATH_PENALTY_LEVEL 3 |
131 |
#define SET_TITLE TRUE |
132 |
#define SIMPLE_EXP TRUE |
133 |
#define SPELLPOINT_LEVEL_DEPEND TRUE |
134 |
#define SPELL_ENCUMBRANCE TRUE |
135 |
#define SPELL_FAILURE_EFFECTS FALSE |
136 |
#define REAL_WIZ TRUE |
137 |
#define RECYCLE_TMP_MAPS FALSE |
138 |
#define RESURRECTION FALSE |
139 |
#define SEARCH_ITEMS TRUE |
140 |
#define NOT_PERMADETH TRUE |
141 |
#define EXPLORE_MODE FALSE |
142 |
#define STAT_LOSS_ON_DEATH FALSE |
143 |
#define PK_LUCK_PENALTY 1 |
144 |
#define CASTING_TIME FALSE |
145 |
#define SET_FRIENDLY_FIRE 5 |
146 |
#define ARMOR_MAX_ENCHANT 5 |
147 |
#define ARMOR_WEIGHT_REDUCTION 10 |
148 |
#define ARMOR_WEIGHT_LINEAR TRUE |
149 |
#define ARMOR_SPEED_IMPROVEMENT 10 |
150 |
#define ARMOR_SPEED_LINEAR TRUE |
151 |
#define CREATE_HOME_PORTALS FALSE |
152 |
|
153 |
/* you can edit the ones below */ |
154 |
|
155 |
|
156 |
/* CS_LOGSTATS will cause the server to log various usage stats |
157 |
* (number of connections, amount of data sent, amount of data received, |
158 |
* and so on.) This can be very useful if you are trying to measure |
159 |
* server/bandwidth usage. It will periodially dump out information |
160 |
* which contains usage stats for the last X amount of time. |
161 |
* CS_LOGTIME is how often it will print out stats. |
162 |
*/ |
163 |
#ifndef WIN32 /* ***win32 we set the following stuff in the IDE */ |
164 |
#define CS_LOGSTATS |
165 |
#endif |
166 |
#ifdef CS_LOGSTATS |
167 |
#define CS_LOGTIME 600 |
168 |
#endif |
169 |
|
170 |
/* DEBUG generates copious amounts of output. I tend to change the CC options |
171 |
* in the crosssite.def file if I want this. By default, you probably |
172 |
* dont want this defined. |
173 |
*/ |
174 |
#ifndef WIN32 /* ***win32 we set the following stuff in the IDE */ |
175 |
#ifndef DEBUG |
176 |
#define DEBUG |
177 |
#endif |
178 |
#endif |
179 |
/* |
180 |
* This option creates more core files. In some areas, there are certain |
181 |
* checks done to try and make the program more stable (ie, check |
182 |
* parameter for null, return if it is). These checks are being done |
183 |
* for things that should not happen (ie, being supplied a null parameter). |
184 |
* What MANY_CORES does, is if one of these checks is true, it will |
185 |
* dump core at that time, allowing for fairly easy tracking down of the |
186 |
* problem. Better to fix problems than create thousands of checks. |
187 |
*/ |
188 |
|
189 |
#define MANY_CORES |
190 |
|
191 |
/* |
192 |
* This determines the maximum map size the client can request (and |
193 |
* thus what the server will send to the client. |
194 |
* Client can still request a smaller map size (for bandwidth reasons |
195 |
* or display size of whatever else). |
196 |
* The larger this number, the more cpu time and memory the server will |
197 |
* need to spend to figure this out in addition to bandwidth needs. |
198 |
* The server cpu time should be pretty trivial. |
199 |
* There may be reasons to keep it smaller for the 'classic' crossfire |
200 |
* experience which was 11x11. Big maps will likely make the same at |
201 |
* least somewhat easier, but client will need to worry about lag |
202 |
* more. |
203 |
* I put support in for non square map updates in the define, but |
204 |
* there very well might be things that break horribly if this is |
205 |
* used. I figure it is easier to fix that if needed than go back |
206 |
* at the future and have to redo a lot of stuff to support rectangular |
207 |
* maps at that point. |
208 |
* |
209 |
* MSW 2001-05-28 |
210 |
*/ |
211 |
|
212 |
#define MAP_CLIENT_X 31 |
213 |
#define MAP_CLIENT_Y 31 |
214 |
|
215 |
/* |
216 |
* If you feel the game is too fast or too slow, change MAX_TIME. |
217 |
* You can experiment with the 'speed <new_max_time> command first. |
218 |
* The length of a tick is MAX_TIME microseconds. During a tick, |
219 |
* players, monsters, or items with speed 1 can do one thing. |
220 |
*/ |
221 |
|
222 |
#define MAX_TIME 120000 |
223 |
|
224 |
/* Polymorph as it currently stands is unbalancing, so by default |
225 |
* we have it disabled. It can be enabled and it works, but |
226 |
* it can be abused in various ways. |
227 |
*/ |
228 |
#define NO_POLYMORPH |
229 |
|
230 |
|
231 |
/* This determine how many entries are stored in the kill log. You |
232 |
* can see this information with the 'party kills' command. More entries |
233 |
* mean slower performance and more memory. IF this is not defined, then |
234 |
* this feature is disabled. |
235 |
*/ |
236 |
#define PARTY_KILL_LOG 20 |
237 |
|
238 |
/* |
239 |
* The PERM_EXP values adjust the behaviour of permenent experience. - if |
240 |
* the setting permanent_experience_percentage is zero, these values have |
241 |
* no meaning. The value in the settings file is the percentage of the |
242 |
* experience that is permenent, the rest could be lost on death. When dying, |
243 |
* the greatest amount of non-permenent exp it is possible to lose at one time |
244 |
* is PERM_EXP_MAX_LOSS_RATIO - this is calculated as |
245 |
* total exp - perm exp * loss ratio. The gain ratio is how much of experienced |
246 |
* experience goes to the permanent value. This does not detract from total |
247 |
* exp gain (ie, if you gained 100 exp, 100 would go to the skill total and |
248 |
* 10 to the permanent value). |
249 |
* |
250 |
* A few thoughts on these default value (by MSW) |
251 |
* gain ratio is pretty much meaningless until exp has been lost, as until |
252 |
* that poin, the value in the settings file will be used. |
253 |
* It is also impossible for the exp to actually be reduced to the permanent |
254 |
* exp ratio - since the loss ratio is .5, it will just get closer and |
255 |
* closer. However, after about half a dozen hits, pretty much all the |
256 |
* exp that can be lost has been lost, and after that, only minor loss |
257 |
* will occur. |
258 |
*/ |
259 |
/* GD */ |
260 |
|
261 |
#define PERM_EXP_GAIN_RATIO 0.10f |
262 |
#define PERM_EXP_MAX_LOSS_RATIO 0.50f |
263 |
|
264 |
/* |
265 |
* WATCHDOG lets sends datagrams to port 13325 on localhost |
266 |
* in (more-or-less) regular intervals, so an external watchdog |
267 |
* program can kill the server if it hangs (for whatever reason). |
268 |
* It shouldn't hurt anyone if this is defined but you don't |
269 |
* have an watchdog program. |
270 |
*/ |
271 |
#ifndef WIN32 /* ***win32 disable watchdog as win32 default */ |
272 |
#define WATCHDOG |
273 |
#endif |
274 |
|
275 |
|
276 |
/* Enable the new material code - it needs some work. You can |
277 |
* enable this, and things will work, just you'll see a whole |
278 |
* bunch more materials show up, and thus a whole bunch more materials |
279 |
* in your inventory, and the sorting for them isn't really good. |
280 |
*/ |
281 |
|
282 |
/* |
283 |
#define NEW_MATERIAL_CODE |
284 |
*/ |
285 |
|
286 |
/*********************************************************************** |
287 |
* SECTION 2 - Machine/Compiler specific stuff. |
288 |
* |
289 |
* Short list of items: |
290 |
* COMPRESS_SUFFIX - selection of compression programs |
291 |
* O_NDELAY - If you don't have O_NDELAY, uncomment it. |
292 |
* |
293 |
***********************************************************************/ |
294 |
|
295 |
/* |
296 |
* If you compress your files to save space, set the COMPRESS_SUFFIX below |
297 |
* to the compression suffix you want (.Z, .gz, .bz2). The autoconf |
298 |
* should already find the program to use. If you set the suffix to |
299 |
* something that autoconf did not find, you are likely to have serious |
300 |
* problems, so make sure you have the appropriate compression tool installed |
301 |
* before you set this. You can look at the autoconf.h file to see |
302 |
* what compression tools it found (search for COMPRESS). |
303 |
* Note that this is used when saving files. Crossfire will search all |
304 |
* methods when loading a file to see if it finds a match |
305 |
*/ |
306 |
|
307 |
#ifndef COMPRESS_SUFFIX |
308 |
/* #define COMPRESS_SUFFIX ".Z" */ |
309 |
#endif |
310 |
|
311 |
/* If you get a complaint about O_NDELAY not being known/undefined, try |
312 |
* uncommenting this. |
313 |
* This may cause problems - O_NONBLOCK will return -1 on blocking writes |
314 |
* and set error to EAGAIN. O_NDELAY returns 0. This is only if no bytes |
315 |
* can be written - otherwise, the number of bytes written will be returned |
316 |
* for both modes. |
317 |
*/ |
318 |
|
319 |
/* |
320 |
#define O_NDELAY O_NONBLOCK |
321 |
*/ |
322 |
|
323 |
|
324 |
/*********************************************************************** |
325 |
* Section 3 |
326 |
* |
327 |
* General file and other defaults that don't need to be changed, and |
328 |
* do not change gameplay as percieved by players much. Some options |
329 |
* may affect memory consumption however. |
330 |
* |
331 |
* Values: |
332 |
* |
333 |
* BANFILE - ban certain users/hosts. |
334 |
* CSPORT - port to use for new client/server |
335 |
* DMFILE - file with dm/wizard access lists |
336 |
* LOGFILE - where to log if using -daemon option |
337 |
* MAP_ - various map timeout and swapping parameters |
338 |
* MAX_OBJECTS - how many objects to keep in memory. |
339 |
* MAX_OBJECTS_LWM - only swap maps out if below that value |
340 |
* MOTD - message of the day - printed each time someone joins the game |
341 |
* PERM_FILE - limit play times |
342 |
* SHUTDOWN - used when shutting down the server |
343 |
* SOCKETBUFSIZE - size of buffer used internally by the server for storing |
344 |
* backlogged messages. |
345 |
* TMPDIR - directory to use for temp files |
346 |
* UNIQUE_DIR - directory to put unique item files into |
347 |
* USE_CALLOC for some memory requests |
348 |
*********************************************************************** |
349 |
*/ |
350 |
|
351 |
/* |
352 |
* BANFILE - file used to ban certain sites from playing. See the example |
353 |
* ban_file for examples. |
354 |
*/ |
355 |
|
356 |
#ifndef BANFILE |
357 |
#define BANFILE "ban_file" |
358 |
#endif |
359 |
|
360 |
/* CSPORT is the port used for the new client/server code. Change |
361 |
* if desired. Only of relevance if ERIC_SERVER is set above |
362 |
*/ |
363 |
|
364 |
#define CSPORT 13327 /* old port + 1 */ |
365 |
|
366 |
|
367 |
/* |
368 |
* DMFILE |
369 |
* A file containing valid names that can be dm, one on each line. See |
370 |
* example dm_file for syntax help. |
371 |
*/ |
372 |
|
373 |
#ifndef DMFILE |
374 |
#define DMFILE "dm_file" |
375 |
#endif |
376 |
|
377 |
|
378 |
/* LOGFILE specifies which file to log to when playing with the |
379 |
* -daemon option. |
380 |
*/ |
381 |
|
382 |
#ifndef LOGFILE |
383 |
#ifdef WIN32 /* change define path */ |
384 |
#define LOGFILE "var\\crossfire.log" |
385 |
#else |
386 |
#define LOGFILE "/var/log/crossfire/logfile" |
387 |
#endif |
388 |
#endif |
389 |
|
390 |
/* |
391 |
* MAP_MAXTIMEOUT tells the maximum of ticks until a map is swapped out |
392 |
* after a player has left it. If it is set to 0, maps are |
393 |
* swapped out the instant the last player leaves it. |
394 |
* If you are low on memory, you should set this to 0. |
395 |
* Note that depending on the map timeout variable, the number of |
396 |
* objects can get quite high. This is because depending on the maps, |
397 |
* a player could be having the objects of several maps in memory |
398 |
* (the map he is in right now, and the ones he left recently.) |
399 |
* Each map has it's own TIMEOUT value and value field and it is |
400 |
* defaulted to 300 |
401 |
* |
402 |
* Having a nonzero value can be useful: If a player leaves a map (and thus |
403 |
* is on a new map), and realizes they want to go back pretty quickly, the |
404 |
* old map is still in memory, so don't need to go disk and get it. |
405 |
* |
406 |
* MAP_MINTIMEOUT is used as a minimum timeout value - if the map is set |
407 |
* to swap out in less than that many ticks, we use the MINTIMEOUT value |
408 |
* velow. If MINTIMEOUT > MAXTIMEOUT, MAXTIMEOUT will be used for all |
409 |
* maps. |
410 |
*/ |
411 |
|
412 |
/* How many ticks till maps are swapped out */ |
413 |
#define MAP_MAXTIMEOUT 300 |
414 |
/* At least that many ticks before swapout */ |
415 |
#define MAP_MINTIMEOUT 300 |
416 |
|
417 |
/* |
418 |
* MAP_MAXRESET is the maximum time a map can have before being reset. It |
419 |
* will override the time value set in the map, if that time is longer than |
420 |
* MAP_MAXRESET. This value is in seconds. If you are low on space on the |
421 |
* TMPDIR device, set this value to somethign small. The default |
422 |
* value in the map object is MAP_DEFAULTRESET (given in seconds.) |
423 |
* I personally like 1 hour myself, for solo play. It is long enough that |
424 |
* maps won't be resetting as a solve a quest, but short enough that some |
425 |
* maps (like shops and inns) will be reset during the time I play. |
426 |
* Comment out MAP_MAXRESET time if you always want to use the value |
427 |
* in the map archetype. |
428 |
*/ |
429 |
|
430 |
/* Maximum time to reset. */ |
431 |
#define MAP_MAXRESET 7200 |
432 |
/* Default time to reset. */ |
433 |
#define MAP_DEFAULTRESET 3600 |
434 |
|
435 |
/* |
436 |
* MAX_OBJECTS is no hard limit. If this limit is exceeded, crossfire |
437 |
* will look for maps which are already scheldued for swapping, and |
438 |
* promptly swap them out before new maps are being loaded. |
439 |
* If playing only by yourself, this number can probably be as low as |
440 |
* 3000. If in server mode, probably figure about 1000-2000 objects per |
441 |
* active player (if they typically play on different maps), for some guess |
442 |
* on how many to define. If it is too low, maps just get swapped out |
443 |
* immediately, causing a performance hit. If it is too high, the program |
444 |
* consumes more memory. If you have gobs of free memory, a high number |
445 |
* might not be a bad idea. Each object is around 350 bytes right now. |
446 |
* 25000 is about 8.5 MB |
447 |
*/ |
448 |
|
449 |
#define MAX_OBJECTS 400000 |
450 |
|
451 |
/* |
452 |
* Max objects low water mark (lwm). If defined, the map swapping strategy |
453 |
* is a bit different: |
454 |
* 1) We only start swapping maps if the number of objects in use is |
455 |
* greater than MAX_OBJECTS above. |
456 |
* 2) We keep swapping maps until there are no more maps to swap or the number |
457 |
* of used objects drop below this low water mark value. |
458 |
* |
459 |
* If this is not defined, maps are swapped out on the timeout value above, |
460 |
* or if the number of objects used is greater than MAX_OBJECTS above. |
461 |
* |
462 |
* Note: While this will prevent the pauses noticed when saving maps, there |
463 |
* can instead be cpu performance penalties - any objects in memory get |
464 |
* processed. So if there are 4000 objects in memory, and 1000 of them |
465 |
* are living objects, the system will process all 1000 objects each tick. |
466 |
* With swapping enable, maybe 600 of the objects would have gotten swapped |
467 |
* out. This is less likely a problem with a smaller number of MAX_OBJECTS |
468 |
* than if it is very large. |
469 |
* Also, the pauses you do get can be worse, as if you enter a map with |
470 |
* a lot of new objects and go above MAX_OBJECTS, it may have to swap out |
471 |
* many maps to get below the low water mark. |
472 |
*/ |
473 |
|
474 |
/*#define MAX_OBJECTS_LWM MAX_OBJECTS/2*/ |
475 |
|
476 |
/* |
477 |
* Turning on MEMORY_DEBUG slows down execution, but makes it easier |
478 |
* to find memory corruption and leaks. Currently, the main thing |
479 |
* that happens with this activated is that one malloc is done for |
480 |
* each object - thus whatever debugging mechanism the malloc library |
481 |
* (or other debugging tool provides, like purify), it can track this |
482 |
* individual malloc. Default behaviour when turned off is that |
483 |
* enough memory is malloced for a large group of objects so malloc does |
484 |
* not need to be called as often. |
485 |
* This should only be turned on if some form of memory debugging tool |
486 |
* is being used - otherwise, turning this on will cause some performance |
487 |
* hit with no useful advantage. |
488 |
*/ |
489 |
|
490 |
/*#define MEMORY_DEBUG*/ |
491 |
|
492 |
|
493 |
/* |
494 |
* If you want to have a Message Of The Day file, define MOTD to be |
495 |
* the file with the message. If the file doesn't exist or if it |
496 |
* is empty, no message will be displayed. |
497 |
* (It resides in the CONFDIR directory) |
498 |
*/ |
499 |
|
500 |
#define MOTD "motd" |
501 |
|
502 |
/* |
503 |
* You can restrict playing in certain times by creating a PERMIT_FILE |
504 |
* in CONFDIR. See the sample for usage notes. |
505 |
*/ |
506 |
|
507 |
#define PERM_FILE "forbid" |
508 |
|
509 |
/* |
510 |
* If you want to take the game down while installing new versions, or |
511 |
* for other reasons, put a message into the SHUTDOWN_FILE file. |
512 |
* Remember to delete it when you open the game again. |
513 |
* (It resides in the CONFDIR directory) |
514 |
*/ |
515 |
|
516 |
#ifndef SHUTDOWN_FILE |
517 |
#define SHUTDOWN_FILE "shutdown" |
518 |
#endif |
519 |
|
520 |
|
521 |
/* |
522 |
* SOCKETBUFSIZE is the size of the buffer used internally by the server for |
523 |
* storing backlogged messages for the client. This is not operating system |
524 |
* buffers or the like. This amount is used per connection (client). |
525 |
* This buffer is in addition to OS buffers, so it may not need to be very |
526 |
* large. When the OS buffer and this buffer is exhausted, the server |
527 |
* will drop the client connection for falling too far behind. So if |
528 |
* you have very slow client connections, a larger value may be |
529 |
* warranted. |
530 |
*/ |
531 |
|
532 |
#define SOCKETBUFSIZE 256*1024 |
533 |
|
534 |
/* |
535 |
* Your tmp-directory should be large enough to hold the uncompressed |
536 |
* map-files for all who are playing. |
537 |
* It ought to be locally mounted, since the function used to generate |
538 |
* unique temporary filenames isn't guaranteed to work over NFS or AFS |
539 |
* On the other hand, if you know that only one crossfire server will be |
540 |
* running using this temporary directory, it is likely to be safe to use |
541 |
* something that is NFS mounted (but performance may suffer as NFS is |
542 |
* slower than local disk) |
543 |
*/ |
544 |
|
545 |
/*#define TMPDIR "/home/hugin/a/crossfire/crossfire/tmp"*/ |
546 |
#ifdef WIN32 /* change define path tmp */ |
547 |
#define TMPDIR "tmp" |
548 |
#else |
549 |
#define TMPDIR "/tmp" |
550 |
#endif |
551 |
|
552 |
|
553 |
/* Directory to use for unique items. This is placed into the 'lib' |
554 |
* directory. Changing this will cause any old unique items file |
555 |
* not to be used. |
556 |
*/ |
557 |
#define UNIQUE_DIR "unique-items" |
558 |
|
559 |
/* |
560 |
* If undefined, malloc is always used. |
561 |
* It looks like this can be oboleted. However, it can be useful to |
562 |
* track down some bugs, as it will make sure that the entire data structure |
563 |
* is set to 0, at the expense of speed. |
564 |
* Rupert Goldie has run Purify against the code, and if this is disabled, |
565 |
* apparantly there are a lot of uninitialized memory reads - I haven't |
566 |
* seen any problem (maybe the memory reads are copies, and the destination |
567 |
* doesn't actually use the garbage values either?), but the impact on speed |
568 |
* of using this probably isn't great, and should make things more stable. |
569 |
* Msw 8-9-97 |
570 |
*/ |
571 |
#define USE_CALLOC |
572 |
|
573 |
|
574 |
/* |
575 |
* These define the players starting map and location on that map, and where |
576 |
* emergency saves are defined. This should be left as is unless you make |
577 |
* major changes to the map. |
578 |
*/ |
579 |
|
580 |
#ifdef WIN32 /* change define path city */ |
581 |
|
582 |
# define EMERGENCY_MAPPATH "\\city\\city" |
583 |
# define EMERGENCY_X 15 |
584 |
# define EMERGENCY_Y 19 |
585 |
#else |
586 |
# define EMERGENCY_MAPPATH "/city/city" |
587 |
# define EMERGENCY_X 15 |
588 |
# define EMERGENCY_Y 19 |
589 |
#endif |
590 |
|
591 |
|
592 |
/* |
593 |
* These defines tells where, relative to LIBDIR, the maps, the map-index, |
594 |
* archetypes highscore and treaures files and directories can be found. |
595 |
*/ |
596 |
|
597 |
#define MAPDIR "maps" |
598 |
#define TEMPLATE_DIR "template-maps" |
599 |
#define ARCHETYPES "archetypes" |
600 |
#define REGIONS "regions" |
601 |
#define HIGHSCORE "highscore" |
602 |
#define TREASURES "treasures" |
603 |
#define BANISHFILE "banish_file" |
604 |
|
605 |
#define MAX_ERRORS 25 /* Bail out if more are received during tick */ |
606 |
#define OBJ_EXPAND 5000 /* How big steps to use when expanding array */ |
607 |
|
608 |
#define HIGHSCORE_LENGTH 1000 /* How many entries there are room for */ |
609 |
|
610 |
#define ARCHTABLE 16384 /* Arch hashtable size */ |
611 |
#define MAXSTRING 20 |
612 |
|
613 |
#define COMMAND_HASH_SIZE 107 /* If you change this, delete all characters :) */ |
614 |
|
615 |
|
616 |
|
617 |
/*********************************************************************** |
618 |
* Section 4 - save player options. |
619 |
* |
620 |
* There are a lot of things that deal with the save files, and what |
621 |
* gets saved with them, so I put them in there own section. |
622 |
* |
623 |
***********************************************************************/ |
624 |
|
625 |
/* |
626 |
* If you want the players to be able to save their characters between |
627 |
* games, define SAVE_PLAYER and set PLAYERDIR to the directories |
628 |
* where the player-files will be put. |
629 |
* Remember to create the directory (make install will do that though). |
630 |
* |
631 |
* If you intend to run a central server, and not allow the players to |
632 |
* start their own crossfire, you won't need to define this. |
633 |
* |
634 |
*/ |
635 |
|
636 |
#ifndef PLAYERDIR |
637 |
#define PLAYERDIR "players" |
638 |
#endif |
639 |
|
640 |
/* |
641 |
* If you have defined SAVE_PLAYER, you might want to change this, too. |
642 |
* This is the access rights for the players savefiles. |
643 |
* Given that crossfire runs in a client/server model, there should |
644 |
* be no issue setting these to be quite restrictive (600 and 700). |
645 |
* Before client/server, multiple people might run the executable, |
646 |
* thus requiring that the server be setuid/setgid, and more generous |
647 |
* permisisons needed. |
648 |
* SAVE_MODE is permissions for the files, SAVE_DIR_MODE is permission |
649 |
* for nay directories created. |
650 |
*/ |
651 |
/* IMPORTANT: there is a race during saving, where the umask is being applied */ |
652 |
#define SAVE_MODE 0660 |
653 |
#define SAVE_DIR_MODE 0770 |
654 |
|
655 |
/* NOTE ON SAVE_INTERVAL and AUTOSAVE: Only one of these two really |
656 |
* needs to be selected. You can set both, and things will work fine, |
657 |
* however, it just means that a lot more saving will be done, which |
658 |
* can slow things down some. |
659 |
*/ |
660 |
|
661 |
/* How often (in seconds) the player is saved if he drops things. If it is |
662 |
* set to 0, the player will be saved for every item he drops. Otherwise, |
663 |
* if the player drops and item, and the last time he was saved |
664 |
* due to item drop is longer |
665 |
* the SAVE_INTERVAL seconds, he is then saved. Depending on your playing |
666 |
* environment, you may want to set this to a higher value, so that |
667 |
* you are not spending too much time saving the characters. |
668 |
* This option should now work (Crossfire 0.90.5) |
669 |
*/ |
670 |
|
671 |
//#define SAVE_INTERVAL 60 |
672 |
|
673 |
/* |
674 |
* AUTOSAVE saves the player every AUTOSAVE ticks. A value of |
675 |
* 5000 with MAX_TIME set at 120,000 means that the player will be |
676 |
* saved every 10 minutes. Some effort should probably be made to |
677 |
* spread out these saves, but that might be more effort than it is |
678 |
* worth (Depending on the spacing, if enough players log on, the spacing |
679 |
* may not be large enough to save all of them.) As it is now, it will |
680 |
* just set the base tick of when they log on, which should keep the |
681 |
* saves pretty well spread out (in a fairly random fashion.) |
682 |
*/ |
683 |
|
684 |
#define AUTOSAVE 1000 |
685 |
|
686 |
/* Often, emergency save fails because the memory corruption that caused |
687 |
* the crash has trashed the characters too. Define NO_EMERGENCY_SAVE |
688 |
* to disable emergency saves. This actually does |
689 |
* prevent emergency saves now (Version 0.90.5). |
690 |
*/ |
691 |
|
692 |
#define NO_EMERGENCY_SAVE |
693 |
|
694 |
/* By selecting the following, whenever a player does a backup save (with |
695 |
* the 'save command), the player will be saved at home (EMERGENCY_MAP_* |
696 |
* information that is specified later). IF this is not set, the player |
697 |
* will be saved at his present location. |
698 |
*/ |
699 |
|
700 |
/*#define BACKUP_SAVE_AT_HOME*/ |
701 |
|
702 |
/* RESET_LOCATION_TIME is the number of seconds that must elapse before |
703 |
* we will return the player to his savebed location. If this is zero, |
704 |
* this feature is disabled (player will resume where ever he was |
705 |
* when he last logged off). If this is set to less than two hours, |
706 |
* it will prevent players from camping out in treasure rooms. |
707 |
* Do not comment this out - it must be set to something - if you |
708 |
* comment this out, the program will not compile. |
709 |
* |
710 |
* This will work to BACKUP_SAVE_AT_HOME at home above, but where the player |
711 |
* where appear under what conditions is a little complicated depending |
712 |
* on how the player exited the game. But if the elapsed time is greater than |
713 |
* the value below, player will always get returned to savebed location |
714 |
* location. |
715 |
* |
716 |
* Set to one hour as default |
717 |
*/ |
718 |
|
719 |
#define RESET_LOCATION_TIME 3600 |
720 |
|