diff --git a/README.md b/README.md index a50cc512e027d06f355e7dc9f0fbded19cf032ae..958412890a179f0352b6e3e0c7a19b188681fc54 100644 --- a/README.md +++ b/README.md @@ -1,92 +1,107 @@ -# IF3210-2023-Unity-BBS +# IF3210 Tubes Unity +### [Ref:Notion](https://momentous-ring-807.notion.site/Agate-Survival-Shooter-b27ea3ef2545482bb10e2e0cda1bbc10) +### Deskripsi +Survival Shooter: Extended, merupakan game ekstensi Survival Shooter dari Unity Learn. Game dibangun dengan Unity 2021.2.16f1. -## Getting started -To make it easy for you to get started with GitLab, here's a list of recommended next steps. +### Cara Kerja, terutama mengenai pemenuhan spesifikasi aplikasi. -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)! +> - Main menu +> Main menu terdiri dari scene untuk memilih opsi-opsi permainan yagn ada. -## Add your files +> - Scoreboard +> Scoreboard menampilkan daftar pemainan yang telah selesai berserta waktu permainan, dengan keterurutan berdasarkan waktu terlama. -- [ ] [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: +> - Game Over +> Setelah player sudah mati atau menang, maka akan muncul tampilan game over. -``` -cd existing_repo -git remote add origin https://gitlab.informatika.org/rizkyramadhana/if3210-2023-unity-bbs.git -git branch -M main -git push -uf origin main -``` +> - Player Attribute +> Player memiliki 3 attribute yaitu **Weapon**, **Movement**, dan **Health**. Weapon awal ialah gun, sedangkan selanjutnya pemain bisa membeli senjata di shop, damage dan karakter tiap senjata berbeda. Movement dipengaruhi oleh speed dengan nilai pengali awal 1. Health awal pengguna adalah 100. -## Integrate with your tools +> - Save and Load +> Menyimpan state dari permainan, baik itu quest, poin, timestamp, hingga weapon dan inventory shop. -- [ ] [Set up project integrations](https://gitlab.informatika.org/rizkyramadhana/if3210-2023-unity-bbs/-/settings/integrations) +> - Cheat +> Menggunakan input tekstual dengan bantuan enter sebelum dan sesuah memasukkan cheat untuk mendapatkan keajaiban dalam permainan. -## Collaborate with your team +> - Weapon dan Weapon Upgrade<br> +> Memungkinkan pemain mengubah dan meningkatkan permainan. Weapon selain deafult (gun) dan upgrade harus dibeli di shop. Senjata terdapat tiga buah yakni gun, shotgun, bow (projectile), dan sword. -- [ ] [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) +> - Shoppkeeper +> Memungkinkan pemain untuk membeli gun atau pet jika berada di sekitar shop dengan syarat menyelesaikan quest untuk mengakses shop. -## Test and Deploy +> - Pet +> Terdiri dari 3 jenis hhewan yang mengikuti pemain dan memiliki kemampuan khusus berbeda (menyerang, buff, dan heal). Pet dapat dibeli di shop. -Use the built-in continuous integration in GitLab. +> - Quest +> Special task yang dapat diselesaikan oleh player untuk mendapat reward. Tiap selesai sebuah quest, maka akan terbuka pintu ke shopkeeper. -- [ ] [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) +> - Scene +> Scene terdiri atas cerita dari prolog dan epilog dari permainan. Player dapat melihat scene Bos jika sampai ke bos level. -*** +### Library yang digunakan dan justifikasi penggunaannya. -# Editing this README +> - Semua Library yang digunakan merupakan bawaan dari UnityEngine seperti, +> > - UnityEngine.UI - Untuk mengatur UI pada canvas +> > - UnityEngine.SceneManagement - Untuk mengatur navigasi antar scene -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. +### Screenshot aplikasi. -## 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. +<div style="display:flex; flex-wrap: wrap; gap: 1%; justify-content:center"> -## Name -Choose a self-explaining name for your project. +<div style="width: 48%;"> +<h5 style="margin-bottom:0;">Intro (input player name)</h5> +<img src="" /> +</div> -## 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. +<div style="width: 48%;"> +<h5 style="margin-bottom:0;">Main Menu</h5> +<img src="" /> +</div> -## 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. +<div style="width: 48%;"> +<h5 style="margin-bottom:0;">Game Over Screen</h5> +<img src="" /> +</div> -## 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. +<div style="width: 48%;"> +<h5 style="margin-bottom:0;">Zen Mode</h5> +<img src="" /> +</div> -## 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. +<div style="width: 48%;"> +<h5 style="margin-bottom:0;">Wave Mode</h5> +<img src="" /> +</div> -## 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. +<div style="width: 48%;"> +<h5 style="margin-bottom:0;">Zen Mode (FPS)</h5> +<img src="" /> +</div> -## 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. +<div style="width: 48%;"> +<h5 style="margin-bottom:0;">Wave Mode (FPS)</h5> +<img src="" /> +</div> -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. +<div style="width: 48%;"> +<h5 style="margin-bottom:0;">Scoreboard: Zen Mode</h5> +<img src="" /> +</div> -## Contributing -State if you are open to contributions and what your requirements are for accepting them. +<div style="width: 48%;"> +<h5 style="margin-bottom:0;"></h5> +<img src="" /> +</div> -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. +</div> -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. +### Anggota Kelompok -## 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. +- 13520043 - Muhammad Risqi Firdaus: Cheat + Weapon +- 13520106 - Roby: Scene + Main Menu +- 13520151 - Rizky Ramadhana: Shokpkeeper + Pet +- 13520162 - Daffa Romy Z.: Gameover + Local scoreboard +- 13520148 - Fikri Ihsan Fadhilah: Quest + Save