This looks like a really cool behaviour tree system and I am keen to try it out. Before getting started, I’d like to know what license this asset has? The other BT assets I have looked at, all mention that they are 1 license per seat and so to license for our whole team, we would need to purchase it 4 times. NodeCanvas on the other hand includes the source code, does this mean that it is licensed to the whole team or maybe just the project?
Thanks for your interest in NC 🙂
The license of the assets are depending on Unity Asset Store. Assets that are under the Editor Extension category are one per seat as you’ve seen already. The rest of the asset outside that category fall under a different license. Here is a copy/paste from the unity asset store EULA to save you some time 🙂
EXCEPT FOR EDITOR EXTENSION ASSETS, END-USER is granted a license to install and use Assets on an unlimited number of computers provided that these computers are either all (i) physically located at a single physical location (“Site”) belonging to END-USER, or (ii) laptops belonging to END-USER which have been made available by END-USER to its employees that are employed at the same Site provided all such computers have appropriately licensed Unity software installed. Consequently, any Asset may only be used at particular Site or on computers assigned to END-USER’s employees employed at the same Site and may only be moved to another Site subject to prior written approval from Licensor. THIS CLAUSE 2.3 DOES NOT APPLY TO ASSETS THAT IN THE UNITY ASSET STORE ARE CATEGORIZED UNDER THE HEADING “EDITOR EXTENSIONS.”
2.4
Editor Extensions: END-USER is granted a license to install and use any Assets which are categorized in the Asset Store as “Editor Extensions” only on one (1) computer. For the avoidance of doubt, Editor Extension Assets are licensed on a per computer basis may not be shared or used concurrently on different computers.
NodeCanvas currently is not under Editor Extensions category, but I can’t promise right now that this won’t change in the future. Right now, you are good to go with a single licence considering the above Unity EULA.
Awesome quick reply Gavalakis! Thankyou. It is nice that we only need to buy one license for the team, especially since we are just in the prototyping phase at the moment 😀
So I purchased a copy of NC and I’m experimenting with it now. It is a very nice plugin, good work! There is one thing that is bugging me though. I notice that NC uses a lot of default parameters, because when I build in MonoDevelop for the first time, I get a list of errors until I change the target .NET version to 4.0. This is fine, since Unity still seems to be able to load up and run the assembly no problem. Everytime I had a new script file it seems to regenerate the project file and revert that setting. Is there any way of making it persist?
Hello. I totaly missed your post. I’m so sorry!
Indeed, there are some default parameters used, but those are mostly in editor scripts.
This is very weird, because I don’t get such errors, but I do not use MonoDevelop that often. Maybe there could be a setting in MonoDevelop that reverts it back somehow?
Did the problem still persists?