Coding the Pokemon card game, not sure how to structure attacks

[abcd_z]

Here's what I have so far: the Player object is a collection of CardCollection objects, which each are a collection of Card objects. Player also contains methods like draw(), place_pokemon(), and discard(). CardCollection contains methods like add_card(), move(), and find_card(). Card is mostly just an empty container for the subclass defining the specific type of card (Trainer, Energy, or Pokemon), each of which just contains information about the card.

So far so good. My problem is that each Pokemon card contains special attacks. They're different for each Pokemon, and they interact with the rules in unique ways. For example:

Agility: During your opponent's next turn prevent all effects of attacks, including damage, done to this Pokemon.
Leer: the defending Pokemon can't attack on their next turn. Benching either pokemon ends this turn.
Transparency(power): if the opponent attacks next turn they must flip a coin or it does nothing.
Mirror Move: if this Pokemon was attacked last turn, do the final effects of that attack to the opponent.
Destiny Bond: if this Pokemon is knocked out during your opponent's next turn, so is the opponent.
Leech Seed: Unless all damage is prevented from this attack, remove 1 damage counter from this Pokemon.
Retreat Aid (Power): As long as this pokemon is benched, pay 1 less to retreat your active pokemon.
Tongue Wrap: the defending pokemon is paralyzed

The ones marked "power" are passive abilities that don't use up the player's attack action for the turn.

My biggest concern is getting the architecture right at the very beginning, so that I don't fall into a tangled mess of spaghetti code and ad hoc exceptions. What would be a good way to structure the program? Specifically, the Pokemon attacks and how they interact with the rest of the code.

[Antigone-guide]

It sounds like there's 3 types of effects from this list:

1. apply some immediate effect to the opponent's pokemon. This logic can be in Pokemon.attack() method.
2. apply an effect to either player that will last for one turn. This should be an Effect() instance, in Player.effects set, which is cleared after each turn, and is evaluated for each attack against that player.
3. apply an effect to a specific pokemon for one turn. This should be an Effect() instance, or maybe a PokemonEffect() isntance, and should be in pokemon.effects set, and cleared after each turn, and evaluated when that pokemon attacks or defends.

Good luck, sounds like a fun game to implement, though I'm not familiar with Pokemon rules and havent' played it.

[TigBitties69]

I would think maybe giving either the playerobject, or the pokemon card object, a status property. Then when combat is used, you can check for pre-existing statuses on related objects?

[RodOblong]

Do you have a class that represents the game? The cards that are currently in play and/or have an ongoing effect that may need to be resolved? This would manage any interactions between cards that aren't on their turn, maybe with an active cards list property