# 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:** 8
**Page:** 1
### Author:  [@yorickausyps](https://community.mp3tag.de/u/yorickausyps)
#### Post date: [November 13, 2025, 6:05pm UTC](https://community.mp3tag.de/t/suggestion-command-sayvar-for-accessing-configuration-settings/70129/1 "2025-11-13T18:05:21Z")
Currently the individual option settings in the Tag Source, the configuration values, can only be accessed by the logical functions:
`IfVar "key" "value"`
`IfNotVar "key" "value"`
where the `key` is used to access the setting which is compared to the given `value`.
This only works efficiently for values of type bool (logical) and for type strings with given choices to select from. There is no method available to read the other possible value types `number` and `string` (with arbitrary text input) in a websource script. A solution for a special, restricted case has been described by @rboss in [An efficient method for assigning numeric inputs into %output%](https://community.mp3tag.de/t/an-efficient-method-for-assigning-numeric-inputs-into-output/63206).
In my example I want to use a configuration value of type text, that allows me to enter a name that the script later can use as a name of a tag:
```auto
{
"type": "string",
"key": "Tag_Notes_Setting",
"title": "Tag field for notes",
"description": "Tag field to use for notes.",
"choices": ["none","COMMENT","NOTES","UNSYNCEDLYRICS"],
"default": "COMMENT"
},
```
For the user to provide a name not in my list of choices I had to use the above code without the choices, but then I see now way to read the value the user did enter.
Therefore I want to suggest the command:
```auto
SayVar "key"
```
that reads the (read only) configuration values and copies the value into an output buffer designated by the most recent `outputto "NAME"`. This should work for any type and make it possible to really efficiently use all possible configuration options.
---
### Author:  [@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")
> [@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.
---
### Author:  [@arb](https://community.mp3tag.de/u/arb)
#### Post date: [November 13, 2025, 8:13pm UTC](https://community.mp3tag.de/t/suggestion-command-sayvar-for-accessing-configuration-settings/70129/3 "2025-11-13T20:13:42Z")
Just noticed some very similar and additional/alternative ideas from this thread:
[Suggestion: 'Splice' command for WS - Development / Web Sources Discussion - Mp3tag Community](https://community.mp3tag.de/t/suggestion-splice-command-for-ws/61854/2) with `$var(name)` as an option. @AreDigg
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [November 13, 2025, 10:10pm UTC](https://community.mp3tag.de/t/suggestion-command-sayvar-for-accessing-configuration-settings/70129/4 "2025-11-13T22:10:45Z")
Thanks for the suggestion -- and all the others who have suggested this before! I've implemented this with this internal test version and hope it works as expected:
[https://download.mp3tag.de/support/F3F01D59-10F6-4D80-913A-7E8E38EA8B58-3-31-11-3/mp3tagv331k3-x64-setup.exe](https://download.mp3tag.de/support/F3F01D59-10F6-4D80-913A-7E8E38EA8B58-3-31-11-3/mp3tagv331k3-x64-setup.exe)
* * *
For the other suggestions, I'd really love to see separate topics for each idea so they don't get lost after this one is marked as solved and can be tracked independently.
---
### Author:  [@AreDigg](https://community.mp3tag.de/u/AreDigg)
#### Post date: [November 14, 2025, 4:20am UTC](https://community.mp3tag.de/t/suggestion-command-sayvar-for-accessing-configuration-settings/70129/5 "2025-11-14T04:20:52Z")
So many new things coming to the framework, I have to take a look at it all.
---
### Author:  [@yorickausyps](https://community.mp3tag.de/u/yorickausyps)
#### Post date: [November 14, 2025, 1:31pm UTC](https://community.mp3tag.de/t/suggestion-command-sayvar-for-accessing-configuration-settings/70129/6 "2025-11-14T13:31:38Z")
Wow, that was a fast response to the wish for this new command. It works properly, and I want to thank you @Florian ! Sorry for not taking time to search for and mention all the others how had proposed this or a similar feature before.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [November 15, 2025, 8:45am UTC](https://community.mp3tag.de/t/suggestion-command-sayvar-for-accessing-configuration-settings/70129/7 "2025-11-15T08:45:02Z")
Thank you! This is now also supported officially in Mp3tag v3.32.
---
### Author:  [@system](https://community.mp3tag.de/u/system)
#### Post date: [December 15, 2025, 8:45am UTC](https://community.mp3tag.de/t/suggestion-command-sayvar-for-accessing-configuration-settings/70129/8 "2025-12-15T08:45:40Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.