One of the issues I am confronting is that I need to have something reusable.

There will be a lot of in-fighting...they're bandits

So if I create different fights for different quests it seems to me that it would become unwieldy.

You say something about "quest script"...is that a script you'd add to the Scripts tab in a quest?

Yes. It's better to create a new script that use the existing script (with the quest stage fragments in), because there's no risk of messing up the fragments as you edit, and it's clearer without all those comments. But in your stage fragments you can set the kmyQuest dropdown to point to your new quest script when you want to access a function, and do

kmyQuest.StartFighting()

for example.

I'm sorry, that went way over my head

If I set it so the fight starts at a Stage then I would have to re-do the entire quest as the fight is supposed to start during the Scene dialog, right?

I mean...the quest is finished other than the fight. I would hate to have to redo it at this point.

No, that was just an example of calling a function in a quest script from a stage. It's fine to start the fight during a scene.

Well, that takes me back to where I was.

A fight that never ends.

Where do I turn on script logging?

I've looked around and can't seem to find it

Thanks!

Attach a script to your quest. Inside this script, define a single function that will start the fight. Then, in the quest stages tab, add a fragment to the stage where you want the fight to begin, and point at the script that you stuck on the quest. Inside this fragment, simply call your function. Getting the fight to stop is as simple as having your quest progress to another stage, calling another fragment that points to your script and runs the same function with some parameter to stop the fight or a new function to stop the fight.

To clarify, you should have a script on the quest script tab with the function. Your fragment should be kmyquest extends myquestscript where myquestscript is the script with the function. Then in the fragment you do kmyquest.myfunction()

I think I understand better...I think...

What you're saying is that scripts are "held" or whatever in the scripts tab, sorta like a container. The functions within those scripts can then be called throughout the quest as long as the stage has been set to the particular script you'll be needing.

Is that about right?

No, not really. Quests, like other objects, can have scripts added to them ('extending' them). These scripts can contain functions which can be called from any stage or scene phase or dialogue fragment. The only difference is that in calling them from a stage you can use the special kmyquest variable, with the kmyquest dropdown box, to avoid having to make a cast in your script. In other words, where in a scene phase you have to use something like

(GetOwningQuest() as MyQuestScript).MyFunction()

in a stage you can set the kmyQuest dropdown to MyQuestScript and then just write

  kmyQuest.MyFunction()

It's a coding convenience, that's all.

But don't put stuff starting or stopping the brawl in your quest stages - I happen to know that those are triggered by your 'detectplayer' marker, and will foul it up. The RegisterForSingleUpdate method I showed works fine.

I think I've been over-thinking all this.

When someone says "quest script" I automatically think the source code that runs the quest itself. It's been about 30 years since I programmed and I'm not used to the meaning of the word "script" as to me it means something a lot more involved than snippets of code with functions like the CK uses and it confuses the heck out of me when people use that and some other words when talking about doing things in the CK.

edit

Heck....I'm still so used to line numbers I use NotePad++ just for that reason lol