> For the complete documentation index, see [llms.txt](https://striga.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://striga.gitbook.io/docs/striga-multicharacter/settings-and-scenes.md). # Settings & Scenes Background scenes, filters, weather, animations, music, color and player settings. Everything here is in `editable/config.lua`. Players can change most of it for themselves, unless you turn that picker off. ## Scenes ### Scene (`Config.Scene`) | Option | Default | What it does | | -------------- | -------- | --------------------------------------------------------------------------------------- | | `Bucket` | `true` | Private routing bucket while selecting | | `BucketBase` | `41000` | Buckets are `BucketBase + player id`. Change it if another resource uses the same range | | `DepthOfField` | `true` | Soft background on the preview camera | | `Shots` | - | Camera `distance`, `height`, `side`, `target` and `fov` for `intro`, `select`, `create` | | `Interp` | - | Camera move times in ms: `Intro`, `Switch`, `Create` | | `Fade` | `350` | Fade time in ms when switching characters | | `Locations` | 2 scenes | Background scenes. The first one is the default | Each location has: `id`, `label`, `ped` (where the preview ped stands), optional `hidden` (where the real player waits), `interior`, `time`, `weather` and optional `shots` overrides. {% hint style="success" %} **Add your own scene:** stand where the ped should stand, face where the camera should be, and type `/mcscene`. Copy the line from the F8 console into `Config.Scene.Locations`. {% endhint %} ## Filters, weather and animations | Table | Options | What it does | | ------------------- | ---------------------------------------------------------------------- | ----------------------------------------------------------------------------- | | `Config.Filters` | `AllowPlayer`, `Default` (`'none'`), `DefaultStrength` (`100`), `List` | Visual filters (game timecycle modifiers). Only in the menu, cleared on spawn | | `Config.Weathers` | `AllowPlayer`, `Default` (`'auto'`), `List` | Weather in the menu. `auto` = the scene's own weather | | `Config.Animations` | list of `id`, `label`, `dict` + `clip` or `scenario` | Ped animations the player can pick | `AllowPlayer = false` turns that picker off for players. *** ## Music ### Audio (`Config.Audio`) | Option | Default | What it does | | -------------------- | ------------------------------------------------------ | --------------------------------------------- | | `Tracks` | `{}` | Music files. They play in order and loop | | `YouTube` | `nil` | Default YouTube link or video id for everyone | | `AllowPlayerYouTube` | `true` | Players may set their own YouTube link | | `Defaults` | `music = 40, sfx = 60, muted = false, anim = 'random'` | Start values for new players | Put your own files in `web/dist/audio/` and list them in `Tracks`. A track is a file name, or a table with `file`, `title`, `artist` and `cover` (only `file` is needed): ```lua Tracks = { 'theme.ogg', { file = 'night.ogg', title = 'Night Drive', artist = 'Striga', cover = 'covers/night.jpg' } }, ``` *** ## Color ### Color (`Config.Theme`) | Option | Default | What it does | | ------------------- | ----------- | ---------------------------------------------------------------- | | `Accent` | `'#eaa45c'` | Main color when there is no HUD theme and the player picked none | | `AllowPlayerAccent` | `true` | Players may pick their own color | | `Presets` | 6 colors | Color presets in the picker | *** ## Player settings Players change their settings in the menu's own **Settings**: volume, mute, scene, animation, filter, weather, color and YouTube link. When Striga Tokyo HUD runs, the same settings (except the YouTube link) are also in the [`/hud` menu](/docs/striga-tokyo-hud/settings-menu.md) after login, through the striga-core settings hub. Changes made there show at the next character screen. Settings are saved per player (by FiveM license) in the `striga_multichar_settings` table. {% hint style="info" %} There is no single switch to lock all settings. To turn pickers off, use `AllowPlayer = false` in `Config.Filters` / `Config.Weathers`, `Config.Theme.AllowPlayerAccent = false` and `Config.Audio.AllowPlayerYouTube = false`. {% endhint %} ### Color priority 1. The color the player picked 2. The Striga Tokyo HUD theme color (if the HUD runs) 3. `Config.Theme.Accent` {% content-ref url="/pages/valc4MZgVO5BfbszqMYS" %} [Exports & Events](/docs/striga-multicharacter/exports-and-events.md) {% endcontent-ref %} --- # 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://striga.gitbook.io/docs/striga-multicharacter/settings-and-scenes.md?ask=&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.