Pure Script vs Stacked Behaviors

#1 I'm pretty new to TGB so this may be the wrong way to do it but I build a behavior for any interaction with the world (user input or AI handling) and use the scripts to define the world behavior. So the behaviors decide what action is performed and the scripts decide what happens when the action is performed.

#2 I started out using behaviours, but quickly moved to using script. This was because I found it easier to think in terms of Datablocks and Object Oriented simulation. I create datablocks for everything in my game, and assign classes in the datablock. I then use event handling callbacks in script to do the work.
I have removed nearly all the behaviours from my code now.

#3 I lvoe the behaviour approach the most.

#4 i mostly go the script way... i tend to recycle some code from older projects, but i tend to start my projects from scratch and barely use any behaviours.

#5 I don't use behaviors UNLESS there is another behavior out there that already does what I want.

My advice is only use behaviors if you need multiple objects to do something similiar. Such as enemies...

#6 and even then, i stick to scripts... i use to code the functions for, say, enemy attacks, and all i do is on the editor give the enemy its parameters on the level (class and any other needed parameter), so whenever i launch the level on the game, if the parameters are ok, they will all act as programmed on its base class functions and stuff.

i dont know. behaviours its a really good addition to TGB, but you need to get used to them, and so far, im not really into them. but they sure are usefull.