I'm working on something with Quest that uses JavaScript frequently, with Quest sending values to a JS function and JS functions passing them back to Quest. ASLEvent only being able to take one string parameter functions really limits what I can do with this. Only being able to get a string back means I have to do annoying conversions and type checking, as I'm sending back and forth multiple data types.

This, combined with the fact that Quest script processing and JavaScript processing seem to be asynchronous makes it even harder to work with. For example, if I were to run Quest Function 1 that calls JS Function (that in turn calls another Quest function that sets object attributes), and then call Quest Function 2 the line after, Quest Function 2 would run before or in the middle of the JS function, causing errors in some situations.

It would be nice if there was a more graceful approach to having Quest and JavaScript communicate, because things that should be very simple end up becoming a hassle.