This is not unique to FileMaker 13. As far as I can remember, this has always been the case. Much like field names, when you set up a button, script trigger or Perform Script step to perform a script, the reference is actually based on a hidden ID generated when the script is created. This is why you can rename a script and not break any references to it.
So the only problems created by two scripts with the same name are when you import scripts and when you go to select a script in specify script dialog and have to figure out which identically named script to select.
please send feature request from Filemaker website.
This report is to clarify wether this behavior is a bug or on purpose and therefor, if this behavior will change with next update or not.
I see pro's and con's for both states and can deal with this easily. Though I don't see the need for a change.
Thank you for your posts.
Having scripts named identically is a conscious decision. Simply, if you have three different access accounts, where each account has access to its own set of scripts. Suppose that each group has a unique "Print Labels" script. It may be confusing for some users to see "Print Labels 1", "Print Labels 2", and/or "Print Labels 3".
Thanks for clarification. I stepped into this coincidentally and now I'm starting to see the Pro's on this behavior.