
Next up
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
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
Here's more incredible art that Jolters made for #GameJoltColors25!
There's still time for YOU to enter!
Artists and posts linked 🔽
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
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 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 954 of coding, I tried using another variable to keep the collision register only at 1; but it's not working like I had hoped
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 955 of coding, I tried using switch checks to fix the collision. It turned out to be a bad idea
6 comments