Well, I think I know the answer but I figured I may have missed something.

So...being able to host my own instance of a browser-based quest game, be it server-side or client-side, is pretty important to me if I'm to start using this for a project I've been kicking around various platforms.

But, in that regard it looks like my only option is to grab the whole server code off of git, which doesn't look very easy to use considering I have zero knowledge of C# other than it's not a squishier version of C, and the whole MS stack in general (spent five minutes looking at the repository for app.js before realizing there isn't one >_<).

I understand that Quest 6/Questkit will do exactly what I need in terms of browser-based. Honestly, it sounds awesome, all hail king javascript, but it still seems a ways off, plus the dearth of activity in that area makes me worried that it's stalled somehow.

So, is it safe to start working on a project with Quest 5 with the expectation that it will eventually be portable to Quest 6 and made web-deployable? Would Quest 6 be backwards compatible? Or should I just bite the bullet and figure out the server code?

Quest 6 will make it possible to take an existing Quest 5 game and play it entirely locally in the browser.

It's been a bit quiet on that front recently, as I've been spending time working on the new forums (and also recently moved house). But rest assured it's still alive! Hopefully by the end of the year I'll have released an initial preview or beta version of the JavaScript-based player.