Loading...
40
2 years ago

For day 415 of coding, I have made it to where the player side settings also apply to the current money count




0 comments

Loading...

Next up

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

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 1139 of coding, I've done some testing and found the collision that caused the infinite loop

Happy Devruary! Devruary Day 20 celebrates @LilianDuleroux ! They're the artist, writer, and game dev behind The Voyage Sinister! We also have a question for the devs of Game Jolt: What advice would you give a new dev?

For day 1135 of coding, I'm working on having the player get knocked back from damage; using contact damage to test it. I don't have it working yet unfortunately

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

Witchspire is a survival-crafting adventure in a world brimming with magic and peril.

Befriend and battle creatures, and conjure up a sanctuary alongside other witches in co-op or single-player.

Try the Next Fest demo: https://bit.ly/WitchspireSteam

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