I have a small dilemma with my IFComp game Threediopolis. It was originally a zblorb, but the debug version spilled over into gblorb. I commented out some kind of bulky test modules, and it’s ok.
But it’s still in danger of needing gblorb, which isn’t so big in itself, but I’d like to keep it as a zblorb file, because that means changing fewer dropbox links etc., and I’d just like the game to still be playable in WinFrotz. But it’s not critical.
So I wanted to zap commands and actions I wasn’t using.
understand "rub" as something new
And that sort of thing didn’t seem to decrease the file size. Neither did changing various constants like
Use NUM_VERBS of 500.
(Okay, I would expect this to increase the file size, but…I’m just trying experiments.)
Now I could technically gut the Standard Rules for this game only, but that’d be too much work.
So I’m wondering if there’re any ways to keep down the need for gblorb, or anything specific to I7 that I could/should vet my code for. Perhaps anything (in general) where I7 eats up resources, but I6 wouldn’t.
For instance, I already know that tables are preferable to lists, and I’m wondering if it’s worthwhile to go with I6 arrays (which I do understand) instead of the “[one of] … [or] [cycling]” syntax.
I suspect there are also places where my code isn’t economical, but that’s my own problem.
Thanks for any and all help!
…and, by the way, is there any way to tell how close you are to needing a gblorb file? Like with the diagnostics such as txd on certain settings or something?