As a package creator, can you install mutable files to the user's Assets folder?

Unity Engine
,
1

I’m working on a fork of an old, open-source Unity asset that was originally released as a unitypackage. I’m trying to bring it over to the new UPM system, but I’m running into a problem similar to what’s described in this thread: Creating a package under Assets/ folder.

The asset uses ScriptableObjects to allow the user to configure the settings. But, all of the files are located inside the Packages folder, so they are immutable — whenever I change a setting, Unity auto-reverts the edit.

I was able to work around this by placing the ScriptableObjects into the Samples folder, as described in that thread linked above. That way, the user can install the sample files to their Assets folder, and they can configure the SOs as they wish. However, this is not ideal, because it isn’t obvious to the user that this “sample” is actually required for the asset to work correctly.

Most Unity assets allow you to change some sort of settings via the Inspector, but I suppose most of these were released as unitypackages on the Asset Store rather than the Package Manager. Is there currently a proper solution to this problem?

2

I store my configs under the Plugins folder and inside an Editor folder if it’s an editor-only config. Example is here:

https://github.com/LurkingNinja/com.lurking-ninja.csharp-templates/blob/main/Editor/CSharpTemplatesSettings.cs

1 Like
3

Thanks! I was able to figure out a solution by looking at your example.