Loading...
31
1 year ago

For day 578 of coding, I have made attempts to address the collision Issue with collisions. The detection seemed to have improved, but not quite enough




0 comments

Loading...

Next up

For day 955 of coding, I tried using switch checks to fix the collision. It turned out to be a bad idea

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

For day 953 of coding, I made a way to slow down the game in order to better see the hitbox interactions

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

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

For day 946 of coding, I'm on the right track in correcting the collision while dashing

For day 948 of coding; I haven't fixed the collision problem yet, but I have managed to pinpoint which script to look into

The Knightling launches on August 28! Wishlist it now so you don't miss out: https://bit.ly/KnightlingSteam

To celebrate the game's impending release, we've added The Knightling Pack and The Knightling Community Pack back to the Shop!

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