Set Game

Assignment 3 of the Stanford CS193p 2020 SwiftUI Course. Simple implementation of a single player version of the Game Set. Full Assignment Document can be found here.

Objective

The goal of this assignment is to give you an opportunity to create your first app completely from scratch by yourself. It is similar enough to the first two assignments that you should be able to find your bearings, but different enough to give you the full experience!

Required Tasks

• Implement a game of solo (i.e. one player) Set.

• When your game is run for the very first time, there should briefly be no cards showing, but as soon as it appears, it should immediately deal 12 cards by having them “fly in” from random off-screen locations.

• As the game play progresses, use all the real estate on the screen in an efficient manner. Cards should get smaller (or larger) as more (or fewer) appear on-screen at the same time, while always using as much space as is available and still being “nicely arranged”. Grid does all this and you are welcome to use it. All changes to locations and/or sizes of cards must be animated.

• Cards can have any aspect ratio you like, but they must all have the same aspect ratio at all times (no matter their size and no matter how many are on screen at the same time). In other words, cards can be appearing to the user to get larger and smaller as the game goes on, but the cards cannot be “stretching” into different aspect ratios as the game is played.

• The symbols on cards should be proportional to the size of the card (i.e. large cards should have large symbols and smaller cards should have smaller symbols).

• Users must be able to select up to 3 cards by touching on them in an attempt to make a Set (i.e. 3 cards which match, per the rules of Set). It must be clearly visible to the user which cards have been selected so far.

• After 3 cards have been selected, you must indicate whether those 3 cards are a match or mismatch. You can show this any way you want (colors, borders, backgrounds, animation, whatever). Anytime there are 3 cards currently selected, it must be clear to the user whether they are a match or not (and the cards involved in a non-matching trio must look different than the cards look when there are only 1 or 2 cards in the selection).

  • TODO: bettter Colors / clearer indication

    --> Shadows

• Support “deselection” by touching already-selected cards (but only if there are 1 or 2 cards (not 3) currently selected).

• When any card is touched on and there are already 3 matching Set cards selected, then …

  • as per the rules of Set, replace those 3 matching Set cards with new ones from the deck
  • the matched cards should fly away (animated) to random locations off-screen
  • the replacement cards should fly in (animated) from other random off-screen locations (or from a “deck” view somewhere on screen, see Extra Credit)
  • if the deck is empty then the space vacated by the matched cards (which cannot be replaced) should be made available to the remaining cards (i.e. they’ll likely get bigger)
  • if the touched card was not part of the matching Set, then select that card

• When any card is touched and there are already 3 non-matching Set cards selected, deselect those 3 non-matching cards and select the touched-on card (whether or not it was part of the non-matching trio of cards).

• You will need to have a “Deal 3 More Cards” button (per the rules of Set).

  • when it is touched, replace the selected cards if the selected cards make a Set (with fly-in/fly-away as described above)
  • or, if the selected cards do not make a Set (or if there are fewer than 3 cards selected, including none), fly in (i.e. animate the arrival of) 3 new cards to join the ones already on screen (and do not affect the selection)
  • disable this button if the deck is empty

• You also must have a “New Game” button that starts a new game (i.e. back to 12 randomly chosen cards). Cards should fly in and out when this happens as well.

• To make your life a bit easier, you can replace the “squiggle” appearance in the Set game with a rectangle.

• You must author your own Shape struct to do the diamond.

• Another life-easing change is that you can use a semi-transparent color to represent the “striped” shading. Be sure to pick a transparency level that is clearly distinguishable from “solid”.

• You can use any 3 colors as long as they are clearly distinguishable from each other.

• You must use an enum as a meaningful part of your solution.

• You must use a closure (i.e. a function as an argument) as a meaningful part of your solution.

• Your UI should work in portrait or landscape on any iOS device. This probably will not require any work on your part (that’s part of the power of SwiftUI), but be sure to experiment with running on different simulators in Xcode to be sure.

Extra Credit

• Have your cards fly in from a deck View located somewhere on screen. This is a little bit more difficult than flying to a random location because figuring out where some other View is will require some investigation on your part.

  --> partly implemented, issues accessing geometry proxy of individual cards

• If you deal from a deck, have the cards be “face down” while on the deck and then flip over as they fly out to their locations when they are dealt.

  --> Dependent on extra credit above

• Draw the actual squiggle instead of using a rectangle. --> used Antonio J Rossis implementation

• Draw the actual striped “shading” instead of using a semi-transparent color.

• When cards match, provide some exciting animation. In other words, use animation to show that cards are matched in Required Task 7.

• Make your fly away more exciting (maybe the cards spin as they fly away?).

• Keep score somehow in your Set game. You can decide what sort of scoring would make the most sense.

• Give higher scores to players who choose matching Sets faster (i.e. incorporate a time component into your scoring system).

  --> Base score of 30 - 1 for each second that passed since the last Set was matched

• Figure out how to penalize players who chose Deal 3 More Cards when a Set was actually available to be chosen.

• Add a “cheat” button to your UI.

• Support two players. No need to go overboard here. Maybe just a button for each user (one upside-down at the top of the screen maybe?) to claim that they see a Set on the board. Then that player gets a (fairly short) amount of time to actually choose the Set or the other person gets as much time as they want to try to find a Set (or maybe they get a longer, but not unlimited amount of time?). Maybe hitting “Deal 3 More Cards” by one user gives the other some medium amount of time to choose a Set without penalty? You will need to figure out how to use Timer to do these time-limited things.