Greetings everyone!
I seem to have a problem with Sugarcube 2.0.0 on Twine 1.4.2 . I have decided to retest my game on mobile. Apparently, when I stared playing and clicked to save. It would say this:
Apologies! Your browser either lacks the capabilites required to support saves or has been disabled them, so saves have been disabled for this reason
The former may, probably, be solved by upgrading your browser. The latter may be solved by loosening its security restrictions or, perhaps, by viewing the game via the HTTP protocol
When I first experienced it, I made it into an Android app using Crosswalk. I figured it must have been something with Crosswalk so I put it on a site and tested it on Chrome and Firefox Mobile. Same response. THEN I tried Chrome Dev. Guess What? Same Response.
So I was wondering, what am I missing? Am I missing a script? Am I doing something wrong here? Do I need something else? Did I screw up?
Yes I know...alot of questions.
Please and thank you for your help.
Comments
When you say, "[…] I put it on a site and tested it on Chrome and Firefox Mobile", I assume you mean the basic compiled HTML file generated by Twine?
What is "Chrome Dev"?
Is this thing available someplace for testing?
Should have been a bit more explanatory on that one, my apologies. But yes, that is basically it. Chrome Dev for Android.
That is also what I found odd too. I figure it would work. But yes, I was referring to the Crosswalk Project.
Yes. Both HTML file standalone and placing it on my testing live site. Again, I was not explaining things well. Which is very odd.
It is uploaded to this post. The .apks and original html file that came with it. It has been zipped for people's convenience.
FYI: Your "uploadGameJolt" macro is not compatible with SugarCube as-is (I assume you downloaded it from GameJolt Trophies/Scores for Twine). It was written for the Twine 1 vanilla story formats. It doesn't look like it would be hard to fix—it seems like it's only a wrapper around the normal Game Jolt API library by Maus. It also seems to be an older version, or maybe you've removed features.
I'll publish an update fixing that soon.
You'll still need to update your "uploadGameJolt" macro though.