AhmadHassan-BTed /CursedTomorrow
A 2D horror-survival and escape game built from scratch in C++. Navigate unsettling levels, survive the glitches, and escape the nightmare. Features a custom C++ game core, robust asset management, and comprehensive system architecture documentation.
★ 4,923⑂ 2👁 1⑃ 1● 0▤ 0
-2
日增长
4,923
stars
2
forks
1
watchers
1
prs
0
issues
0
releases
README
Cursed Tomorrow
A platforming descent into the atmospheric unknown.
---
Cursed Tomorrow is not just a game; it is a manifestation of tension and the human struggle against an encroaching, atmospheric darkness. Designed and engineered by Ahmad Hassan (B-Ted), this project serves as a technical showcase of modular C++ game design and atmospheric storytelling through interaction.
Overview • Showcase • Architecture • Systems • Resources • Development
Overview
The core of Cursed Tomorrow lies in its simplicity and the weight of its atmosphere. Every movement, jump, and collision is tuned to resonate with the player's experience of navigating a world that feels both fragile and hostile.
Core Pillars
- Atmospheric Isolation: A world designed to feel empty yet occupied.
- Precision Mechanics: Character movement that respects physics and player intent.
- Modular Design: A robust C++ foundation built for extensibility and performance.
---
Visual Showcase
The World of Tomorrow
!Main Menu
The gateway into the descent.
| Gameplay | Level Selection |
| :---: | :---: |
| !Gameplay | !Level Select |
| Navigating the void. | Choosing the path. |
| Atmosphere | Death |
| :---: | :---: |
| !Warning | !You Died |
| Signs of what's to come. | The inevitable end. |
---
Architecture Documentation
The project architecture prioritizes decoupling and clear ownership. It is built to scale from a simple prototype to a complex production-grade game.
High-Level System Flow
mermaid
graph TD
subgraph "Engine Loop"
Main[main.cpp] -- |Initialize| Game[Core::Game]
Game -- |Frame Start| Input[HandleInput]
Input -- |Update| Logic[UpdateLevelLogic]
Logic -- |Physics| Phys[Entities::Character]
Phys -- |Render| Draw[Draw]
Draw -- |Frame End| Game
end
subgraph "Asset Management"
Game -.- |Request| RM[ResourceManager]
RM -- |Cache/Load| Disk[(Disk Assets)]
end
Module Relationship
The interaction between modules is strictly managed through the CursedTomorrow namespace.
| Module | Responsibility | Internal Coupling |
| :--- | :--- | :--- |
| Core | Window lifecycle, state machine, and main loop orchestration. | High (Orchestrator) |
| Entities | Individual game actors, physics, and local state. | Low (Independent) |
| Resources | Centralized asset caching and memory safety. | Zero (Utility) |
| Config | Global constants and engine parameters. | Static Only |
---
Internal Systems
Request & Data Flow
The data flow follows a strict unidirectional pattern during the update phase to ensure deterministic behavior.
mermaid
sequenceDiagram
participant P as Player
participant G as Game
participant C as Character
participant RM as ResourceManager
G-G: HandleInput()
G-C: Update()
C-C: Move() & Jump()
C-C: ApplyGravity()
G-G: UpdateLevelLogic()
G-C: Draw()
C-RM: LoadTextureResource()
RM--C: Texture Data
C-G: Render Comp