Note: You can change font size, font face, and turn on dark mode by clicking the "A" icon tab in the Story Info Box.
You can temporarily switch back to a Classic Literotica® experience during our ongoing public Beta testing. Please consider leaving feedback on issues you experience or suggest improvements.
Click hereOne of the things I like to do with my stories, is introduce various features that might only be picked up by attentive readers. Usually this is mundane, in the form of foreshadowing.
For example, in "Toofy", the namesake's victory is only made possible by an event that occurs in chapter four. What happens there, is what makes the twenty third chapter possible.
However, as well as something immersive to the story like that, I also like to break the mould a little. In "Cocktails, Heels & Desperate" I poke fun at myself and my thing for catgirl stories. A self-reference being the highest form of arrogance for a writer, whilst also being self-deprecating.
But the most fun I have, is giving puzzles to my more attentive readers.
Sadly, most of these go unsolved, even when people assume that they have fully solved the puzzle.
"Coming Home" was the first time I embedded morse code into my writing. I thought it was a nice little touch, and fairly obvious. However, even for most people that noticed it, they missed that I wasn't just repeating the same morse code. There's three different messages - most readers only picked up one or two.
However, due to typography and the web, I didn't quite like the way that the morse code came out. The kerning made it more difficult to separate certain symbols.
So, the next time I used morse code, in "Cocktails, Heels, and Desperate", I changed up the symbols. At first, the editor thought it was randomised garbage from my upload and stripped it, and I had to request for it to remain unaltered.
Strangely enough, though, to date nobody has come forward and said that they've managed to decode the very simple messages for that tale. I also made it more obvious that the encoded messages are different.
Finally, my most recent puzzle to date is found in the second half of "System Restore". This one is slightly harder than previous ones.
The puzzle is actually a two parter.
First, the key is encoded in a simple rotation cipher, and presented along with a notification that makes it seem like a glitch, which happens now and then throughout the story. Hidden by the narrative, if you will.
The second part of the puzzle is an encoded message. To decode it, you need to do a simple alphabetic substitution. Basically, write down A-Z, and then beneath it first write the key, and then write the remaining letters of the alphabet, A-Z, without any repetitions. Then you can substitute from one row to another.
I expect that one will go unsolved for a lot longer, but there's four messages to decode, and the last one is extremely obvious and should hopefully prompt more interested readers to go back and find the rest of the puzzle.
However, being a multi-step puzzle, it might be too much for a place like Lit. It is certainly ambitious.
The main reason I like adding features like puzzles to my stories is that beyond "strokability" I want my tales to be re-readable. Some of them follow some pretty standard arcs, once you remove the cruft, so they need something to make you feel more involved.
It's also a way of me as an anonymous authour to directly engage with my audience. To prompt them to reach out in victory, and let me know that they saw me teasing their brain, and triumphed over the challenge.
It helps to create a connection between random strangers.
Some authours on Lit measure their success by the rate of "Hot" marks they get on their stories. Some by the number of reads a tale gets. Others by the star system. And yet more have some wider reaching statistics.
For me, engagement is the metric.
I do consider almost all of my stories to be a success - because I write mainly for myself. I create tales that I haven't seen, or haven't seen in a way that I consider to be polished well enough.
So my stories are a success, because I enjoy them. If they don't succeed, they don't get published. (I've only got a dozen or so failures sitting on my hard drive, waiting for me to rewrite them...)
However, to be more than a success, a story needs to reach the rest of the audience. I get the biggest thrill in knowing that I bring entertainment to other people.
Sometimes, my fantasy stories get a massive braindump from fans trying to predict where it might go, and I absolutely adore it. That they've picked up on all the details I've put forward.
It's a little bit harder to get that kind of response in a down-to-earth romance. There are some, like the infamous box from "Coming Home", and the speculation that it invites. However, for the most part, I don't get to offer up an entire world, just entangled lives.
Thus, the puzzle.
Hopefully, this reminds my readers that there are puzzles out there in my writings, and not all of them have been solved - even the simple ones.
And that I would adore hearing from someone who found and decoded the messages.
I did recognize that there were unusual aspects in the coding in chapter two of System Restore, but the legacy of damage to the contents of my skull combined with the fact that the last (only) programming language I learned was Apple Basic back in the late 70s/early 80s meant that I wasn't going to try to puzzle them out to see if they meant anything or not. I was a hardware guy, not a software guy as a computer tech, though I did have a certain skill at crashing programs and recording what I had done to send off to the programmers so they could bug hunt through their lines of code.
Of course, not that I know that they are actually meaningful, and are ciphers that can be figured out through time and testing, I am tempted to go and puzzle them out. :-D
I knew that System Reboot had to have something coherent in the gibberish, but I'm not talented enough to break the code.
I am proud of the fact that I did successfully read ALL of the morse code messages. I'm nearly certain that we discussed this in a private email something like six months ago.
Thanks for taking me in as more than just a fan of your work. I truly appreciate and enjoy our friendship.
JCL
@anon - The garbage messages in System Restore Ch1 are references to old computing systems. They're just very old timey cultural references (and you might need your manuals from the C64 and IBM PC to work those out). The puzzle is only in Ch2.
I never thought had anything like that, I saw some Easter eggs like some words but never put it together will, not that is a bad thing.
I will admit I was planning to go back to re-read System Restore one of these days to figure out those messages.
The realistic boot sequence (start at FFFF0h, boot through int 19h) made it obvious (to someone in the know) that the messages were meaningful. So I assumed that the garbage output was meaningful too — and it seemed like some sort of code.
Now I have a good reason to check it out. And I'm looking forwards to it!