next »

[lasttea999]

I'll have to take a good look at that code to understand it well, idoru!

So I said that I made my own engine based partly on Grandma Engine. I wanted to share it, but I've been refraining from doing so because the style of the code is a bit odd. But now I've made a new version that should be easier to look at: download from MediaFire

Note that this is a *partial* rewrite of what I'm actually using in my projects; therefore it's missing some features, such as the aforementioned moving platforms. Also, I apologize in advance for the sparseness of the comments!

Thank you again, Mr. Thorson!

[Matt Thorson]

Whoa this thread is getting pretty old but is somehow still active. Moving platform code looks cool, thanks for sharing that with everyone

[FrankTheTank]

I have been playing with this engine for a bit now and it is extremely useful. However, I still haven't figured out a basic concept, don't get me wrong, it's an awesome engine, and this is probably just me being a giant idiot, but I can't figure out how to make objects that act like the floor and slope blocks, as in objects that you won't just fall through when you step or fall on them, I have been putting floors behind basically every single solid thing as a temporary solution, but this is tedious and limits my options a lot.

 In short, how do you make solid objects in this engine?

[ink.inc]

Set the parent object to obj_floor/obj_jumpthrough. That should take care of it.

[FrankTheTank]

Ah, thanks, I knew it was something simple, I should probably read more before I ask stuff that may or may not be completely unrelated to the thread itself.

[Desert Dog]

Don't have '-' in your sprite names. Your sprite/variable names should consist of letters, number, and _ only.

One of the things about GM that I dislike is that you can get away with using strangle symbols like '-' in your project, as long as your using drag&drop, or setting the sprite manually.

Once you get code, though, it all goes wrong.

[Desert Dog]

No problem!

[JMickle]

instead of adding another line, change the parent of o_basicarrow_hit to o_jumpthru, saves you messing up the code too much. I don't know if this will fix it, though, but chances are it will work better.

I don't know how to go about fixing that angled fallthru, though, Maybe have to hack it by making it so you can't stand on arrows that hit more than 45 degrees into the wall? seems realistic enough to me.

[Damian]

Hi, I've been using this engine for a while now and I pretty much know it off by heart. But for the life of me I just can't figure out how to make the player object jump down through a wall object. I've played around with obj_moveable to see if it was a fault with that part of the code. It wasn't, I managed to have all enemy sprites move through but not the player. I'm still playing with the player object to try and  work this out. I think someone else has managed to tackle this problem and if anybody could help me out I'd be very grateful.

Damian

[Sheepolution]

Do you mean with the jumpthru platforms?

I added !keyboard_check(vk_down) in the checkBelow script, and it worked

return place_meeting( x, y+1, obj_floor )
    or (place_meeting( x, y+1, obj_jumpthru ) && !place_meeting( x, y, obj_jumpthru ) && !keyboard_check(vk_down))

Not sure if that was your problem, but it was mine, so my problem is solved xD

[Damian]

  Thank you. I actually have that code already. But seeing that it worked for you and not for me confused me. It seemed logical. My mistake was making new objects and parenting the object floor in my idiocy instead of the jumpthrough object. Again thank you 

[Jawnsunn]

http://www.mediafire.com/?k2oddbn9tsnqf5w
Here's a backup since the link stopped working.

[PlasmaMan]

I'm an almost-absolute-beginner at Gamemaker, and a definite-absolute-beginner with GML. I really can't thank you enough for making this available, it's been a fantastic teaching tool.

[HarrisonJK]

Hey the link to this has gone bad. Is it still on the internet somewhere?

EDIT: Sorry, I just looked through the rest of the thread and found that Jawnsunn's link still works.  

[Matt Thorson]

Fixed the link again! Sorry for always forgetting about it when I change hosts haha. It's at http://mattmakesgames.com/matt/GrandmaEngine.gmk

[Erinock]

Thanks for this, it showed me a different and simpler way to warp between rooms compared to how I used to do it. Thanks, and will give credit when I use it. 

[PureQuestion]

Is this even still linked anywhere on your site, or is it basically just here?

[lasttea999]

Is this even still linked anywhere on your site, or is it basically just here?

Fixed the link again! Sorry for always forgetting about it when I change hosts haha. It's at http://mattmakesgames.com/matt/GrandmaEngine.gmk

---

So I've been using the methods of the Grandma Engine in GM and also in Java, leaving the core algorithm (?) mostly intact, and in my opinion the movement feels great, it's really smooth. But I've been wondering about the efficiency of the method. It does a LOT of collision-checking that other collision-checking methods may not have to do, right?

If I remember correctly, though, I think I was able to get about 100 or 200 simple objects going without lag in GM with this method? It might even be possible to have more objects. I haven't really tested it in Java.

My apologies if this issue has already been discussed within the thread. Thoughts?

[Squid Party]

good engine

[Ant]

@lasttea999 I'm not 100% but I think the only difference in terms of collision detection is that this engine checks for a collision before movement while GM's inbuilt collision detection checks for a collision after movement. So they are both doing the same amount of checking, it's just at different points in the code.