config.lima

#
# Configuration file for the MudOS LPmud driver.
#
# This file is intended for use with the Lima Mudlib and its corresponding
# version of the driver.
#
# The current versions are:
#
# Lima Mudlib:  Lima 1.0b5
# MudOS:        MudOS v22.2b13
#
#
# 951030, Deathblade: updated - reorganized, commented, etc
#

# ------------------------------------------------------------------------
#
# Users of Lima:  you should change the following definitions to match
# your desires, needs, and setup.  Simply follow the directions for each
# option and things should work okay.  Each option will be labeled on
# whether it is required to be changed, or if it is optional.  Anything
# that is optional is subject to your discretion.
#

#
# [ REQUIRED ]
#
# This will be the name of your mud.
#
name : Lima Mud - FluffOS 2019 Demo

#
# [ optional ]
#
# This will be the port number that your users will connect to
#
external_port_1: websocket 7878
websocket http dir: ../build/bin/www

#
# [ REQUIRED ]
#
# This should be the absolute pathname to where you placed your copy of
# the Lima Mudlib.
#
mudlib directory : ./lib

# ------------------------------------------------------------------------
#
# You shouldn't change anything below this point unless you know what
# you're changing.... =)
#

#
# NOTE: all paths below here are relative to the "mudlib directory"
#


#
# this include file is found in the include directories specified below
#
global include file : <global.h>

#
# debug.log and author/domain stats are stored here
#
log directory : /log

#
# alternate debug.log file name (assumed to be in specified 'log directory')
#
debug log file : execute

#
# the directories which are searched by #include <...>
# for multiple dirs, separate each path with a ':'
#
include directories : /include

#
# the file which defines the master object
#
master file : /secure/master

#
# the file where all global simulated efuns are defined.
#
simulated efun file : /secure/simul_efun

#
# file to swap to.  not used if time to swap is 0
# (not used by Lima)
#
swap file : /secure/swap/MudOS_swapfile

#
# Directory to save binaries in.  (if BINARIES is defined)
# (not used by Lima)
#
save binaries directory : /secure/binaries

# if an object is left alone for a certain time, then the
# function clean_up will be called. This function can do anything,
# like destructing the object. If the function isn't defined by the
# object, then nothing will happen.
# This time should be substantially longer than the swapping time.
time to clean up : 7200

# How long time until an unused object is swapped out.
# Machine with too many players and too little memory: 900 (15 minutes)
# Machine with few players and lot of memory: 10000
# Machine with infinite memory: 0 (never swap).
time to swap : 1800

# How many seconds until an object is reset again.
time to reset : 1800

# Maximum number of bits in a bit field. They are stored in printable
# strings, 6 bits per byte.
maximum bits in a bitfield : 1200

# Max number of local variables in a function.
maximum local variables : 30

# Maximum amount of "eval cost" per thread - execution is halted when 
# it is exceeded.
maximum evaluation cost : 2000000

# This is the maximum array size allowed for one single array.
maximum array size : 15000

# This is the maximum allowed size of a variable of type 'buffer'.
maximum buffer size : 400000

# Max size for a mapping
maximum mapping size : 15000

# Max inherit chain size
inherit chain size : 30

# maximum length of a string variable
maximum string length : 200000

# Max size of a file allowed to be read by 'read_file()'.
maximum read file size : 200000

# max number of bytes you allow to be read and written with read_bytes 
# and write_bytes
maximum byte transfer : 10000

# Reserve an extra memory area from malloc(), to free when we run out
# of memory.   If this value is 0, no area will be reserved.
reserved size : 0

# If you set this, the driver doesn't do any handling of runtime errors,
# other than to turn the heartbeats of objects off.  Information about the
# error is passed in a mapping to the error_handler() function in the master
# object.  Whatever is returned is put in the debug.log.
#
# A good mudlib error handler is one of the best tools for tracking down
# errors.  Unfortunately, you need to have one.  Check the testsuite or other
# libs for an example.
mudlib error handler : 1