Yes. I’m sorry, I read and responded pretty quick and some of what I wrote above wasn’t very clear. I believe any changes to client event scripts, project scripts library, or gateway event scripts defined in the project will result in a project update/restart for that project (but not all projects) when saved and published, while changes to global scripts restart scripting for all projects on the gateway.
Client tag events defined on the client tag will also update/restart the clients running the project they are defined in when saved and published. I don’t believe you can have UDT client tags.
Gateway tag events defined on the tag will not update/restart clients. Depending on what the script does, and whether more than one client will be pointing to the same UDT at a time, it may make sense to define the tag change event script in the UDT if you want to avoid client updates when you add a new UDT instance. One drawback to defining tag change scripts on the tag is that they’re not always easy to find (or at least they are easy to overlook).
On the other hand, if these additions aren’t frequent, maybe the client update/restart aren’t a big deal.
@pturmel, I hope I haven’t garbled anything above… please correct if so!