Anyone know what's wrong with this code?

This goes with another code that sets the hspeed, I built slopes into this, but it won't go up them.

Just from looking at it, the part where it's suppose to go up slopes seems iffy to me.

The line:

If I recall, would make it where if you're just touching the ground, then you'll do some weird bouncing thing (because technically, as long as there's not a low ceiling, the coordinates you specify is "free").

It's easier to do something like

This way, it'll only do slope movement if it's not possible to move along a flat area.

If I recall, would make it where if you're just touching the ground, then you'll do some weird bouncing thing (because technically, as long as there's not a low ceiling, the coordinates you specify is "free").

It's easier to do something like

This way, it'll only do slope movement if it's not possible to move along a flat area.

Thing is, the movement doesn't only go up to one, so I have to use hspeed, which is why I did two of them.

I'll try just that but with both of them for now.

EDIT:
Now using:

But it still doesn't work.

This post has been edited by Thingy on Nov 1 2009, 08:03 AM

Lots of things, good sir. Just a hint, try not to ever do things like x+=hspeed, as whenever you set hspeed, vspeed, gravity, and gravity_direction (which should be 270 unless you're gonna do advanced stuff, but let's leave that for now), game maker automatically moves the object... you're gonna make it go crazy. Just set the variables and game maker will work its own set of magic for you. Use that knowledge to change your code and it ought to work better.

Also, place_free isn't the best thing to use. I'd use position_meeting(x,y+1,landobjectnamegoeshere), though the only problem with that is that you have to duplicate that for multiple land objects (unless you have them set to a parent.)

This post has been edited by Miles on Nov 1 2009, 09:02 AM

It's variable movement, e.g. you start slow and speed up, and then slow down again when you release.

I need it to have them.

And place_free is just to check that space is empty, it works okay.

place_free does work, but you'll be walking on enemies and anything else whether you want to walk on it or not.

Also, for variable movement, use hspeed+=1 or hspeed-=1 to set it relative.

This post has been edited by Miles on Nov 1 2009, 02:09 PM

place_free checks for anything that is solid. You don't seriously make every object in your game solid, do you? Enemies, for example, don't need to be solid. >.>

Also, he seems aware of how to do variable movement if he can do x+=hspeed, which is basically the same thing.

Oh, well... sorry. But the x+=hspeed is still unnecessary, as hspeed automatically moves the object. Just saying.

it would still be better to use place_meeting and a parent floor object

This post has been edited by Elyk on Nov 1 2009, 10:52 PM

Either way, I doubt changing my collision script will make slopes work.

I'll do it, though.


And it didn't do anything.

Top notch advice guys.

This post has been edited by Thingy on Nov 2 2009, 04:11 AM

But that's so much work. D:

True.

I was actually going to say this in my last post. Only thing that stopped me was that I was incredibly short on time and needed to catch a school bus.

Now that we're done pointing out non-slope-related things, why not give me some actual help?