Editor Extension Loading Directory

[reepblue]

One thing I noticed when making an extension to the editor is that Windows gets really annoying when saving anything manually to the Program Files folder. Another thing is that you may want certain extensions for specific projects. 

Maybe move "global" extensions to the user Documents folder, and then have the editor also read extensions within the project folder if it doesn't already. 

On that note, I also think the blacklist filter should also be extended to be project based with an entry defined within the Ultra.json file. Maybe I don't want to see .dds files in a project that I want to use .basis files, etc.

[Josh]

There's probably a good reason not to do this. Editor scripts are like application code. A script can do bad things. If the editor just runs whatever scripts appear in somewhere in a non-admin folder, the editor could do bad things. Making the user copy a file into the "Program Files\Ultra Engine" directory ensures that they have to have admin priveleges to complete that step.

I suppose you could put a script in their that load a folder somewhere else and executes all those scripts, but there's still that critical step where the user has to confirm they know what they are doing and are allowed to.

[reepblue]

Ok, makes sense. Sometimes the most convenient setups aren't the most secure.