23 replies to this topic

[Alestance]

I'm in need of a script that if you're above a certain height, a combo which an FFC is above would become walkable, and when you land, it would be solid again. I think it'd be simple to script.

Second I want my L button to be a Jump Button on both overhead AND sidescrolling environments. This, I believe, could also be Achieved. I also want to be able to change the height of the jump twice with which two items gained that would allow you to jump higher.

[Joe123]

So you're scriping holes that you can jump over with the Roc's Feather, right?

What happens when you jump onto them?


The other part would be quite easy, but I'm not quite sure how the system would check to see whether you're in a side-scrolling or a top-down environment.

[Alestance]

not holes, but height variations. Kind of like Beefster's cliff script in reverse.

As for what happens? hmm... not sure. perhaps make him roll back down, if possible.

[Joe123]

Ah!

I get you!
That's quite a nice idea actually.

Which way is down though?
Are you going to only have them on the front of mountains, or on the sides and backs aswell?

[Gleeok]

So you're scriping holes that you can jump over with the Roc's Feather, right?

What happens when you jump onto them?

You can walk on them I'm guessing. I dunno. Maybe you can keep Link->Z or jump a certain number untill you are away from the ffc. I'm really no good with Z to be honest.

edit: well "pushing Link off" a square is easy enough at least.

Edited by Gleeok, 17 May 2008 - 02:44 PM.

[Joe123]

well "pushing Link off" a square is easy enough at least.

How so?

[Alestance]

conveyer, possibly

[Joe123]

Which way is down though?
Are you going to only have them on the front of mountains, or on the sides and backs aswell?

[Alestance]

Down is different in different conditions, but its always either 16 pixels, 32 pixels, or 48 pixels away from the solid combo you land on.

[Joe123]

Ok, I'll see what I can do.

[Gleeok]

How so?

if(Link->Z==0 && this_ffc_is_horiz && !sideview && this_tilewidth==16 && (Abs(y,y)<16 && Abs(x,x)<16)){ if((lx-tx)<=8 && lx-tx)Link->X-=2; Link->InputA/B = false; etc...


...or It would be simpler if you keep an array of ffc->Data ahead of time, to limit the damned else if's. ...Heck there's probably a much easier way, but even so you could just get get one dir working then copy paste the code at least.

[Joe123]

You can't just put '&& !sideview' ¬_¬

[Gleeok]

You can't just put '&& !sideview' ¬_¬

It's psuedo code you numskull.

You could track this with ffc->Data like I mentioned, or a D[] variable. Or whatever.

Edited by Gleeok, 17 May 2008 - 04:46 PM.

[Joe123]

I knowww it is =P

Do you know of a way of checking whether Link is in sideview or not though?
Cause I can't think of one at all.

[Gleeok]

Yeah, of course I do.

You simply make a script for top-down, then make a sideview version of the same script.