You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the mvp, the plan is to have the players deal with most of the logic of the cards in the deck. For 1.0, ideally all of the cards in the horde deck would handle themselves, and the players would only need to do things manually if they play something from their decks that affects the horde's board.
The way I foresee this working is having a function defined for each card, that gets triggered at each possible trigger point, and it will dispatch events depending on what it does.
The text was updated successfully, but these errors were encountered:
I thought about this a bit more over the weekend, and came up with a few ideas for how to do this. Not sure if any of these will pan out, but they're things to think about
Right now, the cards are javascript objects. (ie {name: 'blah'}). I wonder if we could change this so we have a javascript class called Card, and make them be instances of that. Then, we can functions for the various triggers, like enterBattlefield, destroyed, entersGraveyard, etc. I'm not sure if we could store those in the state or not.
One way we can trigger these events is to have something subscribed to the event state, like the view does, and calling the appropriate functions for each card. No idea if this is possible or not.
If 2 is not possible, we can wrap each dispatch event in a function for that dispatch, and it can call the appropriate methods at action time.
For the mvp, the plan is to have the players deal with most of the logic of the cards in the deck. For 1.0, ideally all of the cards in the horde deck would handle themselves, and the players would only need to do things manually if they play something from their decks that affects the horde's board.
The way I foresee this working is having a function defined for each card, that gets triggered at each possible trigger point, and it will dispatch events depending on what it does.
The text was updated successfully, but these errors were encountered: