This is just a collection of miscellaneous stuff, ranging from specific small features of the plugin that I couldn't find where to put, to my own thoughts on some design choices.
It'll be presented in a Q&A format, which will make things easier to understand and can be quickly updated in the future, if necessary.
X Map or Y Map?The fastest answer would be to keep things simple, since it's my first plugin.
But there's more to that. Simplicity often guarantees functionality.
AutoMAT started as an ambitious "one-button-does-all" project. It was supposed to figure out everything on its own and give you back a finished product. But in the process I realized there were simply too many things to account for. There was no way this "tool" would adapt to every single user workflow that there is. And everyone works slightly differently, so it was just unfeasible.
So I went back and tried to make an actual tool. Something that relies on a foundation that is shared across the majority of workflows.
That's the reason behind the limited amount of presets and channels available: the goal was to automate the basics, and leave the more advanced subroutines and options up to the user.
On top of the usual "simpler is better" argument, I couldn't really find a reasonable application for them. Specifically, I think they're unsuited for this kind of plugin.
Custom Presets were also a planned feature once. As I went on with development though, I couldn't think of a practical way to implement them.