The readme still shows info from the start of the project, it should showcase the game and explains what its current features are.

• Pitch the general project and its goal
• Add project banner
• Show game screenshots
• List features
• Link to the 2D course and related tutorials

Having a doxyfile might be a good idea, so new contributors can just use doxygen to generate the documentation, which might be easier to understand the code structure, rather than reading the code manually

For now, the current documentation state is a one big mess:

• It's hard to edit it with having no full featured WYSIWIG editor
• Hard to maintain
• Hard to proofread and apply quick edits by anyone

Reasons to use docute framework and markdown files:

• Markdown files are portable and more lightweight
• Markdown files can be easily edited from absolutely any text editor without having tr

before you start the game you should be able to select a map

You could add descriptions to future tags.
This is more of a gimmick and playing around with git.
Descriptions are plain text and this is how it looks like if you create them completly without github: https://github.com/basxto/gamesPy/releases

Pros:

• Works with local guis for git like gitk
• Works in terminal like git show v1.0.1
• Shows more on repository mirrors (but gitlab is dead

There should be a warning of some sort that some of the game's effects may not be suitable for people with epilepsy. I'm specifically referring to the magnetic orbs in the Frigid Fortress Zone, where they flash different colors at a rapid speed.