I think scripts should be auto-saved to your library when you download them

[PablosScripts]

It makes no sense to have to manually save them once downloaded, it's an unnecessary step and it's very confusing. When I first used the app I was confused about why my downloads kept disappearing every time I went to download a new script!

[Scachi]

+1 ..this is against everything a user is used to.
Like a mail app..you have to save each mail to keep it or it will get deleted when a new mail arrives...not very pratical.

okay..more related to the real topic..
Think about a browser..that is what the Resources feels like..you press download and think you will have saved it to your local device..and not to get it overwritten by the next download.

There is no visible indicator that you have to save it manually...you have to KNOW that you have to save it..or you will loose your work and time you spend configuring the thing your downloaded by the new download.

[Scachi]

Okay, I now understand why you don't have it autosaved..currently this is the only stage where you can assign an Input Translator to a Script/Gamepack.

I have no idea how to solve this in a configurable way with autosaving, maybe we can improve the usability by adding some "Save" button to the Top/Download Area instead.
It can be greyed out when no content is present in this section and highlighted/normal drawn when a script is downloaded already to indicate that this hasn't been saved yet.
Also drawing a blue/red line/arrow on each side to indicate that there is some function when dragging saved content to the left/right.

In addtition to this...
Is it possible to have a warning message when trying download a new file when there is already some unsaved one present ?
One of those message where you can disable it forever (have to use options/reset of the app to show them again) or simply close it when you want to see the warning again.
This way every user will get notified once when there is some unsaved content to make them aware about the need of using the save button.

Here are two mockup images as examples.

A small button at the top right corner, that would leave the space to add an edit button to the saved onces later on to be able to assign a new input translator to a saved pack if there is the need for such a feature.

A row with button: