As I see it, the script tries to write the current value of silentMode to DT’s log window. For that, it uses the handler logMessage which in turn calls DT’s method log message. The latter expects one fixed parameter (the message, which is “silentMode” here) and possibly an additional text in the parameter info. However, the parameter logInfo passed to logMessage is false, i.e. a boolean value. Which makes the call to log message look like
log message "silentMode" info false
which in turn gets converted into
log message "silentMode" without info
(No, I have no idea why that would happen instead of some magic behind the scenes that simply converts info to a string).
You could modify logMessage so that it calls log message (these naming conventions are horrible) like so:
log message logResource info (logInfo as String)
That gives “silentMode”/“false” here in DT’s log window.
Maybe @BLUEFROG or @cgrunenberg have other ideas on that.