walkTo() void?

[lucas92]

Might also post at AG.

Alright, what I need is a walkTo(int x1,int x2,int y1, int y2, int speed) void that would move something to x1 to x2 and to y1 to y2... I don't have any idea of how to do it, and I need it so much... I don't know much about trigonometry and such thing, so that's why I would need that one void... Help?

And no loop... It's for use for scripts and such things.

EDIT-Also, speed is how much to move the thing in pixels each time the void is executed.

[pkmnfrk]

Might also post at AG.

Alright, what I need is a walkTo(int x1,int x2,int y1, int y2, int speed) void that would move something to x1 to x2 and to y1 to y2... I don't have any idea of how to do it, and I need it so much... I don't know much about trigonometry and such thing, so that's why I would need that one void... Help?

And no loop... It's for use for scripts and such things.

EDIT-Also, speed is how much to move the thing in pixels each time the void is executed.

ARGH! The word you're looking for is "function". "void" is a return type. It means that a function does not return anything!

*pant pant pant*

As for your request. So, you want a function that moves... uh, a thing speed pixels in the direction of (x,y)?

Well, an accurate implementation of the function would require an ATan function, which we don't have for some reason. Instead, I propose this naive substitute until we get such a function:

void moveTowards(ffc this, int x, int y, int speed) {
	if(this->X < x) {
		this->X += speed;
	} else if(this->X > x) {
		this->X -= speed;
	}
	
	if(this->Y < y) {
		this->Y += speed;
	} else if(this->Y > y) {
		this->Y -= speed;
	}
	
}

[lucas92]

Oh that's great. :)

Thank you. It was simpler than I thought. :)

[lucas92]

Wait a minute... It's not so much perfect that function... I mean, it would only go in a direction with a 45 degrees angle... And it isn't what I want...

I guess I will use that one for now...

[pkmnfrk]

Well, I just circumvented the lack of ATan, and so you can use this supplemental script, and take its findAngle function to write this script:

import "std.zh"
import "advmath.zh"

void moveTowards(ffc this, int x, int y, int speed) {
	int angle = findAngle(this->X, this->Y, x, y);
	float dx = Sin(angle) * speed;
	float dy = Sin(angle) * speed;
	
	this->X += dx;
	this->Y += dx;
}

[lucas92]

Wow. Just wow.

No doubt I couldn't have done it.
That's just great. Thanks. :)

[pkmnfrk]

DISCLAIMER: I have not tested any of this code, and only know that it compiles. However, if there's any problem with it, please let me know, and I will actually test it.

[lucas92]

void moveTowards(ffc this, int x, int y, int speed) {
	int angle = findAngle(this->X, this->Y, x, y);
	float dx = Cos(angle) * speed;
	float dy = Sin(angle) * speed;
	if(this->X<x)this->X += dx;
	if(this->X>x)this->X -= dx;
	if(this->Y<y)this->Y += dy;
	if(this->Y>y)this->Y -= dy;
}

Even with the mistakes I fixed, it seems to always follow a 45 degrees line then go up with a 0 degree line...

I've made an example quest... Also try to avoid the armos, it will kill you in one hit... Anyway, I needed that function when it climbs the ceiling.

http://www.mediafire.com/download.php?ytmzfjeemmc


Also there are some mistakes in your advmath.zh file. Missed semicolons and such things.

[Gleeok]

That's because pkmnfrk is modifying x,y coordinates based off floats instead of storing them in a seperate variable (such as Vx, Vy), I think. Try changing it to this->V and see if that works, or, use this instead:

void Homing(int speed, int ffc_num, int target_x, int target_y){
	ffc F=Screen->LoadFFC(ffc_num);
	int dx = target_x - F->X;
	int dy = target_x - F->Y;
	float norm = Sqrt(dx*dx+dy*dy);
	if(norm > 0){
 		F->Vx = dx/norm*speed;
 		F->Vy = dy/norm*speed;
	}
}

edit: Had a spontanious idea to make it better. (untested):

void Homing(int speed, ffc f, int target_x, int target_y){
	ffc F=f;
	int dx = target_x - F->X;
	int dy = target_x - F->Y;
	float norm = Sqrt(dx*dx+dy*dy);
	if(norm > 0){
 		F->Vx = dx/norm*speed;
 		F->Vy = dy/norm*speed;
	}
}

[pkmnfrk]

Well, my code should work if you change the second Sin to a Cos (brain fart).

But, I would recommend against using the Vx and Vy variables for this purpose. Reason? If for some reason you stop calling moveTo(), the Vx and Vy variables won't magically revert to zero, and the ffc will continue to move.