
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 1136 of coding, I made some progress with damage knockback. There's still some work to do in order for it to work properly
For day 1139 of coding, I've done some testing and found the collision that caused the infinite loop
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 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
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 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
For day 1137 of coding, the knockback appears to be working. I just need to adjust speed and distance now
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 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













0 comments