The linked post is quite old and this problem no longer applies 🙂
I have actually just re-checked moving NodeCanvas in Plugins folder in Unity 2018.x and everything is working fine. Code “mistakes” (as per linked post) in main assembly do not result in “missing” actions or nodes.
With that said custom assembly definitions is something planned, but unfortunately not before support for Unity 5.6 is dropped.
Please do confirm that moving NodeCanvas in Plugins does indeed works for you as well if you can.
Gavalakis
