- Home /
Should I use preview packages when developing Asset Store assets?
I am currently developing an editor tool that I hope to sell on the asset store. The tool would be used both in Editor and at Runtime. I am very interested in using ECS in this tool, but ECS is currently in preview and also there was recently an announcement that ECS will not be compatible with Unity 2021 till the end of 2021 or later.
Would it be irresponsible for me to use ECS in my tool which I plan to charge money for on the asset store? Also, would it hurt sales if Unity users know that this tool depends on preview packages and they see “Preview Packages In Use” when using my tool in the editor? I’m curious what other asset store developers think and what their experience is. Thanks!
I suggest you avoid ecs right now. Dots will target 2020 branch for some months to come and this alone don't bode well for your plans.
Also, entities are just like overhyped int
indices... you can live without those, just by maintaining few NativeArray
s here and there.
Your answer
Follow this Question
Related Questions
Can we access the thumbnail of a unity package from a custom editor script ? 0 Answers
Missing assembly references when importing/upgrading DOTS stack 1 Answer
Assebly definition dependent on asset store package without assembly definition 0 Answers
Managing "MyAssets" 0 Answers
Why does Unity ship official (preview) packages with in-editor-compilation-errors? 2 Answers