Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(2 edits)

I hope so, I think I just take a timeout.  About  any questions about incognitor and other - you can trust me, I'm JS Developer and know how to work with browsers. Only thing - I'm typing a little too fast and if there is a keyboard shortcut for "Clear code" than I could press it and didn't notice.  
If you don’t mind, I would like to make an offer of autosave: save the game code in another localChange variable, not by Ctrl + s, but by timer. A kind of backup. From it, it would be possible to restore the last autosave.

P.S. Windows 10 x64 / Chrome 79.0.3945.130

UPD. And yes, I have a mid-development version saved.

UPD2. Oh, i remember one more case when I almost lost my game, but stopped immediately. Ctrl+A -> press any key =) It's very very stupid case, but it can be. I once worked with a very similar one. Script is checking for text changes and if the text size quickly decreased to 10% or less - it threw an error.

(1 edit)

I know it's too little, too late, but I have made the following quick changes, and will bolster this in future.

1. Adventuron now stores the previous 10 save revisions (when you press control + s or click the PLAY icon). This should help with disaster recovery.

2. Adventuron now won't save a document if in Keyboard Practise Mode, or if the amount of text in the editor window is less than 64 in length (covers the Control + A, DEL scenario).

3 - If you select "Clear All Text" a backup file will be downloaded from Adventuron to your local file system.

4 - A backup (in localstorage) per game_information / game_name is also stored every time the game is saved, or the tab closed / switched. If the author accidentally clears the editor, then the working storage will be gone, but the last version of the code in localstorage will still be available on a per-game-name basis. This will be the primary form of data rescue in the case of user error, or unforeseen bug.

-----

This is not a long term solution but should help in disaster situations where the code goes missing. 

Why it is not "long term"? These are great solutions, I am delighted. Thank you for such attention!

It's not long term because long-term, it requres UI work around a pseudo file-system (on client and possibly server too), and I don't have time to implement right now unfortunatly. All I can do is try to cover the disaster scenarios in such a small time window.