SUGGESTION: "Exclude" scripts and actually deleting them

[monkey0506]

If you remove a script, the files aren't deleted. This could be useful to "exclude" scripts from a game. However it is impossible to create a new script with the same name or reimport the script. My suggestion would be that scripts handle this in the same manner as rooms do. An option could be implemented to "Exclude [this script] from game" which would work identically to the way "Delete [this script]" or "Exclude [this room] from game" currently work. The only change to the "Delete [this script]" option would be that the files would actually be deleted.

Also the ability to reimport scripts that haven't been saved to SCM would be appreciated. Since this could potentially lead to users distributing ASC/ASH files instead of SCMs, perhaps it should only read scripts that have been manually excluded. Or perhaps "Include existing scripts". In any case it would clearly only be allowed to work if there was a matching ASC/ASH (script/header) pair.

I'd say this request isn't high priority, worst case scenario I copy and paste the scripts into a clone script, delete the original, and rename the clone. Not altogether a difficult workaround, I'd just say it's more of an annoyance since there's no way to overwrite an existing script even if it's not included in the game.

[FSi++]

Since this could potentially lead to users distributing ASC/ASH files instead of SCMs, perhaps it should only read scripts that have been manually excluded.

What's wrong with that?

[Pumaman]

These sound like reasonable suggestions -- would anyone else find them useful?

[monkey0506]

Since this could potentially lead to users distributing ASC/ASH files instead of SCMs, perhaps it should only read scripts that have been manually excluded.

What's wrong with that?

I don't know that there's necessarily anything wrong with it, but it would seem to defeat the purpose of the work Chris did reimplementing the SCM type for exported scripts!