A text-based collectible card game implementation inspired by Hearthstone and Magic: The Gathering, built in C++ with modern object-oriented design patterns.

Sorcery is a two-player card game where players compete to reduce their opponent's life to zero. Players use magic as a resource to play cards, summon minions, cast spells, and activate abilities. The game features a rich interaction system with triggered abilities, enchantments, and rituals.

• 4 Card Types: Minions, Spells, Enchantments, and Rituals
• Complex Abilities: Triggered and activated abilities with targeting
• Enchantment System: Stackable modifications using the Decorator pattern
• Event-Driven Triggers: Observer pattern for automatic ability activation
• APNAP Order: Proper sequencing of simultaneous effects
• Testing Mode: Debug features for development and demonstration

• C++14 compatible compiler (GCC, Clang, or MSVC)
• Make build system
• Unix-like environment (Linux, macOS, WSL)

# Clone the repository
git clone <repository-url>
cd Sorcery

# Build the project
make clean
make

# Run the game
./sorcery

# Use custom deck files
./sorcery -deck1 player1.deck -deck2 player2.deck

# Initialize game with commands from file
./sorcery -init init.txt

# Enable testing mode (bypass costs, enable debug commands)
./sorcery -testing

# Combine options
./sorcery -deck1 custom.deck -init test.txt -testing

• Starting State: 20 life, 3 magic, 5 cards in hand
• Turn Structure: Gain 1 magic, draw 1 card, take actions, end turn
• Victory: Reduce opponent's life to 0 or below
• Board Limit: Maximum 5 minions per player
• Hand Limit: Maximum 5 cards in hand

• Stats: Attack/Defence (e.g., 2/3 means 2 attack, 3 defence)
• Actions: 1 action per turn, used for attacking or abilities
• Abilities: Can have triggered (automatic) or activated (manual) abilities
• Death: When defence ≤ 0, minion dies and goes to graveyard

• One-time effects: Cast and immediately removed from game
• Targeting: Most require specific targets (minions, rituals, players)

• Modify minions: Change stats, abilities, or grant new effects
• Stacking: Multiple enchantments apply in oldest-to-newest order
• Removal: Lost when minion leaves board

• Persistent effects: Remain in play until replaced or destroyed
• Charges: Limited uses, cost charges to activate
• One per player: Playing new ritual replaces the old one

• Bypass magic costs (sets magic to 0)
• Enable draw and discard commands
• Disable deck shuffling for reproducible games
• Useful for debugging and demonstration

Create setup files to automate game initialization:

Alice
Bob
play 1
play 1
end

This would:

1. Set player names to Alice and Bob
2. Have Alice play her first two cards
3. End Alice's turn
4. Continue with normal gameplay

Create custom deck files with card names (one per line):

Air Elemental
Earth Elemental
Bone Golem
Novice Pyromancer
Banish

• New Cards: Add to CardFactory with lambda functions
• New Abilities: Implement TriggeredAbility or AbilityCommand
• New Enchantments: Extend EnchantmentDecorator
• New Events: Add to TriggerManager notification system

• Smart Pointers: std::unique_ptr throughout prevents memory leaks
• RAII: Automatic resource management
• Exception Safety: Proper cleanup on errors

• Separation of Concerns: Clear module boundaries
• Polymorphism: Clean interfaces for different card types
• Error Handling: Comprehensive validation and user feedback