
1. Yes, want to do something for all Employee types in the long run, but in the forseeable future i wont need another Button. Maybe when i introduce Station-Independent Fleets and Trading but i dont have a clear plan yet when i will start working on this (this Part would need one on the Captain, and the Manager one may also be used in any situation at some point, not only when assigned to a Station)
2. partially, yes.. thinking about renaming this Var to $actor.$ut_cac at some point because i stuffed in all kinds of Data about my Script in there not just settings.. so just check for both just in case

Will add your $actor.$InUse == true Var in the next Version, no problem

3. This is mostly because i knew in advance that i will need many functions and it would quickly get difficult to organise everyhing in a consistent manner - so i decided to rewrite the Dialogue tree from Scratch, too and share as much as possible between all Actors to make them completely consistent (ok, only within my Script maybe, but if i ever finish this i will also make my dialogue Tree the default one - may take one or two years till that though i think)
4. Yep i am looking into this, but i stil dont understand how Parameters are passed from MD to lua - i can see where they are acessed in the lua script but i have no idea how the Vars get their Value.. already found out how i could modify the conversation flow, but without passing the Action and next (sub)sections there is no use to this