I didn't knew that. Probably its bugged or his content was never finalized (Or it was simply not intended to visit him)
There shouldn't be any need to make a platform specific version of the game anymore. It runs in a web browser.
If using a file manager to open a file is too user unfriendly for you, this is probably not the game for you.
In absolute fairness, the game does have a couple mobile-specific issues, like the the pop-up text on buttons popping up for a millisecond and then disappearing because it expects a mouseover and doesn't interpret a touchscreen input in the right way. Having a separate mobile version would enable the devs to fix issues like that without worrying about affecting anything for anyone on a PC.
That sounds more like an issue with the overall design rather than a mobile specific issue. It's less relevant for a game like this that has literally no chance of ever winding up on a console, but mouseover popups are a design element that only works on computers, and are very much something you put a fallback for when designing a game. Even if that fallback is as simple as a minimum display time for the popup. If working with something like that on my own game, I'd actually do a minimum display time in combination with suppressing the current popup if a new one is displayed. (In other words, if you're moving through the page only the latest popup will show, and the latest popup has a minimum amount of time before it goes away)
Fair enough. But knowing the general level of expertise that Fen and Co' seem to display (which is to say, not much) my reply was more aimed toward explaining that separating out mobile and PC builds would ensure that if (or more likely, when) they fuck something up, it wouldn't affect the main PC build.
Given their history, I suspect separate codebases would risk being actively detrimental. I know it absolutely was an issue they butted heads against with mobile flash builds.
You have a point. I defer to your expertise, and thank you for reminding me of the mobile flash build fiasco. I remember they stopped supporting IOS entirely despite there being a simple workaround for the issue that caused them to stop supporting IOS. So yeah, in retrospect, you're absolutely correct separate codebases would be a nightmare for them.
The only tip I can give is to not play through joiplay. Use your regular mobile browser. It runs just fine for me on Chrome, firefox, and degoogled chromium. That said, I don't use the save to file function, like, ever, but I did just check and it does work for me. It might be a joiplay specific thing, or it might be something specific to your android. Try running it in your browser and see if it works there.
Yeah I think the "save to file" button not working is a joiplay specific issue. I try running through my browser and images won't load, I think because I'm on a newer version of android. If I navigate directly to the game folder through Chrome the html file doesn't even show up, which is why I'm resorting to Joiplay. I was hoping to figure out how to get the "save to file" button to work so I didn't have to start over every time I want to play the latest version. Weird how "load from file" works but not the other..
That's definitely odd. Is the game on an SD card or internal storage? And did you preserve the file/folder structure? It definitely loads all the images and everything just fine on my android tablet, but I am using an older version of android so that could very well be your issue. Check your joiplay permissions to make sure it has storage permissions, if it doesn't then that could be the issue. If it does then I don't know what to tell ya unfortunately.
It's on internal storage and I never changed the file structure. Joiplay does have storage permissions. I suppose a workaround would be to find out where Joiplay originally keeps the save files and just copy the file but I've looked through everything I can think of and no luck.
