Andrew Plotkin

Am I right in thinking that in the CoS case, the game is accepting character input repeatedly *without* printing to the same window? I think covering that would handle a...

All done. Note that Quixe's startup methods used to be named Quixe.prepare(image, opts) followed by Quixe.init(). I have changed them to follow the new schema: Quixe.init(image, opts) followed by Quixe.start()....

event(msg, others=None, player=None) implemented.

We'd have to test how this affects all the other things you can do by tapping a web page, such as selecting and scrolling.

Export was added in release 2.0.0. I forgot to list it in the README file, though. Import looks possible but perhaps messy.

(Changed title to just "importing"

Hm. That does sound plausible, yes.

XML gameinfo.dbg files can be tens of megabytes, so this should probably wait until gi_load.js switches over to working in Uint8Array.

Or maybe not. If we wind up usurping websocket connections (no more than one open socket per account), then a retry here would be terrible. In practice we are not...

But then maybe we don't need usurping after all. I've (hopefully) fixed the bug re people apparently staying connected forever.