Tastes Like Spelunky Ver.2 (almost done!)

[Sudonimus]

NO. Don't do it.

[grieck]

I was aware of what needed to be changed more or less, as I constantly compare your progress to your previously posted To-Do List.

TOMORROW!?!?!?!?!


LE GASP!!!

[halibabica]

Can you teach me? PLEASE???

What do you want to learn?  I learned everything I know just by reading/mimicking the code.

[Audioworm]

I could even be finished tomorrow...

OHBOYOHBOYOHBOYOHBOYOHBOYOHBOYOHBOYOHBOYOHBOYOHBOYOHBOYOHBOYOHBOYOHBOYOHBOYOHBOY

[gummybears123]

Can you teach me? PLEASE???

What do you want to learn?  I learned everything I know just by reading/mimicking the code.

1. How do I make a gun fire 3 bullets in succession?
2. How do I make  it so that the character changes sprites only after I double jump, and the sprite stays until I run out of double jumps (flaps) or touch a surface?
3. How do I make an enemy ignore the player?

[marsgreekgod]

1) with alarms.
2)With a new state
3) which kind of bad guy? spiders? I said I would help and you never replyed.

I can't wait for this mod!

[gummybears123]

PLEASE be MORE specific......... Alarms? States?

[halibabica]

Alarms are those little clock things you see in the objects' event list.  As far as I can tell, you set a timer for them (like, alarm [ x ] = y (x and y would be numbers)), and then the stuff under alarm x would happen when time y expires.  They're tricky and I don't much like them.  You could probably create your own variable timer instead.

The character states are listed in the script that creates the oPlayer1 object.  You can use them to control what the player can/can't do depending on what state they're in.  You can also control what sprite they look like while doing this and what conditions make them return to normal.

Depends on what enemy.  Somewhere in each one's step event, there's a bit of code that tells it to attack when some conditions are met.  Delete that, and that enemy will no longer attack.

MOD UPDATE: This is going even more smoothly than I thought!  I was worried about my plans for the new paste thing, but it's easier to implement than I expected.   You guys are gonna love this thing!

[gummybears123]

SO alarms for the oBullet? I don't want it to do it for other guns though!

[marsgreekgod]

SO alarms for the oBullet? I don't want it to do it for other guns though!

No for the gun

[gummybears123]

Oh! Thanks!

[Audioworm]

I'm so excited I think I'm gonna explode...

*eeeeeeEEEEEEEEEEEEEEEE*
*BOOM*

[halibabica]

I'm not really sure alarms are the right thing for this.  First, add a variable to oPlayer1's create event called 'shooting' or something like that.  Set it equal to 0.  Then, in the script where the player uses the weapon, have an if case where 'shooting' must be 0 to fire a bullet.  After the bullet fires, set 'shooting' to a number higher than 0 (which number you choose will depend on how fast you want it to shoot again).  Then, add an else case to the 'if shooting = 0' that subtracts 1 from 'shooting'.  That way, it will fire in succession, and only when the 'shooting' variable you made runs down to 0.  After that, all you'll need is some way to break the loop so the weapon doesn't continue to fire after it should have stopped.  That, I'm not sure about.

By the way, have you asked in the GM help thread?  The people there probably know even more than me (especially DariusK).

[Audioworm]

Hey, cool! I'll have to remember that if I ever get GM Pro...

[Kegluneq]

Gummy, there's a whole thread DEDICATED to those kinds of questions. Let us focus on the epicness of this mod here.