multiple abiltities

It's not a problem to add more than one ability. If you look at the JSON the "abilities" key is already configured as an array of dictionary. If you're not familiar with the syntax, notice that the root level "cards" is also an array of dictionary. You just use commas to separate such as this example showing an array of two dictionaries:


[{ key: value }, { key: value }]


In short, simply add another dictionary in the "abilities" array to add another ability to the card. I cant remember if I already programmed support for multiple abilities when the card is being played, but if not, it shouldn't be hard to modify logic to be in a loop so that it can. Try it out and let me know if you get stuck.

Gotcha, I went ahead and tried it so I would see the same issue. The problem is in the way that an ability is attached to a card. If you look in the "DeckFactory" there is an "AddAbilities" method that looks like I had considered the need to support more than one ability per card. However, within the loop each parsed ability is added to the card via "AddAbility" which attaches the ability to the card as an "aspect". The aspect container is just a dictionary, and if you use the simple generic method like I did here, then it will use the name of the generic type itself as a "key" to add the "value" with. This is why it fails when trying to add the second ability, because it cant reuse the generic ability key. There are a couple of ways to solve this:

1. You can provide your own key so there is no naming conflict - such as by giving each ability its own "id" and using that to add it to the card with. The downside to this approach is that it becomes slightly more difficult to get the ability again later, since you need to loop over all the aspects of a container and check their type.

2. You could create a new aspect, perhaps one called "ability container" which holds an array of ability. Then the ability wouldn't need to be an aspect itself. Just make sure all cards have this aspect, and when adding the ability to the card, get a reference to the container and append it to the array.

Either approach will likely require you to refactor code elsewhere in the project. It's a great challenge to learn with though, so I hope you give it a try!

That could work, but keep in mind that each action of the ability may need its own targeting as well. For example, a spell which destroys an enemy, then gives the enemy's HP to the caster. It might be hard to tell the line between what an action is and what the ability is, but so long as you consider all of your intended functionality it could work.

Also, if I were going to take this approach, I would want to refactor the card's ability in the json to not be an array. Then I would make the actions of the ability an array. Then there is no need to worry about nulls, you simply put the logic in a loop over the actions found.

Sounds like a good approach Arghonaut, and I'm glad to hear you've got it all working!

That's perfect - anytime a class starts growing I also start looking for ways to break it up. I'm really glad you've got the inspiration and motivation to try adding new features, and I hope secrets work well for you!

You were close, "compartmentalization" is a word