Asset Store Package: Includes Project Settings, sets scripting to 3.5
Opened this issue · 2 comments
This is on Unity 2019.1 and probably doesn't come up as badly in previous Unity versions: The Asset Store Package comes with the project settings which are then overridden on import. Given that the mod.io UnityPlugin will usually be added to existing projects that have their own project settings already, this can cause trouble. If the mod.io UnityPlugin requires specific project settings, it would probably be preferable to document those and have developers apply them as needed.
When adding the Asset Store Package to an empty Unity 2019.1 project, this also causes compilation errors because it sets the Scripting Runtime Version to 3.5, which is deprecated. The compilation errors show up in the TextMesh Pro package which requires Scripting Runtime Version to be set to 4.0.
They should remove the Project Settings from the asset, they are pretty much useless and overwrite settings you already had on your project. And it works as it is without those settings.
Hi, I've just tested this on the latest release of the plugin [v2.3.0] on Unity 2017.3, 2018.4, and 2020.2 and it appears to leave the settings intact.
Could you test this and confirm @lazydevyo? Thanks!