Loading...
50
2 years ago

For day 328 of coding, I fixed a problem with the player's start position on the map.

Whenever the player goes to a new zone, the next position gets put onto variables that then get used for the next room

This video shows what the problem looked like




0 comments

Loading...

Next up

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 is on my other OCs, Charles Johnson, in a Gamejolt palette

#GameJoltColors25

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

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

There's still time for YOU to enter!

Artists and posts linked 🔽

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

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 948 of coding; I haven't fixed the collision problem yet, but I have managed to pinpoint which script to look into

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 EVEN MORE #GameJoltColors25 great art from you fellow Jolters!

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