Cube 2: Sauerbraten vs Marathon
Side-by-side comparison for macOS
Cube 2: Sauerbraten
6.5Multiplayer & singleplayer first person shooter
Marathon
7.0First-person shooter, first in a trilogy
| Metric | Cube 2: Sauerbraten | Marathon |
|---|---|---|
| Category | Games | Games |
| AI Score | 6.5 | 7.0 |
| 30-day Installs | 5 | 4 |
| 90-day Installs | 15 | 14 |
| 365-day Installs | 52 | 87 |
| Version | 2020.11.29,2020.12.21 | 20250829 |
| Auto-updates | No | No |
| Deprecated | No | No |
| GitHub Stars | — | 759 |
| GitHub Forks | — | 119 |
| Open Issues | — | 79 |
| License | — | GPL-3.0 |
| Language | — | C++ |
| Last GitHub Commit | — | 2mo ago |
| First Seen | Aug 20, 2014 | Feb 10, 2017 |
Reviews
Cube 2: Sauerbraten
Cube 2: Sauerbraten is an open-source first-person shooter that doubles as a game engine, offering both multiplayer and single-player modes. It's ideal for fans of classic FPS games and those interested in modding or creating their own games.
Cube 2: Sauerbraten is a multiplayer and single-player first-person shooter with a built-in game engine for custom levels and mods.
Pros
- + Open-source with a strong focus on modding and customization
- + Versatile, offering both game and engine functionalities
- + Free to play with no paywalls or ads
Cons
- - No auto-update feature, requiring manual checks
- - Low installation count suggests limited popularity
Marathon
Marathon is a classic first-person shooter, part of a trilogy, offering a nostalgic experience with modern enhancements. It's an open-source continuation of Bungie's Marathon 2 engine, appealing to retro gaming enthusiasts and modders.
Marathon is a first-person shooter game, the first in a trilogy, providing an immersive gaming experience.
Pros
- + Open-source with an active community contributing to its development
- + Nostalgic appeal for fans of classic first-person shooters
- + Cross-platform support allowing play on multiple operating systems
Cons
- - No auto-update feature, requiring manual checks for new versions
- - Some bugs reported in the GitHub issues, though actively addressed