2022-06-19 Student Task - Tank Battle

Battle City

Example of gameplay:

https://www.youtube.com/watch?v=fe3oO3zMWWk

You do not have to do anything with visualizations, just take ready-made / sprites and use in your game http://share.yellowrobot.xyz/quick/share-2022-04-12-44491.zip

TODOs

1. Create GIT repo and share it to https://github.com/evaldsurtans (send your repo link to Evalds in chat)

2. Before you start programming the game, using MermaidJS and Typora (or some other tool) create and submit in GIT class diagram of your data structure and at least 3 UML sequence diagrams that shows the common scenarios in gameplay (! read tasks below to better understand this task)

3. Code structure and UML diagrams must be based on OOP (Object Oriented Programming) and MVC (Model View Controller).

4. Model classes (that are not called Model of course, but is something like TankRed, TankGray etc.) are Pydatic dataclasses and json_dataclass and do not contain any functions! At the root of Model classes is Game class that contains all other data classes (aggregation or composition UML). All Model classes must be serializable using json_dataclass function to_json() and then deserialized using from_json()

5. For View use PyGame environment. Class name could be ViewGame it could contain pointer to actual Game class instance.

6. Do not create any UI,. just 2 buttons below game with Tk UI based file dialog to load/save game state as JSON. Only 2 levels needed. https://stackoverflow.com/questions/19476232/save-file-dialog-in-tkinter

7. All logic or Controllers is data-agnostic classes, they do not hold any member variables, just static functions, they work with Model classes. Controllers gets called by ViewGame.

8. Main feature of this game is that you should have function (button) to save Game as json at any time in game, restart app and load it back from where you left off using serialized JSON

9. For different tanks use Inheritance of OOP

10. For Controllers implement Inheritance and Polymorphism so that you would have logic for different tanks in different classes, but the main code would just interact as it would base type of class

11. Encapsulation add private variables to ViewGame that can be accessed only with getters, setters or properties

12. Implement design patterns - make ViewGame as singleton, so that it can be accessed from any controller directly

13. Implement observer pattern, so that controllers would get notified when some event happens and do not need to be updated in every loop

14. Implement Factory pattern, to create tank types based on level and time in game

15. Make sure that game works the same speed at slow and fast computers, use inst.update(delta_time) where delta_time is milisec in between frames, used for speed etc.

16. In Tank game we do not need to have partially broken blocks/obstacles, just make sure that if bullet strikes obstacle it get destroyerd

17. Functions must have single input and single output, cannot have multiple returns

18. All variables should be in the same coding style. Variables are written with small letters and underscores like "user_pictures", private variables "self._user_pictures", Class names for definition are CamelCase "UserPicture"

19. Do no write shpaggeti code, do not call multiple functions in a single line, each line should contain 1-2 function calls, NOT chained together so that code would be readable and debuggable

Some examples of UMLs

Models

Controllers

Views