Hey thanks for the reply. Actually this question and this question here were asked in order to try and get NodeCanvas working a bit more seamlessly with game state code. The way we ended up solving our issue can be found here.
Essentially what we did was create a new node that allows for both code and actions. This allowed us to be a bit more flexible when it came to prototyping / expediting state code (using actions) as well as executing non monobehavior code in a state.
meatloaf
