perpetual-haskelling-initiative

Main repository for the CS141 Perpetual Haskelling Initiative

Rules

Game consists of two 'players', which are represented in game by 'programming languages'
At the start of a game, both players start with 3 cards and 30 'health' points.
A coin is flipped to see which player goes first. The player that goes second gets to draw an additional card from their deck at the start of their first turn and an extra 'point' to spend playing cards in their hand.
Turns alternate between the two players. A players turn ends when they end their turn or a time runs out (30 seconds per turn).

On a given players turn, they start by drawing a card from their deck.
They can then proceed to play cards from their hand and 'attack' the opponent.
Each card will have a 'point cost'. As the number of rounds increases the number of 'points' a player can spend by playing cards increases to a maximum of 10 'points'
Minions can only attack a turn after they have been placed unless specified

Once a players 'health' depleats to 0, the other player wins the game.

If their deck runs out of cards, instead of drawing a card at the start of a turn they take damage.
-- This damage should increase as the number of turns with an empty deck increases (exact numbders tbd)

Decks

Decks can be constructed by the user, but every deck consists of two main parts:

• Cards from a BASE DECK
• Cards from an EXPANSION

Cards from a BASE DECK are focussed on the behaviours of programming paradigms
Cards from an EXPANSION are focussed on the behaviours of specific programming languages

Card Types

There are 3 card types

• Programs (minions)
• Events (Spells)
• Errors (Negative result from a spell)

Programs and Events are playabe, whereas Errors occur as a result of a failed Event.
Programs act as standard minions would in hearthstone. They have an 'attack' and 'health' rating, and are present on the board until 'killed' or removed
Events are single use items which have some effect on the current state of the game.
Errors may be either a Program or Event, but work against the player which caused the Error

Attack/Damage

Each player starts off with 30 'health points'
Direct attacks on a player will decrease their 'health points'

Programs have 'damage points' and 'health points'. They too lose 'health points' from direct attacks. However, if they have an 'attack' rating greater than 0, that amount of 'damage' is done back on the player/Program which made the initial 'attack'

Card Limits

A player can only have 8 Programs on the board at one time.

Deck Ideas

BASE DECKS

• Imperative
  • Weakest cards compared to other BASE DECKS
  • 'Hello World' minion
  • Basic operator Scripts (e.g. add, mult, sub), which alter the attack/health of Programs
  • Spaghetti Code, weak Programs
• OOP
  • Combine Programs into a 'class' (Classes could just be Programs with affects of the Programs that merged to become the class)
  • Could have instance cards which copy a players 'class' on the board
• Functional
  • Recursive Scripts, which apply a specified amount of times, dealing damage to player per recursive call

EXPANSION DECKS

• Java
  • Can use Sequential and OOP
  • Curly Bracket Minions (left '{' and right '}')
  • Try and Catch, combines to Try Catch
  • Loops, to repeat Scripts
  • Waffles, replace all cards on the field with Spaghetti Code
• Haskell
  • Curried function Scripts, increase attack/health of Program
  • Bind card to combine two Programs into a stronger Program
  • Map (Script) which applies a given Script to all players Programs in play
  • Foldr, starting from the right, compresses all of your current cards on the field into a single card with all stats combined
  • Foldl, same as Foldr but starting from the left
  • Maybe Minions, attacks the right target 50% of the time. Otherwise, chooses between all available targets
• Python
  • Whitespace minion, weak minion
  • Certain python specific minions could be able to attack as soon as they are played (much like charge in Hearthstone)