Of course, it's a bad sign when I have to look up the files in question just to refresh my memory, considering that I wrote them.

I think whether you want to treat "roodyinc.h" and "switchgram.g" as shell files to be further-edited or library files is up to you. To be honest, I haven't really been using the system much myself, as I haven't yet updated my text editor templates to use them as multiple files are annoying for cursory projects (which is the bulk of my Hugo coding).

Still, I stand by the hypothetical organizational usefulness, so I'm not going to take the new shells out in the near future. That said, there have probably been 2 or 3 flags added to roodylib.h that I still need to add to the new shell.

So, the new shell definitely has its drawbacks; I'm pretty sure I haven't included every possible library extension, but I don't remember what the logic behind the cut-off was. Just the same, hopefully people like the idea behind it enough that they modify it into somethint that works for them.

P.S. Regardless of whether you change "roodyinc.h" or not, you'll probably want to distribute those files with the rest of your code when sharing the source of your games. Nothing wrong with that.

I did a quick update to "Waiting for The End" the other day, formatting it with the newer version of the Roodylib shell. The only significant difference looks to be that the compilation flags "flags.hug." I think a version of "flags.hug" is supposed to be included in the source directory for every game based on the shell.

What about the other two files included in the shell's directory in the roodylib zip download -- 'roodyinc.h' and 'switchgram.g'? Are these supposed to go into your library directory, to control the settings for all your games, so that you edit these files whenever you want to change a switch or an inclusion?