Loading...
18
2 years ago

For day 413 of coding, I have included an additional option to determine what side the player's information will be placed at.

It doesn't do anything yet, but I'll be working on that tomorrow




0 comments

Loading...

Next up

For day 1141 of coding, I fixed the collision error. It turns out that two of the variables needed for the collision needed to be updated after the speed change from knockback

For day 1146 of coding, I tried shortening the invulnerability period and making the "blinks" more rapid to see how it looks overall

For day 1142 of coding, I made sure the player doesn't ping pong between enemies after being hit #gamedev #gamedeveloper #Gamedevelopment #gamedesign #gamedesigner #coding #dailycoding #dailycodingchallenge #dailycodinghabit #GMS2 #gamemakerstudio2

My game in 50 seconds #indiedev #Gamedev #steam

For day 1139 of coding, I've done some testing and found the collision that caused the infinite loop

@ElPichon 's Chunky JUMP! is a survival-horror platformer where you must survive through the night on your BIRD BOY.

But beware... the Ghabbit is hunting and you must restore power before it's too late!

Play the Demo before March 1: https://bit.ly/ChunkyJump

For day 1145 of coding, I've added the invulnerability time to the lower left portion of the debug screen

For day 1143 of coding, I've set up an invulnerability timer after the player gets hurt. I don't have any other indicators set up yet

I've created a new form of parkour in Weefager! What do you think?

For day 1147 of coding, I put a red shader on the player when the knockback happens. I'll need to see if I can apply a similar shader during the invulnerability period