I'm not sure if this is the same problem or not... If I lock output scrolling, sometimes things go just fine, but often Savitar proceeds to put all output received after the lock was toggled on the last line, making it impossible to view. This persists until input is entered or the bar dividing the output and input is moved.

—Alorael, who doesn't really see this as much of a problem since it's so easy to fix. But it a bug is a bug, and this deserves to be squashed like all the others.

The ability to name triggers instead of just calling them by the text that triggers them would be nice, just like macros aren't only named after their hotkeys.

Another minor change that I'd like would be the ability to put more text into the trigger line.

—Alorael, who also wouldn't mind being able to put a few //notes in along with the reply text. For some of the more complicated and macro-filled triggers, it would help immensely.

I'd vote for C/C++, but only because that's the language with which I am most familiar. Really, almost anything that allows trigger and macro programming is great.

—Alorael, who would have to except a few languages. FORTRAN, for one, is a bit esoteric for casual client-users. A punchcard system might also prove less than popular.