Serious Sam: The First / Second Encounter

Crowd control on a very large scale

The classic Serious Sam games put arcade shooting and overwhelming enemy encounters at the center of play. The First Encounter takes Sam through ancient Egypt against Mental’s forces, with charging monsters, explosive attackers and a large arsenal. Reading the crowd and choosing a weapon for the immediate threat are part of its appeal.

This is the original Classic branch of the series. The existence of HD editions, Revolution and later Serious Sam games does not make their content or technology part of this source port.

SeriousSamClassic · original game publisher description · SeriousSamClassic · project documentation

The two encounters remain separate games

SeriousSamClassic maintains Serious Engine 1.10 for The First Encounter and The Second Encounter. The repository includes the game engine, tools and a dedicated server, with platform-specific packages and build instructions. It also supports a separate XPLUS modification that changes models, textures, effects and weapons.

XPLUS is an optional fan modification, not the baseline appearance of the classic campaigns. The repository additionally points to a Vulkan variant in some platform packaging; choose the instructions corresponding to the package you actually install.

SeriousSamClassic · project documentation

Copy the matching encounter’s resources

Keep First Encounter and Second Encounter data separate. The project’s manual layout uses SamTFE and SamTSE, each with its own archives and supporting directories. The detailed running instructions include Help and, for the First Encounter layout, Levels alongside the GRO archives.

Flatpak, Snap and AppImage packages look in different user-data locations. Follow that package’s first-run prompt or documented path instead of mixing instructions for a source checkout with a sandboxed package. An installation that cannot find data is not necessarily missing the executable.

SeriousSamClassic · project documentation

Use a playing build and the intended content

For source builds, the maintainers recommend Release or RelWithDebInfo for playing. Debug builds can stop on internal assertions that are not intended as a normal player experience. The repository also documents demo builds using official demo resources; those offer demo content, while full campaigns still need the matching Classic game files. This distinction keeps a successful demo launch from becoming a mistaken claim that every retail level is installed.

SeriousSamClassic · project documentation