Loading...
30
2 years ago

For day 384 of coding, I have moved the code for updating the results message into a new function. that function will then run after each total point update

This is to ensure better message accuracy, and to cut out the redundant message checks




0 comments

Loading...

Next up

For day 1160 of coding, I've applied the push to the vertical movement. I'll need to look into why the player gets held into place during the vertical movement

For day 1168 of coding, I've fixed how the player's collision box is displayed. This will make it easier to accurately test collisions

For day 1161 of coding, I've tried adjusting the speed to see if it would affect the vertical collision problem. It did not

Moonlight Peaks is a life-sim where you can live your magical farm life! ✨

Don't miss out on completing our quests celebrating the game to get sticker packs, coins, and more!

Play the FREE demo: https://bit.ly/MoonlightPeaks

For day 1166 of coding; with collision issues still occurring, I'm currently looking into exactly how "place_meeting()" interacts with the objects and tiles

My game in 50 seconds #indiedev #Gamedev #steam

For day 1167, I've noticed that the draw functions seem to not display the boundaries accurately. So far, I have fixed how the player's origin point is displayed

For day 1164 of coding, I did some testing with the moving collisions. I will need to do some tweaking to the code from the results

Happy #WIPWednesday! Are you working on a game? Making some art? Practicing a song? Something else? Tell us in the comments!

For day 1165 of coding; I tried making some changes to the code, but the collision is still acting the same way