# Gameplay Design

**Overview of Game Mechanics**

* Core Concept:\
  Players control a vehicle on a 4-lane road, adjusting speed and using swipe gestures to switch lanes, avoiding collisions with obstacle vehicles.
* Controls:
* * Speed Control: Players can increase or decrease speed using on-screen buttons.
  * Lane Switching: Swipe gestures are used to move the vehicle to adjacent lanes, avoiding obstacles.
* Dynamic Obstacles:
* * The game starts with 1-2 vehicles as obstacles, progressively increasing to up to 8 vehicles as difficulty rises.
  * The position and speed of obstacle vehicles vary, requiring quick reflexes and precise control.

***

**Campaign Progression and Challenges**

* Difficulty Scaling:
* * Early stages feature fewer obstacles and moderate speeds, allowing players to get accustomed to the controls.
  * As the game progresses, obstacle density and movement patterns become more challenging, making speed control increasingly critical.
* Scoring System:
* * Score Calculation: Points are determined by the player’s average speed and completion time.
  * * Faster completion times result in higher scores.
    * Slowing down extends the time and reduces the score.
  * Risk vs. Reward: Maintaining higher speeds increases scores but also heightens the risk of collisions, demanding greater skill and focus.
* Endless Mode:
* * After completing the campaign levels, players unlock Endless Mode.
  * The goal is to race as fast and as far as possible while avoiding obstacles to achieve the highest score.

***

**Integration of Diverse Environments and Dynamic Tracks**

* Variety of Tracks:
* * Tracks are set in diverse environments, such as urban highways, mountain roads, and desert landscapes.
  * Each environment introduces unique challenges, such as reduced visibility in foggy conditions or narrower roads.
* Dynamic Elements:
* * Additional challenges include sudden obstacles like debris, potholes, or roadblocks.
  * These elements require players to adapt quickly, combining lane-switching and speed control for successful navigation.


---

# Agent Instructions: 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:

```
GET https://fusednfurious.gitbook.io/fusednfurious/gameplay-design.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.