Hi! Thank you for playing, for the kind words, and for taking the time to give me detailed feedback! I really appreciate it. It was the first game for all of us, so every suggestion and comment helps - visibility, spotlight mechanics, redirection and wall jumps will certainly see some work after the Jam closes :)
For the torch mechanic you are "ehm" spot on: originally I was thinking of adding a fear counter and tying the torchlight to it and to threats in more or less the way you suggest -illuminating a threats deactivates it for a few seconds; the cost would then be that of increased fear, and hitting max fear would lead to a different ending. However, I barely managed to fit in the deadline like this ^^`
As for the gameplay fluidity, did you by chance also experience absurdly high, floaty jumps? On the computer I developed the game it runs pretty smoothly and the jumps are relatively short and fast, so that there really is only one path possible at all times; however, I tried it on my laptop and the jumps were exaggerated and felt like there was very low gravity, making most moves harder but allowing one to jump through sections in the wrong order. I had similar inconsistencies also while running the game in the editor. If this is what you experienced, would you perhaps also know where could lie the origin of this issue?
Cheers!
Viewing post in Happy Adventures at House Hemels jam comments
well I'm not sure how high you intended the jump to be but I would say mine were pretty strong, I can maybe later make a quick clip for you to check if that's what it is, either that or I download the project directly from git and take a look at things.
How did you code the jump? Is it a force being added, a velocity? Are you doing it in the update method or fixedUpdate() ?
Then my guess is that the movements are indeed not running as they should, so I'm afraid that that might have added extra discomfort to the playing experience. I couldn't replicate the issue consistently enough to pinpoint the cause, but there's also a lot that I still have to learn...
I coded all movements (including jumps and wall jumps) as changes in velocities, which take place in the Update() method, and not scaled by Time.deltaTime (which occasionally popped by online as a solution, but is supposedly incorrect when dealing with body.velocity).
In case you did happen to check the code on git, all movements of the player are in the Controller_V2 class.
In any case, thank you for your time! It's great to find so much support!
Ok, I went to your git repo, but since you don't have the whole project there I can't exactly download and try it out on my own, but my advise to you would be to put a "Debug.log()" inside your Jump() method and then go back to the editor and try to jump a few times and check if that call is not triggering more than once, that would be my first guess. If so, you could make a global bool "canJump" and in place of calling Jump() in the update method you would set that bool to true, and then in the FixedUpdate() you would say if(canJump){ Jump(); }
I'm not sure if that solves it, but you could try it.