Very cool, I was not aware of that project. You have a couple of options: If the source code is just small (a few files) you could include it directly with the example. The license is MIT so this is possible, but of course then it won't get automatically updated. Plus, if someone already has this node editor asset in their project and they import Cubiquity there will be duplicate code and conflicts. You could change the namespace though. Basically this approach is easiest if the code is small (can remove examples). Disable the example by default until the user manually enables it? Or maybe detect this via an #ifdef (not sure what C# makes possible here). Or can you 'catch'/handle the build error with a custom error message? This stuff is not really possible in C++, but C# is a little higher level so maybe there is a way? Have the Cubiquity example code actually download the library?! That seems kind of crazy. What about Git submodules? Complicated I think. You'll have to do some thinking on this to work out is it is practical... maybe just see if you get something interesting working first. Already done The plugins are no longer pulled from 'Streaming Assets' but instead just put in a plugins folder. Only tested on Windows so far. Great, it looks very interesting!