Parsing the event logs relies on the order in which user input and the resulting task action are generated, this is prone to future bugs!

[BenedictWilkins]

The event log parser makes use of the accidental fact that user input events proceed the mapped task related event to determine which events are triggered by a user. This dependence is BAD as it the ordering of logged events depends on the order of the actuator execute calls, if the actuator is ever reordered (or the event logging system changes slightly), then this will break.

A MUCH BETTER SOLUTION:

• Record which actuators belong to which agent in the event log, and map the source field to the given agent to determine if its an avatar that produced the action.