There are times I would like to rename a script group, either because the current name is too generic, or for other optimization reasons. For example, I had created a My Scripts group, but I want to now export it as a template with scripts, and I would rather change that group name to something more identifiable and so it does not affect anyone else who might have a My Scripts group. When I try to rename the group, it says all external references to the scripts in the group will be invalidated. So I have avoided doing the rename. It would be great to have a new group name propagated to any existing templates and configurations. Is this something that could be implemented?

1 hour ago, ParadiseFlight said:

Is this something that could be implemented?

This is only possible to a certain degree.

The issue is this: AAO can only update script names in axis and button assignments and potentially in other scripts = in those assets that it has in its own database. That is what AAO is doing, those are the "internal" assets and they will be updated automatically.
But there is no way that it could update the script names in the "external" assets, like the StreamDeck, WebPages, Gauges, Script Files, Checklists, Conversations - etc. etc. hence the warning.

While it may look convenient at first glance, renaming groups or scripts is very dangerous. I would recommend using unique group names, ideally containing a 3-5 character label for yourself as the author. Just in case you want to share them - everybody is naming their script groups "PMDG737" - which will lead to conflicts when two authors choose the same group name.

Edited October 31, 20241 yr by Lorby_SI

4 hours ago, Lorby_SI said:

That is what AAO is doing, those are the "internal" assets and they will be updated automatically.

Oh wonderful! This was my main concern. I was misinterpreting what internal vs external meant in this context.

4 hours ago, Lorby_SI said:

Just in case you want to share them - everybody is naming their script groups "PMDG737" - which will lead to conflicts when two authors choose the same group name.

Yes exactly. I had released a template with scripts a while ago, and now with more experience how this works I decided I should use unique names before exporting my improvements. Now I can proceed. Thanks!