Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Only selecting an option should trigger that behavior. And my testing on my own Samsung device has the expected behavior. I don’t like the snap to top at all, though, and should probably find another way to implement this.

The settings menu is available prior to leaving the main menu via the sidebar. I will consider mirroring the option on the menu itself.

Unplayable seems like a strong assessment even given the more severe setting issue you’ve encountered, but I suppose that is subjective. Not being able to change autosave frequency and some other small number of options on some percentage of Samsung devices is indeed a bug, but hardly on the level of a priority 1 issue like a softlock, at least for me.

I’ll try to resolve the settings issue for the next update. Hopefully I will be able to find some way to recreate it. Thanks for letting me know.

• There's a sidebar?

→ If I can only access the sidebar in widescreen mode;

→ → It doesn't start in widescreen mode.

→ → Widescreen doesn't automatically turn on\off based on phone orientation.

→ → I can't change to widescreen because the menu bug.

• It may not be unplayable for everyone, but since every dropdown I've tried is borked on my phone,

→ I can only assume all dropdowns are bugged;

→ → I can't turn off autosaving — a precaution I use to try to avoid instant file softlocks.

→ → I can't turn on widescreen — when playing games on my phome, holding it in portrait mode makes it impossible to see various things in browser-based software that are intended to be seen while using a PC. Less importantly, holding it in portrait mode is really, really uncomfortable.

→ → Any dropdowns that appear on any screen would be essentially non-functional.

So while I agree "Unplayable" is unreasonable as a objective rating, it was never intended to be. It is subject to my personal experience and preferences. I apologize if it came off as objective.

(3 edits)

You can’t see the sidebar? Wide screen mode will not fix that, all it does is remove the width constraints on text. It’s not like a landscape mode. You should be able to open the sidebar by tapping the menu button on the top left of the screen.

There are also no other drop-down inputs anywhere else in the game. It’s only supposed to snap on the “change” event, your browser is emitting that event on “input”, which is wrong, but browsers emitting the wrong events at the wrong times is not that unusual. In other words, this should only happen in the settings menu anyway, since in other cases, it wouldn’t be a big deal if both events are triggered at the same time. I should note this is not normal chrome behavior, so I need to investigate.

Also you can manual save at any time. Turning off auto-saving is not necessary to prevent soft-lock.

Edit: How to access the menu is explained during the in-game tutorial, immediately after the first sex scene. I feel like the hamburger icon is nearly universal for menus but I guess I can move that even further up and put it on the first screen of the game.

The 'hamburger' in the top left, or rathet the translucent box it is in, is the exact size of chrome's address bar, so my brain filtered it out, since there was a clear division between it and the rest of the screen, and being a solid colour, on load.

Since the buttons for discord, etcetera, were on the first screen, I hadn't bothered to look for a menu button, as I interpeted the opening page itself as intended to be a menu.

My apologies.

 

On the topic of autosaves, many games I play tend to overwrite your most recently loaded\saved — and in many cases only — save file when autosaving, so I feel most comfortable if I turn it off. I appreciate that, from how you worded it, the game has a dedicated autosave slot. However, if it has multiple auto save slots, I'd still like to turn it off as I have limited storage space.

 

I do appreciate you getting back to me on this. If there's any information that can assist in tracking down the bug, let me know how to find it and I will attempt to get it.

(1 edit)

You definitely should be able to stop the autosaving, and use the settings menu drop-downs in general. I’m having trouble recreating the issue myself, so it’s gonna be hard to find. As far as anything you can do, I appreciate the offer. If you can give me the version number of Chrome you are running, that would be great. You can find it by typing chrome://version/ into the URL bar of the relevant browser.

The autosave does use its own dedicated slot separate from manual saves, and there is only one slot. Saved games are compressed so should be quite small, but you should still be able to shut off autosaves, so this is still an issue either way and not ideal or intended.

I will try to find a solution to the bug, worst case scenario is to change the way the settings menu is implemented to totally avoid the snap-back effect in the first place, which is unsightly even when it is working correctly. However, doing that will take time.

It's appreciated either way that you look into fixing it. Take your time though, rushing is rarely a good practice.

 

I'm not sure how much information on the page you linked is useful, but it looks like it stops being useful starting with "command line"; so I copied everything prior to that:


Google Chrome 96.0.4664.104 (Official Build) (32-bit)
Revision e02d4fbca41e7b45560ab92a4cb4a3f6ab09b68a-refs/branch-heads/4664@{#1274}
OS Android 10; SM-G960W Build/QP1A.190711.020
Google Play services SDK=214102000; Installed=214516030; Access=1p
JavaScript V8 9.6.180.21
User agent Mozilla/5.0 (Linux; Android 10; SM-G960W) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.104 Mobile Safari/537.36

If you need more information, just ask; I'll get it if I'm able to. I don't know what the information in "Revision", "Google Play services", or "User agent" is, but the latter two, to my uneducated brain, appear to have information that may lead to what may be causing the bug. I could be entirely wrong, but I copied everything prior to "Command line" just in case they are useful.