For day 949 of coding, I found that the collision problem is due to both top and bottom hitbox being activated. I've tried to adjust the hitbox to no avail

For day 942 of coding, I still haven't figured out what's going on with the direction. I may need to program in a way to display sprite information to help pinpoint the source

For day 951 of coding, I adjusted the dash speed to confirm my suspicion on why the collision error is occurring. It is indeed the dash is too much for the player's hitbox. I need to figure out why it only really occurs while right against the wall

Here's more incredible art that Jolters made for #GameJoltColors25!

There's still time for YOU to enter!

Artists and posts linked 🔽

For day 943 of coding; to help in finding the source of the sprite troubles, I now have the display show the current frame and sprite being used by the player

Your fellow Jolters are still hard at work making GREAT #GameJoltColors25 art!

There's still time for YOU to be part of it. Check your quest log to get started.

All artists are tagged below! 🔽

For day 950 of coding, I've changed how the collision checks are handled. It seems the one collision is working properly, but now I have some trouble with the collision above the wall

For day 944 of coding, I have fixed part of the frame issue for when the player dashes while standing. I just now have to fix it when the player dashes while moving

Lynked: Banner of the Spark is a colorful action-RPG & town-builder where you and your robot buddies help build a new future from the ground up.

⚠️ The game has a free Steam Weekend from August 7 to August 11!

Try the game now: https://bit.ly/LynkedSteam

For day 952 of coding, I drew a new box for debug that will show the player's movement hitbox in relation to the normal hitbox