Okay so according to @Healthire behavior logging has been improved a bit. But their are several issues that still need to be resolved to make everyone's lives easier. It tells us whats wrong if it crashes on start up, but it doesn't it tell us the actual behavior. Which is actually quite frustrated when you have 7 behaviors. You got SB to launch yey! You spawn in your enemy and are teleported back to your ship. You check the log and this is what you get. https://pastebin.com/9Z6A52dN Welcome to my world the last 3 days. And i've grown tired of trying to figure it out on my own with the limited information that log gives me. I'm going to say that without knowing which behaviors are causing the errors, that when you have a boss with it's own behavior and six modules. Well your gonna have a bad time folks. Case and Point: We need better behavior logging.
That specific error is that it's trying to get a LuaFunction but is getting a LuaValue (probably nil) instead. It means it can't find the function for a node in the script environment. Every node in your behavior must exist as a lua function by the same name, and your nodes must specify what script to load to find that function. But yes, it could have more useful error messages.