diff --git a/README.md b/README.md
index 8eba46c200480d508f85aa90ff97e8425beeed0c..3621ab8e6fee36e83b854bba9b642d8ca6e77ba7 100644
--- a/README.md
+++ b/README.md
@@ -1,93 +1,42 @@
-# IF3210-2024-Unity-SON
-
-
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-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)!
-
-## Add your files
-
-- [ ] [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:
-
-```
-cd existing_repo
-git remote add origin https://gitlab.informatika.org/if3210-2024-02-04/if3210-2024-unity-son.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.informatika.org/if3210-2024-02-04/if3210-2024-unity-son/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [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/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-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!). Thanks 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.
+# Survival Shooter: The Sequel
+
+## Deskripsi Aplikasi
+Survival Shooter: The Sequel adalah permainan tembak-menembak yang berbasis story dengan beberapa quest dan cutscene. Para pemain akan melalui serangkaian tantangan yang harus mereka selesaikan untuk maju ke level selanjutnya.
+
+## Library yang Digunakan
+- **Code Coverage (1.2.5)**
+- **Custom NUnit (1.0.6)**
+- **Editor Coroutines (1.0.0)**
+- **JetBrains Rider Editor (3.0.28)**
+- **Profile Analyzer (1.2.2)**
+- **Settings Manager (2.0.1)**
+- **Test Framework (1.1.33)**
+- **TextMeshPro (3.0.6)**
+- **Timeline (1.7.6)**
+- **Unity UI (1.0.0)**
+- **Version Control (2.3.1)**
+- **Visual Scripting (1.9.4)**:
+- **Visual Studio Code Editor (1.2.5)**
+- **Visual Studio Editor (2.0.22)**
+
+## Screenshot Aplikasi
+Screenshot dari game disimpan dalam folder `screenshots` dalam repositori ini.
+
+## Pembagian Kerja Anggota Kelompok
+- 13521117 - Maggie Zeta RS : Mengerjakan spesifikasi Game Over.
+- 13521161 - Ferindya Aulia B : Mengerjakan spesifikasi xxx.
+- 13521164 - Akhmad Setiawan : Mengerjakan spesifikasi xxx.
+- 13521167 - Irgiansyah Mondo : Mengerjakan spesifikasi xxx.
+- 13521168 - Satria Octavianus N : Mengerjakan spesifikasi xxx.
+
+## Jumlah Jam Persiapan dan Pengerjaan untuk Masing-masing Anggota
+- 13521117 - Maggie Zeta RS : 35 jam.
+- 13521161 - Ferindya Aulia B : xx jam.
+- 13521164 - Akhmad Setiawan : xx jam.
+- 13521167 - Irgiansyah Mondo : xx jam.
+- 13521168 - Satria Octavianus N : xx jam.
+
+## Instalasi dan Menjalankan Proyek
+1. Clone repositori GitLab: https://gitlab.informatika.org/if3210-2024-02-04/if3210-2024-unity-son.git
+2. Buka project dengan Unity Editor versi 2022.3.26f1
+3. Untuk menjalankan game, pilih `Play` pada Unity Editor.
diff --git a/screenshots/cutscene01.png b/screenshots/cutscene01.png
new file mode 100644
index 0000000000000000000000000000000000000000..af0d9a7ce242072c19b8ade593062f1a0abbfbd3
Binary files /dev/null and b/screenshots/cutscene01.png differ
diff --git a/screenshots/cutscene02.png b/screenshots/cutscene02.png
new file mode 100644
index 0000000000000000000000000000000000000000..5034c32959cfacd8ba9652e40cec54e87d09f624
Binary files /dev/null and b/screenshots/cutscene02.png differ
diff --git a/screenshots/cutscene03.png b/screenshots/cutscene03.png
new file mode 100644
index 0000000000000000000000000000000000000000..c509f513dfdd441d74621f9cd246d4ae9920ed45
Binary files /dev/null and b/screenshots/cutscene03.png differ
diff --git a/screenshots/gameover.png b/screenshots/gameover.png
new file mode 100644
index 0000000000000000000000000000000000000000..15cc03cf5331f90dacb70813a33d3238d625ab2b
Binary files /dev/null and b/screenshots/gameover.png differ
diff --git a/screenshots/mainmenu.png b/screenshots/mainmenu.png
new file mode 100644
index 0000000000000000000000000000000000000000..7c2c43fd71153d7ef9675a0ebee77d3fa1a769b5
Binary files /dev/null and b/screenshots/mainmenu.png differ
diff --git a/screenshots/quest01.png b/screenshots/quest01.png
new file mode 100644
index 0000000000000000000000000000000000000000..cd4b04dd1491ee69edc1919f1d7c31a2d827cef0
Binary files /dev/null and b/screenshots/quest01.png differ
diff --git a/screenshots/quest02.png b/screenshots/quest02.png
new file mode 100644
index 0000000000000000000000000000000000000000..6b16f3fbb9c0da6b020ec2bb872e0506362c3e43
Binary files /dev/null and b/screenshots/quest02.png differ
diff --git a/screenshots/quest03.png b/screenshots/quest03.png
new file mode 100644
index 0000000000000000000000000000000000000000..cebf6e13729404642143e265e7b467980c22a823
Binary files /dev/null and b/screenshots/quest03.png differ
diff --git a/screenshots/quest04.png b/screenshots/quest04.png
new file mode 100644
index 0000000000000000000000000000000000000000..4846e5119df20b99a543c710eae76df1e6cc23d7
Binary files /dev/null and b/screenshots/quest04.png differ
diff --git a/screenshots/settings.png b/screenshots/settings.png
new file mode 100644
index 0000000000000000000000000000000000000000..f457f1d519544992e9b9c116b813cb1d5000d68e
Binary files /dev/null and b/screenshots/settings.png differ