Hey there. I have an interactive fiction online at nukuv.blogspot.com and I use the awesome quixe interpreter to let people play it.
First, a warning: This is an adult game.(And a very strange one at that)
But the more important matter. Many many many players run into a *** Run-time problem P7: Too many rulebooks in simultaneous use. error that I never run into when I run it offline. What is going wrong, what can I do! There are no neverending loops that I can detect, and when it comes up, players often report they can’t reload, and all saves are lost.
That question was not directed at you, but at the general community. I think there’s been some talk of doing it, and some people (Aaronius?) have done it with hacks. It’s something I’d like to have for my own games, and it would make it much easier to debug this kind of problem.
Although my first guess would be the same as Zarf’s, this sounds like some kind of memory overflow problem. Is that possible?
Actually, Glulx support was added to Parchment a couple of months ago.
The plugin is done and available at code.google.com/p/parchment-transcript/, but the plugin itself doesn’t support Glulx yet; Glulx support is almost ready but it doesn’t save single-key input correctly at the moment so I haven’t made it available yet.
The most probable explanation is that you have a circular reference somewhere that puts the rulebooks in an infinite loop, like “Instead of doing something when scene X is happening: try jumping” except less obvious of course. The first step is to reproduce the bug so that you can test it yourself. When you know what situation triggers the bug, you can narrow it down or you can try typing RULES ON in the game (inside Inform IDE) so you’ll see what rules are involved in the loop.
Actually, Parchment is itself using Quixe, at least if this is a Glulx game (as it seems to be). So it’s not likely that there’s a Quixe bug that you’re avoiding by using Parchment. But I don’t know anything about the details of the integration (what’s Parchmenty about Parchment + Quixe?), so I could be wrong about that.
In any case, given the nature of the error, I would presume very strongly that the problem is in your code. Regardless of where the issue comes from, you need to figure out how to replicate it before you’re going to be able to tackle it.
I’ve ported GlkOte (the UI part of Quixe) to use jQuery, and have fixed the missing status line in the process, but it really needs more testing. I’d appreciate any testing the community can help with, just try it with this download of Parchment: github.com/curiousdannii/parchm … ball/quixe
Parchment’s Quixe is still fundamentally the same as Zarf’s, the main difference (aside from the QlkOte port in the quixe branch) is that it uses Parchment’s loading code rather than Zarf’s. Which btw, now includes full support for IE! In the future though I plan to mix in more Parchment code into Quixe. For example I want to unify the code which manages getting input from the user so that both VMs feel consistent.