I currently have code like this for beta testers. I want them to see it on solving the game, so that I can ask them specific questions that could spoil things if asked too early:
after killing the big foozle:
if the player has the magic charm that prevents them from getting killed:
end the story finally;
else:
end the story;
if beta-test is true, ask-beta-notes;
to ask-beta-notes:
say "Hey, great work getting to the end! I appreciate your commitment.";
say "Here are some questions that would've maybe spoiled things even if I put them in ROT13. So I wanted to ask now.";
say "Was it too hard to find the hidden door in the closet?";
say "(should I implement difficulty levels or a new initial puzzle, etc.)";
This is certainly more than adequate! However, I was wondering if there was something like so:
volume beta stuff - stuff that goes in the beta-testers' version, which I can compile outside the IDE
report ending the story in victory or defeat:
say "Hey, great work getting to the end! I appreciate your commitment. (Etc.)";
My crude try of “report ending the story” failed because it isn’t really an I7 activity.
This would be ideally simple and avoid futzing if I changed what you need for the best ending. It would also relieve worries of the code leaking into a release version.
Is this doable? Inform 6-based solutions are welcome, too. Thanks!