Thanks to everyone who has played or even just looked at our game! We'll add some QoL updates in the future but the game is complete at the time of the jam ending.
I've submitted but will be testing logic over the next couple of weeks to make sure it's solid. If I have to update the project, will the updates automatically work for the submissions? I see that submissions are currently hidden until the jam completes so I can't test this.
Is there a good place for the jammers to hang and work/chat about the jam? The official arch discord seems to be focused on keeping rooms channeled to sync/async runs, no general.
one strategy is to break all the caps first, then to go for the cores. also, detonating early if you're not fast enough to get to the core allows you to get back to defending. another strategy is letting other turrets die so that your favorite one is at max power. Lastly, make sure you're using the boost to get to the tunnels, it helps reduce time for them to spawn!
I thought we had a voice line that noted it, but you can use the left/right arrow keys to switch, as well as num row 1/2/3/4 for specific turrets, or num pad 2/4/6/8 for specific turrets based on N/S/E/W.
I hear you on the enemies hitting hard, however- We made sure that the game compensated for losing a turret, speeding up other turret fire rates and reload speeds.
The first one is to use Fixed update, which fires on a regular interval instead of at the end of every frame, so framerate independent. I don't think that works well for input though.
Secondly, you can multiply things by time.deltatime, which is the difference in time between the last two frames. When you do this, it can help keep things like move speed consistent. I did this to my mouse input and I think that's the issue- you should only add it to things you need to.
I'm not actually sure why it behaves how it does, but for my next FPS I will be sure to completely revisit and rework my look mechanism approach.
Sadly there are 0 shaders harmed while making this game I'm using a render texture, where I render the camera to a texture, then overlay that texture to the screen. I can then reduce the image size to make it more 'crunchy'.
If I had more time, a custom renderer would have been way more resource efficient, but this runs well enough in browser.
Thank you! I'm not changing the submission at this time out of general fear of breaking something, but with the feedback we've had, I might default the missile controls to the opposite of their start in the future.
