tomlooman/epicsurvivalgame

Third-person Survival Game for Unreal Engine (Sample Project)

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 44 minutes ago
Added to GitGenius on September 20th, 2026
Created on March 20th, 2015
Open Issues & Pull Requests: 18 (+0)
GitHub issues: Enabled
Number of forks: 1,164
Total Stargazers: 3,395 (+0)
Total Subscribers: 372 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 526 days
Stale 30+ days: 3
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Epic Survival Game is a third-person survival game sample project for Unreal Engine built entirely in C++.

The project demonstrates how to construct a complete game framework in Unreal Engine using C++, with emphasis on event-driven architecture and reusable game systems. It covers core survival game mechanics alongside multiplayer functionality, AI bot behavior, a save game system, asynchronous content loading, and UMG-based menus and UI. The codebase illustrates patterns for flexible, maintainable game code following Unreal Engine conventions.

This project serves primarily as a learning resource and reference implementation rather than a foundation for new production games. It originated as a tutorial series and remains valuable for developers studying C++ game architecture in Unreal Engine, particularly those interested in understanding action systems, event-driven design patterns, and multiplayer game setup. The README explicitly recommends the Action Roguelike project as a more current sample for developers seeking up-to-date standards and conventions, as this project uses older approaches from its 2015 origins.

The project maintains branches for multiple Unreal Engine versions, allowing developers to reference implementations across different engine releases. Development activity appears focused on preserving the existing codebase and keeping it compatible with current engine versions rather than adding new features or modernizing the architecture.