Hello, Happy Monday!

For the last few days, I have been debugging and fixing little problems that have shown up in the levels I have created. It is always really funny to see what problems show up when you have lots of levels and playtesting done. The process starts to make clear what works and what doesn't. The big thing I spent my morning on today was an annoying bug where despite the obstacle being there, the Raycast2D wasn't picking it up until after the player had moved around the level even though it should have been picked up first. I reread the code so many times but there was no obvious reason why this was occurring or why it had started, since it wasn't present in the game jam version of Oceans Away.

Well, it turned out that the bug was a single missing line because of how level starts had changed. You see, in the jam version, the levels all started with the player in the same position. However, because I changed the core movement away from a teleport to a tween between positions, and then also said the player start position is level dependent, I forgot to actually set the players starting position before the first raycast is checked. Literally one extra line of code, at the start of the movement system and problem resolved. Anyway, this is just one of many little things that I have been working through. I think I am going to get a new demo out in the near future. I would love for that to be a thing this Friday or next Monday, but we will see what happens.