Spankers, Spankees and Switches of All Ages (18 and above),
I’m cranking away at the content for the second day of episode 3. Not sure
yet when I’ll have it ready though, especially with the holidays.
I’m honestly not too happy about how
this episode is coming together. I don’t think I’ve got Prometheus
and Poseidon figured out yet. But I already threw things out and started
over once, so I don’t really want to do that again. Especially since I’ve
already released a day of content. Regardless, expect more opportunities
to fight alongside Tempestas in the next episode, and a little bit more
time with Natalie.
At this point, the code engine is pretty much complete, and we’re
transitioning into maintenance mode. What that means is that we won’t see
any big changes. There will be some new features, but
they will mostly be quality of life stuff (like auto scrolling combat).
Nothing that will fundamentally change the experience. Here is
my current task list:
1. Improve the performance of the character selection screen.
Sometimes flipping through clothing options, there is an apparently random
delay of a few seconds before responding the player’s input. I think this
is because of some old, poor implementation choices I made when I was first
learning Lua.
2. Cleanup the combat code. The code for combat is *way* more complicated than
it needs to be, mostly because of an abortive attempt to reuse some of the
story mode code. This is the only part of the codebase that I consider truly
gnarly. Simplifying that will make everything so much easier going forward.
3. Autoscrolling combat. This was one of the first feature requests I got, and
hopefully I’ll have an easier time implementing and fiddling with it once I’ve
simplified combat a bit.
4. An additional “help” screen where players can look up characters.
5. Expand the help screen with information on statistics.
6. Add power information to the help screen.
7. Change your outfit without having to go to the character screen.
I’ll accomplish each task between episodes. That should hopefully strike a decent
balance of generating more content, and keeping the codebase healthy.
Of course, this is just a preliminary list. If anybody has experienced
any pain using the game, please let me know. I’ll try to work with you to come
up with a solution, and add it to the priority list.
I’m *especially* interested in anything that makes you feel like you’ve wasted
any time at all waiting on the game, rather than the game waiting on
you. Every minute of your precious time that you dedicate to my game is an honor,
and I don’t want to waste any of them.
AKA
Uploaded a new version. This one doesn’t have any additional content, but does address a concern from Magus Eternal. Now, when you select a power to use in combat, the game will display a brief description of the power. It means one extra key stroke to actually use a power, but it should also help people keep all the powers straight.
AKA
Released the latest version, 3.1.9. This is mostly a maintenance release. It fixes the following bugs:
1. There was some text that wasn’t dynamic, but should be. So we had problems with the game referring to male PC’s as “she.” I fixed all the ones I could find, if people find any more, please let me know!
2. Fixed a crash when fighting Prometheus and Poseidon on the average intelligence. It was the same problem that afflicted Succubus way back when. I really need to start testing on average intelligence in addition to smart. Thanks to a certain fan for emailing me about the problem, and including a log. I knew the issue as soon as I saw the error message!
It also introduces two new stats: victory and defeat. Victory tracks how many optional fights you’ve won, defeat tracks how many optional fights you’ve lost. This will be used when people are gauging how competent you are.
Spanker and Spankee now tracks *all* spanking scenes, not just the ones as a superhero. Or at least, they should. Let me know if you don’t see thsoe stats go up after a spanking!
All saves should be 100% backwards compatible. Victory and defeat will just start at zero. However, this shouldn’t be a problem because the game doesn’t actually use absolute numbers when evaluating how competent you are. Basically, if you’ve won twice as many times or more as you’ve lost, you’re considered competent by people. If you’ve lost twice as many times as you’ve won, people consider you incompetent. If neither, people consider you middle of the road. Spanker and spankee work the same way.
I’ve also improved my event validation some. So that hopefully in the future new content will be more stable (not stable of course, but *more* stable).
AKA
Uploaded a new version with a bug fix for a crash that triggers when you try to use the spank action given to you by s-paddle. Thanks to VikingSpanko over on animeotk for reporting the problem!
I used mediafire this time, because my internet is being painfully slow, and mediafire is more forgiving of slow uploads than Dropbox is.
AKA
I got tired of having to play whack-a-mole with players to track down all the crashes, so I’ve added some validation logic to validate:
1. Every event referenced is defined.
and to warn me:
1. Of all events that don’t have children (i.e. events without choices, or anyway of transitioning automatically). I can’t error on this, because obviously the last event in the game doesn’t have any children! I may go back and add a flag or something to events to allow me to say “this is *supposed* to be an ending event.” Then I *will* be able to error on this.
2. Of all events that are unused. This one definitely can’t be an error, because there are some events that are used, and then become unused. Basically, at the end of the current content, I have an event that says “Thanks for playing blahblah blah.” Obviously, I can’t remove any of those events, or people’s save games will break.
This won’t fix every possible crash (like if there’s a problem in any dynamic text), nor will it fix combat bugs. However, these checks should catch the most commonly reported bugs and crashes.
I’ve also implemented it so that I can turn the validation on and off. It doesn’t run in the version that I post, so it won’t affect startup time!
Anyway, this validation caught a few bugs, so this version fixes them:
1. Male characters weren’t being given the correct default outfit at the start of episode 3.
2. Fixes a bug in the sequence after you defeat a certain villain with a certain ally that resulted in some skipped text.
I also removed a few events that were no longer used.
AKA
New version posted, fixing a crash in episode 2 day 1 kindly pointed out to me by a fan via e-mail. This is what I get for modifying earlier stuff. -_-
Just posted another version that fixes a few crashes in some of the paths leading up to the fight against Prometheus and Poseidon. Hopefully this will fix the problem for Anroop Kaur (thanks for letting me know)!
New version out with a fix to three bugs:
One, pointed out by giant432, was a crash caused by a borked option when talking to Natalie while going to get tutored.
The second, I discovered while getting to the point in the game that crashed for giant432, triggered if you didn’t get spanked by David in class.
One pointed out by Canth, where I’d forgotten to include some choices in an event (that I edited while debugging the new content) way back in episode 1 day 1!
Spankers, Spankees, and Switches of All Ages (18 and above),
I’ve just released the next version of Scarlet Moon: 3.1.0. This version has the first day of episode 3. It includes:
1. Your first of two potential love interests. The current plan is to have one dominant male love interest, and one submissive female love interest. While I’d love to have four possible love interests, things would either get complicated really fast, or generic really fast. I figured these two would cover *most* people who play my game since it does focus on spanking female bottoms. That being said, your gender imposes *zero* restrictions on which love interest you can hook up with.
2. Two brand new supervillains. One male, one female. They work the status system in a way that it hasn’t been worked before, so hopefully you guys will find them fun to fight.
3. An X/M spanking scene. It’s basically just a copy of an X/F scene with all the “he’s” replaced by “she’s” but hey, it’s an X/M scene! It’s also very easily avoidable for people who aren’t into that.
4. A brand new superherine(well, not *completely* new…)! She shows up for all of five minutes, but hey she’s there. You might even get to use her in combat!
5. A chance to really meet Natalie. No, you don’t get to spank that big nerdy bum of hers. Yet…
Get it over at the Downloads section.
AKA
Spankers, Spankees and Switches of All Ages (18 and above),
I’d hoped to have the first day of episode 3 ready by now, but alas, I do not.
Sorry. I failed to account for the fact that it usually takes me about a week
or so to shift my headspace from “writing” to “coding” so I haven’t been as
productive implementing the powers and characters as I hoped. I’m currently
working on implementing the villains’ powers, and the powers for Tempestas.
Should definitely have something by October, possibly earlier depending on how
many bugs I run into.
Also, I recently linked a new game to Other Spanking Games. It’s a CYOA called
the Rear Gaze Hotel. I really enjoyed it, so I’d encourage you to go check it
if you haven’t already. Hopefully, it can keep you mollified until I release new
content for Scarlet Moon.
AKA