> For the complete documentation index, see [llms.txt](https://wiki.thescriptersguild.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.thescriptersguild.com/forge/gameplay/cameras/map-intro-cameras/intro-cameras-in-forge-old.md).

# Intro Cameras in Forge (old)

## Intro Cameras in Forge

Intro Cameras are objects used to create cinematic sequences for pre-game and round intermissions.

### Usage

Intro Cameras require two cameras per sequence. Camera one is placed as "Order 1" and serves as the starting point, while camera two is placed as "Order 2" and serves as the ending point. For example, in sequence 1, camera three is placed as "Order 3" and serves as the starting point, while camera four is placed as "Order 4" and serves as the ending point. Similarly, in sequence 2, camera five is placed as "Order 5" and serves as the starting point, while camera six is placed as "Order 6" and serves as the ending point.

To create smooth transition shots, it is important to physically place, orient, and rotate the Intro Cameras in a way that their movement from start to end does not go through objects. The movement between the two cameras is calculated automatically based on how they are placed.

**Contributors**

b0b is here\
Captain Punch


---

# 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://wiki.thescriptersguild.com/forge/gameplay/cameras/map-intro-cameras/intro-cameras-in-forge-old.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.
