Play-With-Python icon indicating copy to clipboard operation
Play-With-Python copied to clipboard

Updated the UI of the 2048 Game and added some features.

Open Krishcodes-awesomestuff opened this issue 6 months ago • 0 comments

Pull Request for Play With Python 💡

Issue Title : Enhancement: Added Score System and Restart Feature to 2048 Game

  • Info about the related issue (Aim of the project) : Enhanced the 2048 game by adding score display, high score system with file persistence, and restart functionality to improve user experience
  • Name: Krishnaprasath Venkadesan
  • GitHub ID: Krishcodes-awesomestuff
  • Email ID: [email protected]
  • Idenitfy yourself: (Mention in which program you are contributing in.) python

Closes: #issue number that will be closed through this PR

Describe the add-ons or changes you've made 📃

  1. Added Score Display System:

    • Implemented real-time score display during gameplay
    • Score updates dynamically when tiles merge
    • Score display is prominently shown at the top of the game window
  2. High Score System Implementation:

    • Added persistent high score tracking using file storage
    • High score is maintained between game sessions
    • High score display updates automatically when broken
    • Uses 'high_score.txt' for score persistence
  3. Restart Functionality:

    • Added a restart button to the game interface
    • Allows players to start a fresh game at any time
    • Properly resets all game states while preserving high score
  4. Documentation Updates:

    • Updated README.md with new features and functions
    • Added documentation for new methods
    • Updated contributors list
  5. Code Improvements:

    • Added new methods for score management
    • Implemented game state management for restart feature
    • Enhanced user interface with new display elements

Type of change ☑️

What sort of change have you made:

  • [x] Bug fix (non-breaking change which fixes an issue)
  • [x ] New feature (non-breaking change which adds functionality)
  • [ ] Code style update (formatting, local variables)
  • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • [ ] This change requires a documentation update

How Has This Been Tested? ⚙️

I ran it locally in my terminal, it works! no cap

Checklist: ☑️

  • [x] My code follows the guidelines of this project.
  • [x] I have performed a self-review of my own code.
  • [x] I have commented my code, particularly wherever it was hard to understand.
  • [x] I have made corresponding changes to the documentation.
  • [x] My changes generate no new warnings.
  • [x] I have added things that prove my fix is effective or that my feature works.
  • [x] Any dependent changes have been merged and published in downstream modules.

Krishcodes-awesomestuff avatar Apr 08 '25 16:04 Krishcodes-awesomestuff