diff --git a/README.md b/README.md
index f67cf7a5de8db663059d6a3f2cc351a94f182495..e5f8d9e5e833a5b5f36d75c31331b469dd521d6f 100644
--- a/README.md
+++ b/README.md
@@ -1,103 +1,43 @@
-# BubbleSort
+# ChaoticCrates
 
-```plantuml
-@startuml
-class Dummy {
- -field1
- #field2
- ~method1()
- +method2()
-}
-@enduml
+A ChaoticCrates egy többjátékos, körökre osztott online stratégiai játék, melyben a játékosok robotokat irányítanak, és a céljuk a pályán szétszórt színes kockákból különböző építményeket összerakni, melyekre pontokat kapnak. A játékosok két csapat (piros és kék) egyikébe kerülnek. A játék kezdetekor a játékosok a pályán véletlenszerű pozíciókra kerülnek, és a pályából csak a saját környezetüket látják. A korábban felfedezett
+pályarészeket is megjegyzik, de ezek a területek nem frissülnek valós időben. Ha két, egy csapatba tartozó játékos találkozik, (egymás látókörébe kerülnek) akkor onnantól kezdve
+megosztjĂĄk egymĂĄssal a tĂŠrkĂŠpĂźket.
 
-```
+Egy feladat áll egy kirakni való mintából, a lejártáig hátralévő körökből, és a kirakásért járó pontokból. Ha egy csapat sikeresen kirak egy mintát a pályán található kockákból,
+és ezt a mintát a pályán kívülre viszik, majd lecsatlakoznak róla a feladat lejárta előtt, a csapat megkapja a feladatért járó pontokat. A játék előre meghatározott számú körből áll,
+a játék végén a több ponttal rendelkező csapat nyer (döntetlen is előfordulhat).
 
+A pályán a kockák véletlenszerűen helyezkednek el, illetve akadályok is találhatóak, amiket a játékosok el tudnak tisztítani az útból. Mindkét csapat a játék során egyszer használhat egy különleges képességet, melynek hatására a játékban az összes összekapcsolt karaván szétesik. A játékosok a játékot a grafikus felhasználói felület gombjai, illetve a billentyűzet és egér használatával tudják irányítani. A felhasználói felület valós idejű tájékoztatást nyújt a játék aktuális állásáról: többek között láthatjuk a hátralévő körök számát, a csapatok pontszámait és az aktuális feladatot. A játékosok előre megírt chatüzenetekkel tudnak egymással kommunikálni. A kamera a jobb egérgombbal szabadon mozgatható, a görgővel zoomolni lehet, a space gomb pedig a játékos saját karakterére irányítja a kamerát.
 
-## Getting started
+## Mire van lehetőség egy körben?
 
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+- Mozogni
+- KockĂĄra csatlakozni
+- KockĂĄrĂłl lecsatlakozni
+- KĂŠt kockĂĄt Ăśsszekapcsolni
+- KĂŠt Ăśsszekapcsolt kockĂĄt szĂŠtkapcsolni
+- A rĂĄcsatlakozott kockĂĄkkal egyĂźtt forogni
+- AkadĂĄlyt tisztĂ­tani
+- SpeciĂĄlis kĂŠpessĂŠget hasznĂĄlni
+- VĂĄrakozni
 
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+## Képernyőképek
 
-## Add your files
+### Main menu / lobby
 
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+![Menu](/img/menu.png)
 
-```
-cd existing_repo
-git remote add origin https://szofttech.inf.elte.hu/szofttech-ab-2023/group-02/bubblesort.git
-git branch -M master
-git push -uf origin master
-```
+![Lobby](/img/lobby.png)
 
-## Integrate with your tools
+### Gameplay
 
-- [ ] [Set up project integrations](https://szofttech.inf.elte.hu/szofttech-ab-2023/group-02/bubblesort/-/settings/integrations)
+![Game1](/img/game1.png)
 
-## Collaborate with your team
+![Game2](/img/game2.png)
 
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+![Game3](/img/game3.png)
 
-## Test and Deploy
+### Game Over
 
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+![GameOver](/img/gameover.png)
\ No newline at end of file
diff --git a/img/chat.png b/img/chat.png
new file mode 100644
index 0000000000000000000000000000000000000000..15c49673ff1a020bb9d8ab100075c275d7464b2c
Binary files /dev/null and b/img/chat.png differ
diff --git a/img/game1.png b/img/game1.png
new file mode 100644
index 0000000000000000000000000000000000000000..9f5d874ec67ee1437d97b89c7322831b31927dc0
Binary files /dev/null and b/img/game1.png differ
diff --git a/img/game2.png b/img/game2.png
new file mode 100644
index 0000000000000000000000000000000000000000..80cc34749f531dfb249cee37c35f0426cae7e8fa
Binary files /dev/null and b/img/game2.png differ
diff --git a/img/game3.png b/img/game3.png
new file mode 100644
index 0000000000000000000000000000000000000000..105d59486561c6cc9e25d93967a3c394f217b0c3
Binary files /dev/null and b/img/game3.png differ
diff --git a/img/gameover.png b/img/gameover.png
new file mode 100644
index 0000000000000000000000000000000000000000..687f91a620b4ff66fd18041140dd9bd1a012fa20
Binary files /dev/null and b/img/gameover.png differ
diff --git a/img/lobby.png b/img/lobby.png
new file mode 100644
index 0000000000000000000000000000000000000000..1fcc5bbea31e2a16d13c1c302f97190bd5d29080
Binary files /dev/null and b/img/lobby.png differ
diff --git a/img/menu.png b/img/menu.png
new file mode 100644
index 0000000000000000000000000000000000000000..fdcda639167352ce76fab414834bd5e1cbdd33f7
Binary files /dev/null and b/img/menu.png differ