DuckyBoi_XD

GAME DEMONSTRATION - PYPI

I wrote the PyPi method of playing the game in the README. I explained the different steps you need to go through and the different methods for checking your installation

I gave up on implementing Windows compatibility.

This devlog was a combination of days due to it taking a long time to fix and implement the PyPi package. I created many files to support the PyPi packaging and implemented the code for it to work. On the way, I had to create another file to let the user just use a specific command/code to start the game. As far as I know, it should fully work on macOS (not Windows, I need to fix the bug) and should still save the game data.

Now, after completing the terminal craft part, I want to make it playable on PyPI and or Homebrew for better coverage. In this devog, this was a combination of a bunch of days due to inactivity and other focuses. Basically, I integrated a Windows code that would be runnable on Windows, enabling 'w' and 's' as up arrow and down arrow and attempted to configure and fix parts of the code.

I fixed some bugs and errors in the game, like the lack of the command clear_screen() and some errors in the logic. I also updated the release page and created a read me, so it's hopefully easy for people to use and understand this project.

I fixed a bunch of bugs and errors that were appearing in the executable game. I added the executable game file, which is in a tar file, so that people can more easily access it. Sadly, when downloading from GitHub, it will send an error that Apple can't check if it is malware, so I'd have to tell users to either remove it by using a command, or get it from me c:

Updated the exit() code to be sys.exit() to fix errors in the executable code. Also, configuring the executable process and distribution

I fixed some code I forgot to fix/edit, and changed the no more money function so that when you have $0, you are given financial aid ($10), but in their stats, there is a stat called broke count which tracks how many times you needed financial aid. There are still a bunch of features I want to pack into this game, but I'm running out of time (deadline 19th of September). Lastly, I tested the game when it was packaged in an executable file using PyInstaller, and I'm happy to see it work.

I created and finished the help function that was previously in the menu. I am adding infromation about the game and how the rounds work (also the duck replacing jacks). I started on the end function, where if the user has no money left, they have to restart. I might change this where the users are given a bit more money to play with.

I fixed the logic with the X20 round because, for some reason, I didn't change it to track suits. I also continued on the function after winning the game.

I created the base of the X20 round of the suits function, where you need to guess the suit for X20 times the original bet (almost done). I also improved the QoL, adding a bet tracking so the player knows their bet at all times.

I fixed some errors within my code for the X3 round and finished the X4 round in the game. I made sure there were minimal errors and that the output of the code looks nice.

I continued on the second round of the game, over or under. I configured the code to support the new mode, and I found out that a lot of the code didn't work, so I had to attempt to fix it with little hope.

I fixed the logic in the game where the output of the game wasn't working correctly. I realised I might have overused some code, but I think it it pretty good. I started working on the next round

I adjusted the ASCII code to make the card image smaller and more compact. I also made the code to update the stats and track when winning a game.

I finally finished the card output and made the first round work. I probably made it more complex than needed, but at the moment, it works and is good enough.

I finally finished the card ASCII image, which, theoretically, I should be able to use for every round of my game. I tried progressing past the image, but there were tiny problems with the code that I had to fix.

I tried my best to make my card image easier and simpler to use. I still haven't finished it, so I'd have to fix it.

Today I spent SO MUCH TIME trying to configure and create the card ASCII, and I made it, inspired by the Poker over SSH me my friend and I made. I ended up creating a prototype with an image I found nice, but realised the code was a bit overcomplicated and that I wanted to cut it down.

I started on the main game, but before it, I realised I needed to make the icon that tells you what part of the game you're in, as well as showing the multiplier of the round you're in. I had to create a statement that checks variables that will be set during the main game, where they will change the icon depending on the outcome.

I finished the betting check in the main game and added the quick exit (Ctrl-C and Ctrl-D) to the arrow menu.

I started on the main game function. During its development, I created a function to check if it's a float (a number) and if it's a valid money number (2 dp). I also changed the arrow menu function, where the title can be shortened with presets.

I added stats to the stats page and adjusted the save file to save them. I also added/fixed the quick exit using Ctrl-C or Ctrl-D (on Mac) to exit out of the program quickly.

