Classic bug database
The Classic bug database indexes defects and implementation traps in the original Galactic Empire source. It is a reference for players investigating classic behavior and developers maintaining or porting the game. Each published record has a stable ID and its own page. See Classic bug record format for how records are documented.
Published records
Porting and modernization cautions
These are intentional features, design limitations, or integration assumptions in classic GE rather than additional numbered bugs. A port should decide explicitly whether to preserve or change them.
Exposed team diagnostics
The undocumented TEAM DUMPITOUT command prints the team table, including joining passwords and founder secrets, to any player who invokes it. This is a serious information-disclosure risk even though the command does what its diagnostic implementation asks it to do. A modern port should remove it from ordinary player access or restrict it to administrators, as ge-next did with SYS TEAMDUMP. See Team command and Sys command.
Frontend data access
Classic DATA is a documented frontend interface, not merely an accidental debug command. Its published, hardcoded access word does not authenticate a client, and its responses include raw combat state and precise scan information that ordinary commands may conceal. Retaining frontend support need not mean retaining those disclosures: define which information a frontend is allowed to receive and enforce the same gameplay checks as other commands. See Data command and GECP.
NPC behavior tied to class names
Classic selects several Droid behavior routines by matching configured ship-class names. Renaming one of those classes in the ship configuration can silently remove its special behavior even when its other settings are unchanged. This is a configuration constraint rather than a broken default installation; a port can use a separate behavior identifier instead. See Droids and Ship class configuration.
Flux-pod loading conventions
Classic checks for automatic pod loading periodically and only below a fixed active-flux threshold, not whenever an action needs more energy. A ship can therefore fail to fire, cloak, or maintain warp despite carrying spare pods. Some of these outcomes are consequences of the original loading design, distinct from the arithmetic fault catalogued as Classic bug: Flux subtraction underflow. See Flux and Flux command.
Registration and database assumptions
Classic stores registration and trial information in concealed records inside its Btrieve files. A port, roster tool, or database converter must distinguish those records from player and planet records; it should also decide how to handle the original board-bound registration mechanism rather than assuming every record is gameplay data. See Classic registration and security system and Database files.
Shared host output state
MajorBBS's PRF output buffer is shared working state, not a separate buffer for each connected player. A port or emulator that changes when messages are formatted, cleared, or sent can alter who sees a message even when GE's calls appear unchanged. See MajorBBS integration and Classic bug: Filtered broadcast suppresses later recipients for a separate GE-side defect involving multi-recipient delivery.
See also
Home · Play · Reference · Versions & history · Sysop · Development · Classic bugs