intfiction.org

This could mess up the saves the player actually wants (in z-code). If I want to keep a single save to revert to in case I mess up in the game, I think I can currently save and then refresh the browser window to revert (because the save file info is stored in the URL). If Parchment autosaves after every turn, I won't be able to do that so easily, will I?

I was thinking more like a system that many non-IF games have where you have the player's own saves and a separate autosave file. The save info doesn't necessarily have to be stored in the URL.

_________________
Vorple UI library — Beta testing site — Blog

I'm using the most up to date version of google chrome. Mostly because it has the least cluttered interface, as I cannot stand bars. It doesn't reload the page on going back and forward. I tested it out using this post. I've gone back and forth with impunity. But Parchment, Quest and Adrift restart their virtual machines when you go back and then forth.

Also, testing it again just now, has anyone else found Quest to be noticeably slower to load than the other game systems. My experience has been that of the comp games playable online (excluding the web-based games), Adrift loads the fastest, then Parchment, then Quest.

Quest 5 games can take a few seconds to load on the server - it's something I need to look at. Quest 4 games load a bit more quickly. It depends very much on the size of the game - Myothian Falcon is fairly big and takes about 10 seconds to load. Once it's loaded though the performance seems acceptable.

By the way, I'll be deploying an update in the next day or two which adds the ability to save games if you're logged in.

_________________
Quest - create and play text adventure games in your browser

Juhana, exactly my thoughts too. There'll still be the option to bookmark a savefile because they're useful for sharing, but savefiles will be saved to localStorage instead.

Joey, well the Firefox interface is almost the same as Chrome's now, the difference being a separate search box which can be removed. I'm not telling you that you have to change browsers, but just pointing out that this problem is really your browser's fault, and not Parchment's.

Intercepting keys at all scroll positions is problematic because I want the up and down keys to scroll through the page, until you get to the bottom when they'll scroll through the command history. However, I guess we could distinguish between the keys we intercept. Maybe it would be safe to block the backspace key from going back a page at all times? Hmm. I think I'll do that.

Okay, I've updated iplayif.com to catch the backspace key.

And remember, in the future please make an issue in Parchment's bug tracker for any other problems you find!