> For the complete documentation index, see [llms.txt](https://hellstreet.gitbook.io/hellstreet-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hellstreet.gitbook.io/hellstreet-docs/info/game-engine.md).

# 🕹️ Game Engine

**We harness the power of the world's most open and cutting-edge real-time 3D creation tool: Epic Games' Unreal Engine. With its capabilities for photorealistic rendering, dynamic physics, immersive effects, and true-to-life animation, our work is elevated to new heights. All of this is made possible on an open and extensible platform, accompanied by a thriving community that continues to grow.**

<figure><img src="/files/NklgKJISG5Z6OW3yFFUD" alt=""><figcaption></figcaption></figure>

#### Game Engine

{% hint style="info" %}
At the core of HellStreet lies a powerful simulation engine built in optimized C++ and integrated with Unreal Engine 5.
{% endhint %}

This combination delivers a seamless virtual city experience: every district, building, and street in HellStreet is simulated in real time, with physics, lighting, and sound fully synchronized for all players. The simulation is deterministic and server-authoritative, meaning every event and action in HellStreet can be recorded, archived, and replayed exactly. In practice, this allows HellStreet to archive every live event in detail and ensure consistency across all player sessions.

#### The City Simulation <a href="#the-city-simulation" id="the-city-simulation"></a>

{% hint style="info" %}
HellStreet’s urban environment is crafted by teams of experienced digital artists and urban designers.
{% endhint %}

We employ advanced precomputation techniques and an efficient asset pipeline to manage high-resolution content. Many graphical elements (lighting, complex geometry, particle effects) are baked ahead of time using a render farm, then streamed to clients through adaptive level-of-detail (LOD) systems. The result is cinematic visual fidelity that does not overtax user hardware. Dynamic day-night cycles and weather effects are simulated in real time, further enhancing immersion without burdening players’ devices.

#### Spectator and Replay Mode <a href="#spectator-and-replay-mode" id="spectator-and-replay-mode"></a>

{% hint style="info" %}
The engine includes a spectator/cinematic mode that brings even modest hardware up to spectacle-level visuals.
{% endhint %}

By leveraging the deterministic simulation and pre-baked scene data, HellStreet can render events with post-processed effects on the fly. Viewers can watch high-quality replays or live broadcasts of concerts, tournaments, and social gatherings, even on lower-end devices. A dynamic camera system and cinematic filters allow spectators to enjoy polished, camera-driven perspectives of in-world action. This ensures that device capability is no barrier to experiencing HellStreet’s most memorable moments.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hellstreet.gitbook.io/hellstreet-docs/info/game-engine.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.