togs-games among other things, there's two breaking bugs in your game:
Code:
While running game code:
File "game/ch26.rpy", line 108, in <module>
IndexError: list index out of range
After a short search, in ch25, there's four candidates put on the list, for four positions. If you follow Lois advice, neither Kari nor Mallory will be added on the list, and you force
ashley.temp
at 0 (line 905) while not offering the possibility to change this, so she'll never be added to the list despite the possibility being in the code.
Therefore, in ch26 when you force a change for
reception_3
(what also looks like a bug, it should only happen if the position is free because previously hold by Cassie, not for everyone like currently; indent error ?) the
candidates
list is empty, what lead to the error I encountered.
The same error happen later in ch57.
Code:
While running game code:
File "game/ch57.rpy", line 1260, in <module>
IndexError: list index out of range
There's no candidates added to the list before the next chapter, while you remove Kari and Mallory from the list, if they were in it. So, if the player listened to Lois, or decided by himself to not give a position to Kari and Mallory, the list will be empty, and the game will break again.
There's also a lot of inconstancy regarding the girls at reception position. By example, looking at the code in ch65, when you tell Aria that she'll goes to London, you switch from
r1
to
ar
if Aria was "ES Senior Receptionist", as if that position should be assigned to
reception_1
. But in my play while Aria is "ES Senior Receptionist", she's
reception_2
.
It don't even match your own intent, since in ch26, it's Cassie that you force at
reception_1
if either Kari or Mallory where at that position.
But it's just the most obvious issue, because you see the change of interlocutor during the dialog, and because of things like that:
And also because after that, Cassie (who's
reception_1
in my play) disappeared from the reception desk and is expected to start working soon... It's funny that her, who was "ES Receptionist" since so long and is now "ES Senior Receptionist", need to be hired and taught her job, before she can replace Aria that was never at
reception_1
position.
But it's not the only issue here. There's sometimes only one girl visible at the reception desk, while there's two involved in the discussion.
Pointing to the same issue, there's also all those talk about Bree. Like MC being confused by her hairs being sometimes long, sometimes short, or Lois asking her to take care of her skirt. What is really confusing, because Bree was never ever shown at the reception desk before the mess between Aria and
reception_1
.
Talking about it, this issue with Bree is probably the reason why there's, time to time, an image missing for
reception_2
. I guess that it happen when Bree is expected to have her alternate hairstyle... except that it's not Bree that is at that position.
There's also the issue with Kayla being pregnant even while in my play MC cum inside Rei's mouth and
kayla.unprotected
is at 0 as expected... I'm far to be strict regarding the realism in stories, but here it goes a bit too far.
And, looking at bit at the code, there's also many variable adjustment that feel totally wrong. Like by example in ch76:
Python:
if hasattr( lois, 'sapphic' ) and lois.dates & 4 and lois.sapphic < 20:
$ lois.sapphic += 40
else:
$ lois.sapphic = 0
The issue here is that if
lois.dates
have it's 3rd bit raised, then
lois.sapphic
will be either 20 or 40... Therefore it will fallback to the
else
part and be reset while it shouldn't be.
You also force
loisslave
at False in ch70 if her relationship isn't anymore "Slave". What feel right, but conflict with what happen later, by example in ch76:
Python:
if relationship.index( kari.relationship ) > 2 and lois.relationship == "Girlfriend":
[...]
if relationship.index( kari.relationship ) > 6 and loissub:
[...]
if loisslave:
[...]
According to the forced change you did in ch70, Lois can
not have "Girlfriend" as relationship and also be a slave. This despite the dialog clearly showing that she want to stay MC's slave while being his girlfriend, to what MC agreed without hesitation.
All this is a pity, because all in all the story isn't this bad, and probably more coherent than it seem. But all those inconstancy present the characters, as well as the story, as way more versatile than they would probably be without them.
For once there's a game that should deeply adapt to the player choices, making us feel like what we decide really matters. Except that in the end it only matters if the player made the few choices that you can think about, or that you haven't forgot. And, yeah, I'll repeat myself, this is a pity. The game could be good, but in the end it's below the average.
I know its not what people want, but I think that the project would be best served by saving all of the scenes and renders that have been done, but starting fresh with a new base system for the game and building everything back in a more user friendly, intuitive way.
Totally second that.
A good thinking about what variables are needed, a good list of each events and their possible outcomes, and a stronger code as base, could really make a huge difference in the way people perceive the game and the story.
And probably also get ride of the "who and at what position" part, or having it in a more restraint way. The player have the final word when it come to showing interest, or to fuck, a girl, so there's no need for him to decide who will be hired and at what position. Especially since, time to time, there's forced changes.
Having Lois explain that she hired X or Y at this or that position, like she did for Tilly if the player don't chose her as flight attendant, would be enough. If the player isn't interested, he'll just chose to not show interest and decline to fuck her. But at least the code would be simplified and the development made easier; there's part of the code with near to twenty to thirty lines of computation for just for two lines of dialog, that half the players will not even see because they haven't hired the right girls at the right position. And in top of that the story would feel more constant.
Plus, some of the secondary girls have either a story, a sex scene, or a role to play in the main story, but it will only happen if they are at a given position. It's by example the case for Rei. Outside of the possible threesome (where she'll just eat Kayla's cunt) she's a purely background character, unless she's "ES Intern".
Of course, the girl's interview give hint regarding who could be at what position. But let's be honest, no one cared about this, we all chose the girls accordingly of our desire to have sex scenes with them. So, not having to chose wouldn't change much, while not being frustrating, giving the impression that we will never have sex with a girl just because we haven't hired her at the right position.
FaceCrap
There's something bugged with the side images.
I only had two times a missing one, both for kira in a early chapter, but the images exists and nothing in the code pointed to a possible error. Plus, it was limited to a single chapter, all the occurrence that happened before it, or after it, worked fine.
Therefore despite you and me having played the same game and same version, and more or less at the same time, we didn't had the same side images missing :/ As reference, kira smile side image is used 107 times in the game, and the error appear only once in your list.
And for once it's not due to the mess with the girl assignment, because seeing the list it almost exclusively concern girls that aren't hired/assigned by the player.