Jump to content

ge-next installation

From Galactic Empire wiki
Revision as of 13:54, 18 October 2026 by CodexBot (talk | contribs) (Link Btrieve explanation at first mention)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This page gives the ge-next-specific choices and filenames. For the shared installation, backup, and rollback procedure, begin with Installing Galactic Empire; for saved files and resets, see Database files.

Choose a release

Choose a full release archive for a new installation. Both architectures present themselves as ge-next and are intended to have the same gameplay; PROJECT_ARCH identifies the build in version and DATA output. They have different database layouts, so do not substitute one architecture's saved files for the other's. The release DLL is ready to install; source compilation is not required.

ge-arena is a separate module and download, despite sharing ge-next's source tree. Its MPOGA* files are not an upgrade to or replacement for ge-next's MPOGE* files.

ge-next package contents

Files ge-next-specific role
MPOGEMP.DLL, MPOGEMP.MDF Module and definition. The MDF identifies MPOGEMSG, MPOGEHLP, and MPOGESHP as its message resources.
MPOGEMSG.MSG, MPOGEHLP.MSG, MPOGESHP.MSG Main settings/messages, help, and ship classes. Full release archives ship these sources, not precompiled MCV files; use the host's message compilation procedure. See Configuring Galactic Empire.
MPOGEUSR.DAT, MPOGESHP.DAT, MPOGEPLT.DAT, MPOGEMAL.DAT, MPOGETEA.DAT Supplied starting files and, after play begins, the live game. The team file is text; the others are Btrieve files. Database files explains how to back up or reset the entire set.
Matching *.NEW (16-bit) or *.VIR (32-bit) Clean templates for an intentional new game, not a step in a routine upgrade.
MPOGEMNU.TXT, RELNOTES.TXT, FRONTEND.TXT, LICENSE.txt Menu text, release notes, DATA frontend reference, and license. The 16-bit archive also includes optional RLTELNET.SH and a linker .MAP file.

The 16-bit archive retains DOS 8.3 filenames. Keep the files from one release together, including any compiled message resources generated from its MSG sources.

Activating the module

Use MPOGEMP.MDF when adding ge-next to a MajorBBS/Worldgroup menu. With MBBSEmu, use module identifier MPOGEMP in modules.json and point its path at the 16-bit package; Running Galactic Empire with MBBSEmu covers the rest of that setup. Review MPOGEMSG.MSG and MPOGESHP.MSG before admitting players, then compile all three message sources for the installed DLL. The full archive already has starting .DAT files; copying templates over them is unnecessary.

The general installation checklist covers host startup and first-use testing. Do not replace a running game's .DAT files merely because a new full archive contains fresh ones.

ge-next upgrade boundary

ge-next 0.3 renamed the module and data from MBM* to MPO* and changed persistent structures. Saved games from earlier ge-next releases are not directly compatible with 0.3 or later. For later upgrades, read every intervening RELNOTES.TXT; a patch archive may omit files expected to be present from its specified base release.

Use the shared upgrade procedure for backups, merging local MSG changes, preserving live DAT files, and rollback. MBBSEmu installations also have live SQLite .db files; Database files explains their handling. Neither the clean templates nor the starting DAT files in a new archive are a migration tool.

ge-next checks

In the game, HELP VERSION should show the intended ge-next version and architecture. If a frontend uses DATA, verify its pairing and reported project metadata against FRONTEND.TXT. The ordinary menu, ship, scan, roster, persistence, and host-log checks are listed on the general installation page.

See also

Retrieved from "https://manicpop.org/gewiki/index.php?title=Ge-next_installation&oldid=2159"