Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

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.