Today I did some specific tests regarding a feature I never told you about: I planned a function in order to automatically update the plane when the plugin find a newer version, in this way you shouldn't worry about missing and/or manual updates and theoretically you could update every single component of the plane (the code allow this), no matter if the update is about a script, a texture, a sound, an object or anything else... the only possible issue is about the generated data traffic when transferring big files such textures or objects, that's something I need to analyze carefully.
In short when an update is available you'll see this sequence:
You'll decide to accept the update or not, it's up to you.
Let's say that you have accepted the update, so let's stop the main script engine:
starting to get the updated files and apply them:
Finally, you'll be prompted to reload the plane:
If something goes wrong during the update process another window will tell you that, the only issues I found during this process are about internet connection and/or server availability, nothing else, in this case you can reload the plane and then choose to try again or decline the update in order to try later.