addHistory is now only called from within top-level action methods in the player class.

However there still could be duplicate actions/history events going over the wire, that are also being generated locally.

There needs to be an audit done of actions and histories in a network game.  Histories are easier because we just need to check an autosave file on the client and server to see if duplicates are there.  Detecting duplicate actions is more difficult.

I am considering adding a unique id to each action and history event.

network players often have duplicated history events in the history report

it needs to be decided if the history events are going to be sent over the wire, or the network player will reproduce them as a result of getting actions.