You can now host Quest games on any website using Quest Viva’s new WasmPlayer, which is now in Beta.
Unlike WebPlayer, with WasmPlayer games run entirely in the browser - there’s no server component to run, just static files. This means you can have a playable Quest game running on any web host.
It’s like Parchment, but for Quest.
Try it out: All Quest games on textadventures.co.uk have a “Try the new player (beta)” button, to launch the game using WasmPlayer. Eventually this will take over from WebPlayer to serve all games on the site.
Open a local file: Go to play.questviva.com/player and load any Quest game locally. Your file is not uploaded anywhere - the app runs entirely on your device.
Host it yourself: Upload WasmPlayer files to any host like Netlify or itch.io. Upload along with your game file, and set the config to point to it. See the documentation for instructions.
Sounds interesting. Currently, “A Stranger, Unregarded” did not work with the new player on the Quest site. Also, sometimes saving took very long time with other games.
Thanks for the report - that game is fixed now. Saving should also be a little quicker, but let me know if there’s a particular game that is taking an unusually long time and I’ll take a further look into it.
Will it be possible to include Quest Viva WasmPlayer as part of a multi-format interpreter? One of those interpreters that includes multiple interpreters to play different IF formats?
I’ve set up a new Substack, and for my first post I’ve gone into a bit more history about playing Quest games online. It’s a journey that starts with a server in my kitchen.
I’ve just released a new version (6.0.0-beta.50) which gives an easier option for publishing your game to itch.io/Netlify/etc.
You can now export your game from the editor to a single HTML file. This embeds your Quest game data in the player HTML, and that fetches the ~30 MB of Quest Viva WasmPlayer from npm (via jsDelivr).
So it’s a smaller output to upload, and it’s one file, but at the expense of not being quite as self-contained as uploading WasmPlayer yourself (as you’re now relying on a CDN to serve that).
For testing locally it still needs a web server (e.g. npx serve) because of the way the WASM runtime gets loaded, you can’t just double-click your HTML file.