Gashadokuru Escape

Hello this is my team of twos submission for GMTK 2024, ~80 hours give or take

SORRY IN ADVANCE I COULDNT GET WASM WORKING so you have to download it instead of playing in browser, if I had more time I could have.

Gashadokuru Escape -- a game where you run around fighting Oni and a Gashadokuru as from Japanese Mythology. It is built like vampire survivors with active abilities. With a large fightable obstacle that adds a twist. The win condition is killing said obstacle.

Features:

- mouse tracking

- music + sfx

- menu + web playability + ui

- decent physics

- passable combat and feel

- decent challenge

- proper states and pausing and win/lose condition

- healing + cooldown reduction

- infinite repeating map

-cooldowns + 'animations'

-runs on bad specs

-invulnerability on dash and damage instance

---------------------------------------------------------------------------------------------------

If you care about lore

Kian[I] (https://github.com/kpbianco) and Nate (https://github.com/NateLoken) are two SWE who wanted some experience learning Rust. We thought making a game from scratch under time constraints for a gamejam would be fun. 
We used bevy for our game engine and implemented the rest of the systems by hand. The game is exported using WASM for you to play.
We were a team of two and definitely would need more hands on deck next time in order to accommodate a lot of the shortcomings.

Art was done by Kian with some use of AI due to a lack of full time artist, despite efforts of finding one.

Sound was done by Helcorp (those listed below):

Hmlfortrizz, ssspecture, 9pmbedtime, ayojabbi, phear, Prodkillerram and Rx.

Game design, mechanics, core game logic, bugfixing, flow done by Kian

Movement + Enemy logic by Nate

(Resource management, systems, physics, modularization) ^ didn't make it in time 

Known bugs:

-ranged attack buggy

- spawn on reset is not reset to 0, 0 but where you last left off

- flicker indicator for invulnerability sometimes leaves alpha low

- collision impact sometimes trigger more than once

- sometimes particles/sprites will go below other layers 'randomly'

- menu sounds can loop

Things we would change if we did it again:

-WASM

- get more teammembers (game design, art, tester, more programmers, etc)

- properly find a way to support no lifeing for 4 days without falling behind on lifes responsibilities

- use lessons learned in Rust to do our design way different off the get go and make a good modular system to build off of instead of hodge-podging things togethter

- use a development toolkit in a language/paradigm (like C++ OOP) we are more familiar with with greater documentation for issues