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.
SIMPLE Idea, Codex keeps a log of one-time scenes
- Thread starter xiphoidllama
- Start date
The Codex already keeps track of several events. For example, the Dr. Badger "Be a Hero" thing. So it wouldn't be too complicated to let the player re-read viewed (and not repeatable) scenes, but going back and doing it for all of them would be a lot of work.
EDIT: Actually, now that I think about it, aren't most if not all one-off scenes flagged by something that could be used to track them? That way you could just use the flag to let the player re-read them. Maybe make it lore-friendly by incorporating it into the Holo Deck?
EDIT: Actually, now that I think about it, aren't most if not all one-off scenes flagged by something that could be used to track them? That way you could just use the flag to let the player re-read them. Maybe make it lore-friendly by incorporating it into the Holo Deck?
Last edited by a moderator:
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.
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.
Being able to replay the scene because we stored the function that identifies it is one thing. Zevos correctly identified the issue with this, and it's precisely why the mail system works the way it does- when a mail is "sent" to the player, the function that fills in all of the variation in the mail executes and the result of that is what the game keeps around, so random inserts don't change every time you view the mail, or branches that only now apply to your character are displayed even if they would have made no sense at the time the mail was generated.
Technically possible, but it would then mean either:
Keeping the entire rest of the game state around at the time of the scenes initial execution which would be even more data.
Requiring careful inspection of the state as-modified by the scene so that it could be effectively summarised down to only the parts that scene touches and used to shim only the subsections of gamestate that it will read/modify (and then allow those touched parts to be swapped back in after).
The latter has potential other uses, but it's a fuckload of work and imo isn't really _that_ useful. If I got the process down fast enough, then presumably we could keep it active all the time and use it as an undo system, but eeeeh.
Keeping the entire rest of the game state around at the time of the scenes initial execution which would be even more data.
Requiring careful inspection of the state as-modified by the scene so that it could be effectively summarised down to only the parts that scene touches and used to shim only the subsections of gamestate that it will read/modify (and then allow those touched parts to be swapped back in after).
The latter has potential other uses, but it's a fuckload of work and imo isn't really _that_ useful. If I got the process down fast enough, then presumably we could keep it active all the time and use it as an undo system, but eeeeh.
Last edited by a moderator:
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?
Last edited by a moderator:
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?
I don't see this functionality as particularly useful overall though. I mean what is the real return value of such a thing anyway?
Last edited by a moderator:
Basically, if you miss a one-time scene, or just want to revisit it, you can.
It would be far easier for Gedan to create a limited rewind time power. But we already have one, its called save/load.
While, on the surface, this sounds like a vary simple idea, it would:
1. balloon the data size of saves to almost mythical amounts
2. Increase the coding time to implement future stuffs, possibly to increasing the development time to double its current wait.
3. And thats not even including the bessload of work it would take to get the current content ready for this
If you missed something that important there's a save somewhere you can reload. If there isn't you can always play through again. If none of those work for you . . . Save more often and learn from your mistakes.
That's almost never as satisfying as playing through the content naturally, but beggars can't be choosers. Plus some NPCs, mobs and events have great scenes and diologue options that never got finalized in the code (e.g. one of the Penny's first time sex variations).