Thanks for playing! Yeah the self-intersection thing you encountered was the bug I was talking about, but maybe I could have explained that the symbols correspond to intersections earlier. Also, as you might expect, the reason there weren't more levels was because I ran out of time.
Extremely great game :D Only frustration is having to trial and error some of the longer levels. Getting the timing right can be very hard, which makes me wonder whether something like "Move right 2 blocks" would have been better as it would be a lot easier to predict the outcome.
Nice game! One thing: I realised there was no penalty for overshooting, so I could just put a 9 in the for loop and I would not get penalised at all, making that part essentially pointless.
- I had no idea what to do at the start, just something like "Add/remove cubes to construct pathways for the entities to reach all the checkpoints and loop back." would have been very useful.
- Entities moved too slowly, a faster speed or option to speed up would have been useful.
- Sometimes I managed to complete a level before the entity looped back to its starting point, perhaps a bug.
But otherwise, great game and I enjoyed it! Even though it's small, at least you managed to add more content than I did :').
Very nice concept, it's a shame there are no puzzles or anything to do other than spectate NPCs, I think maybe spending some time adding puzzles or something might have been a better idea than adding NPCs to the world, so the player actually has something to do. Unless you didn't have time to do even that, which is okay because I also ran out of time XD.
Nice game! I think it would be nice to have a win/lose condition instead of just maximising a score that is going up on the side, so we know whether we have "completed" a level or not and get a sense of satisfaction when we do so.
Very enjoyable game and nice artstyle! My main complaint is that some of the minigames can be very unforgiving, you could perhaps make the reaction time window a bit more generous, as well as make the hitboxes smaller in that cat running minigame (the 2nd one).
Nice game! And congratulations on your first jam game! My biggest issue is that I went through most of the game without really knowing how the mechanic worked, so making the tutorial clearer and more specific (e.g. 1 Lava + 1 Water = 1 Land, 2 is max for each stat) would go a long way.
Thank you for playing! Sadly I was aware of your issue, but couldn't fix it in time before the jam deadline. If you have a Steam Deck or another PC with a more advanced CPU perhaps you could try playing there.
I'm sorry, I really can't diagnose the issue. I thought it might have to do with whether multithreading was available or not, but I tried exporting a WebGL version with multithreading enabled and it still ran into the same problem. From some online Googling, your Windows CPU doesn't support multithreading but your Mac CPU does. I think this has something to do with the Godot 2D physics engine that is out of my control, I was aware that my game was pretty intensive on the physics engine but didn't have time to optimise it before the deadline. I might have to ask around people that are more familiar with this than I am.
May I know if you are using a very old PC? This is the same problem I ran into on WebGL, which is why I had to remove it. I suspect that if the hardware is very old and doesn't support multithreading or something this problem occurs.
I see. My game involves drawing objects with the mouse and then turning those into physics objects, so it is normal for each collision polygon to have high double-digit or even more than 100 vertices in them. Maybe that's why. I also enabled collision detection to play a sound effect, but I made it so that it disabled itself after one collision, so I don't think that's the main problem. All my physics code is in _physics_process as you said though.
Very nice and well-polished game! Only problem is that some of the puzzles can be a bit frustrating to solve because it's hard to position the objects precisely when you throw them, or it is difficult to position the dimensional box in exactly the right place.
Also how do you get such a pretty-looking game in WebGL? I tried to port my Godot game to WebGL (also in 4.3) but the 2D physics just broke, so I had to remove it.
Very creative take on the theme! The audio in the HTML5 version seems to be a little buggy though. Also, is it just me, or are the obstacles actually symmetric, so you only have to take one side of the bird into account? :D
The artstyle and sound design is very nice, but I managed to complete the game by just spawning skeletons left and right alternately, without using the upgrade mechanic at all, so gameplay wise it could definitely be tweaked.
1. Bring the 1st vine upwards to guide water to itself through the top hole.
2. Bring the 1st vine towards the base of the 2nd vine to guide water towards it. Make it roughly flat where the water lands on the vine body so water is divided between both vines.
3. Using the yellow shiny, guide the 2nd vine over to the hole above the 1st vine to let water flow into it (this is the step that caused the most headaches, as every time I tried to guide the 2nd vine with the yellow shiny the 1st vine would ride along as well, disrupting the flow of water to the 2nd vine, eventually I managed to use a combination of both the yellow shiny and the blue shiny to let the 2nd vine extend far enough ahead of the 1st vine so only the 2nd vine is within the radius of influence of the yellow shiny).
4. Use blue shiny to shrink 1st vine, then use yellow shiny to guide it towards beehive.
By the way, I don't think having the shinies caught in walls is a framerate issue, it's just that when the cursor moves far enough away from the shiny the cursor loses it, which is nothing wrong, but when you are trying to quickly move the shiny away from vines to stop influencing them and you lose the shiny because you accidentally moved through some walls, it can be quite frustrating.
- Sometimes vines will get stuck and I have to restart (in earlier levels)
- The last few levels were very finicky (especially 'Oiler') and I had to retry many times, because it was very hard to use the shinies to manipulate the vines how I wanted, very often I would try to "rush" a shiny past a vine I didn't want to move, but the vine would still catch the shiny and move just a little bit which was enough to mess up the flow of water. Also I would sometimes lose the shiny if I moved it at a very high speed, because it would get caught in some terrain, which was very annoying in the last few levels.
Yeah, during my own playtesting the game would also get laggy when there are too many objects on the board, but I was unable to fix it in time. Still, thanks for playing!
I see. I personally thought it fit the theme quite well, though we all have different interpretations of the theme and that's ok. As regards to your idea, 1) I'm not sure if it would make the game too easy, as part of the difficulty of the game is the lack of control the player has over the shape once it is drawn, making it paramount that they draw it to exactly the right proportions 2) I'm not sure how expanding the shape when it's already on the board would mess with the physics engine, I imagine it would most likely result in unexpected behaviour. Still, thanks for playing!
Very generic idea, but a very polished execution of it, I can easily see this one scoring well in Graphics and Audio. The only bit of polish I would've wanted is a satisfying winning jingle when you solve a puzzle. Undo functionality would be nice as well if there was time.
