why not simply skip this update? it is afterall a beta version.. I just updated to r200 a couple weeks ago, I was on r187 since Nov because of jank issues. There's always the potential for some update that will break your code or force you to rework things a bit... it's par for the course.
Because the saving mechanism is very *integrated* into the coding structure in my game, the idea that I will have to change this very basic of things later on through an ever increasing amount of lines really scares me.
I rather wait for one more release, if really no hope for an improvement for this *new awesome* plugin, then I will go back in fix all the codes and accommodate this awesome bothersome local storage system that makes you wish for a time where improvements actually means improvement and wish the next construct 2 upgrade doesn't come with another awesome feature that requires you to do the following step before you can destroy an object:
Destroying an Object in the next version of construct 2 the same way webstorage is changed in local storage.
Step 1: Call *Is object ready to be destroyed*.
Step 2: A Trigger is return later because parallel processing and all the awesome thing because F you that's why to let you know you can destroy the object now.
Step 3: Now you are allowed to actually called an action called *Actually destroy the object for real now.*
In later more awesome updates, every trigger in Construct 2 will require another trigger before it because F you that's why !
And parallel processing and all that crap.
Because Reasons !