umut-sahin / mythmallow Goto Github PK

Including but not limited to:

• Current level
• Enemies dropping experience object when they die
• Player collecting experience points when it's within a certain range to an experience object (range should be configurable)
• Level progression adjustments (e.g., leveling up should become harder)

Every single text file in the project needs to end with a trailing newline. We should check it in the CI.

CI needs to be modified to create a release and attach pre-built binaries for major platforms to the release.

What a silly mistake...

During the development, jumping back and forth between the game and the IDE is very common. So this behavior needs to be configurable.

Game should be paused automatically when primary window focus is lost, to prevent users from accidental Alt + Tabs.

See:

• https://docs.rs/bevy/latest/bevy/window/struct.WindowFocused.html

These are very valuable metrics both for development and for user experience, so there should be an option to display them inside the application.

CI needs to be modified to deploy the game to a website. If possible, the game for each released version and the game for main should be playable.

This one requires a domain and a server machine to host the assets and the compiled WebAssembly.

Manually implementing physics is very time consuming. And we'll need a lot of features (e.g., spatial queries), which bevy_xpbd already have.

Including but not limited to:

• A new enemy type that can fire a projectile towards the player (would be better after #1)
• Avoidance from the player for this enemy type

Including but not limited to:

• A new menu for settings which can be accessible through the main menu or the pause menu
• Key bindings settings
• Mouse settings (maybe?)
• Display settings (e.g., Scaling, VSync)

Basically a save system with a single save slot.

(requires #4)

Including but not limited to:

• Game Loop
• Players
• Enemies

We should stick to a single committing convention and it needs to be enforced by the CI.

It'd make it easier to debug in the editor.

Including but not limited to:

• HP regeneration (requires #1)
• Attack speed (requires #1)
• Size (maybe?)

Logging is very important for debugging issues experienced by users, so we should use it through the game.

Staring with:

• English
• Turkish

And for later:

• French
• German
• Spanish
• Italian
• Dutch
• Japanese
• Korean
• Polish
• Portuguese
• Russian
• Simplified Chinese
• Traditional Chinese
• Hindi
• more?

Including but not limited to:

• Damage on physical contact with enemies
• Death and game over menu

Currently, the camera just blindly follows the player. This can be improved.

See:

• https://www.youtube.com/watch?v=TdWFzpgnljs
• https://store.steampowered.com/app/1942280/Brotato/ (the first video)

I'd recommend playing Brotato and observing its behavior as well.

Currently, collision detection checks for collisions across all physics entities. This can be improved by partitioning the objects based on their position, and only checking collisions for the current and the surrounding partitions.

See:

• https://stackoverflow.com/questions/1616448/broad-phase-collision-detection-methods
• https://en.wikipedia.org/wiki/Binary_space_partitioning

Including but not limited to:

• Progressing through different levels
• Time limits
• Win conditions

Initial support requires movement and UI navigation with controllers.

See:

• https://github.com/Leafwing-Studios/leafwing-input-manager/tree/main/examples

CI needs to be modified to deploy the book to GitHub Pages. If possible, the book for each released version and the book for main should be accessible.

Including but not limited to:

• A new UI for viewing the statistics
• Play time
• Number of games played
• Number of wins (requires #4)
• Number of loses (requires #4)
• Number of quits
• Enemies killed (requires #1)

Including but not limited to:

• Displaying HP and damage numbers (requires #1)
• Displaying remaining time until game over (requires #4)