Differences

This shows you the differences between two versions of the page.

--- server:running_the_server:settings [2018/03/02 10:28] – created karl
+++ server:running_the_server:settings [2025/04/18 13:08] (current) – external edit 127.0.0.1
@@ Line 6: / Line 6: @@
 ===== Server Settings =====
 ====    fastclock ====
-This setting variable needs to be a positive integer or a Zero (0) .
+This setting variable needs to be a positive integer or a Zero (0) . \\
-A negative value would \\ //LOG(llevError, "load_settings: fastclock must be at least 0" ", %d is invalid\n", lev);// and fall back to the default set in :?: \\
+A negative value would \\ //LOG(llevError, "load_settings: fastclock must be at least 0" ", %d is invalid\n", lev);// \\ and fall back to the default set in //server/include/global.h// \\
-The only function that uses it, is //static void block_until_new_connection(void)// in // server/socket/loop.c//, and just tests it if it is greater than 0 . Setting the fastclock to something like 2 or 10 does not make the server "faster" .
+as //uint8 fastclock; /* if true, clock goes warp 9 */ // .. \\
+The only function that uses it, is //static void block_until_new_connection(void)// \\
+in // server/socket/loop.c//, and just tests it if it is greater than 0 . \\
+Setting the fastclock to something like 2 or 10 does not make the server "faster" . \\
+Older servers until including v1.11.0 used this variable once more in // server/server/[[:dev:weather]].c// \\ and also tests if it is set greater than zero; \\
+found in //void tick_the_clock(void)// to call the //write_skymap// function. \\
-Older servers until v1.11.0 used this variable one more in // server/server/[[:dev:weather]].c// and also tests if it is set greater than zero; found in //void tick_the_clock(void)// to call the //write_skymap// function. \\
 My impression was that the Computer's CPU used one whole Core 100% when setting fastclock to 1 . \\
-So it seems not advisable to set it to anything else than 0 . But therefore the //skymap// is not painted in the //var/crossfire/weather.ppm// 300x300 pixels picture; it's field in the middle of the bottom row of the picture of 9 climate maps stays black. \\
+So it seems not advisable to set it to anything else than 0 . \\
+But therefore the //skymap// is not painted in the //var/crossfire/weather.ppm// 300x300 pixels picture; it's field in the middle of the bottom row of the picture of 9 climate maps stays black. \\
 The weather.ppm can be easily converted by ''ppmtoxpm weather.ppm >weather.xpm'' to be viewed. \\