To be honest, it would have been a better idea to adjust the decodeParameters implementation so that you could write those functions directly in “Text” entry mode there in the plugin parameters.
I’ll make a note to do that when possible, will likely have it trigger on values that begin with ( or function. (That will still be precompiled only once then, so no eval overhead.)
Still no ETA for this or characters-on-windows-support, since I’m still not in good shape to code anything complicated, unfortunately.