Project Goals

[akstoulil]

Hello everyone, I just had a quick question about what we are each working on. The last time we met up I don't think I knew what everyone was going to be working on. I want to make sure that when I pick what to work on that I don't wind up working on something that someone else is already working on. I was just wondering what everyone is deciding to work on, and if any progress has been made. Any feedback regarding what we are all going to work on is appreciated!

[minin43]

Well, one very important job is for someone to outline a skeleton for the main driver functions. No real code needs to be written, really, just getting a good outline down will need to get done with some function and class names as needed.

[akstoulil]

Ok, sounds good to me. Thanks for responding!

[minin43]

We also need a player class that can be used by both the player playing the game and any additional opponents the game may control. Not sure about a dealer, since the end-round stuff is primarily arithmetic comparing each person's total to the dealer's.

[akstoulil]

Have you figured out anything about what is causing the errors in the skeleton project that we have so far by the way? Also you mentioned that we need to outline a skeleton for the main driver functions. Should I try to create an outline that we can use for that?

[minin43]

No I haven't quite touched the program since I last pushed an update, so I'm thinking my syntax is incorrect but again I haven't touched it to double check.

Yes, if someone could get an outline going for the main driver functions that would be a good start.

We also need an outline for the in-game opponent's logic regarding when to do the different actions (take a hit, pass, double down, etc). No code is needed but we're assuming the opponents are intelligent and should probably follow this logic provided on the Blackjack Wiki page (located halfway down the page).

It's starting to become slightly irritating our other 2 partners have yet to participate in the project outside of class, even just verbally.

[akstoulil]

BlackjackPseudocode.docx I think I just a basic outline/pseudocode template written for how the project might be structured. Look over this when you get the chance and let me know what you think of it so far. Also you might want to copy the code over into an editor of your choice in order to make it more readable. It wouldn't let me upload .cpp files, so I had to insert it into a word document.

[agkingrey]

Hey there guys, here is another copy of that diagram that we made up last week. Just move one of the items from the list from the left side, to the "working on" column. That way we always know who's working on which part. Sorry about not checking this sooner, neither of my connected emails are sending me notifications consistently for some reason when someone comments on here. I think it's only when someone makes a new post. Lets all try to put in a couple hours tonight and tomorrow on each section. I'm going to spend tonight fleshing out the main driver file, with partial pseudocode, and regular c++ code, as I feel fairly confident in C++, and hopefully, it'll help us get a better understanding of how the program will flow. This page is now my homepage, so if I open chrome on my desktop, I'll see this.

https://docs.google.com/spreadsheets/d/1ntOQsEozPR0eYqInqFJRe_-W32mcmjLFcFHE1Tc4SLI/edit#gid=0

[minin43]

I think the reason why you're not getting notifications is because you're not "subscribed" to the repo. At the top right of any page within this repo should be a "Watch" button. Click it and you'll receive updates about everything done to it (besides maybe pushes).

[minin43]

So some critiques and comments on the pseudo-code @akstoulil wrote:

• The game ought to be played through until you've ran out of chips to bet (because we have to include betting, otherwise some of the game's mechanics - doubling down for example - are rendered useless) and not a possible one-time-through sequence.
• We'll have to incorporate betting into the opponent decision-making as well as everything else.
• Going off of that, the idea that you continue playing until you're out of chips to bet, "shuffling the deck" won't need to be hard at all. Each card is already uniquely identifiable with it's number and suit, so all you'd need to do is retrieve every available card (which is probably always going to be every card, but we're going to want to write it as if that isn't the case) and stick it into a one dimensional card type array, randomize that one array, and pull 0 from it every time we draw, (either deleting the old table and recreating a new one after every draw or use a counter variable to pull from the table and increasing the counter variable after a draw) but we always want to make sure we mark the card as "drawn" in the master card table (which will be e-z since it's 2D and the numbers and suits remain consistent).

[agkingrey]

I like the main driver file pseudocode, I started working on some of it already, per the doc I shared. I'm worried about continuing any farther if Austin Stoulil has began work on it as well. I'll start working on the splitting function file instead tonight, until we can get this all sorted out tomorrow. See you guys soon.

My critiques on the main driver file pseudo:

• A lot of the processes you provided(including splits, winstates class to decide whether player wins, etc) should be handled by the respective class files, rather than handling it in the main driver, we should only be really calling methods for the most part in main.

• When it comes to chips, after a round, we should have either: "enter the number of chips you'd like to bet", "or type 0 to end the game". That way the user can quit whenever they desire. This process should most likely be handled by the chip class.

P.S.: I'll be in front of my computer until about 2-3 a.m., if you see this early Austin, shoot me a message whether or not you are working on the programming for the main driver file, and I'll adjust what I'm doing tonight accordingly.

[minin43]

Let's make sure we get all of our updates pushed before we have class tomorrow.

I'm worried that direct pushes, though, will overwrite just-changed code unintentionally. We may need to look into creating pull requests instead.

@agkingrey Help me out here, I'm not certain which one of us is wrong. Classes are objects, no? What kind of classes are you thinking we're going to be creating? What "chip class"? Your chips only need to be a numeric value tied to the player class (which will be a real thing) which is changed based on the bet amount and the round outcome.

But I like the idea of entering "0" to "exit the table" (and quit the game). Smart thinking.