Thanks for the feedback AFRLme; while trying to understand your reply I realized that I wasn't clear on the difference between destination actions
and immediate actions
. It all falls to place now! Initially I hadn't noticed that both Destination and Immediate actions
offer an Execute Command on the Object
action - (Sebastian had mentioned it earlier but somehow it didn't sink in). Now this clarified both my initial question and the later one - Destination actions
make my character walk and align to the target object before execution of the supplied action block, while immediate actions
will execute the actions on the spot. Answering the second question, if I wanted to just look at the mountain without walking all the way there, I just had to write my actions inside an immediate command block (and not a destination one as I did).
I understand your suggestion that it is "better to leave the looking actions for the right mouse button/examine command". But if you must (eg. the mountain pass is covered in mist, but it occasionally clears - if you click on it when it's clear you start walking the path, if you click on it when it's misty, you make a remark about Eldritch varops lurking and stay where you are) then you say that I should avoid having both an immediate and a destination interfrace commands since the immediate always overrides the destination one. So far so good!
Now the next part please feel free to leave unanswered; it's me trying to sqeeze more theoretical understanding - but it's not something I *need to know* at this time, I'm past my initial obstacle at the time of writing.
You went a bit further in your explanation- You tried to answer the what if I wanted sometimes to look first and then walk towards the mountain; while other times only look at it. Yet Both times using the same mouse button. Did I get it right?
While this was not my initial concern (the display text actions were there merely for debugging purposes) I'd like to understand your tip a bit better.
So your suggestion boils down to this: use multiple interface commands and swap/rewire them (via set cursor/set command). The swapping is based on criteria and is performed whenever the cursor enters the target object area (on mouse over). Is that what you meant?
I also understood the usefulness of using the call action part inside another action in order to avoid doing twice the job if they share something in common; but to be honest I didn't quite catch the trick with triggering/calling a destination action block from within an immediate command block...
Thanks again for helping me out!