Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 81
    • Issues 81
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • dulst
  • core
  • Wiki
  • Custom Card Properties

Custom Card Properties · Changes

Page history
Update Custom Card Properties authored May 06, 2020 by Administrator's avatar Administrator
Hide whitespace changes
Inline Side-by-side
Custom-Card-Properties.md
View page @ 166acdc7
...@@ -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.
......
Clone repository
  • Analytics Events
  • Animations
  • Basic Effect Building
  • Change Log v13
  • Change Log v14
  • Change Log v15
  • Change Log v16.1
  • Change Log v16.2
  • Change Log v16.3
  • Change Log v16.4
  • Change Log v16.5
  • Change Log v16.6
  • Change Log v16.7
  • Change Log v16.8
  • Change Log v16
View All Pages