Thank you for using the Card Game Toolkit for Unity !

Card Prefab Creator

To open the Card Prefab Creator window, go to Window > Card Game Toolkit > Card Prefab Creator.

You can dock the window like any standard Unity editor window. 

 Sprite Sheet to Card Prefabs – Setup Guide 

Before using the Card Prefab Creator, make sure to:

• Slice your sprite sheet with Unity's Sprite Editor.

• Organize the sheet so cards in each suit appear sequentially (e.g. from Ace to King).
  
  

Steps:

1. Assign your sliced sprite sheet to the Sprite Sheet field.
   
   

2. Set the Destination Folder (right-click the folder in Project view > Copy Path > Paste).
   
   

3. Set the Suit Amount and Suit Names (you can rename and reorder).
   
   

4. If the total sprites exceed (suit count × cards per suit), remaining sprites will be named "Missing Suit", unless skipped via the Skip Indices array.
   
   

5. Optionally assign a layer mask and enable card shadow creation.
   
   

6. Click Create Prefabs. Prefabs will appear in the folder within a few seconds.
   
   

Mistake? Just delete the prefabs, tweak settings, and recreate!

Card scripts and components

Card Components

• Card Data: this is the component that olds the cards data;

exposed variables: 

• int value; 

• string suite; 

• Sprite front; 

• Sprite back;

Automatically assigned by the prefab creator.

If Use Card Back is disabled, CardData.back will be null.

You can also assign values manually through code.

• Card Behaviour: 

Handles card interaction logic.

Behaviour Settings:

• flipDuration (float)
  
  

• cardScaleFactor (float)
  
  

• cardScaleDuration (float)
  
  

• cardHoverTiltSpeed (float)
  
  

• dragSpeed (float)
  
  

• cardMovementRotationStrength (float)
  
  

• snapToCursor (bool)

Exposed Variables: 

• CardData Data { get }

• Transform CardVisuals; 

• Sprite[] Sprites; // [0] = front, [1] = back  

• SpriteRenderer spriteRenderer; //CardVisuals renderer

• SpriteRenderer shadowRenderer; //null if prefab was creating without "Create card shadow" enabled

• bool IsFaceUp  { get }

• bool IsScaledOne  { get }

• Vector3 MousePos;

Exposed Methods: 

• RefreshSpritesData(); //use this after changing card data's sprite at runtime

• SetContext(ICardContext context);

• MoveToPosition(Vector3 destination, float duration);

• FlipCard();

• ToggleCardFace(bool faceUp); //sets the card visual renderer's sprite to front (if true) or back. Instant (no animation)

• Scale(bool up);

• HoverRotation(); //animates the tilt of the card visuals, relative to MousePos;

• RotationReset(); //sets the card visuals rotation to Quaternion.identity; Instant (no animation)

• BeginCardDrag(bool isAnchored = false);

• DropCard(bool resetRotation); //stop dragging

Input and Context System

CardBehaviour uses Unity’s Input system way of handling mouse input.

• OnPointerEnter, OnPointerMove, OnPointerExit

• OnPointerDown, OnPointerUp

This means that for CardBehaviour to register these events you need:

➤ A PhysicsRaycaster2D component on your camera

➤ An EventSystem object in your scene

• OnTriggerEnter2D, OnTriggerExit2D
  
  

To determine how a card behaves in different scenarios, it calls context methods like Context.OnHover(this).
This decouples card logic from interaction rules, allowing context-based control.

Card Contexts 

ICardContext methods

• OnMouseEnterCard(CardBehaviour card);

• OnHover(CardBehaviour card);

• OnDrag(CardBehaviour card);

• OnMouseExitCard(CardBehaviour card);

• AddCard(CardBehaviour card, bool destroyObject = false, bool flip = false);

• GetContextPosition(); //returns a vector3

Board

The Board component is the most simple context. It only contains the ICardContext functions that either call card.someMethod (here card is the CardBehaviour calling the context's method) or do nothing.

CardPile

fields

• List<GameObject> cardDeck; //in the case of a draw pile this would be filled with your card prefabs

• bool AllowAddCard; //can the player add to the pile?

• bool AllowTakeCard; //can the player take from the pile?

The card dealer demo shows 2 CardPile, one as a draw pile and the other as a discard pile.

methods

CardPile implements the ICardContext interface, but only uses AddCard (if AllowAddCard is set to true) and GetContextPosition. It contains other methods:

• DrawRandomCard(Vector3 destination, ICardContext destinationContext = null); //instantiate a random GameObject from the cardDeck list and removes that card from that list. Calls SendDrawnCardTo(destination).

• GetTopCard(Vector3 destination, ICardContext destinationContext = null); //instantiate the GameObject at the last index in the list, removes it from the list. Calls SendDrawnCardTo(destination).

• RemoveCardFromDeck(GameObject card);

DrawRandomCard and GetTopCard will set the drawn card's context to destinationContext if the field isn't null. Does nothing if AllowTakeCard is set to false. SendDrawnCardTo() calls card.MoveToPosition().

Hand

fields

• bool UseHandMax; //is there a maximum to the number of cards that can be added to the hand

• int MaxCards; //only used if UseHandMax is set to false

• float MaxHandWidth; //the maximum spread of the hand, on the x axis

• float CardTargetSpacing; //The spacing between cards if MaxHandWidth is not met

• bool CurvedFan; //place the cards in the hand to form a fan (cards in the middle are higher)

• float FanCurveHeight; //The curvature of the fan. Only used if CurvedFan is true

The Hand component also contains private functions that are unique to it.

Demo scene

Card Dealer Demo:

The Card Dealer Demo scene serves as an example on the proposed structure for your card game.

How To Test:

• click play 

• click on the draw pile to draw a random card

• click the drawn card to flip it up

• drag it either to the hand region, or the discard pile

• you can arrange the cards in your hand by drag and dropping them

• you can right click on a card to add the Sheen effect to it

• you can the space bar while hovering a card to dissolve it

Shaders and effects