Initial release.
This commit is contained in:
parent
7857a94c81
commit
0e005f6c4c
3 changed files with 128 additions and 91 deletions
20
LICENSE.md
Normal file
20
LICENSE.md
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
# GNU Affero General Public License v3.0
|
||||
|
||||
Copyright (C) [2024] [Mr Finchum]
|
||||
|
||||
This program is free software: you can redistribute it and/or modify
|
||||
it under the terms of the GNU Affero General Public License as published by
|
||||
the Free Software Foundation, version 3 of the License.
|
||||
|
||||
This program is distributed in the hope that it will be useful,
|
||||
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
||||
GNU Affero General Public License for more details.
|
||||
|
||||
You should have received a copy of the GNU Affero General Public License
|
||||
along with this program. If not, see <https://www.gnu.org/licenses/>.
|
||||
|
||||
---
|
||||
|
||||
## Additional Notes:
|
||||
This program is licensed under the AGPL-3.0, which requires that any modifications or derivative works distributed or used over a network must also be licensed under the AGPL-3.0.
|
||||
96
README.md
96
README.md
|
|
@ -1,93 +1,7 @@
|
|||
# Rock Paper Scissor Card Game
|
||||
# Rock Paper Scissors Card Game
|
||||
|
||||
A little game to play the classic Rock Paper Scissors game with a twist.
|
||||
Instead of freely selecting between Rock, Paper, and Scissors, you get a hand of three cards, potentially with only rocks.
|
||||
It is a semi-random 52-card deck with an unbalanced distribution of cards, meaning some cards are less likely to occur. For example, only 5 out of 52 cards are stones, so it is very unlikely the other player has a stone. Selecting scissors gives a higher chance of winning.
|
||||
|
||||
|
||||
## 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/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
|
||||
|
||||
```
|
||||
cd existing_repo
|
||||
git remote add origin https://gitlab.com/CodeByMrFinchum/rock-paper-scissor-card-game.git
|
||||
git branch -M main
|
||||
git push -uf origin main
|
||||
```
|
||||
|
||||
## Integrate with your tools
|
||||
|
||||
- [ ] [Set up project integrations](https://gitlab.com/CodeByMrFinchum/rock-paper-scissor-card-game/-/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/user/project/merge_requests/auto_merge/)
|
||||
|
||||
## 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/)
|
||||
- [ ] [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.
|
||||
This project is in its early stages. Some features are planned, but currently, it just runs in the terminal, and you can select cards. The *AI* selects a card completely at random. If there is a draw, you continue with the cards you started with. If one player wins, new cards are dealt.
|
||||
|
|
|
|||
103
src/main.py
Normal file
103
src/main.py
Normal file
|
|
@ -0,0 +1,103 @@
|
|||
import random
|
||||
|
||||
def rock(lst, n):
|
||||
for _ in range(n):
|
||||
lst.append("Rock")
|
||||
return lst
|
||||
|
||||
def paper(lst, n):
|
||||
for _ in range(n):
|
||||
lst.append("Paper")
|
||||
return lst
|
||||
|
||||
def scissors(lst, n):
|
||||
for _ in range(n):
|
||||
lst.append("Scissors")
|
||||
return lst
|
||||
|
||||
def build_deck():
|
||||
cards = [rock, paper, scissors]
|
||||
deck = []
|
||||
|
||||
random.shuffle(cards)
|
||||
for i in range(2):
|
||||
n = random.randint(5, 20)
|
||||
deck = cards[i](deck, n)
|
||||
|
||||
missing_cards = 52 - len(deck)
|
||||
deck = cards[2](deck, missing_cards)
|
||||
random.shuffle(deck)
|
||||
return deck
|
||||
|
||||
def give_cards(deck):
|
||||
"""Give 3 cards to both player and AI, removing them from the deck."""
|
||||
return [deck.pop(0) for _ in range(3)], [deck.pop(0) for _ in range(3)]
|
||||
|
||||
def battle(user_card, ai_card):
|
||||
"""Returns 1 if user wins, -1 if AI wins, 0 for a tie."""
|
||||
if user_card == ai_card:
|
||||
return 0
|
||||
if (user_card == "Rock" and ai_card == "Scissors") or \
|
||||
(user_card == "Paper" and ai_card == "Rock") or \
|
||||
(user_card == "Scissors" and ai_card == "Paper"):
|
||||
return 1
|
||||
return -1
|
||||
|
||||
def play_cards(user_hand, ai_hand):
|
||||
"""Handles playing cards until a winner is determined or cards run out."""
|
||||
while user_hand and ai_hand: # Keep playing until hands are empty
|
||||
print(f"\nYour cards: {user_hand}")
|
||||
|
||||
while True:
|
||||
try:
|
||||
user_choice = int(input(f"Select a card (1-{len(user_hand)}): ")) - 1
|
||||
if 0 <= user_choice < len(user_hand):
|
||||
break
|
||||
except ValueError:
|
||||
pass
|
||||
print("Invalid choice. Try again.")
|
||||
|
||||
user_card = user_hand.pop(user_choice)
|
||||
ai_choice = random.randint(0, len(ai_hand) - 1)
|
||||
ai_card = ai_hand.pop(ai_choice)
|
||||
|
||||
print(f"You played: {user_card}, AI played: {ai_card}")
|
||||
|
||||
result = battle(user_card, ai_card)
|
||||
if result == 1:
|
||||
print("You win this round!")
|
||||
return 1 # User wins
|
||||
elif result == -1:
|
||||
print("AI wins this round!")
|
||||
return -1 # AI wins
|
||||
else:
|
||||
print("It's a tie! Play again with remaining cards.")
|
||||
|
||||
print("No cards left, this round is a draw.")
|
||||
return 0 # Round is a draw
|
||||
|
||||
def play_game(best_of = 3):
|
||||
"""Main game loop."""
|
||||
my_deck = build_deck()
|
||||
user_score, ai_score = 0, 0
|
||||
rounds_to_win = (best_of // 2) + 1
|
||||
|
||||
while user_score < rounds_to_win and ai_score < rounds_to_win and len(my_deck) >= 6:
|
||||
user_hand, ai_hand = give_cards(my_deck)
|
||||
|
||||
round_result = play_cards(user_hand, ai_hand)
|
||||
|
||||
if round_result == 1:
|
||||
user_score += 1
|
||||
elif round_result == -1:
|
||||
ai_score += 1
|
||||
|
||||
print(f"Score - You: {user_score}, AI: {ai_score}")
|
||||
|
||||
if user_score > ai_score:
|
||||
print("\n🎉 You won the match!")
|
||||
else:
|
||||
print("\n🤖 AI won the match!")
|
||||
|
||||
# Run the game
|
||||
play_game(best_of = 5)
|
||||
Loading…
Add table
Add a link
Reference in a new issue