Hmm...also seeing that line in the developers notes, "You'll have to earn their trust because they have lives to return to if they survive their situation."...is sort of a turn off. And definitely not feeling like a harem vibe ending will happen with that type of statement.
That's sophisticated developer speak for 'they're not braindead turbo-sluts who instantly worship the MC's cock like he's the divine embodiment of fornication on Earth'. In other words, they are actual characters. They have lives, thoughts, desires, and motivations more complex and beyond the scope of just being sex objects for the protagonist (and by proxy, the audience).
Yeah its why ILS is just so goated, the writing is actual writing. The characters have to work their way through mental blocks and stuff needs to be positioned correctly, you need to give proper answers, and appeal a certain way. It's a bit minimalistic by nature, because they definitely dont want to over-bloat text but its refreshing at the same time because it kills me inside so many titles I enjoy where characters hook up once and its like "i love you, I love you more, no I love you more!" ..gag
Agreed. However i like that the dev puts in stuff like this, he did that in N&T too. It's pretty realistic, there will always be survivors who lack survival instincts and are liabilities.
Not lying per se, just how they're choosing to implement the UI. In every version since there has been scenes and a gallery, they added in a whole row to the UI, with later versions adding in scenes that filled it out. So ver0.3 had 3 'locked' scenes at the end of the update, ver0.4 had 2, and now ver0.5 has 1. Presumable whenever the row gets filled and they need more space, they'll add a whole additional row and start filling it in as they go.
Yes, curious about the new ''Sydney'', thought i don't think we move to the hospital soon.
I'm sorry, but an uncaught exception occurred.
While running game code:
File "renpy/common/00action_file.rpy", line 452, in __call__
renpy.load(fn)
Exception: Couldn't find a place to stop rolling back. Perhaps the script changed in an incompatible way?
-- Full Traceback ------------------------------------------------------------
Full traceback:
File "renpy/common/_layout/screen_load_save.rpym", line 35, in script
$ ui.interact()
File "renpy/ast.py", line 922, in execute
renpy.python.py_exec_bytecode(self.code.bytecode, self.hide, store=self.store)
File "renpy/python.py", line 2218, in py_exec_bytecode
exec(bytecode, globals, locals)
File "renpy/common/_layout/screen_load_save.rpym", line 35, in <module>
$ ui.interact()
File "renpy/ui.py", line 298, in interact
rv = renpy.game.interface.interact(roll_forward=roll_forward, **kwargs)
File "renpy/display/core.py", line 3213, in interact
repeat, rv = self.interact_core(preloads=preloads, trans_pause=trans_pause, pause=pause, pause_start=pause_start, **kwargs)
File "renpy/display/core.py", line 4037, in interact_core
rv = root_widget.event(ev, x, y, 0)
File "renpy/display/layout.py", line 1059, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "renpy/display/transition.py", line 48, in event
return self.new_widget.event(ev, x, y, st) # E1101
File "renpy/display/layout.py", line 1059, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "renpy/display/layout.py", line 1059, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "renpy/display/screen.py", line 720, in event
rv = self.child.event(ev, x, y, st)
File "renpy/display/layout.py", line 1059, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "renpy/display/layout.py", line 1249, in event
rv = super(Window, self).event(ev, x, y, st)
File "renpy/display/layout.py", line 245, in event
rv = d.event(ev, x - xo, y - yo, st)
File "renpy/display/layout.py", line 1059, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "renpy/display/layout.py", line 1059, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "renpy/display/behavior.py", line 979, in event
return handle_click(self.clicked)
File "renpy/display/behavior.py", line 914, in handle_click
rv = run(action)
File "renpy/display/behavior.py", line 322, in run
new_rv = run(i, *args, **kwargs)
File "renpy/display/behavior.py", line 329, in run
return action(*args, **kwargs)
File "renpy/common/00action_file.rpy", line 452, in __call__
renpy.load(fn)
File "renpy/loadsave.py", line 769, in load
log.unfreeze(roots, label="_after_load")
File "renpy/python.py", line 2173, in unfreeze
self.rollback(0, force=True, label=label, greedy=greedy, on_load=True)
File "renpy/python.py", line 2005, in rollback
self.load_failed()
File "renpy/python.py", line 1923, in load_failed
raise Exception("Couldn't find a place to stop rolling back. Perhaps the script changed in an incompatible way?")
Exception: Couldn't find a place to stop rolling back. Perhaps the script changed in an incompatible way?
Yes. I have seen this several times when you load a save, but tried to load a save from a previous version of ren'py, maybe a version with some sort of mod (which you haven't load this time), or loaded a save from a version with no mod (and you have one now). Outside of that, haven't had any issues with Toxicity.
Some people gotta try to get the most possible points, have 1 run through the game, and see everything, without looking at the provided PDF walkthrough the Dev does. It has to be in game. Some people are on mobile devices, and switching screens to a PDF vs game is harder. I get it, but also, the Dev can only do so much.
Well, you don't even need the walkthrough: just save, make a choice, check how the game points changed, then rollback (or load) if you aren't happy with your choice.
Or just use URM. It shows all the info before you select a choice. Basically, a universal walkthrough mod with an editor. Never needs updating on a new update and it won't break your game/saves.
