Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

I started the game over from scratch; no skipping the intro or anything

Edit: I have since realized that it also gave me a new instance of the starting quest to talk to Irith and learn about her plans, and pressing the tower duties button again did in fact give a second duplicate copy of the quest.

(2 edits)

This is curious, especially as it would be a game breaking bug.

I downloaded V0.5a Mac and win from this site, played it from scratch until I could execute Tower Duties and could not find anything wrong. It can not reproduce it in either OS release.

Can you send me a screengrab of your ingame debug info screen (you get it when clicking in the top left corner while in navigation mode). Looks like this:


Also, can you briefly describe whether whether issue is 100% reproducable and how (e.g. start new game, get up in morning, do bath task and at 9:00 execute "Tower Duties" command....)

Version 0.5a has been download a zillion times since release and I would get (rightly so) flooded with bug reports if such an obvious error was in the build.

Anyway, thanks in advance for your cooperation.  If it leads to finding the issue you'll get an access link for the latest version (0.5.1 patreon) as "bug reward". ;)

y.v.


This is a screenshot from a brand new run, actually following the exact order of events you suggested as a test!

I started a new game (not skipping the intro), got up on day 1, completed the bath task, and did the Tower Duties option at 9:00, which  went directly from a black screen saying "You spend an hour fixing things in the tower..." to a black screen with the opening line of the game's intro, then on through the rest of the intro all the way through until waking up on day 2 of the game, having completely bypassed the rest of day 1. All I've done so far on day 2 was step out of the storage room so the text of the debug info could have a background it stood out against

(I also did another test following the same steps for a new game, where I did skip the intro, and the only difference in the debug info screen there is that Irith ARO was 5 instead of 6).


Additionally, it seems to me like it isn't actually game-breaking, just feature-breaking? The only thing it does seem to break for me is the tower duties feature itself; I first noticed the duplicate starting quest issue in a run of the game where I'd gotten far enough to have the portal room key, and seemed to still be able to keep going forward with the story, so the only thing the bug is doing to my playthrough is depriving me of any way of passing an hour if I have nothing to do but just want to advance time in the day, unless there's eventually going to be something that I'll need to specifically do the tower duties to unlock (or something that only happens at a certain time of day that I don't have enough actual things to do to advance time to get to it)?

Anyway, thanks for helping me look more into it, and if there's any more info you could use from my side of things, just let me know!

(1 edit)

Thx. I reviewed the code again, the described sequence is impossible for all intents and purposes. 

Reproduction  tests with the 5.0a versions I archived was not successful in producing that behaviour , all worked as designed (pc and mac).

I'm at a loss, but still curious how this can occur.

The only possible way for an erroneous  code flow as described to be even theoretically possible is if the "from _call... " commands renpy adds when the distro is compiled are somehow jumbled/ wrongy compiled / inserted
In that case it should be reproducible, however, which it isn't.

Anyway, I went into the code once more, stripped all the 300+ from commands throughout the codebase per script and recompiled. The mac file is available in the OP as v0.5b mac. Can you D/L and check the behaviour?

(1 edit)

Would it be doable to get a windows version of 0.5b?

In the meantime, I'll go ahead and try a fresh install of 0.5a, just in case something somehow managed to get corrupted on my first install, or something? I'm not sure how anything like that could've happened, but at this point it's the only thing I can think of as to why I could be experiencing a bug that stubbornly refuses to be replicated on the dev's own system.


Edit: Wow... apparently that's exactly what I needed to do? Now I feel bad for how much time you spent debugging something that was just... idk, internet ghosts messing with my initial download/install in the most arbitrary way, or something?

Thanks for all the help trying to figure this out anyway, thought!

See OP for 0.5c ;)