Since both Starship and Alien have:

• capacity to be damaged (health)
• can fire bullets
• movement
• states
• ...
  create an ABC-Class which is built upon States logic (see data/aliens/.toml) and Loadout (see config/.json::starship). Consider that Info field is included into states, since states are a behavior-oriented part of an enity, which also defines the current state's loadout, (this means that default/initial state has some preset loadout, usually hidden but can be described inside a config, and is overriden by every next state if the defenition is present).

For Starship entities, which are generally conrolled by the player, tthe json-config defines only current loadout; the states are a fixed internal propery, while the Alien entity can freely define states, but currently has loadout set by same presets.

The logic and method of definition should be abstacted from entity itself excetp the fact that it is an Alien or Starship entity - methods of getting the aproppriate config-objects are outside of the entity constructor class.

Move on from direcory storage to sqlite

• Introduce reactor item to loadout, consider its per-sec energy restoration
  • If ship's current energy capacity reches 0 or lower, disable firearms and movement until it restores

• Primary weapon costs
  • per shot
• Thrusters during-movement costs
  • Constant per-second energy consumption so it requires powerfull enough reactor, with same of higher energy per sec production.
  • Moving L/R causes 1.2 more energy consumption

• Power outage scenario and item outage pipeline

Linux at 2560:1600 resolution: during runtime of a level framerate falls near 45 (mostly 53-54) FPS every 0.6-1.3 seconds.

This issue was not noticed on macOS at the same resolution, windows needs to be yet tested.

Sections are more input flow control oriented, while scenes are more about sprite(lists) interactions.

Stage 1

• invasion view
  • merge player and alien sections into a single scene
    - they remain separate, added mixins
  • replace background
  • replace overlay section with scenes
• main menu view
  • replace background section with same scene
  • section with UI buttons stays the same? - yes, section inherits info about keyboard events throught veiw.

As described in #21 - this logic will be reused in several other places, specifically, a more pronounces Pause screen and other views.

Currently theres no benefits of low-powered mode, the disatvantage is constant freefall fallback and shutdown of autofire. This could be n opportunity to include some AOE special/spam attack trigger on reactivation of movement and/or firing, evading mechanic?

Moving Items class to pydantic's BaseMode allow for in-place validation of item paramters, which removes any if all self-written validation boilerplate.

Requirements:

• black
• flake8 (or derivates) - general codestyle checks
• docstring checker tooling (considering numpy doscstring style)

Since the current direction of using interconnected APIs of most in-game entities of #50, it may be more effective to migrate those '.md's to a project's wiki + current documents.

Currently its white window.

Theres 2 possible solutions:

Add texture and consider aerial perspective -> add layers of star dust (3) with different movement and animation speed. On z-axis hisher ones are more bright, velocity is higher and descending on layers. Patterns of dust specs can be different, mainly they should not overlap.

1. Draw.
2. Possibly more accurate for the vibe - using https://imagearchives.esac.esa.int/index.php?/category/1 archive photos with changed alpha-channel

On type-smalls do not randimise since it will look less simplistic.

Reconsider and expand current level logic as of current one:

name = "1"

[[waves]]
# alien types present of a level
spawns = ['dummy_ufo', 'castle_wall_sontra']
# randomly generate enemies but their total health
# should not get bigger than that number
total_enemy_health = 400
# score/experince from killed aliens required to pass this wave
pass_score = 30
# interval in seconds before density_multplier increase
interval = 30
# how many enemies and their speed will increase at next interval
density_multiplier = 1.7

# enemy_size_restrictions

When reactor reaches 0, it keeps subtracting, and no outage/freefall timeout launches.

Consider compiling with nuitka.

Resources:
https://api.arcade.academy/en/latest/tutorials/compiling_with_nuitka/index.html

This presumably is caused by the fact that every alien calls an update() mathod in their designated object on a sprite list of particles, which is shared across all active (not reaped by emiter) Alien instances so as a result we get multiple update calls per frame.

• #56
• #57
• #62
• Upscale Imperfect Copy sprites (pending)

Since most of the audio currently present is still in early stage - thematically, consder adding some sort of sound test mode shortcut from the menu.

• #53
• #52
• #51

https://api.arcade.academy/en/latest/gui/concept.html

Add menu with buttons to start main gameplay loop. For backgroud currently use resources main_menu.png

See #31 (comment)

• Support additional percent-like parameter at Hull
• Add chance-driven logic to Starship class

Consider hiding more difficult and aggresive states behind an XP cap, which only works only on te second+ playthrough of a level. Aliens which were defeated in their all hidden states achive eternal state. Some states my be hdden by another cnditions.

Double L-L / R-R movement momentarily launches ship in that direction. During it ship is made invicncible - DSs' roll iframe.

• FPS counter
• Starship current energy levels
• Average energy consumption per second

Since every item of active equipment needs a texture, combine and apply them to a starship sprite

Document in separate .md logistics of free fall mode, borders and movemnt/firing

Pressing L + R + D prevents ship from movement, it will recieve 2x damage but starts process of repair.

Plan out how aliens should move

Starship entity currently has these categories of equipment:

• hull
• weaponry
• engine
• thrusters

Look through and assess extensible categories and/or more parameters -> move to sql at #1