Kyoob 3.1 - Hey look, an update!

[Moosetroop11]

Looking forward to it. I haven't played this in ages.

[fruckert]

I apologize for my hasty statement and hope that this screenie of the shield and new tip system will placate the rabid rending of my flesh.



The shield works by going into attack mode, and then pressing the magic button.
Doing that again makes them fly out in said spiral pattern.

[drenrin2120]

When they fly out, do they do damage to enemies? That'd be spiffy.

[fruckert]

Yup.
They also ignore collisions with blocks, so it's a nice way to damage everything in the area, albeit lightly.

[SaiKar]

I apologize for my hasty statement and hope that this screenie of the shield and new tip system will placate the rabid rending of my flesh.

Sorry, but nope. Gnaw.

[fruckert]

oh noooooo *death*

I kind of programmed myself into a corner. I have no idea how to effectively make sure that enemies hit Kyoob, and vice-versa.
Until I bang my head at that wall enough times to tunnel through, I can't really do much.

[Geocide]

You're using GameMaker in this game am I right? If that's the case then I see alot of potential to go over to a powerful language such as C++ and build a game entirely from scratch. Ofcourse if you have worked for so long with it, you might wanna stick to it but I'd like to see you port this into C++ in where you have more control of what to program.

If you now are using GM I don't have a clue what built-in features that has.

But in C++ I would do something like:

Create my enemies (you already have enemies I assume)
Create a list in where I put all the enemies.
Loop through the list and check which enemy the player collides with (or bullets or w/e).
Execute whatever action you'd like.

Enemy enemy1;

Enemy enemy2;
Enemy enemy3;
EnemyList.push_back(enemy1)
EnemyList.Push_back(enemy2);
EnemyList.push_back(enemy3);

Now you'd have 3 enemies in the list.

for(int i = 0; i < EnemyList.size(); i++)
{
if(player.collideswith(EnemyList (i)) player = dead;
}

The reason I'm writing this is so that something similar might be written in GM or so and might give you a hint or so. I've never used GM myself since I wanna do my games from scratch.

[Prpl_Mage]

I think his problem is the Gauntlet-problem. Both the player and the enemies get hurt at the same time when they collide.

[fruckert]

That is a fascinating solution to the problem.
I'll try modifying it to work with GM, and my more complex enemies, although I absolutely suck with for() loops, so I'm not sure how well that will turn out.

Purp: Only certain enemies you can jump on, some have spikes. And some only hurt you when they attack, etc.

[fruckert]

New enemy in the list.

I haven't worked on enemy collisions yet, though, so... =[

I have, however, made this fairly kickass tooltip system that I'm very proud of.

[fruckert]

May I get a delete on this?
I'm planning on revitalizing the whole thing, with an actual physics engine and whatnot.
This thread is kind of redundant at this point.

[SaiKar]

What? I am have the sadness!