# Suggestion: Command SayVar for accessing configuration settings

**URL:** https://community.mp3tag.de/t/suggestion-command-sayvar-for-accessing-configuration-settings/70129
**Category:** Web Sources Discussion
**Created:** [November 13, 2025, 6:05pm UTC](https://community.mp3tag.de/t/suggestion-command-sayvar-for-accessing-configuration-settings/70129 "2025-11-13T18:05:21Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![arb](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/41988e/32.png) [@arb](https://community.mp3tag.de/u/arb)
#### Post date: [November 13, 2025, 6:18pm UTC](https://community.mp3tag.de/t/suggestion-command-sayvar-for-accessing-configuration-settings/70129/2 "2025-11-13T18:18:00Z")

</div>

> [@yorickausyps](#):
>
> copies the value into an output buffer designated by the most recent `outputto "NAME"`

Another benefit would be if this was available:

- in `[ParserIndexScript]` and `[ParserAlbumScript]` as a persistent output buffer
- immediately as `%NAME%` to be used in `[SearchBy]`, `[IndexURL]` and `[AlbumURL]`, thus making it possible to inject user-specific data like a language or API key into a URL request. This _could_ save needing multiple .src’s [Best way to handle region/language codes - Development / Web Sources Discussion - Mp3tag Community](https://community.mp3tag.de/t/best-way-to-handle-region-language-codes/69962) @GMK

Only further amendment would be output buffers created by settings might need prefixed automatically by Mp3Tag with “Var\_” to distinguish from any other created outputs.

---

_[View the full topic](https://community.mp3tag.de/t/suggestion-command-sayvar-for-accessing-configuration-settings/70129)._