> For the complete documentation index, see [llms.txt](https://profpivec.gitbook.io/documentation-and-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://profpivec.gitbook.io/documentation-and-tutorials/game-creator/tools-for-game-creator./in-game-screen-capture.md).

# In-Game Screen Capture

The Screen Capture component is used with an Action, allowing you or your player can create screen shots during game play.  You can create a Trigger for Screen Capture, or even toggle a condition if you want to use an automated repeating capture.

![](/files/-M1URh1zQk3kMLcgbLDl)

This Trigger should execute the Action Tools/ScreenCapture. This Action will take a screen shot in low res (formats are png, jpg, or tga), and will be saved with a unique name prefixed with what ever you add the the Prefix slot. Images will be saved in the Game Folder, or in the Persistant data folder on a mobile.

![](/files/-M1USIjYqvcsfTU4v6mS)

If you select High Resolution, the Images are in hiRes (many times larger) but will add to the overhead and may cause a delay in Game Play. The High Res feature  should normally be used for taking promotion images and not for your player to use.

However, when using High Resolution, the images can be taken from different cameras other than the Player Camera, providing a unique perspective on screen shots. Simply add another Camera to your scene and drag it into the appropriate slot.

The final three settings are as follows:

1. Delay Start - this setting is from zero to 10 seconds and adds a delay from when the trigger is pressed until the screen capture is taken.
2. Repeat Every -  this allows you to repeat the screen capture. The setting is from zero (do not repeat), to repeat once every 60 seconds. 
3. Log Data - select this check box log image data and save name to the system log.

If you use the Repeat feature, you must cancel the repeat or it will continue forever. To do this, execute the Tools/StopScreenCapture Action.

![](/files/-M1UWXDA5GBKNRjrORvk)

Simply drag in the Action that started the repeat, and execute with a trigger of your choice.

{% hint style="success" %}
Screen Captures also work on Mobile, see the Mobile Example included in this Module.
{% endhint %}


---

# 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://profpivec.gitbook.io/documentation-and-tutorials/game-creator/tools-for-game-creator./in-game-screen-capture.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.