MacOS Mojave removes all support for non-Apple scripting additions. You’ll need to find alternatives for all the Scripting Addition commands used in your scripts.

Why continue to use a discarded tool when we have what we need to do the job?

When Satimage is active, the offending instruction reads:

Applescript:

set myResult to change "(HD)" into "" in myResult without case sensitive

We may achieve that with :

Applescript:

use AppleScript version "2.3.1"
use scripting additions
use framework "Foundation"

my changeCaseInsensitive("aaa (HD) bbb (Hd) cc", "(HD)", "")

on changeCaseInsensitive(aString, |before|, |after|)
   set aString to (current application's NSString's stringWithString:aString)
   set aString to (aString's stringByReplacingOccurrencesOfString:|before| withString:|after| options:(current application's NSCaseInsensitiveSearch) range:{0, aString's |length|()}) as text
end changeCaseInsensitive

CAUTION, the final coercion as text is required because, without it we would get something like :
«class ocid» id «data optr000000009002250040600000»

Code borrowed to Nigel GARVEY.

Yvan KOENIG running High Sierra 10.13.6 in French (VALLAURIS, France) mardi 25 septembre 2018 17:51:55

MacOS Mojave removes all support for non-Apple scripting additions. You’ll need to find alternatives for all the Scripting Addition commands used in your scripts.
Seriously?
System Integrity Protection sounds suspiciously like "We only want our software on these machines"
Well, I already gave the boot to my iPhone. Traded it in for a Samsung phone which I find WAY better than the iPhone.
Maybe the Mac is my next casualty.
I love Applescript, always have. But friends, it is dying...

https://latenightsw.com/mojave-brings-i … y-changes/