> For the complete documentation index, see [llms.txt](https://apex-studio.gitbook.io/dash-core-endless-runner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apex-studio.gitbook.io/dash-core-endless-runner/03_core_runtime/endless-treadmill-mechanics.md).
# Endless Treadmill Mechanics
### Chapter 1: The Endless Treadmill Mechanics
Unlike traditional games where the player character traverses world space, Dash Core utilizes an inverted traversal paradigm. The player remains physically constrained along the Z-axis, while the entire world is mathematically pulled backward.
#### 1.1 The EnvironmentTreadmillManager
This manager acts as the primary pacemaker for the game's simulation. It handles the progressive acceleration curve of the world using smooth damping matrices defined within the EnvironmentProfileData. This ensures that speed transitions are fluid and free of jarring physics spikes.
#### 1.2 The AI Smart Spawner & Bitmask Filtering
To guarantee an engaging yet fair experience, the treadmill engine integrates a deterministic AI Director. Instead of randomly instantiating obstacles, the spawner utilizes a structural Bitmask system to evaluate lane occupancy. The algorithm actively prevents the generation of impossible scenarios (e.g., completely blocking all three lanes simultaneously without providing a valid escape route or jump sequence).
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://apex-studio.gitbook.io/dash-core-endless-runner/03_core_runtime/endless-treadmill-mechanics.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
