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
  • Issues
  • #30

Closed
Open
Created Jan 02, 2019 by Kaoru Aoi@dulst-admin💬Owner

Custom Passing

Criteria: Passing is one of the most confusing parts of the effect builder currently. There are all kinds of weird things like $0 and $card and $destroyed that have no relevance to any particular card. There are other passings such as $attackTarget and $attacker that are potentially misleading - they only refer to physical attacks and not spell attacks.

Let's discuss how we can improve this.

  1. Allow tooltips for passing.
  2. Stop the auto-10 most frequently used passings in the list. Most of them are irrelevant.
  3. Should passing auto include variables that are already defined on the card?
  4. Allow globally set and defined passings? Built like custom actions.
Assignee
Assign to
Time tracking