> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/live-config/viewing-and-editing-live-config-1.md).

# Editing Locally

{% hint style="success" %}
verified: 2025-11-20 version: v39
{% endhint %}

Live config changes can be made locally for development purposes.

When you run with Play-In-Editor, live config settings will be generated for your game session, which can be navigated to from the editor pop-up on the bottom right corner of your screen.

<figure><img src="https://970394512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft3SBfOIsRz4GCNFFpae7%2Fuploads%2Fgit-blob-2f60333961e7e9556d456234a704718bde3e2b32%2Fimage%20(799).png?alt=media" alt=""><figcaption></figcaption></figure>

Clicking `Open` opens an explorer window containing `json` files of your available live config settings.

<figure><img src="https://970394512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft3SBfOIsRz4GCNFFpae7%2Fuploads%2Fgit-blob-947854c62758ec6ce9deae89130452693e31be4a%2Fimage%20(800).png?alt=media" alt="" width="331"><figcaption></figcaption></figure>

Open these files on your text editor of choice and view/amend your settings as necessary. Once the file is saved, your setting changes should be picked up by the PIE client/server within seconds.

<figure><img src="https://970394512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft3SBfOIsRz4GCNFFpae7%2Fuploads%2Fgit-blob-062201ea683339f0b9364f35aa9a9dc8e2614bfd%2Fimage%20(801).png?alt=media" alt="" width="334"><figcaption></figcaption></figure>

Note that any changes you made will not persist between PIE sessions. A new set of config files would be generated every time a new PIE session is started. If you'd like to make changes to your setting that persists, refer to [Overriding Defaults](/platform-documentation/creation/unreal-development/features-and-tutorials/live-config/overriding-default-live-config-settings.md).\
\
It is highly recommended that you test any changes made to Live Config (i.e. either after[Adding New Settings](/platform-documentation/creation/unreal-development/features-and-tutorials/live-config/adding-new-live-config-settings.md) or [Overriding Defaults](/platform-documentation/creation/unreal-development/features-and-tutorials/live-config/overriding-default-live-config-settings.md)) on PIE before deploying your world. Any errors on your Live Config setup will result in the following failure pop-up to appear instead, and you can refer to your Editor logs to debug the issue.

<figure><img src="https://970394512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft3SBfOIsRz4GCNFFpae7%2Fuploads%2Fgit-blob-256978be01392ee97909a14b9d7f24f08f73bf38%2Fimage%20(148).png?alt=media" alt=""><figcaption></figcaption></figure>

## Via The Console

see [Live Config Console](/platform-documentation/creation/unreal-development/features-and-tutorials/live-config/viewing-and-editing-live-config.md#via-the-console)


---

# 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://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/live-config/viewing-and-editing-live-config-1.md?ask=<question>&goal=<user_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.