> For the complete documentation index, see [llms.txt](https://xeavin.gitbook.io/global-gameplay-settings/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xeavin.gitbook.io/global-gameplay-settings/home.md).

# Home

<figure><img src="/files/y9lhq6l2nexfPoSzATUO" alt=""><figcaption></figcaption></figure>

### Description

There are three types of settings in the game: graphics, controls, and gameplay. Unlike graphics and controls, which are stored in separate configuration files, gameplay settings, such as battle, system, and sound, are stored in each save file.

As a result, the music in the title menu plays at full volume after starting the game, since gameplay settings such as sound volume have not been loaded yet. This is especially frustrating because it can not be worked around by adjusting the total volume with the volume mixer, as that resets each time the game is started.

### Features

This mod ensures that gameplay settings are globally stored and applied, rather than tied to individual save files.

Settings will now persist across different save files, eliminating the need to reconfigure them when switching between saves.

Additionally, this change solves the issue mentioned above, as gameplay settings will now be applied before reaching the title menu.


---

# 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://xeavin.gitbook.io/global-gameplay-settings/home.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.