New TODO:

• create short tutorial lvl to showcase and think of game mechanics
• Refactor for code consistency (ex: consistent variables and @exports and @onready)

Gameplay feathers

• Think of way, that would clearly indicate ground hight (walls, pits, ground ect)

Multiplayer

• REDO (but probably as a last thing)

AI bots

• Enemy
  • Create Enemy or/and Entity class
  • Implement basic states (stay, patrol, attack)
  • Design basic enemy (and npc perhaps)
  • Implement enemy spawn system (for if auto generated)

UI

• Menu needs and overhaul
• Style menu (main/setting/start game)

Docs

old docs iguess

Commits

Commit Individual Final Changes: Aim to commit "logical chunks" of work as you complete them. You do not need to push each commit immediately, but ensure each commit represents a discrete, functional change.

Please write clear commit messages to indicate what each commit does.

For example: Lets say you set out to create a new weapon and maybe fix few bugs. If you create a new weapon and make it functional, but haven't lets say completed the visuals, commit it anyway with a comprehensive message like add crossbow functionality. If you later fix a bug, commit that fix separately with a message like fix reload bug. When you then add visuals, animations, ect for the weapon, commit with a message such as add crossbow visuals.

Regularly Push Changes: Don't forget to push your commits regularly to the remote repository to ensure your work is backed up and accessible to everyone. 🐈🐈‍⬛

Merge Conflicts: If you encounter merge conflicts when pushing feel free to create new branch (if it still lets you) or back up your work other way, most conflicts are resolved automatically but in some cases you might be required to make them manually (usually you can just open them in vs code and then go through them).

Working on Large Features: For substantial changes or features, create a separate branch. This allows for focused development without disrupting the main branch which also means that any of the work you make won't be lost or unused. Name branches descriptively, such as feature/megabegabobega-feature or rework/weapon-system.

Server Guide

run in a container or vm using the --server flag. cmd example:

"project name.exe" --server

or

"project name.exe" --server --headless

Naming and Formatting conventions