Basically when you unlock a one-time scene, the codex can keep a "transcript" of whatever it was so that you can revisit it when you like. That way, you never lose out on conversations you may have missed.
“Do you have anything that isn’t showing up on the main list i might be interested in?” You ask. Jade gives you a knowing smirk. “I have something… unorthodox if you are interested.” She moves over to a discrete tank in the corner, holding several colorful, slithery shapes. “These little fellas are called Cock Snakes!” She exclaims. {If pc encountered cunt snakes: You recoil, an accusation quickly coming to your lips. Jade cuts you off “They’re legal, with a permit”} You pause, and begin to examine the snakes closer. “They are colorful, sure, but they look rather normal.” The smirk returns to Jade’s normally cheerful face. “These little beauties can attach themselves to you, integrate themselves into your body. They even produce normal cum if you don’t have any junk to begin with. Some systems use them as a natural alternative for dealing with a lack of dicks to go around.” Huh. {If cock: “What if you already have…” Jade grins. “They’ll replace your current endowment. Don’t worry, you’ll be null for less than a minute.” } {Not bimbo, not brute: You idly imagine having one of those snakes slithering down in your {If [pc.lowerUndergarments]: [pc.lowerUndergarments].}{else: nether regions.} Maybe this could work after all. {If Brute: It would be awesome to have an actual python between your legs. }{else if Bimbo: Or… maybe not. }
The problem is that most of the scenes in the game examine your character and determine what you see based on it. The difficulty of writing for TiTS is your not writing for a single, static character. You're writing something that is meant to be as highly varied as the characters that can see it.
Bellow is a scene i wrote for a pet project of mine. It checks if you've encountered cunt snakes, if you have a cock or not, if/what your lower underclothes are, and for bimbo/brute speech and has different dialogue (or lack of dialogue) for each variable. To create a list of one time events, you would need to store the values for each variable for each one time scene, which would quickly require more save space then everything else combined. And thats not even considering the programming nightmare that it would take to make it happen.
Counterpoint: TiTS already stores previous pages as a snapshot; there's a back button you can press to review scenes after you read them. It just only holds 3 pages, is all.
Counterpoint: Doing this effectively requires storing the post-parser scene text in save files. This gets more complicated when we talk about what a scene is- what about scenes that are split into multiple pages? What about scenes that have optional variants? Also we realistically have to at least store the author alongside that, and whilst we're at it we might as well sort the bust display out too and the scene/room name.
Counterpoint: Wouldn't it be, relatively, easier on a coding level to simply have a set of stored calls to the story page for said encounter and possibly even a stored set of pc attributes than it would be to store the text of the whole scene?
haha yeah I see that . . . I was apparently posting as you were having your convo with noob >.<
I don't see this functionality as particularly useful overall though. I mean what is the real return value of such a thing anyway?
Basically, if you miss a one-time scene, or just want to revisit it, you can.
Or, just. Y'know -- read the scene off the github or copy-paste the text the first time you see it and save that on your laptop.