# Action Goup

**URL:** https://community.mp3tag.de/t/action-goup/19056
**Category:** General Discussion
**Created:** [June 18, 2017, 10:46am UTC](https://community.mp3tag.de/t/action-goup/19056 "2017-06-18T10:46:10Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [July 22, 2018, 9:51am UTC](https://community.mp3tag.de/t/action-goup/19056/13 "2018-07-22T09:51:25Z")

</div>

> [@sheepdisease](#):
>
> These are files created/used by mp3tag so therefore it is relevant.

A documentation is only relevant if the files represent a user-interface.  
They don't.  
The user-interface is implemented in MP3tag and is described in the help.

If you prefer to do it in a different way you do it at your own risk.

There has been a discussion about the contents of the INI files and a way to edit them directly:

> [@\[X\] Comments in MTA](https://community.mp3tag.de/t/x-comments-in-mta/17994/4):
>
> Regarding the filetype ".INI" Wikipedia says: "Semicolon (wink at the beginning of the line indicate a comment. Comment lines are ignored." [https://en.wikipedia.org/wiki/INI\_file](https://en.wikipedia.org/wiki/INI_file) Although a Mp3tag MTA textfile looks alike a standard INI textfile, it is not documented, that both filetypes are interchangeable. One tricky way to add comments into a Mp3tag MTA script file can be as following ... Action "Format value". Field: MY\_MTA\_COMMENT Formatstring: $char(0)'here is a comment line' DD…

The conclusion was: nothing that the user has to temper with directly.

---

_[View the full topic](https://community.mp3tag.de/t/action-goup/19056)._