Allowing user to cancel walking towards a location that triggers a cut-scene

actually it should trigger the action when the character reaches its object destination unless you set the action triggering to "immediately". 

Ah Sebastian! Such silliness, I didn't even test it - I assumed right off the bat that it wouldn't work! 

It's best if you leave observation/examine type display texts to your examine command or right mouse click.

One thing you could do is in the mouse over action check a condition then set another command (not a good idea to have both immediate & destination actions for same command inside of a scene object/characters action list because it will always trigger the immediate one instead - same goes for left click immediate action. Anyway, my point is that you could on mouse over query a condition or value & then set a command accordingly which you can then use to trigger certain actions. Now, what you could do is have it call the destination command action block at the end of the immediate command executed action block.

Sorry if this is not making much sense. Don't seem to have my wordsmith hat on the day. I use this method a lot for when I want the player to be able to trigger an observation display text on a scene object with both right click & my standard left click command. It's useful because I only have to create the relevant action parts once & then I can use the call action action part to call either the command or right click action block.

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).

What you have said more or less sounds about right to me.

& sorry. It's sometimes hard to explain things with words alone & I often forget not everyone speaks English as their primary language & it doesn't help that I tend to ramble on a bit.

Anyway, yeah basically you could check a condition or value on mouse enters an object to determine if x or y command should be set. I've had to do this myself sometimes as I've wanted to trigger certain specific actions or show a specific cursor depending on if player has already interacted with an object before. Let's say that I want the player to be able to use a scene object, maybe twist a water valve or move a box, so what I would do is on mouse over initially show the use cursor, but if player has already interacted with the object then I want to show the examine/look cursor instead.

A more complicated thing for me was needing multiple object interaction positions for the same object. In 4.x & below (no idea about 5.x) it's not possible to update the interaction position with action parts or Lua script, so I ended up having to create multiple scene objects layers on top of each other with different interaction positions. The top most layer checks which command/item I'm currently holding then updated a condition or multiple conditions to hide the current object & show the one I wanted to interact with. It was a pain to rig up & would have been so much easier & less time consuming if I could have just updated the interaction positition with a single line of Lua script. It annoyed me to no end.

thanks @AFRLme for explaining (and adding that last workaround for updating the interaction position - )!