I mean what I think people didn't understand, is that I don't plan on blocking your guys from cheating. This is not a bug with a particular game, or really a bug at all. Let me be clear, this is a hard limit to the amount of data SugarCube can store on your computer, imposed by developers of SugarCube Twine. Sugarcube just doesn't raise the quota by default. There's obviously ways to increase the limit, since many websites store way more than 5mb.
#Gamcore become someone how to#
There may be a way to bypass this size quota limit in SugarCube, such as forcing it to save to a seperate cookie, but I'm not overly familiar with SugarCube to know how to go about doing this.
Easiest way to clear them is to type "localStorage = " to wipe the entire array out, but this will delete all your saves for all HTML games.Īnother way to go about this is if you look at your browsers cookies (google how to do this since its different for each browser) you will find a cookie that either has no name, or is name "file://" and delete that cookie, but this will, again, delete all your HTML game saves.
#Gamcore become someone full#
If you're getting a quota error, the array will be full of lots of different entries. If you open a SugarCube game (to force it to access this cookie/namespace) then open your console and type "localStorage", you'll see what I'm talking about. The only way I know of how to fix this error is to either delete this cookie, which will delete all your HTML game saves for all games you've played in the past, or to go to the individual games and delete the saves manually, which can be difficult as you may have deleted the game itself, as I had done. One of the hard limitations of most internet browser is that it forces a 5-10mb size limit on the size of this cookies, so if you're like me, and have played a multitude of different HTML games found on this site (and others) and have saves from all of them, eventually you hit that limit, and SugarCube games will just start throwing a size quota error when you try to add to that array. SugarCube has one fatal flaw in its save system, and that is, *ALL* game saves are stored in a single array as a type of cookie.
#Gamcore become someone code#
Get rid of both of those bits of code and just store the hashed value of whatever string you choose as the password.Įdit again: It's 20ER12, just confirmed myself.Ĭlick to expand.What is the error it's giving you? In any case, thats probably a mistake that you're hashing two seperate strings to the same variable. Not actually sure which one is being hashed to the value I stated above "1477922508" but one of them is. I see both 20ER12 and CD41NJE being hashed to the same variable. *types in console ".rr = 99*Įdit: Just noticed that you're hashing two entirely different strings to the same variable in your HTML. "Oh no, I don't know the password, I cant get my +15 Kate corruption." Most Twine developers don't even try, either because they don't know how, or realize that its ultimately a futile endeavor since the variables are exposed. I have to give you credit though, for at least attempting to obfuscate the password. It will mean you would have to hash the strings on your side before release, and then only have the hashed value in the released HTMLīTW, the hashed passwords are stored in that same SugarCube variable object I mentioned above, but at least they're gibberish numbers and not plaintext strings. Bath: 1477922508,At least then you won't be hashing the "key" in the same place as the "lock".
0 kommentar(er)
