Refresh my memory, we talked about making the player itself a component, correct?
Yup, a single player component because health mana pool, hand, board, grave, etc all relate to the player.
Does the world become the entity at that point? Or the game state? The reason I ask is because the System object takes an Entity as an argument. If the Player is a component it leaves me unsure what is supposed to become the Entity. I'm trying to build the mental model of how all the pieces will fit together.
the world is a not an entity. it represents the game loop. The (S)ystem needs to be updated/changed. they current System was only to get that test to turn green.
the player component will contain (ManaPool, Hand, Graveyard, etc); then we can create inherited component of HumanPlayer and AIPlayer.
I also think that each card should be a separate entity.
here is where i saw the serialized action/func; http://mikehadlow.blogspot.com/2011/04/serializing-continuations.html (no bad to remember a post from 2011 ;) ). it looks like they may not work if the version changes or the app is recompiled.
here is another way of possibly adding them: http://mikehadlow.blogspot.com/2013/04/lua-as-distributed-workflow-scripting.html