The point is that it isn't annoyingness... it's doing exactly what you told it to:
Maximize for MP regen, and if a slot doesn't have a specific MP regen, use the fuzzy matcher to decide which of the other possible modifiers to apply to each slot.
Now, if you wanted it to JUST maximize for MP regen, you should have run what icon suggested:
maximize mp regen, -tie (I like putting the comma in there to let it know I'm changing between components)
This means only modify equipment slots if doing so will help my goal of getting more MP regen. Anything else is not worth changing for.
By using annoyingness, a subjective emotive term, about the code doing exactly what you told it to you're highlighting a failure to understand what you're requesting, not conveying the emotion you're desiring to share. Better would be expressing the exact behaviour that is confusing you (note that these are examples, and would still have been marked not a bug, as the true issue is your desire to avoid the 'tie' function):
Maximize command changing familiar equipment incorrectly
Familiar equipment changed when using maximize mp regen
If you want to make this easier to do, I'd suggest making yourself an alias similar to this:
PHP:
alias notiemax => maximize -tie, %%
then you can just run "notiemax mp regen max" and it will get you as much mp regen as it can possibly get, without affecting any slots that won't be improved by the change.
Also, "the next best thing" isn't subjective. It's following the chart given in the
wiki article, and available to anyone who actually checks on commands...