Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Amo]

Hi Folks,

is there any way to get out of WME the following information:
When clicking somewhere in the scene, WME does know, if the actor needs to walk, or not.
When he needs to walk, he needs the correct target coordinates, right?
Is it possible to catch these coordinates?

[metamorphium]

of course. Actually it's not hidden information. If you click in the scene, the scene.script gets called, which contains

on "LeftClick"
{
   actor.GoTo(Scene.MouseX, Scene.MouseY);
}

so to make long story short, Scene.MouseX and Scene.MouseY is what you're looking for.

[Amo]

Hi Meta,

thats a starting point, but not really what I am looking for. Hm, hard to describe for me...

When clicking somewhere, lets say 800, 400
and the script starts, as it recognizes, that the actor has to move now, we need the information, that
the leftclick method is running and directing the actor to 800, 400.
In short: We need the values, in this case 800, 400

[Mnemonic]

That's what meta said. Those are the mouse coordinates at the time of the click, i.e. the target point.

[metamorphium]

Amo: it's very easy and that's why I've directed you to that file. In scripts/scene.script you modify this LeftClick method so it will also make the task you requested. So this is the point where you'll get the coordinates

In your case Scene.MouseX will return 800 and Scene.MouseY will return 400 and you know that the scene was clicked and actor is going there
There are two ways how to approach the solution - Either modify this method to your liking which as a trap - if you click on region, this won't get triggered, or make a daemon script and use global variable for determining if this particular LeftClick was pressed.

[Amo]

So it is possible e.g. to print then 800, 400 on the screen via Game message?
And the next thing: Is this working also with goto.object this?

regards

Martin

[Mnemonic]

What exactly do you need it for anyway? If you need to trap all GoTo calls, you can as well write your own GoTo() method.

[Amo]

Yes of course we can, but the raw scripting of all game scenes is complete, means the actor can interact with all objects. Changing all these methods to new would take days.

[Mnemonic]

Well... no, not really. The point of overriding built-in methods is to be able to only do it in one place only.

[Amo]

Which means if we want to override the goto.this method, we would have to change it in all scenes vor every object? Damn, what a pity, so the idea behind all this stuff is useless, as we do not have the time...

[Mnemonic]

If you override the built-in GoTo method by writing your own implementation in actor's script, then ALL the GoTo calls in the entire game will be routed to this overridden method.

[Amo]

So... there must be one implementation in the actorscript? Never thought about it, as there is no goto method in that script.

[metamorphium]

because it's not overriden yet.

your actor.script could look like this:

#include "base.inc"

method GoTo(x,y)
{
  //   Do whatever you want with those coordinates.
   this.GoTo(x,y); //and call the original method
}

very similar would be GoToObject logic.

[Amo]

OK, that overriding sounds interesting.

thanks for the answers.