... | @@ -8,6 +8,10 @@ Custom card properties may be put into the card editor. Commonly used custom pro |
... | @@ -8,6 +8,10 @@ Custom card properties may be put into the card editor. Commonly used custom pro |
|
|
|
|
|
name auto-renames your card in-game into the whatever the name value is. Deck editor will also recognize name and use it to control deck and card count limits. This way you can have multiple different cards using the same name, allowing for skins or different Rules based on the game mode.
|
|
name auto-renames your card in-game into the whatever the name value is. Deck editor will also recognize name and use it to control deck and card count limits. This way you can have multiple different cards using the same name, allowing for skins or different Rules based on the game mode.
|
|
|
|
|
|
|
|
### hoverPreviewOff
|
|
|
|
|
|
|
|
Turns off the automatic hover preview.
|
|
|
|
|
|
### allowAnyPlayer
|
|
### allowAnyPlayer
|
|
|
|
|
|
By default player interaction events such as `click`, `mouseenter`, and `mouseleave` only fires for the player that owns the card (or any player if the owner is neutral) and if the player is also the `turnPlayer`. allowAnyPlayer on the card causes the event to fire without such limitations. The last player to interact with the card is saved onto the card itself with the `clickPlayer`, `mouseenterPlayer`, `mouseleavePlayer` properties. This is great for cards and UI elements that are not part of gameplay, such as emotes.
|
|
By default player interaction events such as `click`, `mouseenter`, and `mouseleave` only fires for the player that owns the card (or any player if the owner is neutral) and if the player is also the `turnPlayer`. allowAnyPlayer on the card causes the event to fire without such limitations. The last player to interact with the card is saved onto the card itself with the `clickPlayer`, `mouseenterPlayer`, `mouseleavePlayer` properties. This is great for cards and UI elements that are not part of gameplay, such as emotes.
|
... | | ... | |