Sysop documentation

This section covers installation, configuration, operation, maintenance, and recovery for system operators.

Installation and operation

• Installing Galactic Empire
• ge-next installation
• Running Galactic Empire with MBBSEmu
• Classic registration and security system
• Database files, backups, and upgrades

Configuration

• Configuring Galactic Empire — files, compilation, and safe customization
• Main configuration reference
• Item and equipment configuration
• Classic main MSG file
• Ship class configuration
• Galaxy configuration
• Sys command

Operational priorities

Keep executable, compiled messages, class table, and persistent structures at the same release. Back up related databases as a consistent set. Treat insert, update, delete, record-size, and message-ID errors as integrity problems rather than harmless log noise.

Test cleanup as well as startup. GE relies on recurring host callbacks and nightly lifecycle transitions, so a module that accepts commands immediately after loading is not yet fully verified.

Scope

Configuration articles identify whether they apply to classic, ge-next, ge-arena, 16-bit, or 32-bit builds. Stock values are examples, because GE has always permitted substantial sysop customization.

Home · Play · Reference · Versions & history · Sysop · Development · Classic bugs