hopefully I can answer some of your (and Neil's) questions. Snipping, cutting and tugging on your original text is not marked.
Eternal Density wrote: ronaldkr wrote:
Eternal Density wrote:So... This 0 sand/castles issue... I require additional information if I'm to fix it.
Is it a version problem? I have version 1.71 and no problems with "Save"/"Import"/"Export", but I haven't used "Load" for the last 1--2 days.
Eternal Density wrote:Well loading is working just fine on my phone so I dunno. If you briefly open the hotdog in a second tab to see if it loads, then close it, you will be able to test without risking your currently working game.
Disbled autosave and did that, everything loaded properly here. The version number shown was 1.72
Eternal Density wrote:Also I don't understand how you can be on 1.71 without having loaded within the last dip, since 1.71 was only released less than a dip ago.
To get v. 1.71: Probably I hit F5 for another tab not realizing that the SB tab was still active. My heap was last restarted 2013-09-29 (bad practice I know, but Time has eroded my ways a bit), and Opera did not crash since. It's a memory hog all the same, gobbling up >600 MB RAM, but no memory hole.
Eternal Density wrote:ETA downloading Opera
This is a major problem with Opera. What I have is version 12.15, which I would describe as the configurable, slimmer sibling to Firefox that actually does print what you are wanting to print (exceptions are not the rule). They had the great idea to jump to major version 15, using the Chrome rendering engine and throwing out everything from the UI that had made Opera attractive. Bookmarks? Why would users want such a thing. Ugh.
So when you got a JS console you downloaded probably v. 15 -- that works like Chrome.
Now if loading in v. 12 works here and in v. 15 at your place this really points to mustarded data at Neil's installation as you already suspected. :nervously looking at the date of my last backup:
Chirping mustard! (had to be said at this point)