I told my friend about the encryption I added to my save file, and he told me it was way too easy to decode and alter the save file. Even though the code is open source, meaning you can see how it's encoded, I decided to make the save file more secure and not only use base64, but a couple of other methods, which I will now state here, but you can see in the devlog photo if you can read it.

I fixed my values and formatting of my code. I finished the name pick function (for now) and kept my colours and format of my output consistent.

Troubleshot the bug where the text before the arrow key function was too high. I'm just stupid. I removed some code from where I was debugging

I improved on some code relating to the name function and the starting function. I added a single key tracking to use for press any key to continue statements. I also added clear comments to my code, to better organise it.

Here, I created the arrows function, which will create a cool component that will make the game feel smoother and improve QoL. With this, I created a quick menu page and improved the name function.

The last part. I added a status page, which shows the status of the game. There is also a link to the status website from Uptime Kuma.

I added a function to clear the terminal screen, so it's like a game. I created the name value, and I'm happy to know that it was saved through the save file. Lastly, I made a function to print a separator line for a cleaner look.

Added colours and decoration effect to text for the future. I wanted to add a name function, so I added a name value to the save file. I made sure to add a bunch of notes to the save file since it was very complex for my brain, and I needed to understand what was happening in it.

This is the start of my project for TerminalCraft. I will be making the first round of Ride the Bus in Python with many extra features. I made all the files and created the save file system using JSON, and made the card rankings and card deck for the game. Special parts: Used base64 for encoding the save file

We needed to add a status page on the website so everyone could see if the server was up or not.

I fixed the wording in the 'about' text.

(previous time got added to the previous devlog) I finished the about section, finishing the inspiration section and the credit section. I made their boxes fixed to the text and fixed a bunch of mistakes like spelling, grammar and useless code that's not needed. I also created and finished the Readme for this website.

I started on the About section, where I started writing about the inspiration for the project and why we made it in the first place.

I finished the guide section, adding the showdown stage, as well as adding a box of text to explain hand rankings. This required me to change the typewriter function so that the colour for the suits would appear. After finishing the guide infromation, I made the text boxes fixed so there isn't an earthquake when looking at the last box.

I added more information to the guide. I added information about the Flop, Turn and river and how they work/what happens.

I added some more information to the guide, talking about the pre-flop stage. I adjusted some formatting with the guide page, made the typewriter function writer faster if it has been writing for too long and optimised the background.

I added a terminology section in the guide so that people can understand common terminology in poker.

I had to, again, fix the code due to my friend removing the features by accident. I make the logo of the game on the top left in a nice green colour scheme with a > representing SSH and the Spade representing playing cards. I also wrote I bit more in the guide while adjusting the code to make it look nice.

