Rlogin.RemoteIP : string : Specifies the Remote IP of the instance to be permitted to connect via Rlogin to MBBSEmu Rlogin.Compatibility : string : Default is the same as not being configured, WG3NT enables a fix to prevent extra characters from showing up on initial connections from a WG3 server Rlogin.Port : int : Specifies which port the Rlogin Server should bind to Rlogin.IP : string : Specifies which IP the Rlogin Server should bind to (Optional, defaults to all) Rlogin.Enabled : bool : Specifies if the Rlogin Server is enabled Telnet.Heartbeat : bool : Specifies if the Telnet Server should send a "heartbeat" to the client at a regular interval (NOTE: Can cause issues with MegaMud but help other clients that disconnect when there are extended periods of no activity) Telnet.Port : int : Specifies which port the Telnet Server should bind to Telnet.IP : string : Specifies which IP the Telnet Server should bind to (Optional, defaults to all) Telnet.Enabled : bool : Specifies if the Telnet Server is enabled Module.DoLoginRoutine : bool : Specifies if users logging into the system should be displayed the "Login Routine" for the modules currently running
This way you're able to play a Module you purchased for your MajorBBS 6.25 system, as well as a Module you purchased later with your Worldgroup 2.0 system even though their registration or unlock codes are tied to different BBS Activation Numbers. Using this option, you're able to specify a unique bturno that the module will receive. The problem is the registration numbers or unlock codes for these modules are bound to a specific Activation #. Many sysops over the years had registered copies of MajorBBS 6.25, Worldgroup 2.0, or even consolidated Bulletin Board Systems from other sysops which all had valid & legal registrations. : string : Correlates to GSBL->bturno for the specified module.
This is the registration # for your MajorBBS/Worldgroup instance and is used by many modules to generate a unique module registration/activation code for your Bulletin Board System. Value of 18 minimum is recommended - depending on your hardware ymmv, 144 works well on modern processors while keeping CPU bturno. Timer.Hertz: int : Controls speed of main BBS program loop execution. Some Modules make use of this configuration value to display the name of the Bulletin Board system to the users. You can specify a custom appsettings.json file using the -S command line switch.īBS.Title : string : Correlates to MAJORBBS->bbsttl.
By default, MBBSEmu will look in its current directory for this file. MBBSEmu uses a standard JSON format Application Settings file for all configuration values.