2 years ago

For this week's submission, I made an elden ring




0 comments

Loading...

Next up

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

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 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

The Witchspire Art Competition has come to Game Jolt!

To celebrate Witchspire's demo launch, Envar Games want to see your Witchspire fan art. Complete the #WitchspireArt quest to enter!

Learn more about the art competition: https://bit.ly/WitchspireArtCompetition

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

Don't miss out on the #WitchspireArt competition!

To celebrate Witchspire's demo launch, Envar Games want to see your Witchspire fan art. Enter to win an Amazon gift card!

Complete our quest to enter.

Learn more: https://bit.ly/WitchspireArtCompetition

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

For day 1144 of coding, I've set the player sprite to flash in and out during the time of invulnerability. It's not great, but it can serve as a base for something better

This week's Fan Art Friday celebrates Stardew Valley! Accept the quest in your quest log to get started.

For day 1140 of coding, I have found where the infinite loop is happening through GMS2's debug mode. I haven't been a able to fix it yet unfortunately