I started on the guide section, where I will explain (to people who don't know) how to play poker and how to play poker in the SSH.

My friend decided to add a bunch of features while changing parts of my code and breaking some of my features, so I had to fix them. I added a link to SoM from the icon on the top left and cleaned the fox and text.

Adjusted code for the SSH box while adding more information on how to play the game + QoL addition. Fixed a problem with the code's typewriter function breaking.

I switched the logo back to SoM because it's more suitable and fixed the typewriter function so it more easier to use. I also added information on how to play the game. While doing this, I had to alter some code so the features would work.

Added a feature where the button text would glow if you're on the page.

I changed the links to the other pages from a box with the text that controls the link function to a button that controls the link function. I resized the buttons and switched the SoM image with the Hackclub image because I think it contrasts better.

I added a box that is fixed on the top of the screen with important uses, like the logo of SoM and links to other pages. I fixed the information box to be a fixed size and spaced out the links to look nice and professional. Currently the SoM logo looks a bit weird so I might need to change it.

Fix - I had to fix the cross-compatibility with my code, and I had a friend help me test it. I realised that the getch wasn't working properly, so I added a function that is more complicated but works. I also added a QoL indentation to show whose turn it is in the blackjack game.

I changed some values in the text and box, and I added a typewriter effect that I plan to use on all text in boxes. I also changed the background, where I went to Photoshop and made it bigger.

Because I'm bad at coding in Python, I decided to make the website for the game. I worked on the front page, where I added a title with glowing text and a box for future information. I also played with the glowing code for the title.

Our plan is to create a poker game that you can play with other people using SSH. I am doing this with Qincai. I started by helping create the plan of what we are going to do and tested a bit of the code.

Started on my PyPi package and GitHub Actions. I created many files (with the help of my friend and Copilot) where I can publish a PyPi package to make it simple for people to play the game. There are still some issues and a few little parts I need to fix, but I've pretty much completed it.

Continued on the main Python code. I spent a lot of time trying to figure out the working of the ace function and ended up using AI to help me, so I didn't need to struggle with it anymore. After that, I created the split function, which can only be played once, because it was easier to code that way. I think I have finally finished the game, and now I need to turn it into a PyPI package.

Continued on the main Python code. I found out there were still many errors in my code, like the type writer function creating errors with text from variables. I was able to fix it, but there were still other errors, like my ace not changing, which I still have to fix.

Continued on the main Python code. I got help from a friend and made a typewriter function where the text will output like a typewriter. After this, I checked all my code and fixed all parts that had errors or problems. After this, I created the advanced blackduck (blackjack) and added most of the double-down feature, but sadly, there are still errors.

Continued on the main Python code. Finished all the user's options and started coding for the dealer to finish the game. I created a base code that the dealer will repeatedly add more cards, didn't add a way to stop it. I also added the base code for the dealer to announce the outcomes.

Continued on the main Python code. I changed the hand system from a list to a dictionary so I can have the value of the cards in there, which made it way simpler to calculate the total. I made the total counter (toggleable) and fixed all the hit code. I started on the stand function but quickly left it to work on the losing function.

I started the boba workshop 2 weeks ago and realised I can turn it into a SoM project. Today I did the Swirl workshop where I added more information and made it cooler. c:

Continued on the main Python code. I created the dealing system and options when starting the game. I also created a functional betting page where you can bet the amount you want. There are still problems in the base game.

Continued on the main Python code. I fixed and created the blackjack game mode, where you can select either normal or advanced. I made a settings page where you can turn the game mode to a specific one and turn on a card total counter.

Continued on the main Python code. I finished fixing all the errors on the ATM function. I also started on the BlackDuck (Blackjack) game and settings page.

Continued on the main Python code. I continued on the ATM function and almost finished it; all I need to do is fix any errors. I changed the name function so people can only put string text.

Continued on the main Python code. I created and finished the name function, where users can insert their name and an ATM feature, where if players run out of cash, they can use an atm to get more money.

Continued on my main Python code. Finished my information code, where you can read about the information for the game (How to play, Terminology, Card Values, Tips and Tricks). Fixed/finished the card variables. Added code terminology in my README, mostly for variable acronyms.

Continuing on my main Python code, in the information section of the menu, I completed the How to play (Normal), How to play (advanced) and started on the card values information. I also fixed/changed the way I assigned the variables by using for loops to put them in a dictionary, which I can later use.

Continued on the main py code. Continued on the menu, where I finished the terminology section and almost completed the 'How to play(normal)' section. I also added error messages when selecting options that weren't available.

I started on the menu function, where you will be able to start the game, access information and settings, and quit the game (including the CTRL-C and CTRL-D keys). In the information menu, I created more menus that can help with playing and provide tips for the game.

Started off by creating the repo and the code files. In said code files, I created my main Python code, which I have labelled and established the variables in my game. (Labelling each variable might be necessary)

I fixed an error when using CTRL+C to exit the game. I adjusted some code and tested it on Windows. I wrote some PyPI installation instructions, but I doubt it will be much help. (I somehow removed my older hackatime file of the original one in the code tunnel, so I'm using another one)

I wrote a bit about what I was thinking of doing in my readme. To sum it up, I don't think I should continue making the game in Python due to its complexity with being compatible with the website functions. I decided to move away from Python and start learning JavaScript, HTML and CSS. I also spent a lot of time trying to configure the pip for my mini game to use as a demo.

I didn't do much today because I rested for a large portion of the day. I tried to use the pygame and pygbag, but I found it really difficult to do. I wrote a bit explaining my mini game and left it there.

I tried to import pygame and try to make the web app, but I didn't really do much (deleted everything)

I finished the mini game called Lucky Room. Today I completed the last 3 games (it's easier to write them because of previously structure of other game). I also did some polishing with adding a wallet feature, exit functions, and author message. I tried to check for most of the errors by testing it so I hope I got most of them. I might try to make it into a quick and skuffed desktop game but for not the code is finished in its v1 stage.

Today, I continued on my mini game. In the last devlog, I said I would post more devlogs. I also said that I'll post my next devlog after I finish the dice roll and coin flip. I overestimated how hard it would be, and I decided to finish today's session by finishing the dice roll code. I got my dice roll game to work and secured it with a bunch of conditions so it's really difficult to break it (I hope).

I finished my learning stage and briefly explained the very basic parts of Python in my README. I finished the for loop, while loop, function, try-except and PIP. I plan to learn other parts along the way because I doubt if I learnt it at this stage, I would remember. I start on my mini game, where it's pure luck, and I've already learnt some new stuff like input() . Currently, I'm really excited to continue on and create a functional game. I think I should be doing more devlogs instead of doing one at the end of each day. So, I'll do my next one once I finish the first 2 luck games (dice roll and coin flip).

I did SO MUCH WORK today. I finished the list of tutorials and moved on to statements like if, elif and else. I also finished up the match function, which is so useful that I was amazed. I fixed up some small errors with the read me and read through a bit of some tutorials I skipped due to their complexity and uselessness. P.S. I had a heart attack when I found my time reset for SoM, but it might have been a syncing issue, but some kind people from SoM Support tried to help fix. Thank you, Shreyas and Ambe!!!

I added more information for my README to give a better idea of what I'm planning to do/achieve.

I finished casting (pretty simple, just changing data type) and almost finished string tutorials. I currently working on explaining and understanding the methods and different functions in string. I should try to make a small little game to make sure I understand all the mechanics I learnt

I learnt a lot more about Python's code. I understood the different kinds of data types there are, and looked through the thorough explanation of the numerical data types. Through this, I found a module reference to the random function. This would be perfect for my gambling game project. I followed through the reference sheet like it was a tutorial, noting and showing my understanding the my learn.py files in my repo. I have finished the random function reference, and I'm about to start the next part of the tutorial, casting.

I learnt a bunch of things in Python like 'print', variables, syntax (only if statements) and comments. I showed my understanding and explained each part in my learn.py file in my repo.

I think i have finally finished the case for my project, polished the PCB, made a table for BOM, updated BOM and started on production files and importing finishing files.

I thought I finished my case, but I forgot to check the length of the potentiometer, meaning I have to either redo the case or pick a different potentiometer. Probably both. I also wrote a lot in my README, but I haven't finished yet.

Journal Time (catch-up time from last night)

Worked a lot on my case on fusion. The coding platform for my repo and what I track 90% of my time broke. So there isn't much time on this Devlog.

Actually fixed the DRC errors in the PCB thanks to Person 20020. Added some finishing touches on PCB Started on the case, which is going pretty good

I actually got help for my PCB, and guess what, it was from my personal dm to Person. TYSM PERSON20020 for helping when no one else will. (a lot of trial and error) I'll write a journal tomorrow. I FINISHED PCB TIME TO DO CASE. (definitely spent more than 7 minutes but whatever

I didn't really do much; I mostly waited for help with my DRC errors. I did shop for the rest of the parts for my components and wrote June 28 in my journal. I updated the BOM with the extra parts.

I wasn't able to do much due to errors that I couldn't fix. Spend a long time in Kicad trying to fix it with no hope. I asked Highway for help. Updated Journal for June 27

Realised I need to word this like a journal, so yeah. I finished my June 26 journal. Wires all my PCB, a lot of DRC errors that I need help with. (more info in repo)

I started on my PCB editor, wrote progress on REPO (sadly some hackatime time got deleted because I forgot to add devlong and it was in the morning)

Parshly fixes schematics, wrote journal

Finished daily journal and started PCB, not good, need help. D:

I finished all the schematics of my project, chose all the footprints and got started on the PCB part. I also rethought the looks and how all the components would fit in.