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:
-[ ] [Set up project integrations](https://agile.bu.edu/gitlab/HX/tetris-but-2048-demo/-/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)
-[ ] [Automatically merge when pipeline succeeds](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!). 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.
# Group9Project DEMO
## Project Name:
Tetris but 2048
## Category:
Tetris-like Animated game.
## Description:
Combine the fast-paced falling block mechanics of Tetris with the number-merging gameplay of 2048. Merge blocks, create bigger numbers, and score high！
## How to run our game:
1. Clone our code with the Link:https://agile.bu.edu/gitlab/ec327_projects/group9project.git
2. In terminal use command : "git checkout demo"
3. Open the folder you have downloaded in Android Studio.
4. Click Device Manager, and click Create device. We recommend you to choose Category: Phone, Name : Pixel 2, API Level: 30.
5. When everything is ready, click the green triangle at the top right toolbar.
“Tetris but 2048” is a game where players aim to merge numbered blocks and score high before there is no space to fit any new blocks. The game features a playing field where numbered blocks will fall at regular intervals.
The player can move the blocks horizontally using arrow keys and rotate using a rotate button. When two or more blocks with the same number touch vertically, they will merge into one block with a value equal to the sum of the merged blocks. The game includes many types of blocks with different values and colors.
The game features two difficulty levels - normal and difficult - that differ in block falling speed, which players can adjust in settings. The game ends when the blocks reach the top of the screen and there is no more space to add new blocks.
Players earn points based on the sum of the values of blocks in the playing field. The game includes a score that displays at the top of the game page.
Min. Requirement:
Players can move the blocks left or right using the arrow keys and rotate them using the up arrow key. The blocks will fall automatically, but players can pause the game by pressing the pause button.
The blocks will fall automatically once the game begins. Users will have the ability to control some of the moving pieces through input. We provide the user with four buttons to control the moving blocks: left, right, rotate, and pause.
The game includes a score that changes based on the user's ability to satisfy requirements. There's a score displayed at the top of the game page that shows the points the user earns by summing up the values of blocks in the playing field.
The game features a simple-to-use graphical user interface. All buttons and texts are clear and easy to see and use.
We also provide clear documentation of the game's rules in the README file.
The game does not require any Internet or network connectivity, as it can be played locally. It does not violate the copyright of Tetris or any other game. While our game is inspired by Tetris and 2048, it is fundamentally different from them.
## Potential Feature have been done:
1. Allow the user to interact with the game by moving the phone:
When you are shaking your phone, the following block will rotate once.
Provide a high-score list that persists when the app is closed and then reopened: when the game is done, it will jump to a new page tells your score and then it will show you your rank and the 3 highest score the play have got.
2. Allow the user to tweak the rules of the game being played: In the set, you can adjust the difficulty of the game. Blocks will fall faster in difficult mode.
3. Add sound effects for specific activities in the game: sound will be played when you click the button or shake phone to rotate block or when blocks are merged.
4. Do all calculations in C++ and connect them to the app through Android's Native Development Kit: the function of sorting score and calculate the score in the game are wrote in C++.
## Design decisions:
Pause game - We used a timer to implement the pause function. When the pause button is pressed, the timer is stopped, which means that the game will stop updating and the blocks will stop falling. This creates the effect of pausing the game. When the pause button is pressed again, the timer resumes, which means that the game will continue updating and the blocks will start falling again.
Rotate Block when shaking the phone - Shaking the phone will causes the blocks to rotate once. To achieve this, we created a variable that records whether the block has already rotated due to shaking and refreshes it every time cycle to ensure the block rotates only once per time circle.
