The current way to advise the user of deprecated method calls is rude: we changed something; the user did nothing wrong; but, particularly if the method call is in a long loop, the user may get flooded with repetitive warnings in the post window (and, if it’s a time-sensitive loop, the user may be unable to ignore the performance penalty of the repeated posts).
Instead, what if we provide scripts to search for keywords that may be deprecated? This is easy in unixy platforms; I’m not sure about Windows.
There may even be ways to report search results proactively (run a search when opening a file in the IDE, say, though automatically checking quark .sc files isn’t so straightforward).
Thinking of this particularly because were discussing deprecation of Condition. That is likely to bite a lot of users in unexpected places. It would be worth considering how to have a gentler user experience here.